The fourth chapter of the Shared systems track, rewritten in the Eve edition
on 12 September 2026. Forty inherited slides become a forty-eight-slide chapter
under the sophia id. It follows the plan in EVE-V1-REDESIGN-TODOS.md; the
receipt is under verification/.
The job#
A member asks Sophia what supports a claim. Back comes prose with citation markers, a list of claims, a map from each claim to its sources, and one word describing how grounded the answer is. The chapter takes that envelope apart and asks, of each part, what it was computed from.
The answers are narrower than the words suggest, and saying so precisely is the chapter's job. Sophia is also three things at once — live, built-but-unwired, and specified — and almost every wrong statement about it comes from mixing those up.
Running example. One question — what supports this claim? — asked of the live answer path. Executed on this host against the pinned modules: a deterministic extractive composer, a response sanitiser that drops any claim a model cannot attribute, a four-signal source scorer whose weights sum to one, and a BM25 index with canonical parameters that the answer path never calls.
Three learning promises (the cover)#
- How an answer is composed — one corpus, one deterministic composer, one envelope.
- How a source is judged — four weighted signals, a floor, and a lifecycle.
- What is actually reachable — live, built-but-unwired and specified are three states.
Three things to remember (the close)#
- Ask what computed the word. Grounded is a count. Credibility is mostly a host.
- Ask what the cleanup checked. Identifiers exist; meaning was never examined.
- Ask whether it ran. Real, tested, and imported by nothing.
Bridge. The next chapter turns to Iris, where the question is not what a claim is grounded in but what the platform is allowed to remember about the person asking.
Sections#
Six sections of seven, seven, six, six, seven and seven, plus the cover and the close. All six fall inside the plan's five-to-seven range.
| Section | Slides |
|---|---|
| What Sophia is, and is not | six substrates, two operations, three postures, two paths, three routes, the ladder, the spec boundary |
| Composing one answer | the route, one corpus, the composer, the thresholds, the envelope, a worked case, four lanes |
| The words the answer uses | claim labels, three vocabularies, the cleanup, three endings, five signals, a contradicting claim |
| Judging a source | the request, four weighted signals, the floor, the lifecycle, readiness, the cascade |
| Reading evidence through the adapter | the contract, three roles, an honest empty, trace export, the consumer map, evaluation, the review |
| Built, and not wired | BM25, the fact-check loop, the contradiction loop, ingestion, source adapters, four stores, the gate |
Treatment decisions#
- No capture. Sophia's only direct surface is a workbench, and the chapter's subject is an envelope rather than a screen. Every claim is executed or read at the pin instead, and the receipt lists what was run.
- All forty inherited slides are rewritten in place. Nothing merges away. They arrived spread across four manuscripts; two of those held nothing but Sophia slides and retire, and the other two keep everything else.
- Eight slides are new: a cover, six section dividers and a close.
- No table. Nine inherited slides were tables. Every one of them read better as a card grid, a compare panel or a stat panel, so the chapter ships without one.
- All three stat panels are declared
measured, because every number on them was produced by executing a pinned module on this host. - The three postures are carried on every slide that needs one. Live, built-but-unwired and specified are not a disclaimer; they decide what proof a claim needs, and the chapter labels capabilities rather than hedging about them.
What this chapter does not establish#
No model was called, no deployed service was reached, and no member data was used. The composer, the sanitiser, the source scorer and the BM25 defaults were executed in isolation against declared inputs; the routes, the adapter and the verification loops were read at the pin. Nothing here shows what any interface displays to a member, which is a limit the chapter states on its own closing slides rather than only here.