Status: Design record, build authorized for PR1. Date: 2026-10-05. For Mateo (ids and contracts) and Seth (the Reader). It builds Q6 of the Consolidated Reader decisions and §3 "One colour vocabulary" of the proposal. It delivers the first two acceptance lines of FND-008: the theme-to-engine map beside RISE_CURRENT_THEMES, and each engine rendering all nine themes. B2b, page chrome and the Settings accent, is the third line and follows as its own record. Ground: origin/main = fcc88280. Every code fact is path:line at that commit; nothing was run or rendered, and anything marked (inferred) or (computed) was reasoned from the code, not seen. The owner questions are in §8, each with its answer line.

Q6 as recorded (docs/product/discussions/2026-10-05-consolidated-reader-decisions.md:14): "The nine themes are the only colours a reader or a model sees. The Settings accent is removed and page chrome follows the reading's theme; the ambient drone is removed." Builds B2 and D2. The record adds (:22): "B2 adds its colour maps beside RISE_CURRENT_THEMES and never edits it."

FND-008 (docs/product/tasks/FND-008.json:13-17) has three acceptance lines. B2a delivers the first two:

1. A theme-to-engine map sits beside RISE_CURRENT_THEMES, keyed by the same nine ids; RISE_CURRENT_THEMES is unchanged and the FND-006 guards stay green.
2. Each engine renders all nine themes.

