Paid access documents
Learn the sandbox. Connect one workflow. Prove one closeout.
This hub explains AutoKirk in plain language for paying customers and open-alpha builders. The goal is simple: connect important work, require proof, and use the board as the truth surface.
Implementation guides
Start narrow. Expand after proof.
Getting started
Understand the first proof rule, the intake link, and the board.
Customer intake
Send requests, forms, jobs, or follow-up work into AutoKirk.
AI agent boundary
Let AI act without letting AI self-certify completion.
GitHub and Vercel
Require proof before code and deployment claims become accepted.
Supabase proof checks
Use database evidence, RLS checks, function results, and receipts.
Stripe-triggered obligations
Let payment start work without pretending payment proves fulfillment.
API examples
Send a claim, attach evidence, and receive governed status.
Board guide
Read open work, missing proof, receipts, and recent activity.
Public contract
JSON in. Governed status out. Receipt when accepted.
The public contract is intentionally small. The customer does not need to know the kernel internals to use the proof boundary.
POST /api/intake/source
{
"source": "ai | github | stripe | form | custom",
"claim": "work completed",
"evidence": {},
"idempotency_key": "unique-action-key"
}