Context
The mandate, relevant knowledge, prior decisions and known uncertainty.
SYS / 01The operating model
From intent.
To accountable action.
A mandate holds the purpose. Authority defines the boundary. Evidence preserves the result. Explore the seven objects that make the loop coherent.
INT / 01UNFORMED
What should become true?
The desired change, expressed in human terms. Still open to questions. Not yet an instruction to execute.
ILLUSTRATIVE EXAMPLE
“Prepare our next release without compromising reliability.”
Clarify the outcome
MND / 02ACCEPTED
What are we accepting responsibility for?
An accepted objective with an owner, scope, budget, constraints and evidence-based conditions of completion.
ILLUSTRATIVE EXAMPLE
Release v0.8 after security checks and staging acceptance. Production requires owner approval.
Assemble the work
ORD / 03ASSEMBLED
How should the work be organized?
The operating unit around a mandate: roles, dependencies, handoffs and independent checks.
ILLUSTRATIVE EXAMPLE
An architect proposes. A reviewer challenges. A validator checks. An operator executes.
Delegate authority
IVC / 04BOUNDED
Who is authorized to act?
A machine actor bound to a role, context, capabilities and an explicit authority scope. More than an unbounded agent.
ILLUSTRATIVE EXAMPLE
A release validator with read access to the repository and staging logs. No production write access.
Perform an invocation
INV / 05RECORDED
What exactly was attempted?
One bounded execution under a mandate. Its inputs, authority, provider revision and result stay attached.
ILLUSTRATIVE EXAMPLE
Run the staging acceptance suite against revision 7a12. Stop if the budget or permission boundary is reached.
Inspect the evidence
EVD / 06VERIFIABLE
Why should we accept the result?
An inspectable artifact or observation tied to an acceptance condition—not an actor’s self-reported confidence.
ILLUSTRATIVE EXAMPLE
A test result, an approved diff and a deployment receipt linked to the same release revision.
Retain the learning
MEM / 07PERSISTENT
What should the organization retain?
The useful institutional record: decisions, exceptions, accepted methods and the evidence supporting them.
ILLUSTRATIVE EXAMPLE
The failed check, its root cause and the revised release rule become context for the next mandate.
Inform the next intent
SYS / 02Authority down. Evidence up.
Structure is not
a suggestion.
The operating model only matters when the execution layer enforces it. A prompt, an approval badge or a brand term is not an access control.
Read the authority modelSYS / 03The composition before the act
Context. Capability.
Authority.
Capability
The eligible tools, skills and reasoning available to the actor.
Authority
The resources and actions the actor may use, and the conditions that stop it.
Together, they define a bounded Invocation.
SYS / 04Questions worth resolving
What Antecant is.
And what it is not.
Is this an agent framework?
The focus is the organizational layer around execution: mandates, authority, responsibility and evidence. An agent framework can supply the runtime underneath that layer. This site demonstrates the operating model; it does not ship a connected agent runtime.
Is an Invocant just another word for agent?
Not exactly. In this model, an agent becomes an Invocant when it is bound to a mandate, role, context, capability set and authority scope. The distinction describes responsibility, not a new type of model.
Does the website execute real work?
No. Control is a deterministic browser-local simulation. It does not connect to external providers, execute commands or access your systems. Every sample record is labeled.
Where does human judgment belong?
At mandate acceptance, consequential authority gates, unresolved uncertainty and outcome acceptance. Clear structure should reduce unnecessary interruptions without hiding important decisions.
Can I connect this to my existing stack?
The operating model is designed to be provider-neutral. The documentation supplies reference schemas and architectural expectations, not a currently available integration API. Any adapter needs independent implementation and testing.
NEXTA more deliberate kind of autonomy