The first chapter of the The other rooms track, rewritten in the Eve edition
on 12 September 2026. It merges the nine-slide arete introduction and the
forty-three-slide arete-humane-engagement field guide into one chapter under
the arete id. It follows the plan in EVE-V1-REDESIGN-TODOS.md and the track
brief in the-other-rooms-track.md. The receipt is
under verification/.
The job#
Arete is the room where a member keeps a practice: habits, a daily check-in, a streak meant to forgive, a weekly review, and a quiet place to set an intention. The handbook describes one compassionate loop. The repository distributes it across contracts that validate, a domain library that calculates, a route that writes, pages that render fixtures, and a separate tool tree with a browser-local model of its own.
The chapter asks one question of every step: what validated this, what calculated it, what stored it, and what was rendered from an authored fixture. The answers differ more than the member-facing language does, and naming the owner each time is the whole method.
Running example. Mira. A partial check-in on Tuesday, a missed window on Wednesday, a smaller return on Thursday, a closed review on Sunday, and one private intention that evening. Five moments, four owners, and one gap: the canonical record can say she did forty-two percent of the practice, the route she posts through accepts only a status, both rows store fifty, and the missed Wednesday is not stored at all.
Three learning promises (the cover)#
- Every claim has an owner — a contract, a model, a route or a fixture.
- Preview is a register — the pages say so, and the chapter keeps it.
- Two rows, four absences — the write does not create the rest.
Three things to remember (the close)#
- Name the owner. Contract, model, store or fixture are four kinds of true.
- Say what was kept. A recalculation is not a memory.
- Credit the label. A page that says preview is doing it right.
Bridge. The next room is Nyx, read the same way: validated, calculated, stored or rendered.
Sections#
Six sections of five to eight, plus the cover and the close.
| Section | Slides |
|---|---|
| The room, and what stands behind it | the week, six words, two carried slides, five evidence levels, the routes, the hub |
| Two trees, and the records a day makes | three objects, what each page reads, the tool tree, four tiers, the families, two records |
| Missing a day | a goal, a routine, three policies, five stages, counting, an offer, the page, the phone |
| What the write actually keeps | the evidence spine, the trigger rule, the write, the status table, the row, the fold, the gap |
| Friction, coaching, review and neighbours | three vocabularies, the translation, the ladder, coaching, the four acts, three weeks, the neighbours |
| One offering, and what is true | the page, the gate, the record, the drift, the matrix, the priority, the week |
Treatment decisions#
- Two slides are carried unchanged.
lilith-v1-0androom-maturitybelong to the Meet Lilith track and are taught there; this chapter keeps them in place in its opening section rather than restating where the room sits. - Four introduction slides are rewritten in place.
arete-engagement,arete-check-in-contract,arete-recoveryandarete-friction-reviewbelong to the reviewed foundation, so they keep their identifiers and are re-authored in the Eve edition: the three intention objects, the status table, the invitation that records a refusal, and the explanation ladder. - Eight inherited slides merge away. Three of the old introduction are absorbed by the deeper treatment of the same subject, and five humane slides join a neighbour: the domain friction taxonomy into the vocabulary comparison, rest-days into the miss counter, concept links into the cross-domain map, the persistence map into the maturity table, and the read-next map into the close.
- Two tables in fifty-one slides. The status table, where a producer needs the exact values side by side, and the honest matrix at the end: six behaviours, what outlives the request, and how far the claim can be carried. Everything else that was a comparison grid is a card grid, a record anatomy or a compare panel.
- Four captures, all of actual routes. The hub with its BFF deliberately switched off, the recovery preview, the review preview and the offering with text typed into it. Each carries the pin, the fixture scope and the hash.
- The decision tree is the offering gate, because that is the one place in the room where a refusal is a first-class outcome.
- An independent source check of the draft found thirty-one wrong,
overstated or unsupported claims, each re-verified at the pin and fixed before
the first build. The largest: the recovery record has no stored trigger count,
only a rule that a non-manual record must cite evidence; the stored rows keep
the exact posted status, and what the route never accepts is a percentage or a
reason; the recovery engine does run on the member path, and the recovery page
is the surface that does not call it; one check-in writes two rows, the
canonical one insert-once;
rest-daysis not a canonical cadence; the two friction vocabularies share no value at all; and the durable offering record carries no manifest, because the hashes come from a separate route that stores nothing. - Eleven layout findings were fixed before the sweep passed: a five-card grid does not fit 1280×720, so nine became four-card grids, two case studies became three-node cases, and the maturity table lost its widest column.
What this chapter does not establish#
Nothing here touches a deployed service, a real member account, generated media or delivery to another person. The captures are of actual routes rendered from the pinned revision with declared input — one of them with its service deliberately unavailable, which is evidence about the page and not about an outage. The recovery engine's stage is quoted only where a route actually returns it, and no claim is made that the mobile check-in reaches a route at all.