LaunchfilesDocs · hypothesis-led
A receipt is durable, inspectable proof that work ran under a scope. Terminal state and side-effect status are never inferred from UI polish. Model output alone is not a completion receipt.
Docs hubGet startedllms.txtAgent capabilities
Hypothesis-led documentation. No ranking, traffic, or outcome guarantees. Public discovery is not execution authority.
Actor, scope, terminal state, side-effect status, and evidence refs for completed work. Trace correlation when available.
Run, gate, side-effect, and memory-approval receipts are different objects. Collapsing them into one green badge creates false confidence.
Launchfiles executes this through bounded work orders, deterministic pre-commit gates, dual-ledger verification, and cryptographic approval receipts. Rather than generating unverified audit essays or soft-green theater, autonomous agents operate inside strict byte-range boundaries with verifiable unit economics, human review gates, and deterministic regression guarantees across every production change.
| Dimension | Unbounded AI Chat / Audit Essays | Launchfiles Bounded Work Orders & Receipts |
|---|---|---|
| Execution Scope | Unbounded chat, hallucinated advice, unverified file rewrites | Bounded AST patches via work orders and pre-commit gates |
| Verification & Proof | Soft-green claims without receipts or regression checks | Dual-ledger verification with cryptographic receipts |
| Opportunity Discovery | Invented keywords and unranked suggestions | Statistical triage via Search Repair Radar |
| Economic Model | Opaque token burn with zero outcome guarantee | Transparent pricing with strict byte-range safety locks |
Next safe action
Prefer receipts over claims. Prefer fail-closed honesty over impressive incompleteness.