AutoKirk platform
Use the whole chain.
From autokirk.com to Supabase workspace truth: checkout or login, resolve account, register the source, generate an intake link, send test work, and open the board.
Runtime chain
Public site, repository code, and Supabase capability now point at one product path.
This screen should not be a brochure. It is the working route from activation to governed intake and board-visible truth.
- autokirk.com explains the governed proof boundary
- Stripe checkout or returning login opens the customer path
- Supabase Auth resolves the actor and workspace membership
- The platform registers a connected source through the governed API surface
- The generated intake link receives work, events, payment-triggered work, or agent claims
- The board shows open work, proof-ready work, receipts, and integrity state
Next.js product surfaceSupabase AuthWorkspace membershipSigned board URLConnected-system registrationStripe checkout and webhook intakeManual, webhook, form, CRM, email, agent, MCP, automation, job-system, payment intake
Customer #0000
Attach AutoKirk to its own SDLC.
Use the same platform flow a customer uses. GitHub, GitHub Actions, Supabase, Vercel, Stripe, and the board keep doing their jobs; AutoKirk governs whether their claims are allowed to close.
branch_protection_mainproof_gate_statussupabase_project_healthstripe_webhook_intakeboard_runtime_evidence
Preparing account
Setup
Create one governed intake rule.
Answer plain-English questions. AutoKirk will register the connected source in Supabase-backed governance and give you an intake link for the system, automation, payment path, or agent where work starts.