# Chapter 5 · One sentence, and what decides whether it returns · brief · 12 September 2026

The fifth chapter of the _Shared systems_ track, rewritten in the Eve edition on
12 September 2026. Forty-four inherited slides become a fifty-two-slide chapter
under the `iris` id. It follows the plan in `EVE-V1-REDESIGN-TODOS.md`; the
receipt is under `verification/`.

## The job

A member says something in passing. It might be kept, and if it is it will come
back later in some other conversation. Everything between those two moments is
governance: a record with twenty-one fields, one of eight scopes, a retention
clock, a consent decision per category, and a filter that asks not only whether
the member agreed but whether this is the right conversation to bring it up in.

The previous chapter asked what a claim was grounded in. This one asks a harder
question, because the subject is the member rather than the world: what is the
platform allowed to remember, and what must it decline to mention.

**Running example.** One member says: _I prefer ten-minute practices._ Executed
on this host against the pinned modules: a twenty-one field entry contract over
twenty-nine categories, eight scopes whose summaries outlive their detail, a
four-factor ranker that weights what the member said at twice what the model
inferred, and a recall filter that requires consent and the right conversation
before a sensitive memory returns.

## Three learning promises (the cover)

1. **What is kept** — a governed record, not a useful sentence.
2. **What comes back** — four weighted factors, and a budget per surface.
3. **What the member controls** — consent per category, and rights over all of
   it.

## Three things to remember (the close)

1. **Ask for both keys.** Consent stores it; a relevant conversation mentions
   it.
2. **Ask whether it was applied.** A ledger row, a tombstone and a queued notice
   all fall short.
3. **Ask which list the rule is on.** Nineteen labelled, eleven policied, four
   reaching nothing.

**Bridge.** The next chapter turns to Psyche and Lilith, where the question
moves from what may be remembered to how an interaction is allowed to behave in
the moment.

## Sections

Six sections of seven, seven, seven, seven, eight and eight, plus the cover and
the close.

| Section                                   | Slides                                                                                                   |
| ----------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| What a memory is                          | the boundary, three postures, the anatomy, revisions, categories, four owners, six substrates            |
| Where it lives, and for how long          | eight scopes, two vocabularies, blueprints, retention, promotion, decay, compaction                      |
| Getting it back                           | the pipeline, four factors, budgets, the audit envelope, a token, a conflict, a masked handle            |
| What must not come back                   | nineteen labelled, two keys, two gates, inference, the write ladder, a worked case, failures             |
| What the member agreed to, and may demand | the consent record, the ledger, withdrawal, shared consent, three rights, delete, export, the controls   |
| Who else may look                         | the rights lifecycle, inspection, its policy, its boundaries, replay, the bridge, evaluation, the review |

## Treatment decisions

- **No capture.** Iris has a member-facing memory centre in the plan, and the
  pinned feature page marks it partial — so a capture would either show an
  unfinished surface or imply a finished one. Every claim is executed or read at
  the pin instead. The "at least two diagrams and one real capture" checkbox is
  therefore left unchecked, as it was for chapters five, seven, eight, nine and
  eleven. The chapter has thirty-one diagrams and no table.
- **Forty-two slides rewritten, two carried.** `substrate-responsibilities` now
  lives in the Sophia chapter and `eve-memory-consent` in the Eve context
  chapter; both are already in the Eve edition, so the guide lists them and this
  chapter authors neither.
- **Two manuscripts retire.** `content/73-v1-iris-depth-a.json` and
  `content/74-v1-iris-depth-b.json` held nothing but Iris slides.
- **Eight slides are new**: a cover, six section dividers and a close.
- **Two sections run to eight.** Rights and inspection each needed their whole
  argument in one place; splitting either would have separated a control from
  the evidence it owes.
- **No table.** Eight inherited slides were tables and every one reads better as
  a card grid, a compare panel or a stat panel.
- **All four stat panels are declared `measured`**, because every number on them
  was produced by executing a pinned module on this host.

## What this chapter does not establish

No member data was used, no deployed service was reached and no durable store
was written. The entry contract, scope retention, recall ranker, privacy
classifier, storage gate, recall filter and redaction were executed in isolation
against declared inputs; the store, consent ledger and inspection machine were
read at the pin. Nothing here shows a finished member memory interface, deployed
erasure, authenticated inspection or cross-device acceptance — which the chapter
states on its own slides rather than only here.
