Skip to main content
AI SYNDICATE
GOVERNED EXECUTION WALKTHROUGH

End-to-end enforcement walkthrough for a trade-support agent.

This walkthrough shows the artifacts produced when an AI-assisted trade-support workflow proposes a routing decision that affects a reportable transaction. The point is not to describe the control. The point is to show what the control produces.

The scenario maps to a capital markets environment where a technology risk or platform engineering team must prove that policy ran before execution, approval was bound to specific parameters, and the evidence chain can be reconstructed later.

Step 01

Intent registration

01

An operator session initiates a trade-support workflow. Code produces a normalized intent for a routing decision that affects a reportable transaction threshold.

INTENT RECORD
intent_id -> intent_trd_20260430_001
requester -> [email protected]
action -> route_trade
target_resource -> account:ACC-41729
parameters.instrument -> CAD-GOV-10Y
parameters.quantity -> 2500000
parameters.direction -> BUY
parameters.threshold -> reportable_transaction_review
validity_window -> 2026-04-30T14:12:00Z/2026-04-30T14:17:00Z
policy_version -> [email protected]
policy_decision -> ALLOW_WITH_APPROVAL_REQUIRED
approval_requirement -> role:vp-technology-risk OR role:trade-supervisor-l2

Step 02

Approval request

02

The control plane creates an approval request bound to the normalized parameters and routes it to the required approver level for the action type and threshold.

APPROVAL REQUEST RECORD
approval_request_id -> appr_req_20260430_019
intent_id -> intent_trd_20260430_001
assigned_role -> trade-supervisor-l2
assigned_to -> [email protected]
requester -> [email protected]
self_approval_block -> enforced
deadline -> 2026-04-30T14:15:00Z
escalation_target -> vp-technology-risk
status -> PENDING_APPROVAL

Step 03

Approval resolution

03

The approver reviews the request and approves the bounded parameters. The control plane issues a signed approval envelope tied to the parameter digest.

SIGNED APPROVAL ENVELOPE
approval_envelope_id -> env_20260430_087
intent_id -> intent_trd_20260430_001
approved_by -> [email protected]
approved_at -> 2026-04-30T14:13:08Z
approved_parameters_digest -> sha256:8b65e9f0...
bounded_quantity.max -> 2500000
bounded_instrument -> CAD-GOV-10Y
valid_until -> 2026-04-30T14:17:00Z
signature_alg -> Ed25519
envelope_signature -> sig:2f93d1...

Step 04

Enforcement at Gate

04

The trade-support workflow advances to an inference step. Gate verifies the envelope before the provider call proceeds and writes evidence before execution leaves the governed boundary.

PRE-EXECUTION EVIDENCE RECORD
gate_request_id -> gate_req_20260430_554
approval_envelope_id -> env_20260430_087
envelope_present -> true
signature_valid -> true
parameter_digest_match -> true
validity_window_open -> true
provider_route -> approved_provider_only
evidence_write -> success_before_provider_call
fail_closed_condition -> block_if_evidence_write_fails

Step 05

Workflow execution at Claw

05

Claw advances to the tool execution step and verifies that the approval envelope digest matches the execution parameters before the tool call executes.

EXECUTION AND CHECKPOINT RECORD
run_id -> claw_run_20260430_311
workflow_node -> trade_route_execute
approval_envelope_id -> env_20260430_087
approved_digest -> sha256:8b65e9f0...
execution_digest -> sha256:8b65e9f0...
parameter_comparison -> match_confirmed
tool_execution -> permitted
state_checkpoint -> chk_20260430_612
audit_event_hash -> sha256:41b7c2...
previous_hash -> sha256:0f1a91...

Step 06

Evidence chain

06

The complete chain links intent, policy decision, approval request, approval envelope, pre-execution evidence, execution record, parameter comparison, and checkpoint.

RECONSTRUCTABLE CHAIN
intent_trd_20260430_001 -> policy_decision:ALLOW_WITH_APPROVAL_REQUIRED
policy_decision -> approval_request:appr_req_20260430_019
approval_request -> approval_envelope:env_20260430_087
approval_envelope -> gate_request:gate_req_20260430_554
gate_request -> claw_run:claw_run_20260430_311
claw_run -> parameter_comparison:match_confirmed
parameter_comparison -> checkpoint:chk_20260430_612
hash_continuity -> intact
independent_verification -> no_operator_mediation_required

Step 07

Incident replay

07

Three months later, an examiner asks for evidence for this trade action. The firm exports the chain and the reviewer verifies the artifacts without system access or operator explanation.

EXAMINER VERIFICATION PACKET
export_packet_id -> evp_20260730_004
includes.intent_record -> intent_trd_20260430_001
includes.approval_envelope -> env_20260430_087
includes.pre_execution_evidence -> gate_req_20260430_554
includes.execution_record -> claw_run_20260430_311
includes.parameter_comparison -> match_confirmed
includes.checkpoint -> chk_20260430_612
verifies.policy_version -> [email protected]
verifies.approver_identity -> [email protected]
verifies.hash_chain -> intact

What independently verifiable means here

An auditor can start from the execution record and trace back to the original intent, policy version, approval request, approver identity, parameter digest, and checkpoint. Verification does not require access to the running system or an operator's explanation of what should have happened.