Define the three schemas

Each memory kind answers a different question - schema follows.

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

Prompt Capsule

Define schemas for the three stores. EPISODIC (what happened): {session_id, date, task, outcome, notable_events[], artifacts_touched[]} - compact narrative records of sessions and incidents. SEMANTIC (what is true): {statement, topic, provenance, confidence, source_episodes[]} - atomic declarative facts. PROCEDURAL (how to do): {goal, preconditions[], steps[], verification, failure_modes[], last_validated, source_episodes[]} - executable recipes. Write two real examples per store from my project history, including one entry that must be SPLIT (a session story containing both a new fact and a new recipe) to demonstrate the routing discipline.

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

Three schemas with real examples including a demonstrated split.

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.

Schemas capture type-distinct fieldsProcedures include verification and failure modesThe split example shows one input becoming multiple typed entries

Do not continue if…

! Facts phrased as stories, so recall returns anecdotes when the agent needs truth
! Procedures without verification steps - recipes that cannot be trusted
! Episodes hoarded forever at full fidelity, bloating the store
! No links between layers, so a failed episode never corrects the stale procedure

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.

The examples are interchangeable across stores. Sharpen with the question test: episodes answer 'what happened?', facts answer 'what is true?', procedures answer 'how do I?' - rewrite each example until it answers only its own question.