# Chapter 2 · One saved preference, and seven things to prove · brief · 12 September 2026

The second chapter of the _Shared systems_ track, rewritten in the Eve edition
on 12 September 2026. Twenty-nine inherited slides become a thirty-nine-slide
chapter under the `v1-contracts-tenancy` id. It follows the plan in
`EVE-V1-REDESIGN-TODOS.md`; the receipt is under `verification/`.

## The job

The previous chapter established what a stored row is. This one follows a single
write across the boundaries between a button press and that row: the canonical
shape it has to satisfy, who was allowed to send it, the key that decides
whether a repeat is the same write, the tenant and zone it lands under, the
store that receives it, and what can still be read if it half-failed.

The answers are not uniform, and the chapter's job is to say which boundary each
claim belongs to. Three of the mechanisms turn out to be complete, correct and
barely reached — and in each case the gap is precise enough to name.

**Running example.** One member changes one preference. Executed on this host
against the pinned modules: an optional idempotency key scoped to a tenant, a
token whose scopes are checked by a locally-defined helper, and a tenant taken
from a header that the verified claim is never compared against.

## Three learning promises (the cover)

1. **What shape it has to be** — one canonical contract, and how much of it is
   stored.
2. **Who was allowed to send it** — two role registries, and what the routes
   actually test.
3. **Where it landed, and what remains** — a tenant, a zone, a store, and the
   receipts afterwards.

## Three things to remember (the close)

1. **Ask who turns it on.** A complete mechanism, requested by no shipped
   client.
2. **Ask which one runs.** Two role registries; 353 local copies decide.
3. **Ask what the evidence tops out at.** Executed, counted, read and measured
   are four different strengths.

**Bridge.** The next chapter follows the same requests outward into events, jobs
and discovery, where the receipts this one looked for are supposed to be
produced.

## Sections

Six sections of six, three, five, five, five and seven, plus the cover and the
close. One falls outside five to seven and it is deliberate: the shapes section
is one contract read three ways.

| Section                          | Slides                                                                                    |
| -------------------------------- | ----------------------------------------------------------------------------------------- |
| The contract and its projections | the case, the owner, the spine, exports, the alignment manifest, generated artifacts      |
| What a half-answer means         | the three fields, four shapes, the adapters between                                       |
| Who is allowed to act            | the domain registry, the foundation, two role registries, 353 copies, OAuth               |
| One key, one request             | the refusal points, eligibility, the fingerprint, four outcomes, who asks for it          |
| Where the write lands            | the tenant, the zone, routing against enforcement, a rights request, the stores           |
| What survives the write          | four gates, two deletions, the cascade, a rename, recovery, four ceilings, seven receipts |

## Treatment decisions

- **No capture.** The chapter's subject is a request path, not a surface. Every
  claim is executed or counted at the pin instead, and the receipt lists what
  was run.
- **All twenty-nine inherited slides are rewritten in place.** None belongs to
  the reviewed foundation, and all twenty-nine lived in one manuscript, so
  nothing moves between files and nothing is carried in. Ten slides are new: a
  cover, six section dividers, two teaching slides and a close.
- **The old manuscript is retired.** `content/69-v1-contracts-tenancy.json` held
  these twenty-nine slides and nothing else, so it empties and is removed rather
  than left with no slides in it.
- **Two legacy diagrams retired.** `v1-contracts-persistence-projection` and
  `v1-contracts-openapi` carried `diagrams.json` graph entries that would have
  overridden their new Eve compositions.
- **Every heading citation is kept.** The inherited slides were bound to
  fifty-six reviewed source units by the headings they cited, and the assembler
  restores each slide's headings so the review stays bound. The regenerated
  assignment now holds fifty-eight: every original unit, plus the request-flow
  and five-commitments units this rewrite genuinely teaches.
- **No table at all.** The comparison the plan expected to stay a table — the
  four shapes the partial-failure envelope's three fields can take — reads
  better as a compare panel with the refused shape in its own column, so the
  chapter ships without one.
- **Five slides depart from the layout the plan named**, each because the slide
  turned out to teach a different shape than expected: `residency-enforcement`
  and `tombstone` became compare panels, `persistence-projection` a stat panel,
  `field-change` a step-journey and `partial-recovery` a card grid. The receipt
  gives the reason for each.
- **Both stat panels are declared `measured`**, because every number on them was
  produced by executing a pinned module on this host or counting at the pin.
- **An independent survey** of the request path is recorded in the receipt. Six
  of its findings were re-verified here before use.

## What this chapter does not establish

Nothing here touches a deployed service, a real member account or a live
database. Every module was executed in isolation against declared inputs, and
every count was taken across the repository at the pin. No claim is made that a
request from a real client behaves this way in a deployment.
