The runtime arrow

Runtime does not jump directly from OCG to Shared Attention. It starts from accepted revision truth and loops each receipt into the next action.

Enteraccepted revision
→
ActAPI / SDK
→
FunctionCalltyped execution
→
OIG Commitlive truth moves
→
Receiptnext attention

Read first: Code → Graph → Commits explains the OCG/Meta mechanism, materialization, proof, and WorkspaceRevision acceptance boundary that runtime depends on.

What the loop must preserve

A runtime action should preserve the actor or request provenance, API capability, FunctionCall, branch, projection, prior head, resulting OIG commit, and receipt. Failure should remain specific and leave durable state unchanged.

That chain lets an Interface, CLI, service, human, and agent observe the same causal event instead of correlating logs after the fact.

Inspectable runtime safeguards

Kernel foundations define FunctionCall execution, OIG commits, replay, provenance, fail-closed mutation, and receipts. Agent participation remains inside typed API and Service boundaries, and every accepted mutation carries its causal evidence forward.