LaunchfilesDocs · hypothesis-led
A mission is a bounded founder or agent job with mode, evidence, gates, and approval boundaries. Mission types differ by allowed actions. In V0, no mission type may publish or deploy production changes without separate approval paths that remain outside this public docs graph.
Docs hubGet startedllms.txtAgent capabilities
Hypothesis-led documentation. No ranking, traffic, or outcome guarantees. Public discovery is not execution authority.
Pick the mission type that matches the job. If evidence is missing, the system should degrade honestly rather than invent completeness.
Website missions, SEO/GEO, search expansion, and content. Evaluation and UX gates appear as related capabilities, not unrestricted execution.
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.