docs:

README.md

@@ -46,6 +46,10 @@ This is a product and architecture position, not a claim of handling CUI or sati
 
 Each product is useful on its own and integrates through documented, runtime-neutral contracts. Ledger does not require Perseus, Vault, or any specific agent runtime.
 
+For the governance bridge between durable memory decisions, recall posture, and
+hash-only Ledger evidence, see [Memory governance and Ledger provenance](docs/memory-governance-provenance.md).
+For a copy-pasteable local setup, see [Local Perseus + Vault + Ledger integration](docs/local-perseus-vault-ledger.md).
+
 ## Quick start: record a verifiable event
 
 ```bash

docs/authorized-action-receipts.md

@@ -16,6 +16,11 @@ references and hashes and commits them to the organization event chain. This
 keeps raw prompts, secrets, tool output, and policy bodies outside the Ledger
 while preserving an independently verifiable evidence trail.
 
+For the related memory retention, admission, deletion, curation, and recall
+posture mapping, see [Memory governance and Ledger provenance](memory-governance-provenance.md).
+The [local Perseus + Vault + Ledger integration guide](local-perseus-vault-ledger.md)
+shows the same boundary in a scratch deployment.
+
 ## Roles
 
 | System | Responsibility |

docs/evidence-receipts.md

@@ -1,5 +1,10 @@
 # Perseus Evidence Receipts
 
+For the cross-product mapping from memory lifecycle and recall posture to these
+hash-only fields, see [Memory governance and Ledger provenance](memory-governance-provenance.md).
+For a local Perseus + Vault + Ledger walkthrough, see
+[the local integration guide](local-perseus-vault-ledger.md).
+
 An evidence receipt is a task-scoped, machine-readable view of hash-chained Ledger events. It answers a bounded question:
 
 > For this externally identified task or artifact, which recorded autonomous-system actions exist, what resource allocation accompanied them, and does their containing organization ledger verify?