Governance state
The runtime declares its governance state as a string. The primary state for in-progress work:validate_governance_state verifies the state is recognized:
Traceability statuses
Every contract or feature in MobKit carries a traceability status. The strict status set used for validation:Validation
STRICT_TRACEABILITY_STATUSES set. Unknown statuses produce a GovernanceValidationError.
Baseline verification
The optional source-baseline check can verify that the required Meerkat API symbols are available in a local Meerkat checkout. Supply the checkout explicitly, or setMEERKAT_REPO; there is no machine-specific default:
- Required Meerkat crates are present
- Expected API symbols are exported
- Version compatibility is maintained
Required symbols
TheREQUIRED_MEERKAT_SYMBOLS constant lists every Meerkat API entry point that MobKit depends on. Missing symbols produce a BaselineVerificationError.
Governance contracts
validate_governance_contracts runs the full governance validation suite:
- Governance state validation
- Traceability status validation
- Baseline symbol verification
governance_check) for CI integration.
Governance validation errors
CLI tools
MobKit provides standalone binaries for governance checks:
These can be run in CI pipelines to enforce governance before merge.
See also
- Decisions — runtime policy enforcement
- Configuration — release metadata validation
- Architecture — crate structure
