Eve library

Chapter 7 · Charter, actors and invocation · brief · 10 September 2026

Guide

Revision 1

On this page

The first chapter of the How Eve works track, rewritten in the Eve edition on 10 September 2026. It follows the plan agreed on 9 September and recorded in EVE-V1-REDESIGN-TODOS.md. The receipt for the delivery is under verification/; this file records what the chapter is for and why it is shaped this way.

The job#

The first track showed what Eve can do. This one explains how any of it works, starting with the part that decides everything after it: the charter she is held to, the four planes that keep usefulness apart from authority, and the invocation that turns a gesture on a page into an authorised turn.

Running example. An operator selects a brief's introduction and asks Eve to revise it without publishing.

Three learning promises (the cover)#

  1. What Eve is for — a builder capability across every workspace, and an acceptance question that is still open.
  2. Where authority lives — four planes that share infrastructure and share nothing else.
  3. How a request begins — a typed envelope carrying the object the person meant, and no more than that.

Three things to remember (the close)#

  1. Authority lives in a plane, and is checked at a boundary.
  2. An invocation is a transition, and the client's half of it is untrusted.
  3. Report the boundary that stopped, rather than claiming completion.

Bridge to chapter eight. What a request needs in order to be about anything.

Sections#

Four sections, opened by a section-divider that names all four.

Section Slides
The charter and its planes the glossary, four parties, the charter, four planes, their evidence
Where a request starts identity, the surface inventory, choosing a surface, page context
What it passes through the envelope, five checkpoints, task families, six tool layers
When it bends guidance that yields, one worked revision, a failed boundary, an exercise

Treatment decisions#

  • The track opens with a glossary, as the plan asked. Eight terms the second track uses precisely where the first used them loosely — plane against surface, and grant against confirmation, are the two pairs that cause the most argument. It is a new slide, eve-charter-glossary.
  • Two legacy graph diagrams retired. eve-four-planes and eve-request-lifecycle were both driven by diagrams.json, which overrides a slide's layout to the legacy graph. Rewriting them as a layer-stack and a sequence-lanes removed two of the twenty-two entries in that file, which is the first real progress on the blocked Phase A migration item.
  • The four parties are a card grid, not an actor-map. The map's contract requires the four canonical actors in their canonical order; this slide's four parties are the person, the assistant, the owning service and the verifier, which is a different set. Forcing it would have misnamed two of them.
  • Ten titles lost their full stops. Seven of the ten inherited slides from the old foundations guide ended in a full stop, which no other chapter does.

What was rebound#

  • Sixteen slides moved out of content/02-eve.json, content/21-eve-deepdives.json and content/50-eve-invocation-detail.json into a new content/64-eve-charter.json; the first two keep the slides that belong to chapters 8–12, and the third is now empty and removed.
  • catalog-source.json: the guide's slide list is the new reading order.
  • Four assignment fingerprints re-reviewed rather than re-pointed: each claim was read against its rewritten slide, confirmed to still hold, and given a dated note saying what changed and what did not.
  • The evidence-comparison contract in test_eve_design moved to scenes-editors, because no Eve chapter uses that layout any more.