Launchfiles logoLaunchfiles

Docs · hypothesis-led

Website missions

Website Missions convert a page request into a conservative plan: mode, source environment, risk tier, allowed and forbidden actions, team, gates, and approval boundary. Plans keep publishAllowed false in V0.

Docs hubGet startedllms.txtAgent capabilities

Hypothesis-led documentation. No ranking, traffic, or outcome guarantees. Public discovery is not execution authority.

Modes (summary)

build_new_page, audit_existing_page, create_page_spec, repair_page, compare_page_versions, optimize_live_page, rendered_qa_only. URL without repo access routes to audit/recommendations, not silent code mutation.

Forbidden

Autonomous publish, deploy, inventing proof, or claiming production mutation without receipt and approval.

How does Website missions work in an agent-first engineering harness?

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.

DimensionUnbounded AI Chat / Audit EssaysLaunchfiles Bounded Work Orders & Receipts
Execution ScopeUnbounded chat, hallucinated advice, unverified file rewritesBounded AST patches via work orders and pre-commit gates
Verification & ProofSoft-green claims without receipts or regression checksDual-ledger verification with cryptographic receipts
Opportunity DiscoveryInvented keywords and unranked suggestionsStatistical triage via Search Repair Radar
Economic ModelOpaque token burn with zero outcome guaranteeTransparent pricing with strict byte-range safety locks

Next safe action

Learn the contract, then run a bounded mission.

Prefer receipts over claims. Prefer fail-closed honesty over impressive incompleteness.