The first chapter of the Shared systems track, rewritten in the Eve edition on
12 September 2026. Twelve inherited slides — eleven of the architecture guide's
own and one carried from Orientation — become a thirty-four-slide chapter under
the architecture id. It follows the plan in EVE-V1-REDESIGN-TODOS.md; the
receipt is under verification/.
The job#
Every chapter before this one was about a room. This one is about what the rooms stand on: one contracts package, one registry that says which contract belongs to which domain, one database schema generated from it, and one service in front of all of them.
The chapter asks three questions of one stored row — who owns it, what the registry produced for it, and what happens when somebody asks for it to be deleted. Unlike the room chapters, the answer here is mostly that the substrate is real and wired: a hundred and six non-test files reach the persistence library, ten of the aggregation routes a member touches return the partial- failure envelope, and the erasure cascade reports itself incomplete rather than claiming a success it did not achieve. The defects that do exist are all in one place: not in what a record is, but in agreeing which record an identifier names.
Running example. A Veritas timeline row, written on this host through the
pinned contract repository against a declared delegate double: six contract
fields, ten control columns, a canonical payload hash of 7a02417a…, and four
null tombstone columns, under the tenant tenant-a.
Three learning promises (the cover)#
- What makes a row owned — a registry, ten columns, and one unique identity.
- What the registry produces — a table, a specification, and a client.
- What delete means — two operations, and only one of them is erasure.
Three things to remember (the close)#
- Ask what enforces it. Four records of ownership; the insert decides.
- Ask what serves it. 330 generated paths; zero registered routes.
- Ask what it refuses to claim. An incomplete receipt beats a silent pass.
Bridge. The next chapter takes the same contracts into tenancy and persistence proper, where the two keys of this chapter become an operational question.
Sections#
Six sections of three to five, plus the cover and the close.
| Section | Slides |
|---|---|
| Who owns a row | four answers, three domain counts, five commitments, the registry, the row |
| From a contract to a column | one schema generated four ways, what the generator makes, three addresses, the handoff |
| What a write settles first | the chain, the four steps, four refusals, two patterns, who may ask |
| When only some of it worked | the envelope, the trace, where it is and is not |
| Tenant, region and store | what travels, two keys, which stores are open, what survives a restart |
| Two meanings of delete | marked or removed, the rights table, the worked rename, depth is not reach |
Treatment decisions#
- No capture. This chapter has no member-facing surface of its own; its subject is a row, a registry and a route table. Every claim is executed or counted at the pin instead, and the receipt lists what was run.
- Eleven inherited slides rewritten in place. Seven belong to the reviewed
foundation and keep their identifiers for that reason; none is merged away.
map-of-the-platformis carried in unchanged from Orientation, where it was rewritten. architecture-read-handoffsmoves off theownership-handoffslayout, as the plan directs, tosequence-lanes. That layout is still live in four field-guide depth slides, so its contract tests were repointed atsophia-live-flow— the same shape — and made specimen-agnostic rather than deleted.- One legacy diagram retired.
partial-failure-contractcarried adiagrams.jsongraph entry that overrode its new card grid; the entry is removed with the rewrite, and the build test that used it as its no-declared-geometry specimen was repointed atisis-dispatch. - One table, and readers need it side by side. The three different addresses the same domain has, depending on whether you read the registry, the generated specification or the running service.
- All four 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, never taken from prose. - The delegate double is declared on the slide that uses it. The contract
repository is executed against a fake Prisma delegate that filters on
wherethe way the real one must, so the counts reported are the repository's arithmetic; the receipt records what that double could not see. - An independent source check of the shared architecture is recorded in the receipt, including the one finding that corrected a claim this chapter had already drafted.
What this chapter does not establish#
Nothing here touches a deployed service, a real member account or a live database. The contract repository was executed against a declared delegate double, not Postgres; the cross-tenant collision the chapter reports was measured by a fixture that is checked into the repository, not by this run. No claim is made that any row reached a database on this host.