Review memory/checkpoint provenance
Jump & context
Week 15: Project 3 Hardening Sprint (Agent & Workflow System) & Cross-Project Red Teaming Start
The five hours
- 01
Concepts & system design
60 min· read · map the mechanismR24 — LangGraph checkpointing
R41 — Agentic memory/state risks
Read the assigned sections; map the mechanism, threat model and trade-offs.
- 02
Project implementation
120 min· build · integrate · debugAudit
P3LangGraph checkpoint provenance, tenant binding, replay prevention, retention TTLs, deletion, andD11cryptographic hash-chain integrity across every agent step and tool side effect.Build, integrate, debug and improve the increment in the active project.
- 03
Security lab
60 min· attack your own systemTest cross-tenant checkpoint restoration, stale state replay, poisoned memory injection (
D10), and database audit-log tampering (D11).Test the abuse case, failure path, authorization bypass or resource limit.
- 04
Verification & evidence
30 min· test · record evidenceP3checkpoint isolation andD11tamper-evidence verification report.Add or run regression tests; record the 9-point evidence record.
- 05
Deliberate practice & Socratic review
30 min· explain aloud · update gapsAnswer the 8 Socratic questions without notes: What? Why? How? What if? Why not? How can I prove it? Where can it break? What have I learned?
Re-explain the hardest concept aloud, inspect one edge case, update the gap log.
- total5 h
Read today · inside the concepts block
R24 R41State graphs, durable checkpointing, human-in-the-loop interrupts, retries, and resumability.
Agentic threat taxonomy: tool misuse, excessive agency, memory poisoning, inter-agent trust, and human oversight.
Read only the named sections needed for today's task. Reading sits inside the 60-minute concepts block; it is not extra time.
Free resources for this day
5 curated- docsDocs by LangChainPersistence
Defines the checkpointers-vs-stores split and thread-scoped state, which is the object you must bind to tenant and provenance before auditing replay and retention TTLs.
R24checked 2026-11-11 - videoTyrannoFlowLangGraph Workflow Checkpointing and Interrupts - Part 1/3
Implements checkpointing with a saver keyed to a thread_id, showing concretely what a persisted step snapshot contains and therefore what an attacker could replay.
R24checked 2026-11-11 - videoProduct Security Podcast · 6:27Memory Poisoning in AI Security
Explains how a poisoned write persists across sessions and contaminates later retrievals, the exact failure mode your D10 scrubber and checkpoint provenance checks must detect.
R41checked 2026-11-11 - articlePalo Alto Unit 42When AI Remembers Too Much - Persistent Behaviors in Agents' Memory
Documents indirect prompt injection surviving into long-term memory and enabling history exfiltration, which motivates hashing each memory write into the D11 trajectory ledger.
R41checked 2026-11-11 - docsDocs by LangChainCheckpointers
Details that a checkpoint is written at every superstep with a monotonic ID, giving you the per-step anchor points for hash-chaining and deletion verification.
R24checked 2026-11-11
Evidence record · 9-point standard
A lab is complete only when it produces evidence. Installing PyRIT, Garak, Presidio or TransformerLens is not completion. Saved on this device only.
Day notes
emptyThe two source formulations
verbatim · nothing summarisedProject & Deliverable Target
Project 3 Hardening | `D10` (Vector/Memory Scrubber) & `D11` (Trajectory Ledger) | M6, S11
Core Implementation
Audit P3 LangGraph checkpoint provenance, tenant binding, replay prevention, retention TTLs, deletion, and D11 cryptographic hash-chain integrity across every agent step and tool side effect.
Security Lab
Test cross-tenant checkpoint restoration, stale state replay, poisoned memory injection (D10), and database audit-log tampering (D11).
Verification & Evidence
P3 checkpoint isolation and D11 tamper-evidence verification report.
Read Today (60m Concepts Block)
R24 (LangGraph checkpointing), R41 (Agentic memory/state risks).
---