Cookbook
Task-oriented recipes. Each one is copy-paste, tested against the public sandbox, and ends in a verifiable outcome (verdict + ledger receipt).
Govern every OpenAI call without changing application code. One env-var swap.
CLI Firewall on the shell, MCP Gateway on the tool calls, Glass Box Ledger on every action.
Per-tool specialist Guardian for stripe.create_refund — schema-aware and intent-aware.
Wrap any LangChain LLM call with the Guardian, apply RFC 6902 corrections inline.
Three-stream architecture (ops / security / audit) with the right retention per stream.
Block destructive shell commands from Claude Code, Cursor agents, Devin, and friends.
Drop-in PII Guardian, with a forensic record of every redacted span.
Per-tenant LoRA hot-swap, per-tenant Glass Box Ledger partitions, per-tenant SLAs.
Conventions
- All recipes assume
TRINITITE_API_KEYandTRINITITE_BASEare exported. - Every recipe ends in a verifiable outcome — typically a
ledger_idyou canGET /v1/logs/:idto confirm. - Where curl is shown, equivalent Python and Node tabs follow.
- Sandbox keys (
tk_test_…) work for every recipe; production keys (tk_live_…) require an enterprise plan.