LaunchfilesDocs · hypothesis-led
A gate is an independent evaluation step. Producers must not self-certify high-stakes outcomes. Missing evidence lowers authority; it never invents completeness.
Docs hubGet startedllms.txtAgent capabilities
Hypothesis-led documentation. No ranking, traffic, or outcome guarantees. Public discovery is not execution authority.
Roles produce; gatekeepers/critics evaluate. One model call owning both creation and judgment is an anti-pattern.
Incomplete context should block high-risk actions and still produce honest next work (repair orders, needs_repair shells, bootstrap packets).
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.