Implementation: ENABLED (environment recording, effect receipts, egress guard on some paths) · SHADOW (tool call compiler) · Exposure: INTERNAL. See status labels. Tools are how a run changes the world. In the target design, the kernel treats every tool call as a typed, authorized, receipted effect, not as text a model emits.

​
Architecture contract

​
The Agent ISA

The instruction set has seven groups: Observation, Decision, Mutation, Execution, Version Control, Verification and Control. Control covers BRANCH, PARALLEL, JOIN, RETRY, ROLLBACK, CHECKPOINT, REQUEST_EVIDENCE, ESCALATE, WAIT_FOR_DEPENDENCY and FINISH. Each instruction declares input and output schemas, side-effect class, reversibility, evidence produced, permissions and timeout. The primitive registry lists the 191 registered IDs.

​
The path of one effect

Tool family, operation, candidate arguments, schema validation, policy validation, a signed intent, execution inside an ExecutionEnvironment, a typed result and a receipt. Compile and execute are separate steps, with authorization between them.

​
Current implementation

On main, every spawned node has an execution environment recorded in the ledger, network egress goes through one shared guard, and effects leave signed receipts in an internal receipt chain. The typed Tool Call Compiler is on main behind a flag that is off by default, and runs in shadow when enabled.

​
Availability

​
Developer relevance

Declare an honest effect class for every tool. Assume the call will be gated, fenced and receipted, and that a retry of an external effect needs an idempotency key.