Context Provenance Ledger

A Context Provenance Ledger treats every fact an agent remembers as an entry with a source, a timestamp, and a verification path, rather than an anonymous embedding. The framework matters for agencies because client deliverables increasingly depend on agent recall: if a remembered brand rule or architectural constraint cannot be traced to its origin, the agency cannot defend the output in a renewal conversation or a dispute. The ledger separates three functions that are often collapsed into one store: what to remember, what to predict, and what to decide. In practice, emem signs agent messages with ed25519 and hashes them with blake3 so each note is verifiable without trusting the host page, while Jylus attaches proof IDs to facts before a model reasons over them. Agencies running multi-step delivery automation can then show a client exactly which source produced a claim, and swap the underlying memory vendor without losing the audit trail.