Docs · hypothesis-led

Authorization

Access is scope-bound. Public discovery is not workspace access. Challenge tokens are prefix-limited and time-limited. Missing scope or product boundary fails closed rather than inventing permission.

See scopes in contract Challenge education

Docs hub Get started llms.txt Agent capabilities

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

Layers

Public discovery → authenticated challenge → future customer workspace read/propose → internal orchestrator only. Higher layers never inherit lower-layer openness.

How does Authorization 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