KERN: one economic control system for autonomous actions

Identity/governance, treasury, escrow, verification, operation finality, forensic trace, operator control plane, adapters, and workflows in one fail-closed system.

Canonical launch spine (single demo)

Operator data table
StageWhat happensRoute
1. Request ingressAgent/API submits high-risk procurement/finance action envelope./docs/quickstart
2. Policy + evidence + verificationKERN evaluates allow/deny/review posture fail-closed./launchpad/canonical-demo
3. Operation + trace continuityTerminality and causality are linked before economic completion assumptions./console/settlement/operations/[operationId]
4. Webhook + operator continuitySigned delivery and operator audit routes close the loop./console/webhooks/inspector

What exists today in-repo

Canonical money path

repo-current

execute_money_action remains the enforced value-moving semantics boundary.

Launch surfaces

repo-current

Launchpad + Console + Docs + Web are aligned to one deterministic demo spine.

Integration contracts

repo-current

Adapter envelope templates are in-repo for browser/API/payout/webhook insertion points.