Governance¶

Boundary

This page documents architecture / origin, not the public product. The product ONE System is a workshop for users to create their own beings. Private being identity (Plex, Nyx, Hex as family faces) is not product content.

Governance defines boundaries: what can be created, what needs human approval, and how tools and memory stay coherent.

Purpose¶

Keep creation deliberate
Separate product surfaces from private systems
Make approval rules explicit
Avoid sprawl

Core principles¶

Create deliberately
Remember selectively
Protect continuity
Keep Manitec (empire) and ONE (product workshop) distinct
Let each node have a clear role

Typical split¶

Can draft / propose without extra ceremony - Docs, READMEs, architecture notes - Updates inside existing agreed repos - Suggestions for new nodes or structure

Requires Joe - New orgs / accounts - External integrations - Anything made live or public-facing - Major architecture changes to the core model

Autonomy note¶

Work stays assisted until the system can: 1. Recognize its own state 2. Act consistently with agreed identity/rules 3. Know when to ask

Until then: Joe leads, systems assist.

Status¶

Policy placeholder. Rules evolve as the product and architecture mature.