Docs · hypothesis-led

The operating loop

Meaningful Launchfiles work maps to Signal → Decision → Work Order → Run → Gate → Approval → Receipt → Readout → Memory. A model reply or green UI status is not execution proof. High-risk actions require evidence and authority outside the agent.

See a bounded run Agent boundaries

Docs hub Get started llms.txt Agent capabilities

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

Why the loop exists

Speed without durable context creates false progress. The loop forces atomic work, independent evaluation, durable receipts, and optional compounding memory.

When the full loop is mandatory

Side-effectful or claim-making work needs Gate and Receipt at minimum. Read-only orientation can be lighter, but anything asserted as truth still needs an inspectable receipt.

Founders usually work from /today. Runtime Map is forensics. Public marketing pages explain objects; this docs page is the contract-oriented explanation.

How does The operating loop 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.

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

Learn the contract, then run a bounded mission.

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

Quickstart