Eve library

Chapter 1 · Who may ask, and what may be released · brief · 13 September 2026

Guide

Revision 1

On this page

The first chapter of the Creation track, and the chapter that opens it. Rewritten in the Eve edition on 13 September 2026: ten inherited slides become a fourteen-slide chapter under the isis id. It follows the plan in EVE-V1-REDESIGN-TODOS.md; the receipt is under verification/.

The job#

A member asks for an image. Two separate questions have to be answered before anything is generated, by different code at different moments: may this member reach this surface at all, and may this particular output be released. A system that conflates them refuses the wrong people and releases the wrong things.

This substrate exists because of an audit finding. The release gate was real and tested and had zero importers — nothing consulted it before dispatching a generation, so the guarantee that Isis is the only path was a statement of intent rather than a property of the code. Two modules closed that gap, and they are what this chapter executes.

Running example. One image request, followed from the surface check to the moment a provider is or is not called. Executed on this host against the pinned modules: a four-tier entitlement check that denies by default, a nine-gate release evaluation over a complete seven-proof measurement, and a guarded dispatcher that called the injected generation function exactly once when everything held and not at all in any of four refusals.

Three learning promises (the cover)#

  1. Who may ask — four tiers, twenty-eight surfaces, and a plain 404.
  2. What may be released — nine gates, three kinds of floor, a proof bound to each one.
  3. What proves it held — the provider is injected, so a refusal is a call that never happened, and that is countable.

Three things to remember (the close)#

  1. Ask which check refused. A 404 is an entitlement answer; a denial names gates and proofs.
  2. Ask which floor was crossed. Safety blocks, quality reviews, a zero floor does not apply at all.
  3. Ask how many times the provider ran. It is the one claim here that is measured rather than declared.

Bridge. The next chapter turns to Atelier and the editorial Studio, where the question moves from what may be generated to what a person does with it afterwards.

Sections#

Two sections of five, plus the cover and the close.

Section Slides
What may be generated the two checks, the four tiers, the surface guard, the dispatch seam, the three registries
What actually runs it model intake, the providers, the execution substrate, the worked case, the failure case

Two sections, not more. Ten content slides will not carry a third divider without a section of two or three.

Treatment decisions#

  • No capture. The creator and operator generation surfaces are the ones this chapter is about, and capturing one would show a surface without showing the decision behind it — which is the chapter's entire subject. The executed dispatch matrix stands in its place, and the "at least two diagrams and one real capture" checkbox is left unchecked, as it is for six earlier chapters. The chapter has eight diagram layouts and no table.
  • Nothing retires and nothing is carried. content/07-creation-and-studio.json keeps eight Atelier and editorial slides and content/24-creation-deepdives.json keeps twelve Atelier and Living Scenes ones; both will be trimmed again by the next Creation chapters.
  • Four slides are new: a cover, two section dividers and a close.
  • This chapter creates the Creation track, its label, its summary and its reading route, which is the first half of the A2 plan item done for this track.
  • creation-audiences becomes a compare-panel rather than a card grid: the product labels and the enforced identifiers are exactly two vocabularies on aligned rows, and the mismatch is the teaching.
  • generation-boundary and isis-dispatch become decision-trees rather than step-journeys: each is a verdict with named refusals, not a sequence.
  • isis-worked becomes a case-study and isis-registry-lifecycle a state-machine, both recorded in the receipt.

What this chapter does not establish#

No generation was produced, no provider was called and no credentials were used. The release gate, its dispatch guard and the guarded dispatcher were executed in isolation against a declared measurement; the registries, the provenance bundle, the tier resolver and the provider environment contracts were read at the pin. The source itself says the live provider paths are exercised at deploy time with a real key rather than in continuous integration — so this chapter can demonstrate correct refusal and cannot demonstrate generation, which it states on its own slides rather than only here.