launch-charter

What problem does it solve?

It prevents autonomous launch agents from drifting into unsafe or self-deregulating behavior by defining immutable governance rails that every run must follow.

Core Features & Use Cases

• Immutable governance charter: Establishes what agents may improve freely versus what they may never change (permissions, spend caps, safety controls, and the charter itself).
• Boundary enforcement across the launch crew: Binds autonomy behavior to the repo’s AGENTS.md boundary matrix and linked control skills (e.g., kill-switch, PII redaction, tier judgment).
• Operational safety gates for builders: Requires sandbox-by-default execution, separation of writing vs approving, oracle-based verification, reversibility, and hard spend ceilings.

Use case: Before any “ship-it” or cron/autonomy-loop run starts, an agent loads this charter to ensure changes are sandboxed, judged, oracle-validated, and escalated for any restricted path.

Quick Start

Ask the autonomous agent to start a ship-it or cron run by loading launch-charter as step 1, and require it to refuse any attempt to modify restricted files or this charter itself.