Launchfiles logoLaunchfiles

Docs · hypothesis-led

Approvals

Authority stays outside the agent. Approvals grant exact scope for side effects such as publish, deploy, send, spend, or durable memory writes. Absence of approval means the action remains forbidden.

Docs hubGet startedllms.txtAgent capabilities

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

What approvals cover

Production mutation, public side effects, billing changes, and promoting interpretation into company memory.

Marketing twin

See /agent-approval-workflows for the founder explainer.

How does Approvals 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.