Obligation map
From legal requirement to executable control.
01
Decide before execution
Apply a deterministic policy boundary before an autonomous system signs or submits a financial transaction.
02
Record the reason
Keep the policy version, input digest, outcome, rule, and timestamp needed to reconstruct every automated decision.
03
Escalate material actions
Route threshold or sanctions-sensitive activity to explicit human approval rather than letting the model improvise.
04
Make mutation detectable
Bind records in a SHA-256 chain and anchor the current head so later edits cannot pass unnoticed.
Reconstructable record
intent → policy@v1.4 → APPROVE → sha256:a3f8…b2f0 → optional public anchorRun the readiness check →