decisions/PRE_DEPARTURE_DECISION_MANIFEST.md
CANON SUBORDINATION — this document is PROPOSAL-TIER: it serves canon and never outranks it.
The canon: the CVD · the T1 foundation docs · the T0 registries (registries/) · the spine
(docs/spine/CH_*.md) · the region pages (_source/02_Tier_2_Region_Pages/). Authority order:docs/DOC_MAP.md§ 0.
Canon served (scanned from this document's own citations — widen it by hand where it is thin):
T0_Interior_Space_RegistryREAD THAT CANON FIRST — open it and derive from it before you build anything from this document.
If this document disagrees with canon, CANON WINS and this document is the defect — fix the
document, never the canon. Nothing here is applied until it is ratified into canon.
Status: LIVE BOARD (minted 2026-07-29 by the weave completeness critic's highest-leverage finding).
Tier: T99 operational — sets no canon. Authority for any item below is the source doc named in its
row, never this table. Maintenance rule in the last section: this board is edited in the same commit
that records a ruling, and register entry GAP-212 is the gap that says what happens if it is not.
Why this exists. Pending decisions were spread across at least thirteen live surfaces with no single
ranked view, and a marker scan over docs/ finds **60 documents carrying at least one pending-Josh
marker** — of which the overwhelming majority are HISTORICAL, markers left behind after the ruling
landed. There is currently no way to tell a live decision from a fossil without reading each doc, so
the cheapest possible ruling and the most expensive one look identical from outside. This table is the
one place that distinguishes them, and the cheapest-form column exists so a five-minute answer is
never queued behind a brief.
Read this before the table; it re-orders everything under it.
The board cadence is RULED serial-until-calibrated (twenty-fourth sitting): one board at a time until
the first-pass approval rate reaches ~90%, then all remaining boards at once. The program sizes the
trailing window at ten reviewed boards, so the phase boundary needs **about ten boards reviewed
one-at-a-time** — roughly 9 to 10 boards at ~15 plates each, on the order of 135 to 150 plates, each
board blocking on a review before the next generates.
Against that, the binding plan's own departure line is **ambiguous, and the ambiguity is the
decision**. docs/PRE_5090_BUILD_PLAN.md (ledger 2026-07-28x) plans WORST-CASE-FIRST: box arrival
possibly Thursday 2026-07-30, Josh off work Thursday afternoon, "get things going before I leave to
the airport", a 5AM flight with a ~2AM airport departure the same night — so the operative assumption
is that the entire hands-on window is Thursday evening. The same entry then says: "if the flight is
the previously-recorded 08-07, everything after Thursday evening is slack and nothing changes."
So the on-shore calibration window is either zero days (worst case, departure Thu 07-30 night) or
about eight (departure Fri 2026-08-07). Under the worst case the ruled calibration phase cannot
complete before departure at any batch size. Three honest options, and the ruling already
half-solves it:
wherever he is. Costs nothing structurally, because his own ruling already made boards
asynchronous — web pages checked at convenience. It does not shorten calibration; it just starts
the clock earlier.
per sitting instead of one, reaching the ten-board window in two or three sittings. This trades the
ruling's own best property (each correction lands before the next board generates) for calendar
speed, and it is the option that genuinely re-opens a ruling.
in batches of three, reviewed within N days, the pipeline continuing on the ratified grammar
between reviews). This is the smallest change to the ruling and the only one that makes the
calibration phase survive travel by design rather than by luck.
RECOMMENDATION: (a) plus (c) — start day one and rule the remote rhythm, leaving the serial
one-at-a-time property intact. Strongest objection: if the worst-case flight is real, even (a)
plus (c) means calibration completes abroad on a phone, and a taste calibration done on a phone
screen is a worse calibration — in which case (b) for the first three boards only, on a laptop
before departure, is the honest trade.
✅ RESOLVED 2026-07-30 (twenty-sixth sitting): BOTH flights are real — tonight (~2AM,
post-box-arrival) is a WEEKEND trip; Friday 2026-08-07 begins TEN DAYS abroad. Boards ruled
(a)+(c): calibration starts tonight, reviews at Josh's convenience from anywhere.
⚡ SUPERSEDED IN FRAMING 2026-07-30 (twenty-seventh sitting): SCRUB THE SCHEDULE. Josh:
"You run 24/7/365 - not on my schedule. I have the same exact capability remote as I do in
person." Once tonight's remote setup proves out, LOCATION NEVER ENTERS A PLAN AGAIN — the
flight facts stay true and stop mattering. The only location-bound class is
physically-hands-on hardware work (tonight's eight non-negotiables). This document's very
name is now historical: it is the DECISION MANIFEST, ranked by what each answer unblocks,
with no departure framing.
Ranked by the product of what it unblocks and how cheap it is to answer. cheapest-form is what the
answer could be, not what a brief would like it to be: ONE-WORD (a yes, a no, or a letter),
ONE-LINE (a sentence of scope), BRIEF (needs the full alternatives pass, already written or named).
| # | decision | blocks what | cheapest-form | source doc |
|---|---|---|---|---|
| 1 | ~~Which flight date~~ STRUCK 2026-07-30: RULED twenty-sixth sitting — BOTH real (weekend trip tonight; ten days from 08-07); see the resolved header fact | — | — | struck; DECISIONS twenty-sixth sitting |
| 2 | ~~Board calibration vs departure~~ STRUCK 2026-07-30: RULED (a)+(c) — boards start day one + the remote rhythm | — | — | struck; DECISIONS twenty-sixth sitting |
| 3 | ~~The solo-L/M composition~~ STRUCK 2026-07-30: RULED IN FULL — Legendary = mastery-gated PER ITEM (per-weapon legendary questlines; ARMOR legendaries source through the mythological realms Ch 66-74); Mythic = POST-GAME, the infinitely playable Epilogue until the MMO expansion. Solo reaches both; the solo-caps reading is dead | — | — | struck; DECISIONS twenty-sixth sitting item 3 |
| 4 | ~~Kokoro vs D-VO-POLICY~~ STRUCK 2026-07-30: RULED (c) — synthesis for named non-story classes only; vo_tier = voiced_performance / synthesis_permitted / subtitle_only as data; chain docs corrected | — | — | struck; DECISIONS twenty-sixth sitting item 4 |
| 5 | ~~Item-economy sizing~~ STRUCK 2026-07-30: RULED (c) — the per-region floor binds; the computed band recorded never ratified; FR-075 arms; no §17.12 number | — | — | struck; DECISIONS twenty-sixth sitting item 5 |
| 6 | ~~The interior-geometry vector~~ STRUCK 2026-07-30: RULED (c) THE HYBRID with the diegetic-portal mitigation IN the ruling — portals only for large below-grade, always staged as passage/descent; T0_Interior_Space_Registry mints; the W-SPACE tooth certifies interiors by their own bounds; Liang Bua un-terraces | — | — | struck; DECISIONS twenty-sixth sitting item 6 |
| 7 | ~~Rank 18's ONE bundled brief~~ STRUCK 2026-07-31: RULED IN FULL 2026-07-30 (all seven live items, twenty-sixth/twenty-eighth sittings; "Rank 18 CLOSES") — the row outlived its own ruling by a day; the maintenance-rule miss is recorded as WO-C in docs/proposals/BUNDLED_BRIEF_2026-07-31.md | — | — | struck; authority docs/proposals/RANK18_BUNDLED_BRIEF.md banner + docs/spine/DECISIONS_PENDING_JOSH.md L363-495 |
| 8 | The presentation doctrine — camera, cut and transition covers | rank 19; the CN5.2 template bake, which cannot start without it; FR-061's cut-class schema | BRIEF (small; it precedes a bake) | docs/PRE_5090_BUILD_PLAN.md rank 19; docs/proposals/PRESENTATION_DOCTRINE.md |
| 9 | ~~The pick economy~~ STRUCK 2026-07-30: RULED at the twentieth sitting ("I agree with recommendation d") and APPLIED at ledger 2026-07-28z — the brief doc's stale status was the fossil; authority docs/spine/DECISIONS_PENDING_JOSH.md twentieth sitting | — | — | struck; ruling authority DECISIONS twentieth sitting |
| 10 | Slice-art throughput — if the art bill does not fit the calendar, does the bill get cut or does the schedule move | GAP-211; the slice art schedule; any honest ship date. Needs the rate table GAP-211 proposes before it can be answered with numbers. RULED 2026-07-31 (thirtieth sitting): roadmapped until answerable — the rate table seeds on benchmark day, revises from box-days 4-7 actuals; this row RE-PRESENTS the moment a slice days-total is a query | ONE-LINE (which side gives) once the rate table exists | register GAP-211; docs/concept_art/density_model.csv; DECISIONS thirtieth sitting |
| 11 | ~~Weapon naming~~ STRUCK 2026-07-30: RULED as recommended — the 72 mechanical placements batch-ratify after the naming-register re-read precondition; display names via the naming pass as one stream | — | — | struck; DECISIONS twenty-sixth sitting |
| 12 | ~~The 71 legendaries~~ STRUCK 2026-07-30: RULED as recommended — ids + questline slots mint NOW, names per region-leg beside row 11; row 3's ruling ADDS realm-road armor legendaries to the same roster discipline | — | — | struck; DECISIONS twenty-sixth sitting |
| 13 | ~~The 30-row reward-taxonomy exception list~~ STRUCK 2026-07-30: RULED at the seventeenth sitting ("The taxonomy exception review - confirm as applied") — authority DECISIONS seventeenth sitting item 2 | — | — | struck; ruling authority DECISIONS seventeenth sitting |
| 14 | ~~The mastery-grade NAME mapping~~ STRUCK 2026-07-30: RULED at the sixteenth sitting ("yes agree on the grade band mapping" — the GRADE_BAND_MAPPING artifact ratified: Adeptus Minor=6, Magus=12, two grades spanning two levels) and APPLIED in the grade-band sweep; the residual is the naming-pass EXECUTION, not a ruling | — | — | struck; ruling authority DECISIONS sixteenth sitting |
| 15 | ~~D-DEFEAT-AXIS~~ STRUCK 2026-07-31: RULED 2026-07-24 (Josh overruled: rated-M, HP 0 = death; protected-only 1-HP withdrawal) and IMPLEMENTED — this row was born a fossil (minted 2026-07-29, five days after the ruling); FR-062's "Josh-pending" marker is WO-A's highest-value fossil | — | — | struck; authority docs/PRE_5090_BUILD_PLAN_VOL2.md L1619 + L1669 |
| 16 | ~~Rank 4 — the GRAND_SAGE voice-row~~ STRUCK 2026-07-31: RULED 2026-07-30 (J7 — "kept, re-classed off tts_casting"; Josh: "J7 agreed with your recommendation") | — | — | struck; authority docs/spine/DECISIONS_PENDING_JOSH.md L429 |
| 17 | The Continuo box-window review brief — Josh routes it to the Continuo lane and returns a compressed one-day worklist | the ruled ONE-DAY Continuo occupancy target on the new box | ONE-LINE (route it) | docs/PRE_5090_BUILD_PLAN.md ledger 2026-07-28x; docs/5090_SETUP_RUNBOOK.md |
twenty-fifth sittings are settled and are not re-asked; where a marker in some doc still says
otherwise, the marker is the defect and the sitting is the authority.
settlement IS to a player, but the non-boss engagement spec's absence from the ranked queue, the
art-loop ownership hops, the rank-namespace bridge and the re-audit vehicle are the director's and
are register rows, not Josh rows.
entries on it.
Register entry GAP-212 is the gap this section closes by hand until it has a tooth.
discipline the factory contract already binds for per-chapter promises. A ruling recorded in
DECISIONS and not struck from here makes this board actively misleading.
guessed honestly. A brief that exists and is not listed here is invisible again.
this file also reads as the decision history in ranked form.
date. Re-measure it when the board is next revised rather than carrying the figure forward — that is
exactly how the register's own Section counts line came to read 9 while the document held 132
entries.