B2b (the third line: page chrome follows the reading's theme; the Settings accent is removed) is a second PR. B2a leaves it exactly one thing: the accessor sessionColorThemeId(session) (§4), and it does not touch the :root colour defaults the embed poster reads (src/live/host/LiveHost.css:122, :153, :159, per the chrome-accent map §7).

The one rule. A reading has one theme, on session.presentation (src/core/models.js:310-313), accepted only when its colours match (src/core/session-presentation.js:112-120). Every engine turns that theme into its own value at the moment it is built. An explicit author value wins; the engine's own "no choice" value takes the theme; with no theme, every engine behaves exactly as today. The "no choice" values are named once and tested once: attractor 'white' (the compiler fills it for every reading, src/core/session-compiler.js:264-269; normalizeFieldStyle too, src/core/visual-style-definitions.js:124), Klee 'random' (:133), Harmonograph climate 'auto' (:147), plate palette 'auto' (:150, :153).

What this changes for readers. Only readings that carry a theme today: Jev and Kev answers, rolls and Today, the two samples, and Composer. Composer renders byte-for-byte as today (its cues already carry explicit rows, src/core/rise-current.js:217, :237, and it runs no Gallery engine, :268); a test proves it for all nine themes. Library, Keystone, Chapel, Journey, Workshop and Reader-setup readings carry no theme and do not change.

Module. src/core/theme-engine-map.js, beside src/core/rise-current.js. Not inside it: the Worker imports rise-current.js to admit Currents (worker/mcp-server.mjs, worker/mcp-gate0.mjs; grep) and must not learn engine knowledge.

Imports, read-only. JEV_COLOR_THEMES (src/core/jev-color-themes.js:9) for key order; RISE_CURRENT_THEMES (src/core/rise-current.js:122-132) for the attractor and Genesis columns by reference, so the two tables cannot drift and Composer invariance holds by identity; validateFlameRecipe (src/core/flame-recipe.js:137) for the one derivation it owns. No visuals import. First load: rise-current.js is not in the shell (src/app.js:13 imports only session-compiler.js statically; rise-current.js is imported by src/live/** and the Worker only, grep), and every importer of the map is a lazy chunk (§4), so measure:first-load (scripts/measure-first-load.mjs:40, :47-58) should not move. CI is the check.

Rule for cells. Engine ids, plus an engine's own dial where the engine has no neutral native (two sat values for silver, one for classic). Never a hex colour: colours come from JEV_PALETTES through sessionColorTheme, as rise-current.js:118-121 already says.

One full entry.

jade: Object.freeze({
  attractor: RISE_CURRENT_THEMES.jade.attractor,   // { system: 'aizawa', palette: 'jade', form: 'bilateral' }, the same object
  genesis: RISE_CURRENT_THEMES.jade.genesis,       // { preset: 'gravitational' }, the same object; Klee Lines reads it too
  turrell: 'ethereal',                             // a key of Turrell PALETTES (src/visuals/turrell.js:38-88)
  neural: 'growth',                                // a key of NeuralNetwork.palettes (src/visuals/neural.js:26-72)
  ostensoria: Object.freeze({ palette: 'teal' }),  // Ostensoria generate options (src/visuals/ostensoria.js:369-382)
  apparitio: Object.freeze({ palette: 'holo' }),   // Apparitio generate options (src/visuals/apparitio.js:110-120)
  livingFlame: Object.freeze({ composition: 'verdant-current' })  // the Flame look's opening composition (C1); hue is computed, §3
})

The nine rows (attractor and genesis are always the RISE_CURRENT_THEMES rows):

Fractal Flames, Harmonograph, Rock Garden, Focal and night streaks have no column: the first three derive from the reading's three colours, Focal already takes the accent, streaks have no theme map (docs/product/CONSOLIDATED-READER.md:295).

Exports.

• THEME_ENGINE_MAP, frozen at every level.
• themeEngine(themeId, engine): the cell, or null for an unknown theme or missing key (own keys only, the jevPalette shape at src/core/jev-palette.js:40-42).
• accentFlameAnchors(colors) lives in src/core/conductor.js (factored out of buildAccentFlamePalette, :652-658, which keeps calling it); the map re-exports nothing of it.
• rockGardenInk(colors) → { backgroundColor: ground, strokeColor: 'rgba(r, g, b, 0.8)' } from the ink, or null.
• themedFlameRecipe(recipe, colors) → the validated recipe with macros.hue rotated so the palette's saturation-weighted mean hue lands on the accent's hue (§3), or the input when colors is null.
• themedFlameLookup(lookup, colors) → id => themedFlameRecipe(lookup(id), colors), null-safe, identity when there is no theme.
• Beside sessionColorTheme in src/core/session-presentation.js: sessionColorThemeId(session) → session.presentation.colorTheme when sessionColorTheme(session) is non-null, else null. One gate, so engines and chrome always agree.

Guard test src/core/theme-engine-map.test.js (one it per line):

• Object.keys(THEME_ENGINE_MAP) equals [...JEV_COLOR_THEMES] in order.
• Every row has exactly the seven keys.
• For every id, row.attractor toBe RISE_CURRENT_THEMES[id].attractor and row.genesis toBe RISE_CURRENT_THEMES[id].genesis (identity; an edit to the contract table fails rise-current.test.js:367-381 and this test together).
• row.turrell is a key of new Turrell(div).palettes (turrell.js:97); row.neural a key of new NeuralNetwork(null).palettes (neural.js:26); row.ostensoria.palette and row.apparitio.palette are ids in OSTENSORIA_PALETTES / APPARITIO_PALETTES other than auto (visual-style-definitions.js:43-62); any sat is in (0, 1]; row.livingFlame.composition is in FLAME_PRESET_IDS (flame-presets.js:144).
• No cell is 'auto', 'random' or 'white'.
• The module source contains no #rrggbb (read the file, regex).
• Frozen at every level.
• themedFlameRecipe: for every theme and every non-spectral composition, the saturation-weighted circular mean hue of paletteLut(result) (flame-math.js:209-222) is within 15° of the accent's hue; prismatic-knot keeps macros.hue 0 under every theme; flameStructureKey (flame-recipe.js:178-181), id and name are unchanged; probeRecipe(result).visible is true (the pattern at flame-math.test.js:22); with colors null the input is returned.

The B3 engine-lists guard (src/core/engine-lists.test.js:38-40) is not tripped: engine keys are unquoted property names and the module writes no quoted list of three ids.

Precedence everywhere: explicit value wins; the no-choice value takes the theme; no theme means today. "Where lowered" is the last hop, because that is the only place the no-choice value is still distinguishable from an author's choice (the compiler fills white, admission re-derives a decision byte for byte, src/app/jev-reading.js:60-64, and the Director keys on the authored cue, src/visuals/visual-field-director.js:35).

Today. The theme is one object, session.presentation = { colorTheme, textColor?, backgroundColor?, colors }, written by Jev and Kev (src/core/jev-config.js:57-65), rolls and Today (src/core/roll.js:161-162, :170), Composer (rise-current.js:270) and the samples; Reader setup carries it unread (ChamberOrbital, per the theme-flow map); the Session stores it as-is (models.js:310-313); the next Archive division keeps it (session-successor.js:57 per the maps). The Chamber accepts it only when colors equals jevColors(colorTheme, textColor, backgroundColor) (session-presentation.js:112-120), paints six variables on its pane (Chamber.js:882-900) and hands the colours to the fractal at session entry (chamber-session-factory.js:320 → visual-cortex.js:2327-2328). Why a cue refuses a theme: rise.experience-program.v1 admits only the keys a cue's kind allows (src/core/experience-program.js:339-356, onlyKeys at :122-128), so a colorTheme key fails PROGRAM_UNKNOWN_FIELD; a field cue's config is opaque metadata (:380-384), which is how Composer carries a theme's effect, baked as explicit engine rows (rise-current.js:217, :237), never the theme. The legacy visualProgram keeps colorTheme on procedural cues only (visual-program.js:112), which Jev's dual and triple arcs use (src/core/jev-sequence.js:117-121); the Chamber applies it at each phase (Chamber.js:2262, :910-925).

After B2a: nothing new is stored. No field joins a cue, a program, a Current or a decision. The theme stays on session.presentation; the lowering is a pure function of (cue, sessionColorThemeId(session), the map), so replay is deterministic and a saved program replays exactly. Five consumers:

1. Chamber.mountVisualFieldCue reads sessionColorThemeId(this.session) at mount for the attractor row and the Genesis preset (§3). Both entrances end there: initializeGenesis and initializeAttractor call the Director directly (Chamber.js:2628-2646), scheduled cues arrive through it too (:2276). The Director keys on the authored cue (visual-field-director.js:35); the theme is constant for the reading, so no key change.
2. The session boundary. chamber-session-factory.js:310-348 adds colorTheme: sessionColorThemeId(session) beside flameColors (:320), plus ostensoriaPalette: 'auto' and apparitioPalette: 'auto'. Both identity functions clear them (visual-cortex.js:688-705 and :715-734, where flameColors: null already sits at :703, :731), because the cortex is a singleton and harmonographClimate shows what an unreset key does to the next reading (the Navigator preview draws with the previous reading's climate, :1731-1733, per the plates verification). The wiring guard src/content/imagery/imagery.test.js:246-249 gains the three names.
3. The cortex's points of use (§3): _themed(engine) = themeEngine(this.config.colorTheme, engine); flameColors for the derived engines.
4. Follow text's director (reading-state.js:105), the Workshop export (Chamber.js:2133) and the Page fallback (Chamber.js:3985) build flame recipes through themedFlameLookup.
5. Home's backdrop (reading-backdrop.js:30-82) reads decision.config.colorTheme for the attractor row and the plate look, so the preview matches the reading it opens. The module is a dynamic import from Home (src/components/Home.js:326, preloaded by src/app/home-preload.js:22), so the map and rise-current.js join a chunk the budget does not count (measure-first-load.mjs:47-58 counts index.html's own tags and the Home-* chunks).

Jev arcs and R6. A dual or triple arc changes colorTheme per phase (jev-sequence.js:103-121), and the Chamber repaints chrome and the fractal (Chamber.js:910-925). B2a keeps that path (the decision record gives R6 to C4, decisions.md:12) and makes the engines follow with the chrome: applyScheduledColorTheme replaces its direct fractal call (:923) with visualCortex.updateConfig({ colorTheme, flameColors: sessionColorTheme(this.session) }, { preservePresentation: true }), which already forwards flameColors to the fractal (visual-cortex.js:2327-2328) and now re-resolves Klee Lines, the plates (setLook aborts the bake under way, so plates are not one plate late) and the Harmonograph's next figure. So a Jev arc still changes colour mid-reading until C4, and chrome, flame, plates and lattice change together. Ending per-phase colour now is owner question M3, with the test inversions listed in §6 ready. Composer cues carry no colorTheme (field cues drop it, visual-program.js:120-129).

Readings with no theme (Library, Keystone, Chapel, Journeys, Workshop, Reader setup with nothing carried in): sessionColorThemeId is null, every resolver returns the engine's own value, and every engine behaves exactly as today: white filament, random Genesis, cycling Klee presets, random Turrell and Neural, the reliquary/ice coin toss, random climates, mood flames. B2a gives them no default theme; what their chrome shows once the accent is gone is B2b's decision, and the default look's colour (Gallery, classic) arrives with C1.

Reader setup colour control: not in B2a. Reader setup has no theme control today (theme-flow map §3, confirmed). The proposal places Colour inside C1's Customize look sheet (CONSOLIDATED-READER.md:426, :447-456), and C2 cuts the first screen to eight controls. B2a makes that control a one-line write: set presentation = { colorTheme, colors: jevColors(colorTheme) } into ChamberOrbital's config, which is already saved and sent at Begin, and every engine follows through the carriage above. Until C1, a theme reaches setup only by Adjust from Home. The cost: B2a's acceptance is exercised through Jev, roll, Today, Composer and Adjust readings, and the tests use compiled sessions directly.

Quality changes (R3). Nothing here touches a quality tier: the attractor's steps never change system, palette or form (CONSOLIDATED-READER.md:530), the flame's tier change keeps the recipe and its LUT, and the plates bake a finished still.

Kept, with the reason:

• ember: the theme (jev-palette.js:6); Iris and Spectral ramps (ostensoria.js:46; apparitio.js:32); the label of climate emberDawn (visual-style-definitions.js:35); a Turrell palette (turrell.js:68); the composition ember-cathedral (flame-presets.js:20-21); the roll temper (roll.js:97-102). Engine ids are the engines' own vocabulary and saved Workshop cues carry them (normalizeProceduralStyle would turn a renamed id into auto, visual-style-definitions.js:150). Where a theme id meets an engine id in the map they mean the same thing (ember → ember, ember, ember). The temper becomes the Iris look in C1 (Q2).
• nocturne: a temper (roll.js:79-84) and a soundscape (jev-config.js:5); names no palette, climate or composition; C1 and C5.
• prism: the theme and a Spectral ramp (apparitio.js:30); mapped to each other deliberately.
• jade, rose, citrine, silver: themes and attractor palettes of the same name (visual-style-definitions.js:16-19); mapped to each other by RISE_CURRENT_THEMES. rose is also a focal glyph (:72), prism's ink name (jev-palette.js:31) and, after B2a, an Iris ramp: a colour word used by an engine for the same colour, the ember pattern. jade is also the gecko accent's label (chamber-accent.js:24 per the maps): goes with the accent in B2b.
• lilac, teal, ivory: Iris ramps and ink names, or accent labels; the accent labels go in B2b.
• theme as a parameter: KleeEngine.generateRandom(theme = 'harmonic') means a preset (klee-enhanced.js:1299 per the maps). Left; mentioned so the reader does not take it for a colour theme. The new module is THEME_ENGINE_MAP, not another …THEMES, and its keys are registry engine ids plus attractor, genesis and livingFlame, never display names.

Retired: nothing in B2a. The second colour vocabularies a model still sees (Jev's visualPalette and kleePreset menus, src/core/decision/recommend.js:80-94; the flame treatment criteria, treatments.js:21-32) are owner question M1.

Fixed contracts untouched. rise.current.v1, rise.experience-program.v1, the compiler input, RISE_CURRENT_THEMES and RISE_CURRENT_VISUALS, ATTRACTOR_VISUAL_MANIFEST, validateJevRecommendation and the admission surface: no file under src/live/**, worker/**, src/core/rise-current.js, src/core/jev-palette.js, src/core/jev-color-themes.js, src/core/visual-control-contract.js, src/core/decision/**, src/app/jev-reading.js, src/core/roll.js (S2, answered 2026-10-05: its signal and garden temper lists are edited after all; see §8) or src/core/session-compiler.js is edited.

Guards that stay green, by path:

• src/core/rise-current.test.js:49-62, :263-290, :336-365, :367-433 (the FND-006 table, brightness ceiling, frozenness): unchanged; the map holds the rows by identity.
• src/core/rise-current.test.js:234-253 (the Composer cue reaches applyScheduledVisualCue unchanged): unchanged; B2a lowers inside mountVisualFieldCue, never by rewriting the cue.
• src/visuals/attractor-manifest.test.js, src/core/jev-palette.test.js:27-31: unchanged.
• src/visuals/attractor.test.js:88-95 (ten palette ids), src/visuals/turrell.test.js:168-179, src/visuals/ostensoria.test.js:37-62, src/visuals/harmonograph.test.js:58-65, :67-89, src/visuals/klee-field.test.js:32-39, src/visuals/living-flame/flame-math.test.js:14-33, src/core/decision/recommend.test.js (menus), src/core/visual-catalog.test.js, src/core/engine-lists.test.js:38-62: unchanged and green.
• src/components/read/Chamber.jev-colors.test.js:9-21, :23-38, :40-50, :52-67 and src/components/read/Chamber.journey.test.js:264-284: assertions unchanged (:52-67 passes because updateConfig forwards flameColors to the fractal). src/core/jev-sequence.test.js:52-53, e2e/jev-sequence.spec.js:52-56, e2e/jev-steering.spec.js:128-130, e2e/night-drive.spec.js:22-35: unchanged.
• src/components/reading-backdrop.test.js:56-69, :71-81, :102-121: unchanged.

Tests that change or are added, by path and how:

• NEW src/core/theme-engine-map.test.js: §2.
• src/core/session-presentation.test.js:21-38: add sessionColorThemeId: the id when the colours match, null when they do not or there is no presentation.
• src/core/conductor.test.js:419-433: add the literal before/after check of buildAccentFlamePalette(JEV_PALETTES[id])[64] and [255] for the nine themes, and accentFlameAnchors returns five triples.
• NEW src/components/read/Chamber.theme-engines.test.js: the attractor and Genesis cases of §3 including the Composer-exactness loop (compileRiseCurrent for each of the nine themes; the attractor and genesis cues mounted with and without the theme give the same AttractorField options and KleeField preset; cobalt's literals thomas/blue/mirror and architectural).
• src/visuals/visual-cortex.test.js:232-249: add the plate keys, _plateLook precedence, _kleePreset resolution, Rock Garden literals, Harmonograph anchors, and that beginSessionVisualIdentity({}) and resetSessionVisualIdentity() set colorTheme null and the plate keys auto. :2181-2190: a second run with colorTheme: 'rose', flameColors: JEV_PALETTES.rose, asserting what each engine spy receives (turrell 'ganzfeld', neural 'organic', harmonograph anchors, rockgarden the rose ground and ink, apparitio { palette: 'marian' }, ostensoria setLook { palette: 'rose' }, kleeFlashes configure preset harmonic).
• src/content/imagery/imagery.test.js:246-249: the forwarded-field list gains colorTheme, ostensoriaPalette, apparitioPalette. It fails until the factory adds them: the guard doing its job.
• src/components/read/Chamber.jev-colors.test.js: :9-21 gains the nine-theme Focal loop; :52-67 gains visualCortex.config.colorTheme === 'prism' after the phase.
• src/components/reading-backdrop.test.js: add white + cobalt → blue row; an ember plate decision passes look: { ostensoria: { palette: 'ember' } }.
• src/visuals/turrell.test.js, src/visuals/apparitio.test.js, src/visuals/ostensoria.test.js, src/visuals/plate-field.test.js, src/visuals/harmonograph.test.js, src/visuals/harmonograph-field.test.js, a small Neural case, src/core/passage-visuals/reading-state.test.js, src/core/passage-visuals/workshop-export.test.js: the additions in §3.
• src/core/visual-style-definitions.test.js: if it pins the Iris list, rose joins it (B3's visual-catalog.test.js:142 pins attractor and Klee options only, per the maps).
• docs/specs/ARCHITECTURE.md §3: the generated diagram prints module counts (scripts/build-architecture-diagram.mjs:142-148), so PR1 runs npm run docs:diagram and commits the result (CI requires no diff, .github/workflows/ci.yml:41-42). src/core/system-design.test.js:123-140 forbids core and visuals importing components; the map obeys.
• For the coordinating agent, not this PR (AGENTS.md keeps .github/workflows/* with it): add src/core/theme-engine-map.test.js and src/components/read/Chamber.jev-colors.test.js to the pull-request vitest list (ci.yml:44-77), and e2e/theme-engines.spec.js to the sharded suite.

The Workshop plate palette bug is fixed here. The Workshop offers and saves an Iris or Spectral palette per passage (src/components/make/Workshop.js:1555-1564, :4001-4006), the program keeps it (visual-program.js:113-114), and the live cortex drops it: applyCue copies only the Klee preset and the climate (visual-cortex.js:622-628), PlateField bakes with no options (plate-field.js:324, :327, :361), and only the dev-only MP4 stage applies it. The theme needs exactly that wire, and the rule "an explicit author value wins" requires the live path to see the author's value at all. Cost beyond the theme: two lines in applyCue, the two keys in styleChanged (:629-632), and setLook's abort.

Seven pull requests, each small, tests first, each green on CI before the next. Locally run only the named files (npx vitest run <file>); never the suite (owner's rule). Lane: Seth builds (S), Mateo reviews PR1 and PR2 (M owns the ids and Composer parity).

PR1: the map and the accessor (core only). Create src/core/theme-engine-map.js, src/core/theme-engine-map.test.js; edit src/core/session-presentation.js (+ test), src/core/conductor.js (+ test), docs/specs/ARCHITECTURE.md (regenerated).

1. Write conductor.test.js's before/after literal test against the unrefactored code: print buildAccentFlamePalette(JEV_PALETTES[id])[64] and [255] for the nine ids once, paste as literals, run npx vitest run src/core/conductor.test.js, green, commit.
2. Write theme-engine-map.test.js (§2) and the sessionColorThemeId test; run; red (module not found).
3. Write the module and the accessor; factor accentFlameAnchors out of buildAccentFlamePalette; run the three files; green.
4. npm run docs:diagram; commit the regenerated file. Verification on CI: the pull-request job plus the full suite on main.

PR2: the field renderers at mount (Chamber). Create src/components/read/Chamber.theme-engines.test.js; edit src/components/read/Chamber.js:2397-2427 and src/components/reading-backdrop.js:34-38 (+ test). Interfaces consumed: themeEngine, sessionColorThemeId.

1. Write the mount tests (attractor row on white, explicit purple stays, Genesis random → theme preset, Composer-exactness loop over nine compiled Currents, no-theme cases, night-drive keeps speed); run; red.
2. Implement the two resolutions at :2404 and :2421, and the backdrop's attractor; green. Verification: rise-current.test.js stays green (run it).

PR3: the cortex carriage, Klee Lines, Turrell, Neural, Rock Garden. Edit src/app/chamber-session-factory.js:310-348, src/visuals/visual-cortex.js (config defaults :262-270, resets :688-734, _kleePreset at :1008 and :2316, forward condition :2314, _themed, stills :1693, :1726, :1759-1763), src/visuals/turrell.js:291-293, src/visuals/neural.js:89-91, src/components/read/Chamber.js:923; tests imagery.test.js:246-249, visual-cortex.test.js, turrell.test.js, a Neural case, Chamber.jev-colors.test.js. Interfaces produced: config.colorTheme, _themed(engine), _kleePreset().

1. Add the three names to imagery.test.js; run; red. Write the cortex tests (resets, _kleePreset, spies under colorTheme: 'rose', Rock Garden literals) and the Turrell/Neural generate(key) tests; run; red.
2. Implement; green. Verification: visual-cortex.test.js:2181-2190 green with and without a theme.

PR4: the plates, the rose ramp and the Workshop fix. Edit src/visuals/plate-field.js (look option, setLook, :324, :327, :361), src/visuals/ostensoria.js (rose ramp and preset at :43-65; setLook and :283), src/core/visual-style-definitions.js:43-54, src/visuals/visual-cortex.js (applyCue :622-632, _plateLook, _syncPlateField :2058, :1745, updateConfig → ostensoria.setLook), src/components/reading-backdrop.js:43; tests plate-field.test.js, ostensoria.test.js, apparitio.test.js, visual-cortex.test.js, reading-backdrop.test.js.

1. Tests first (§3); run; red. 2. Implement; green. 3. Render the rose ramp once (the stills script's harness, step PR7) and tune the anchors by eye before merge.

PR5: the Harmonograph's colour. Edit src/core/conductor.js:753-767, src/visuals/harmonograph-field.js:46-48, :211-213, src/visuals/visual-cortex.js:2008-2015, :1731-1733; tests harmonograph.test.js, harmonograph-field.test.js, visual-cortex.test.js. Tests first; the "same figure, new anchors" and "no mutation of FLAME_PALETTES" cases are the point.

PR6: Living Flame. Edit src/core/passage-visuals/reading-state.js:105, src/components/read/Chamber.js:2133, :3985; tests reading-state.test.js, workshop-export.test.js; the hue test already lives in PR1's map test. Tests first.

PR7: the browser check and the render pass. Create e2e/theme-engines.spec.js (Playwright, the sharded suite on main; the gate list is the coordinating agent's). It uses the harness scripts/build-engine-stills.mjs:146-159 already uses: window.__RISE_TEST__.ensureVisualCortex() (src/app/test-bridge.js:21), cortex.init(), then for each of the nine themes cortex.beginSessionVisualIdentity({ colorTheme, flameColors: JEV_PALETTES[theme], activeTypes: [...] }) and cortex._renderContinuousProceduralWork(engine) for klee, turrell, neural, rockgarden, harmonograph, ostensoria and apparitio. It asserts each still is painted (non-ground pixels exist) and, per engine, that the nine stills differ (mean colour of non-ground pixels distinct across themes) and, for the derived engines (rockgarden, harmonograph, fractal), that the dominant hue lies within 25° of the accent. The attractor and Genesis are covered per theme by PR2's mount tests plus the existing themed e2e (night-drive.spec.js, Composer's live-mcp.spec.js); Living Flame by the LUT hue and probeRecipe raster in PR1 (a real CPU draw, the flame-math.test.js:22 pattern). Also: extend scripts/build-engine-stills.mjs with a --themes flag that writes nine stills per engine to a scratch folder (an artifact for eyes, never committed) so the owners run the render-and-tune pass on the B2a branch before PR4 to PR6 merge; everything they tune is one id or one dial in the map.

What the Visual Lab and the benches keep. The native lists stay for authors: the Visual Lab's full Living Flame bench with its hue control (VisualLab.js per the maps), the Workshop's Filament, Climate, Klee climate, Iris palette and Spectral palette selects (Workshop.js:1529-1564), the Navigator's Preset and Climate benches (visual-taxonomy.js:123-126), Settings › Affect (Emotions.js:54-71) and the Visual Catalog manifests. After PR4 a Workshop Iris or Spectral palette reaches the live reading for the first time. The theme map is what readers and models see.

Marked M (Mateo) or S (Seth). Only what changes what a reader gets or is hard to reverse.

• S1. Under a theme, B2a treats the attractor's white as "no choice" and mounts the theme's full row (colour and shape, the brightness-safe pair). A signal roll draws white one time in three (roll.js:93) and a Jev white answer is possible: cobalt readings then get thomas/blue/mirror instead of aizawa/white/kaleido, prism readings halvorsen/neon/mirror without streaks (Composer's prism). Alternative: palette only, keeping the config's form, which puts neon on kaleido outside the tested ceiling. Confirm the row, or keep white explicit until C1 rewrites rolls as looks.

  Answer (Mateo, 2026-10-05): under a theme, 'white' is no choice and the attractor takes the theme's full RISE_CURRENT_THEMES row (system, palette and form).

• M1. Jev and Kev still answer visualPalette (ten attractor colours) and kleePreset (recommend.js:80-94) beside colorTheme, and admission requires both (jev-reading.js:42-43). B2a honours an explicit model answer (a purple filament under cobalt stays purple), so Q6 is met for those readings only when the model answers white or random. Decide whether a later M-lane change derives both from colorTheme inside choiceConfig (fields kept, so admission passes) and stops asking the model; it changes the evaluation cases and recommend.test.js's menu pin.

  Answer: pending.

• M2 (with S). Jev dual and triple arcs change colour per phase (jev-sequence.js:103-121; Chamber.js:910-925). B2a keeps it and makes the engines follow the chrome, per the decision record (R6 → C4). Ending it now is one deletion (Chamber.js:2262 and :910-925) with these inversions ready: Chamber.jev-colors.test.js:23-67, Chamber.journey.test.js:264-284, e2e/jev-sequence.spec.js:52-56 (sessionTheme and color become the opening theme's), e2e/jev-steering.spec.js:128 (#E84BFF → #C8AE83), and the scene demo (classic then prism). It also leaves the model's middleTheme and finaleTheme answers inert. Now, or C4?

  Answer: pending.

• S2. Rolls keep their temper lists until C1, so a signal roll's blue or purple filament and a garden roll's named preset stay under the theme. A one-line alternative in Seth's lane: delete palettes from the signal temper (roll.js:93) and set the garden temper's klee to ['random'] (:105), so rolls take the theme now, at the cost of one shift in Today's seeded sequence on the deploy day. Now, or C1?

  Answer (Mateo, 2026-10-05): delete the signal temper's palettes list and set the garden temper's klee list to ['random'] in src/core/roll.js now, so rolls take the theme (one shift in Today's seeded sequence is accepted).

• S3. Every nearest-native pick, the rose Iris ramp and the flame offsets are unrendered. Who runs the render-and-tune pass (PR7's --themes stills) before PR4 to PR6 merge, and is a shared pick (classic/citrine on dawn, amethyst/jade on holo, cobalt/rose on marian, four themes on organic) acceptable for engines no look depends on?

  Answer: pending.

• Nothing was rendered. Every pick is a formula or a nearest-hue judgement; the render pass (PR7) is the honest check, and every pick is one id or dial in the map.
• Reader-visible changes in themed Reader readings, which are the feature: the ember temper's plates go from prism and reliquary/ice to ember ramps; the nocturne and salon tempers' Harmonograph takes theme anchors over random chords; a white draw or white answer takes the theme's attractor row (S1); Genesis under a theme with random locks one preset (episode variety becomes seed variety); Turrell and Neural lose per-still variety under a theme (R6); Jev arcs still change colour mid-reading until C4 (M2).
• Explicit model and temper values stay (M1, S2): Q6 is not fully met for a Jev reading whose model chose a palette, until Mateo decides.
• Genesis colour is preset-level: classic/rose, amethyst/prism, ember/citrine and cobalt/silver each share a scheme, exactly as Composer draws them. C4 must not vary the Genesis preset within a reading, or the colour changes.
• The cortex is a singleton: colorTheme and the two plate keys must be cleared in both identity functions; the reset test guards it.
• Page stills for Iris come from a queue baked with no options (ostensoria.js:282-283); setLook must flush it on change or a themed Stream reading opened in Page shows a reliquary or ice plate first (an R6 seam).
• First load: the map imports rise-current.js (13.7 KB raw) into the Chamber and backdrop chunks, not the shell. If measure:first-load moves, the fallback is to hold the two Composer columns by value with a toEqual guard against RISE_CURRENT_THEMES in the map test.
• The generated architecture diagram changes (module count); forgetting docs:diagram fails CI (ci.yml:41-42).
• Engine grounds stay fixed (#0A0A0C baked into plates, Klee and the Harmonograph; [10,10,12] for the flame); the theme ground shows only behind the attractor and the Living Flame, and in the Turrell and Neural palettes' own grounds. Matching grounds is D1's or C4's, because doing it for Genesis changes Composer's pixels.
• MP4 export is dev-only and unthemed; the CPU flame still takes the hue (it samples the same LUT), so no renderer disagreement is introduced.
• The guards for pane colour (Chamber.jev-colors, Chamber.journey) and theme-engine-map.test.js run only on main until the coordinating agent adds them to the pull-request list.

Published from docs/product/discussions/2026-10-05-one-colour-vocabulary-design.md. Edits made here are overwritten on the next push to main.