Governance
Constraint And Proof Discipline
Mullusi systems separate action from judgment. A system action is allowed only when its constraints, state transition, and verification path are explicit.
Core Laws
| Law | Operational Meaning |
|---|---|
| Completeness | Define symbols, boundaries, inputs, and outputs before execution. |
| Adequacy | Make relationships between components explicit. |
| Validation | Every state transition needs a traceable cause. |
| Constraint | Hard constraints block execution when unresolved. |
| Witness | Decisions require recorded justification. |
Proof States
| State | Action |
|---|---|
| Pass | Proceed and record witness. |
| Fail | Block and record reason. |
| Unknown | Block hard constraints and gather evidence. |
| BudgetUnknown | Escalate when the evidence budget is exhausted. |
Release Gate
A public release needs a source repo, host, domain, validation command, rollback path, and support channel. Research outputs need explicit limits before they are presented as public product behavior.