REFInvocants & invocations
Compose actors and actions
Make responsibility legible across a changing fleet.
This documentation describes the Antecant operating model. The website demonstrates it locally; it does not connect to an autonomous runtime.
An actor with a role
An Invocant is a machine actor placed under a mandate, role, context and authority scope. Its underlying model or runtime can change while the responsibility and record remain attached to the work.
Bound one execution
An Invocation records one attempt: its mandate, actor, input reference, source revision, authority snapshot, start and end states, resulting artifacts and errors. Do not equate a chat response with a completed operation.
Separate doing from checking
An implementer can propose a result. A validator checks it against the mandate. A consequential approval should not be granted solely by the same actor whose work is being approved. Independence must be real, not two role labels on one unchecked output.
Stop deliberately
Define timeout, budget, dependency-failure and revocation behavior. Retry only under an explicit policy. A stopped run should leave enough evidence for another actor or a human to understand what happened.