Split memory into layers

Different lifetimes deserve different homes.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule

Restructure the memory store into two layers. WORKING: entries from recent sessions (default: last 14 days or last 5 sessions), loaded eagerly, expected to be noisy. LONG-TERM: consolidated entries with provenance, loaded via index/recall. Migrate the existing store: entries confirmed more than once or user-stated go to long-term; the rest goes to working with their dates. Update write paths (new observations land in working; direct user preferences may go straight to long-term) and read paths (session start loads working fully plus the long-term index). Verify layer counts and loading behavior after migration.

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

A migrated two-layer store with correct write and read routing.

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.

Your notes for this step

Track what changed, failed, or needs follow-up. Notes export with the flow.

Pass the Verify Gate to complete this step

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

Migration rules applied and loggedNew writes route by evidence typeSession loading reflects the layer split

Do not continue if…

! A single flat store aging into a landfill
! Consolidation summaries that quietly destroy unique facts
! Pruning by age alone, deleting rarely-used but critical knowledge
! No metrics, so decay is discovered only when the agent gets visibly dumber

If the AI messes this up

Use this when:

- it only made visual forms or placeholder UI
- buttons do nothing or only log to console
- data is not persisted - state disappears on refresh
- something that worked before is now broken

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

Everything migrated to one layer. Re-check the rules: the split keys off evidence and confirmation, not just age - a day-old user-stated preference belongs in long-term.