RecipesTyped inputs, outputs, approvals
Run API
Automate Boetica without bypassing governance.
Drive recipes, templates, app-creation runs, build/remediation runs, thread messages, event subscriptions, idempotency keys, and MCP integration through the same policy, budget, sandbox, and evidence gates as the workspace.
Run API
External automation enters through the same gates.
The API lists recipes, creates app-creation/build/remediation/babysit runs, messages threads, subscribes to evidence events, and uses idempotency keys without bypassing policy or proof.
RunsCreate, build, remediate, babysit, export
EventsTask and evidence subscriptions
MCPGoverned connector with protected secrets
POST /runs -> create_app / build / remediatePOST /threads/:id/messages -> queued or blockedwebhook.deliver() -> signed delivery proofidempotentpolicy-boundsigned webhooks
Signed recipes
Recipes declare typed inputs, allowed repos and task kinds, output schema, evidence kind, budget, approvals, rollback, timeout behavior, and events.
Idempotent runs
External systems can create app-creation, build, remediation, babysit, evidence export, and procurement runs without duplicate dispatch.
Event subscriptions
Task, budget, autonomy, incident, rollback, and evidence events deliver through signed webhooks with proof.
Create
Runs start through preflight, not raw prompts.
API-created app builds and repo work still resolve trust, policy, budget, branch protection, sandbox, reviewer, evidence kind, and blockers before execution.
- List recipes
- Create app runs
- Create repo runs
- Use idempotency keys
Subscribe
Events carry delivery evidence.
Outbound webhook deliveries are signed, retried, reconciled, and recorded without storing raw payload bodies or provider credentials.
- Task events
- Evidence events
- Budget alerts
- Incident and rollback events
Signed remediation PR
boetica/auth-rate-limit-pr
@@ apps/web/src/app/api/login/route.ts- await password.verify(body.password)+ await limiter.consume(requestIp)+ await password.verify(body.password)+ await audit.append(evidencePacket)
evidence packetKMS + Sigstore (cosign)
- packet hash
- 91f4e2a0
- prev hash
- 5e1c8a44
- trust boundary
- sandbox attested · egress denied
- merge policy
- platform-eng / human merge
SOC 2 CC6.6signedNIST AC-6signed
Integrate
MCP is governed like every other connector.
MCP and developer integrations require scope, protected-secret approval, audit, and policy enforcement before they can trigger repo-changing work.
- Connector scope
- Protected secrets
- Audit trail
- Policy-bound actions