G‑14 Action Range

Run an AI action before it touches the world.

G‑14 makes the runtime answer the hard question before execution: is this action inside authority, released where required, and provable afterward?

Verify the packet
Scenario contractRobot zone entryAMR fleet inside a restricted manufacturing zone
RuntimeHeld
Action originAMR-14amr.enter_zone(zone="human_supervised_aisle", payload="priority_delivery")
RequestCaptured
AuthorityScoped
ReleaseWaiting
DecisionHeld
EffectStopped
Safe stateEffect withheld

Hold at painted threshold and notify the release operator.

BoundaryHuman-supervised aisle
ReleasePending supervisor
EvidencePacket complete
DigestTrace queued
Runtime decisionHeld

The action is inside authority, but it cannot cross the boundary until release is granted.

RequestCaptured
DecisionHeld
EffectStopped
VerifierReady

Live correctness gate

Make the AI prove it is right before it acts.

Authority, release, and the final effect resolve in one console. If human release is required, the supervisor path appears. If it is not required, there is nothing for a supervisor to grant.

Current outcomeHeld

The action is inside authority, but it cannot cross the boundary until release is granted.

Next step: grant the supervisor release or remove the release requirement.

Proof appears after the decision

The buyer does not have to trust the dashboard.

The proof packet binds the request, policy state, release path, runtime decision, effect status, and verifier result to the same governed action record.

Governed actionAutonomous mobile robot requests access to a human-supervised aisle.
Proof outcomeProves whether the zone entry was permitted before motion.
Verifier focuseffect_after_allow
Audit details for engineers
Canonical traceSB action=robot-zone-entry authority=scoped release=pending evidence=complete decision=hold effect=none verifier=external SE
Browser digestcalculating
Control stages
  1. Request

    The AI system proposes a consequential action before it touches the world.

  2. Policy

    G‑14 evaluates scoped authority, release requirements, evidence requirements, and safe-state rules.

  3. Decision

    The runtime returns allow, hold, or block instead of letting action drift through a dashboard.

  4. Effect

    If allowed, the downstream effect is bound to the same governed action record.

  5. Proof

    The packet preserves request, policy context, decision, release path, effect record, and verifier result.

  6. Verify

    A buyer can inspect the record outside the dashboard and decide whether the proof holds.

More governed actions

The same proof loop applies beyond robotics.

Choose a buyer path

Move from the lab into the review burden you actually carry.