Memory Write Policies
Memory & Context
60-90 minutes0/4 steps0%
Step 2 of 4
Attach provenance and confidence
A memory without provenance is a rumor.
First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.
Prompt Capsule
Extend the memory entry schema with metadata: {content, type, provenance: {session_id, date, evidence: 'user-stated' | 'observed-success' | 'observed-failure' | 'inferred'}, confidence: high | medium | low, last_confirmed}. Rules: user-stated preferences and observed successes/failures start high; inferences start low; confidence rises when a later session re-confirms (update last_confirmed) and falls when related actions fail. Update the write tool to require metadata and the read path to render it compactly (e.g. a [high, user-stated, 2026-07] suffix). Backfill existing entries with best-effort metadata, marking unknowns explicitly.Paste into EmergentFull Build: complete implementation prompt with explicit requirements
Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.
Actual change check
Expected after this step
All memory entries carrying provenance and confidence, backfill included.
Should NOT happen
- An existing feature broke
- A button only logs to console
- Data disappears after refresh
- Errors fail silently with no visible state
This is what should exist before you continue. If reality does not match, do not move on.
Track what changed, failed, or needs follow-up. Notes export with the flow.
Pass the Verify Gate to complete this step