FIELD NOTE / LINKEDIN
Agent memory is three different records.
The short film, the complete written thought, and the evidence behind it.
The LinkedIn conversation link will follow its public release.
Agent memory is three different records.
Video caption
Agent memory is three different records.
A policy change affects rationale; a new event affects state.
Supervisors can supply current context with provenance.
My rule: Version, refresh, revoke and test it.
Narration uses Eric's authorized AI voice clone.
#EricFieldNotes
Full written post / accessibility read
A generated approval service needs design rationale, an execution journal and customer-state truth. Those records answer different questions. One markdown summary should not be allowed to stand in for all three.
The design record explains why delegation was allowed under a versioned policy. The journal records attempts and receipts. The entitlement service owns current access. A later revocation must invalidate the cached conclusion without rewriting history.
Let a supervising policy role retrieve the current rule and specific exception, then pass the builder a bounded packet containing source, effective time and unresolved questions. Keep protected acceptance tests outside the builder's control.
Name who updates each record, what change invalidates it and what readback proves its use was safe. Do this because durable memory is valuable only when the next worker can distinguish old belief from current authority.
Narration uses Eric's authorized AI voice clone.
#EricFieldNotes
Four-beat scene transcript
1. Agent memory is three different records.
A generated approval service needs design rationale, an execution journal and customer-state truth. Those records answer different questions. One markdown summary should not be allowed to stand in for all three.
Visual: Mixing them creates confident but untraceable state.
2. Each layer has an invalidation rule.
The design record explains why delegation was allowed under a versioned policy. The journal records attempts and receipts. The entitlement service owns current access. A later revocation must invalidate the cached conclusion without rewriting history.
Visual: A policy change affects rationale; a new event affects state.
3. Inject only the relevant slice.
Let a supervising policy role retrieve the current rule and specific exception, then pass the builder a bounded packet containing source, effective time and unresolved questions. Keep protected acceptance tests outside the builder's control.
Visual: Supervisors can supply current context with provenance.
4. Operate memory like a data product.
Name who updates each record, what change invalidates it and what readback proves its use was safe. Do this because durable memory is valuable only when the next worker can distinguish old belief from current authority.
Visual: Version, refresh, revoke and test it.
Research and claim limits
- DORA 2025 State of AI-assisted Software Development (S225)
- GitHub Copilot Agents application card (S226)
- NIST AI RMF Core (S227)
The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.