REFMandates
Define a mandate
An accepted outcome, not an unbounded task.
This documentation describes the Antecant operating model. The website demonstrates it locally; it does not connect to an autonomous runtime.
Required fields
A mandate has a stable identifier, an accountable owner, an objective, constraints, a maximum budget, authority scopes and acceptance conditions. A desired outcome without a checkable completion condition remains intent.
Readiness is a decision
A mandate becomes ready when its missing information is resolved, its dependencies are understood and its authority is explicitly granted. Readiness is not inferred from how persuasive the initial request sounds.
Children narrow the parent
A child mandate can specialize the objective or reduce its allowed actions. It cannot grant itself broader access, increase a shared budget or silently change the parent’s completion criteria. Shared budget accounting must happen in the enforcing runtime.
Completion is evidence-based
A mandate may be ready, active, gated, satisfied, paused or abandoned. A failed invocation is not the same as a failed objective. Preserve failed attempts and use them to decide whether to retry, revise or stop.
{
"schema_version": "1.0",
"id": "MND-019",
"owner": "human-owner",
"objective": "Prepare a release for owner-approved deployment.",
"constraints": [
"No production changes without approval",
"No access to production credentials"
],
"budget": {
"maximum_usd": 40
},
"authority": {
"allowed": [
"repository:read",
"staging:validate"
],
"approval_required": [
"production:deploy"
]
},
"acceptance": [
"Staging checks pass against the release revision",
"Independent review is recorded",
"Owner approves the exact release revision"
]
}