Source motivation
Current context-engineering and collaborative-agent patterns increasingly require action systems to preserve not just the outcome of an action, but the exact context and policy basis that justified it.
Problem
Ledger has strong receipt primitives, but action records do not yet consistently capture the exact context bundle or policy bundle that informed the action.
Proposal
Add context-hash and policy-hash attachment to Ledger action stages.
Potential scope:
- attach stable hashes for context artifacts and policy manifests to proposed and executed actions
- support replay-friendly resolution of those artifacts where visible
- make those hashes available in execution preview and receipt surfaces
- standardize hash-bearing stage records across action flows
Why now
As context compilation and approval gating mature, Ledger should be able to answer not only what happened, but what exact grounded context and policy frame produced the decision.
Success criteria
- proposed and executed actions carry stable hash references
- receipts can reconstruct the exact context basis for an action
- upstream tools can render concise grounded previews from the same identifiers
Source motivation
Current context-engineering and collaborative-agent patterns increasingly require action systems to preserve not just the outcome of an action, but the exact context and policy basis that justified it.
Problem
Ledger has strong receipt primitives, but action records do not yet consistently capture the exact context bundle or policy bundle that informed the action.
Proposal
Add context-hash and policy-hash attachment to Ledger action stages.
Potential scope:
Why now
As context compilation and approval gating mature, Ledger should be able to answer not only what happened, but what exact grounded context and policy frame produced the decision.
Success criteria