Operating principles

1. Least privilege: services use separate locked identities and exact local listeners.
2. Typed actions: the controller exposes named workflows rather than generic commands.
3. Evidence before status: tests, checksums, audit records, and live checks support deployment claims.
4. Human accountability: Founder approval is distinct from legal, security, or professional authorization.
5. Reversible changes: release symlinks, configuration archives, and verified backups support rollback.

External-effect boundary

The active private controller cannot send communications, execute trades, move funds, accept investors, issue digital assets, change DNS, or deploy production code. Those capabilities require separate reviewed systems and evidence that applicable approvals exist.

IP evidence

The Founder IP Center records architecture, dated evidence, status, and review notes. Unfiled items remain labeled unfiled; the system does not convert internal documentation into a legal filing claim.