# Chapter 2 · Making it, and being answerable for it · brief · 13 September 2026

The second chapter of the _Creation_ track. Rewritten in the Eve edition on 13
September 2026: eleven inherited slides become a fifteen-slide chapter under the
`atelier-studio` id. It follows the plan in `EVE-V1-REDESIGN-TODOS.md`; the
receipt is under `verification/`.

## The job

A member writes a line in the Atelier and keeps a plate. A creator carries that
plate into Oshun Studio, cites it in a lesson and publishes it. Months later
somebody swaps the illustration. Four different systems owned those four
moments, each with its own record, its own vocabulary of refusal, and its own
idea of what "done" means — and a reader who cannot tell them apart will read a
convincing preview as a publication receipt.

**Running example.** One illustration, from the line that made it to the
published lesson that has to give it up. Executed on this host against the
pinned modules: a twelve-state editorial machine walked over all one hundred and
forty-four ordered state pairs, an asset replacement classified four different
ways, a lineage admission rule measured against the edges the release path
actually emits, a translation asked about every input it was written from, and
an emergency publish path asked what it will and will not defer.

## Three learning promises (the cover)

1. **Four commitments, four records** — make, keep, author and publish leave a
   specimen, a scene, a version and a published state, and three of the four are
   invisible to anyone but their author.
2. **A replacement is classified** — identical bytes invalidate nothing; a
   replacement nothing can classify invalidates everything, on purpose.
3. **Ask what maintains the field** — two alarms in this chapter read a list
   with exactly one producer in the repository, and that producer writes `[]`.

## Three things to remember (the close)

1. **Ask which record.** "Done" means one of four things.
2. **Ask what maintains the field the alarm reads.** An alarm over an
   unmaintained list answers with silence and looks like working code.
3. **Ask what the emergency path will not skip.** What a system declines to
   defer under pressure is its most honest statement of what it values.

**Bridge.** The next chapter turns to Living Scenes, where the artefact stops
being a file and becomes a score that runs.

## Sections

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

| Section                  | Slides                                                                                                        |
| ------------------------ | ------------------------------------------------------------------------------------------------------------- |
| Making and keeping       | the four commitments, the house rules, what each medium owes, the output record, the replacement decision     |
| Authoring and publishing | the workspace, the lifecycle, what outlives an edit, what counts as a signature, the worked swap, the failure |

**Two sections, not three.** Eleven content slides split five and six; a third
divider would leave a section of three.

## Treatment decisions

- **A real capture, and the first in several chapters.** `atelier-house-rules`
  becomes a `capture-callouts` slide over a new harness,
  `tools/presentations/tests/atelier-room-capture.mjs`, which renders the
  shipped `AtelierIndex` from the pin over its own fixture and asserts the room
  count, the house-rule count and the refused draft handoff off the rendered
  DOM. The capture shows both halves at once: five rooms with three printed
  house rules, and the "Draft unavailable" notice a scene id the member does not
  own actually produces. Two images are installed under `assets/atelier/`; the
  chapter uses one.
- **`content/07-creation-and-studio.json` retires.** It held nothing but this
  chapter's eight slides. `content/24-creation-deepdives.json` gives up three of
  its twelve and keeps nine for the Living Scenes chapters.
- **Four slides are new**: a cover, two section dividers and a close.
- **No table.** Two inherited slides were tables; neither needed exact values
  side by side, so `creative-media-classes` and `atelier-studio-failure` became
  compare-panels with the executed values in the notes.
- **`output-lineage` becomes a step-journey** rather than a flow: it is a record
  gaining obligations, and each step leaves one.
- **`asset-library` becomes a decision-tree** with two questions: the
  replacement classifier is a decision with four named outcomes, not a list of
  library features.
- **`editorial-lifecycle` becomes a state-machine** showing the published half
  of the twelve-state machine, including the two states whose names the
  architecture diagram still gets wrong.
- **`collaboration-and-templates` becomes a stat-panel**, because what the
  review layer actually contributes is four countable rules.
- **`atelier-studio-worked` became a case-study of three steps, not four.** The
  four-step version ran 6 px over at 1280 with audio chrome; the translation
  step folded into the classification step rather than shrinking the text, since
  the staleness teaching already has its own slide.

## What this chapter does not establish

No generation was produced, no provider was called, no asset was stored and
nothing was published. Every module executed here is pure — timestamps are
arguments rather than clocks — so a passing verdict is a statement about the
inputs it was handed. The capture is the shipped component over its own fixture
at a pinned commit: the room presentation data is fixture-backed at this pin by
design, which the chapter states on the slide rather than only here. The one
live seam in the Atelier is the image cast, which returns
`provider_not_configured` without a credential, and this chapter did not call
it.
