Purpose
Keep project state fresh without burying unreviewed transcript noise in long-term memory.
When to use it
- A meeting changes project state.
- An email confirms a blocker or owner.
- You need durable context for future agent runs.
Inputs
- Current project state
- New evidence
- Update policy
Outputs
- Proposed memory patch
- Confidence
- Review notes
Steps
- Read the current project memory before proposing changes.
- Extract only durable facts, decisions, owners, blockers, and next actions.
- Keep transient chatter out of memory.
- Produce a proposed patch with source evidence and confidence.
Quality checks
- The update does not overwrite source-of-truth files blindly.
- Every durable claim has evidence.
Failure modes
- A temporary task is stored as permanent state.
- The update conflicts with a newer source.
Privacy notes
- Memory updates can persist sensitive context.
- Require review for customer names, personnel issues, or financial details.
Example prompt
Propose a project memory update from this new evidence. Include only durable changes, source links, confidence, and review warnings.
Example structured output
{"patch":[{"field":"nextStep","value":"Validate vendor cycle field","source":"meeting:s22"}],"confidence":"high","review":["Check source-of-truth owner"]}