This map records a complete editorial read of the pinned 161-line
V1/docs/eve/memory-grounding-and-continuity.md. It adds four exact assignments
to the existing context-layer assignment and keeps five meaningful units open.
It does not establish current storage, retrieval, deletion, grounding, reader
comprehension, listening or product acceptance.
Reviewed assignments#
The earlier
eve-opening-boundaries.json file
binds Four context layers. The new
eve-memory-grounding-boundaries.json
file binds:
| Source unit | Guide and slide(s) | Complete teaching boundary |
|---|---|---|
83f3ae210994c1d99df67c89 · Conversation continuity, lines 60–72 |
eve-memory-detail / eve-detail-continuity-fences |
Authoritative append record, bounded compaction, explicit-token/conflict resume, restored/missing-state disclosure and fresh authorization. |
905677926c61fbfe5a30cfc1 · Iris memory, lines 73–95 |
eve-memory-detail / eve-detail-memory-governance, eve-detail-forget-resurrection |
Every owned governance concern and assistant invariant, including separate operator scope and resurrection-resistant forgetting. |
40e6473ab2af333944532f58 · Sophia grounding, lines 96–115 |
eve-memory-detail / eve-detail-claim-support |
Governed claim composition, extractive/gated mode and every required per-claim source, support, currency, authority, production-mode and limitation disclosure. |
31dd6bea44ea12bbafa7b45b · Retrieval and docs search, lines 116–126 |
eve-memory-detail / eve-detail-retrieval-state |
Bounded canonical retrieval, source and audience/layer state, explicit misses, continued grounding and separation of documentation, live state and actual outcome. |
Every slide cites the exact heading and source at inventory revision
1ceae52c7896a59ac74a4429d410f3218f0b91c6. Additional examples and
implementation cautions do not widen these assignments beyond the complete
source units.
Units that remain unassigned#
The source contains ten meaningful units. Five now have reviewed assignments; five remain open:
- Eve Memory, Grounding, and Continuity, lines 1–27: the guides teach the four data roles but do not preserve the complete twelve-edge entity model and its explicit non-substitution semantics as one unit.
- Page-context handoff, lines 41–59: the invocation and context slides cover the envelope and validation rules, but do not identify the named Assistant handoff context-carry journey or consolidate every minimal-typed-context rule into complete evidence for this unit.
- Privacy, retention, and data rights, lines 127–139: the data-store slide preserves every lifecycle field and the distinct store purposes, but does not identify both named member journeys and their separate memory-control versus account-deletion/DSAR roles.
- Degraded and conflict states, lines 140–154: the slides distribute most of the seven postures, but the stale-artifact explanation omits the source's full refresh, confirmation or decline choice.
- Related, lines 155–161: no slide explains all five linked documents and why each belongs beside the memory/grounding contract.
No assignment follows from citation or high lexical overlap. Each future assignment must cover its whole unit and pass exact unit, revision, slide, citation, guide and assembled-fingerprint checks.