Memory and Context Packs

Engine-neutral continuity

Every round captures an immutable, versioned Context Pack before execution. It contains the task instruction, prior round and conversation state, mission PRD, Living Project Context, task/mission work references, effective project/task rules, design guidance, recalled memories, source revisions, authority, and the exact render budget. The pack contains no target engine or hidden provider session id.

Claude Code, Codex, Cursor, and other engines receive adapters over the same pack. Native resume may make a same-engine continuation faster, but disabling resume or switching engines still supplies the complete task state.

Temporal memory

Iterel remembers typed decisions, constraints, preferences, facts, procedures, unresolved questions, failures, and accepted outcomes with their source and time. A correction supersedes the current fact without falsifying history. Retrieval combines exact lexical matches, deterministic local vector scoring, authority, recency, and task proximity.

Authority and conflicts

Task instructions and governing rules outrank canonical project sources, which outrank task state, ordinary references, and untrusted intake. Conflicting evidence is preserved and shown; it is never silently blended into one convenient answer.

Local and cloud stores

Collaborative projects use project-scoped Postgres memory under row-level security. Machine-local projects use packaged SQLite with FTS and the same ranking contract, without normal Supabase, Vercel, hosted analytics, or paid embedding traffic.

Audit and Forget

Task Activity shows the pack hash, sources, recalled memories, authority, and ranking evidence used by a round. Forget removes an obsolete memory from future recall and appends a redaction event; it does not erase the historical task or receipt.