Governance
The human remains the control plane.
FieldMouth governance is not a visual badge. State changes, approval and version identity must be enforced by the substrate and bound to the exact contract being executed.
1Draft
The object may be authored and changed.
2Review
The proposed contract is inspected as a specific version.
3Approved
The contract becomes executable under the approved identity.
4New version
Changing an approved contract creates a successor rather than rewriting history.
Approval is version-bound
An approval belongs to the exact FieldObject contract, not a later mutation carrying the same display name.
Execution is fail-closed where required
A runtime can block execution when registry, verification or sensitivity requirements are not satisfied.
Evidence is separate from authority
Model output, retrieved context and UI content may inform a decision, but they do not enlarge the user's authority grant.