# Nyx · One night, computed and reported · receipt · 12 September 2026

Chapter two of _The other rooms_, delivered in the Eve edition on 12 September
2026. Nine inherited slides become a thirty-five-slide chapter under the `nyx` id. The brief is [authoring/nyx-chapter.md](../../authoring/nyx-chapter.md); the
track brief is
[authoring/the-other-rooms-track.md](../../authoring/the-other-rooms-track.md).
Machine-readable state is in [state.json](state.json).

## What was delivered

Thirty-five slides in the guide: thirty-four authored here, plus `lilith-v1-0`
carried unchanged from the Meet Lilith track. Twenty-six are new — a cover, five
section dividers, a close and nineteen teaching slides — and 44.1 minutes of
narration. All eight of
Nyx's own inherited slides are rewritten in place; five of them belong to the
reviewed foundation (`foundation-coverage.json`) and keep their identifiers for
that reason. Nothing is merged away.

## Evidence

- **The pinned ephemeris, executed here.** A transpile loader compares every
  file with the pin before running it. For 12 August 2026 at 22:40 UTC from
  51.83° N, 1.86° W: Julian day 2461265.444444, Sun altitude −20.47°, Moon
  altitude −19.99°, Moon distance 367,654 km, illuminated fraction 0.0006,
  elongation 2.82°, phase `new`, Sun set 19:37 UTC, Moon set 19:40 UTC. The
  2026 Perseid peak meets a new moon, and the engine says so from the
  algorithms.
- **The pinned contract, executed here.** 38 exported schemas, 13 of them enums;
  11 event families, 27 event types, 11 prediction-source kinds read back. One
  canonical observation accepted; refused when the quality band says
  `not-visible` under five percent cloud, when two attachments share an
  identifier, when a region name is empty, and when the duration exceeds a day.
  Accepted again when the cloud cover is unknown — the rule only fires on a sky
  known to be clear.
- **Two captures, rendered from the pin with no server.** The member routes
  cannot be driven on this host, so both use the pinned bundler with declared
  boundary mocks: the shipped observation form with its network edge captured
  (the posted body read back: five fields to `/v1/nyx/observations`), and the
  shipped room over a tonight card the shipped builder computed for the running
  example. Both are byte-stable across runs.
- **The library suite, run here.** 42 files, 365 tests, 364 pass. The one
  failure is at the pin and reproduces in isolation: the canonical search
  adapter labels a saved Moon `celestial-object` where its own test expects
  `saved-object`.
- **An independent source check** of the draft found **twenty-two** wrong,
  overstated or unsupported claims. Every one was re-verified against the pin
  and fixed before the first build. The largest corrections:
  - the canonical observation schema **is** imported at runtime — it is
    registered as a persistence contract on the server's boot path;
  - the observation route **does** write a canonical row, and puts the member's
    free-text target into the column the contract restricts to twenty-seven
    event types, so the row it writes is one the schema would refuse;
  - the room has **four** per-member stores and the erasure registry names two
    Nyx partitions, so the rights gap is specific to the field log;
  - the home perspective and the event-action controls are served by the room's
    named router after all — only the tonight, almanac and observation routes
    live in the general stubs file;
  - the rise-and-set routine is **not** pinned to a published value: it is
    checked against itself, and it carries its own larger stated error, which is
    the approximation behind the printed 05:11 and 19:40;
  - the almanac is built from ten of the directory's nineteen depth tools, and
    the two root-finders named belong to the upcoming-events feed;
  - the default observer is 134 km from the site this sky was computed for, not
    fifty; 367,654 km is close to perigee, not "nearer than average"; the home
    fallback is one evening six months stale, not six months of history; and a
    negative reminder lead resets to the two-hour default rather than clamping
    to zero.

## Checks

| Check         | Result                                                                |
| ------------- | --------------------------------------------------------------------- |
| Build         | 1,564 slides, 681 sources; freshness check clean                       |
| Python suite  | 481 tests pass                                                         |
| Node suite    | 489 tests pass                                                         |
| Browser sweep | 35 slides × 1440, 1280 with audio chrome, 390 and print — 0 findings    |
| PDF           | 35 pages, exact authored visual text, the one table complete           |
| Narration     | 1,564 tracks verified, nothing pending; 44.1 minutes in this chapter    |
| Bindings      | no assignment or teaching file binds a Nyx slide                       |

Five sweep findings were fixed before it passed: the stat panel and the sequence
lanes each declared an `exampleLabel` their layouts do not paint — the
provenance moved into the notes and each number's own source path — and the five
section dividers overflowed by nine to twenty pixels until their subtitles were
shortened.

## Treatment deviations

Three, each deliberate:

- `nyx-tonight` ships as a **stat panel** rather than a step journey: its content
  is four executed numbers with units and a source path each, and a geocentric
  computation has no actors to give a journey.
- `nyx-worked` ships as a **timeline** rather than a step journey: it is six
  moments of one evening with what each leaves behind.
- `nyx-failure` ships as **sequence lanes** rather than a table or card grid: it
  follows two journeys — a tapped row and a delivered reminder — that end in the
  same not-found panel, and the point is the path.

## What this chapter does not establish

Nothing here touches a deployed service, a real member account, a device or a
network. The captures render pinned components with declared mocks and the
posted body was recorded, not sent. No claim is made that an observation reached
a database on this host, that a reminder was delivered, or that the standalone
astronomy API is wired to the consumer path — it is not.
