SLICE_COMPLETION_BOARD.md

assets/SLICE_COMPLETION_BOARD.md

The Slice Completion Board

When will we actually have a complete and AAAAA polished chapter 2, chapter 3, and complete vertical slice?
-- Josh, 2026-08-05

Nothing in the slice is above GREYBOX today, and the honest answer to WHEN splits in two: the parts that are gated on WORK have a measured rate and can be stated in waves; the parts that are gated on ASSET CLASSES THAT HAVE NEVER PRODUCED ONE UNIT have no rate, and any date for them would be invented.

*Emitted 2026-08-06 05:19 UTC by harness/site/emit_slice_board.py from harness/site/slice_board_data.json. Canon 90e56655, build 98cfd9c. Every count on this board is computed from that file; nothing is typed in by hand.*

Where the slice actually stands

The matrix below is 14 nodes x 5 domains = 70 cells. Their tiers:

tiercellsshare
ITERATION5071%
GREYBOX811%
CONTENT-COMPLETE1217%
POLISH00%
AAAAA-VERIFIED00%

0 cells sit at POLISH or above. The top two rungs of the ladder are unoccupied across the whole slice, and nobody has ever claimed them.

The ladder (fixed vocabulary)

Per-domain, the rungs mean this:

What this board is standing on

What landed after the audits were written

W14-2 -- [SUPERSEDED 2026-08-06 -- original claim kept below] The creature rim is BUILT -- the half two waves named and did not build.

A kicker/backlight on the creature itself, placed behind it relative to the camera every frame, on lighting channel 1 with only creature primitives receiving that channel, so it cannot spill onto the understory and any measured change is a change in subject pixels by construction. It ships OFF (r.Humanity.CreatureRim 0) and the A/B is a command line rather than a map edit that has to be reverted. || SUPERSEDED 2026-08-06: the A/B this entry said had not been run WAS run, and the lever is REFUTED. Eight arms including a 500x saturation move the subject's own luma by 0.0003 against an OFF baseline whose own spread is 0.0339. See the L23-RIM entry: the root cause is that 45 cd at 232 cm is 8.36 lux against a 128,000 lux sun and it is aimed at surfaces the camera cannot see. The lever is KEPT at default OFF and filed as BUG-0054.

W14-2b -- [SUPERSEDED 2026-08-06 -- original claim kept below] The instrument that can see a subject-only lever now exists.

The frame ruler was a median over ~1,700 tiles; a creature covers tens of them, so a subject-only lever could not move it and 'below the noise floor' would have been ambiguous between 'the lever does nothing' and 'this ruler is blind'. The capture now emits each declared subject's screen box from the actor's own world bounds through the camera basis the frustum tooth already builds -- engine ground truth, not a detector -- and the measure reads inside it: subject local contrast, and the subject-vs-ring edge separation a silhouette is actually read on. || SUPERSEDED 2026-08-06: the instrument was used. Eight arms ran on it, and what it saw is that the lever never reaches the shading -- see L23-RIM. The instrument itself is vindicated and it also produced its own protocol finding: at a creature station the OFF spread is 5-20x the spread at a readable control, because the subject WALKS between runs.

W14-3 -- The encounter KIND stops being inferred from the last three characters of an id.

GetEncounterKind() read the mechanic rail off the sub-boss id suffix, which reads a POSITION IN A CHAPTER as a MECHANIC, and was wrong on five of the nine sub-boss ids the stage tools place. The kind is now DECLARED in three vectors with no inference at any step, and three ids are deliberately left UNDECLARED because their canon rows describe mechanics none of the built rails implement -- declaring one would be the invention the change exists to refuse. Measured: Encounter 2/2, Combat 51/51, Quest 13/13 green.

W14-4 -- [SUPERSEDED 2026-08-06 -- original claim kept below] Wave 13's own reading of its one RED is REFUTED by measurement.

Wave 13 reported the Ch 2 kill run's unmeasured tell-to-impact window as 'a legitimate absence on a run where the player kills fast'. A telegraph ledger now records every windup when it OPENS and again when it REACHES ITS STRIKE FRAME, somewhere the enemy's death cannot take with it. Re-run at HEAD on the same script and real key presses: twelve windups opened and all twelve reached impact, on the very run whose record said no window was ever measured. Two instrument defects are named. THE FIX IS NOT IN THAT COMMIT -- the evidence landed first and the tooth is still honestly RED. || SUPERSEDED 2026-08-06: the fix landed (game 4653e4f). Two derivations were deleted -- the live-enemy scan that skips exactly the enemies that telegraphed on a kill run, and an unconditional read off the currently-WINDING enemy whose zero overwrote the NOT-MEASURED sentinel. Re-measured at HEAD on real key presses: the two pre-fight stations correctly read -1 NOT MEASURED, the old defect's own station now reads -1 instead of a phantom 0, and the fight stations read armed 8 / reached 8 / tell_to_impact 0.557139 s. Verdict GREEN, asserts 3/3. Wave 13's run-level RED is retired ON ITS CAUSE rather than by loosening a band.

CANON-05:41 -- The three Chapter 2 contract asks are ANSWERED. The audits' 'three open gaps' is now FALSE.

Two world-state keys are minted, both integer, both monotonic, because canon's own noun is a mark on a track and the live client already counts exactly that. The first is written on the FOUGHT ROUTE ONLY -- stepping the lane or attuning the breath opens the source intact and writes nothing, fighting the guardian down opens the same water and costs one mark; both are wins and the mark is the price of the easier one. It deliberately does NOT touch the integrity score, because an automatic integrity penalty on a lawful route is a soft ban on that route. The second is ONE track with TWO writers, because both sources state the same predicate about the same place at the same moment, and splitting them would mint a distinction canon does not make; a clean evasion writes NOTHING, so the pressure is the price of survival-by-force and never a tax on being hunted. The creature's element is RULED rather than floored. And the light the canon sentence names turns out to be already present in the zone's own geometry, so the clock stand-in has a real anchor to become.

CANON-05:51 -- The music RULER now exists, and the fourteen themes have been scored against it.

The audits measured that the rubric existed only as one prose line saying it was dispatched, with no file anywhere. That is now false: the rubric is authored with seven scored axes and fifty features, every band naming the exemplar track it came from, and it is armed as a gate at 26 of 26 green. Three instrument-enforced laws: no single scalar anywhere (the schema has no overall key and a control asserts its absence, because the collapse to one score is what let fourteen unanchored themes ship); every band names its exemplar; and nine not-computable features carry their reason and are EXCLUDED from the denominator rather than scored as passes. Building the hook-less control exposed the rubric's own vacuity -- a held pad was passing four axes by satisfying every ceiling with nothing in it -- so four floors were added in response. A rubric that cannot fail a bad melody is not armed.

CANON-NOT-FOLDED-IN -- [SUPERSEDED 2026-08-06 -- original claim kept below] Four more rulings landed inside the read window and are NOT reflected in the cells below.

Named here rather than silently absorbed, because a board that quietly folds in work it did not measure is worse than one that declares the edge of its own read. (1) THE WORLD VERDICT: greybox plus library assets lit for legibility was never going to read at the comparator's top tier, and the world-visual program re-charters on the plates method with its comparator finally armed. (2) THE VOLUME PIVOT: prove-then-batch never batched while the workstation idled, so generation at scale becomes the default posture and two more comparators arm. (3) THE STATUE DIAGNOSIS: creature animation is named as the third unqueued half, the class now has a name and a census owner, and the serpent gets its archetype solver. (4) THE MANNEQUIN CENSUS: the human-character half was unqueued and is now a lane. Items 3 and 4 are the two ASSET classes this board's critical path names as having no demonstrated throughput -- so both now have an owner, which is the precondition for a rate ever existing, and neither has produced a unit yet. || SUPERSEDED 2026-08-06 on items 3 and 4, which this entry said had an owner and no unit. Item 4 (the human-character half) HAS PRODUCED ITS FIRST UNIT: the protagonist is imported, recombined and is the shipped boot default -- see L23-CHAR. Item 3 (creature animation) has produced MEASURED OUTPUT and an honest NO-GO: a limbless solver landed as assets, the snake moves across 96 rendered frames, and the finding is a measured deformation ceiling (99th percentile edge stretch 11.73 on the first pass, 2.82 after) with the bind seam deliberately held so a breathing lump never ships as progress. Two of the five zero-throughput asset classes have now produced something; neither has produced a RATE.

W14-LEDGER -- [SUPERSEDED 2026-08-06 -- original claim kept below] The wave-14 items are NOT yet in the ledger.

QA/bench/LEDGER.md ends at wave 13's honest-tier line. The two wave-14 commits carry their evidence in their own bodies and in w14_telegraph_ledger_evidence.json. No gate-51 comparator verdict has been written for wave 14, so the three standing verdicts below are wave 13's and are the newest that exist. || SUPERSEDED 2026-08-06 BY MEASUREMENT: QA/bench/LEDGER.md is 5,272 lines and now carries wave 15 (the attended claim falling, the ten masters, the judge refuted by its own control), the protagonist import, and the garment lane's own section down to its owed list. The world-visual rungs live in their own W1-W7 rung documents rather than in the ledger. WHAT STANDS UNCHANGED is the part that mattered: no gate-51 comparator verdict has been written past wave 13, so every comparator claim on this board is still wave 13 vintage.

L23-VFX -- THE TEN ABILITY-VFX MASTER SYSTEMS EXIST, RENDER, AND WERE BUILT WITH NO EDITOR WINDOW. This board's step-1 critical path is CLOSED.

CP-1 read 'an attended GUI session on the workstation, never started -- zero partials, no staging manifest.' Both halves are false. Six headless probes established that UE 5.8's NiagaraToolsets statics are reachable from a commandlet -- proven first on a throwaway system saved and RELOADED FROM DISK with all nine user parameters readable, and with one reader caught being blind on the way (an FInstancedStruct payload whose import_text does not complain even about a struct path that does not exist, reported as a named missing API rather than claimed as done). The ten family masters were then assembled in a 13-second headless commandlet. Content/VFX/Elements holds NS_Element_ Air, Earth, EtherCrown, EtherThirdEye, EtherThroat, Fire, Lightning, Poison, Vegetation and Water -- ten of ten, counted on disk. And 'the asset exists' was not allowed to stand in for 'the asset drew the frame': twenty -game runs, ten families by two tier bands, each driving a real key press with the verb rebound from a named canon row, counted the renderer's own path label at niagara 60 / declared-procedural 0. The four D127 automation teeth are 4/4 green at HEAD and the presence tooth still reads 72 beats fired, 56 rendered, 16 declared zero-length, ZERO silent nothings -- now on the niagara path instead of the primitive. The build caught two of its own defects by reading back rather than trusting the write: a doubled mesh renderer, and two families silently keeping the engine's debug gnomon material because a mesh renderer keeps its material behind bOverrideMaterials.

L23-CHAR -- THE PLAYER STOPPED BEING AN ENGINE MANNEQUIN, and OWED-1 closed end to end tonight.

This board says 'the player is a scaled engine mannequin at leg scale 0.76' and 'there is no hero character asset in the project' in four places. The protagonist landed as a real asset and plays the game on real key presses; tonight OWED-1 recombined the authored head onto the THINNED body and made that assembly the SHIPPED BOOT DEFAULT. The recombine is measured, not asserted: 0.359 mm mean at the 104-108 cm cut plane on the head's own geometry, 0.00043 mm anywhere on the face above the chin, and 0.0 mm on every DRAWN vertex of every face-mounted shell -- with a positive control at the waist reading 10.7885 mm against a predicted 10.7671, because a ruler reading ~0 at the neck and a broken ruler produce the same output. The seam prints 0.0514 cm before and after, equal to the body's own tessellation step, which is also the control: a surface crossing, not a rim, and not worse than the build it replaces. The default flip WIDENED the AUTO fit rule with a measurement instead of hard-setting it -- arm C, the recombined mesh, reads 13.36% penetrating and -5.876 mm worst poke-through, identical in every figure to arm A, the base the outfit was actually draped on, against arm B's 49.91% on the thick body -- so the next lane to point the body cvar somewhere else still gets caught. The boot was then handed NOTHING and read back: cvars empty, base SK_CHAR_0001_CHILD at 72,236 tris, one layer bound by leader pose, 82,752 total. And it was LOOKED AT: four CINE_TIER frames of the no-cvar boot.

L23-RIM -- CP-2 WAS RUN AND THE LEVER IS REFUTED. The creature rim was never in the same order of magnitude as the key.

This board's step-2 -- 'NOTHING blocks it, this is a command line' -- was taken, and it returned the rarer result: the lever does not work. Eight arms, three rim-OFF baselines to establish a noise floor, two at authored strength, a 25x mutation, a 500x saturation and a channel-0 diagnostic. Every ON reading sits inside the OFF spread, and the 500x arm moves the subject's own luma by 0.0003. The lever's own positive control -- CREATURE RIM ARMED firing nine lines on every ON arm and zero on every OFF arm -- is what makes 'built but silently inert' distinguishable from 'built and too weak', and the answer is a light that never reaches the shading at all. The ROOT CAUSE was then named by arithmetic on two already-committed numbers, no further capture required: 45 cd at a 232 cm light-to-subject distance is 8.36 lux against a sun of 128,000 lux -- 0.0065% of key, and thirty-six times weaker than the 300 lux fill this map's own lookdev calls 'a trace, not a third of a sky'. And the placement spends even that on pixels nobody reads: the light sits behind the subject on the view axis, so N.L clamps to zero on exactly the camera-facing surfaces the legibility measure reads. Filed BUG-0054, open, lever untouched at default OFF, two arms specified. A protocol finding outlives it: the OFF spread at creature stations is 5-20x the spread at readable controls because THE SUBJECT WALKS between runs, so a subject-local A/B against a wandering AI is measuring the wander.

L23-WORLD -- THE WORLD-VISUAL PROGRAM RAN SEVEN RUNGS AND THE ISLAND'S CELL DID NOT MOVE -- but four of its named holes changed shape.

W1 through W7 plus the L5 items landed between the two reads. What is genuinely new and measured: THE ISLAND HAS NAVIGATION for the first time -- invoker-driven dynamic generation rather than a bake, because a static bake over 14.1 x 10.1 km is hundreds of megabytes inside a 610 MB umap that invalidates on every terrain edit; the volume is sized from the terrain meta and read back off the actor at 14.123 x 10.145 km exact, the agent is built from the pawn's OWN capsule rather than UE's default, and 8 of 8 bearings project and resolve. Its own control is the finding: max path over straight-line distance is 1.0000, with six of eight bearings returning two-point paths of exactly the straight-line length -- the mesh encodes NO OBSTACLE, so W6's 159 solid canopy occluders never reached the navigation data. A CLEAN-CAPTURE GATE exists: humanity.UI.Hidden takes 5 chrome panels and 4.430% of frame pixels to 0 and 0.000%, measured on W5's own chrome detector one cvar apart -- after a first cut that withheld the AddToViewport calls and killed the engine, which is written down because the stronger guarantee was the wrong one. MUD TRACKS have a consumer, measured in a running game with a carry_off control that still walked seven steps and laid seven prints -- and its headline owed is that wetland, the only real carry surface, has NO WEIGHTMAP, so the consumer works and the mud is unreachable. W7a is REFUSED and W7b BLOCKED by the same defect: the composed station id world_composed_04 moved 3.65 km and 802 m down under W5's camera re-solve, so every probe pinned to that id is photographing a different place, and the mask-authority ablation numbers are RETRACTED rather than quoted.

L23-AUDIO-RIG -- THE EXEMPLAR ACQUISITION RIG IS ARMED AND THE CORPUS IS STILL 182/182 MISSING. The audio domain did not move.

The masterpiece program named exactly one human step in its first rung -- buy audio, drop it in the exemplar directory -- and nothing existed to receive it. One command now scans that directory: decode, measure against the program's OWN vocabulary (tempo as a function with its adjustment events, the lane entry/exit map and interlap matrix, the drop/raise/break event grammar with the silence budget as a first-class parameter, the complexity step map), match a corpus row, flip MISSING to ACQUIRED with an sha256 provenance block, or reject with an honest exit code. Its licence to measure anything is a control that runs FIRST, every time: a synthetic signal with a planted tempo, planted lane entries, a planted drop and a break, encoded to AAC and decoded back through the same ffmpeg path a purchase takes, plus a negative control and a zero-guard -- 24 of 24 green, armed as gate music_acquire. Two of those controls are regression teeth for a defect the file shipped and its own control caught: ffmpeg echoes the input path inside its error text, so a garbage file merely NAMED protected.m4a came back REJECT_DRM, which is the worst false positive available because it sends the buyer to re-purchase a file that only needed re-downloading.

L23-GARMENT-RED -- The garment proof suite ran and landed RED on its own face, and the two harness bugs that ate most of it are fixed with their defects as controls.

Nine legs under one input-focus lock; eight came back rc=1 and the record landed saying so rather than being re-run until it was green. TWO OF THOSE REDS WERE THE HARNESS, NOT THE GAME. prove_garment_swap.py unpacked a DeadlineResult as a 4-tuple and died AFTER the engine leg had run, throwing away a real measurement at the last line. capture_world_frames.py kept its --script argument relative, so the engine received an unresolved path it could not open and wrote failed=true with zero shots, three times, at 132 s each -- and the crash in relative_to was the SECOND symptom, destroying the sidecar after the run. Both are fixed with the old expression kept as the arm's own control, so the check reports when it stops controlling anything. The re-run is green on both: three states with the layer bound by leader pose and the unequip restoring the base triangle count exactly, and sixteen CINE_TIER shots across four arms where the dead run produced none. The stride-band and guardian-assert legs are STILL RED and are not this lane's to close -- they are the open conditions BUG-0043/BUG-0048 and the guardian encounter already own, and they are not regressions.

The matrix

nodeCANONWORLDPLAYARTAUDIOfloor
PrologueGREYBOXITERATIONITERATIONITERATIONITERATIONITERATION
Chapter 1GREYBOXITERATIONITERATIONITERATIONITERATIONITERATION
Chapter 2CONTENT-COMPLETEGREYBOXGREYBOXITERATIONGREYBOXITERATION
Chapter 3CONTENT-COMPLETEITERATIONGREYBOXITERATIONITERATIONITERATION
Chapter 4CONTENT-COMPLETEITERATIONGREYBOXITERATIONITERATIONITERATION
Chapter 5CONTENT-COMPLETEITERATIONGREYBOXITERATIONITERATIONITERATION
Chapter 6CONTENT-COMPLETEITERATIONITERATIONITERATIONITERATIONITERATION
Chapter 7CONTENT-COMPLETEITERATIONITERATIONITERATIONITERATIONITERATION
Chapter 8CONTENT-COMPLETEITERATIONITERATIONITERATIONITERATIONITERATION
Chapter 9CONTENT-COMPLETEITERATIONITERATIONITERATIONITERATIONITERATION
Chapter 10CONTENT-COMPLETEITERATIONITERATIONITERATIONITERATIONITERATION
Chapter 11CONTENT-COMPLETEITERATIONITERATIONITERATIONITERATIONITERATION
Chapter 12CONTENT-COMPLETEITERATIONITERATIONITERATIONITERATIONITERATION
Chapter 13CONTENT-COMPLETEITERATIONITERATIONITERATIONITERATIONITERATION

Per-domain census:

domainITERATIONGREYBOXCONTENT-COMPLETEPOLISHAAAAA-VERIFIEDremaining items named
CANON02120040
WORLD13100033
PLAY10400035
ART14000036
AUDIO13100046

SPOTLIGHT: Chapter 2

Chapter 2 is the only chapter anyone has actually played, and it is GREYBOX in three of five columns and ITERATION in art.

domaintierremaining items
CANONCONTENT-COMPLETE3
WORLDGREYBOX7
PLAYGREYBOX5
ARTITERATION7
AUDIOGREYBOX5

What is true

What is not true yet

Shortest path to CONTENT COMPLETE: Fight the main boss by input at the canon sites; WRITE the two world-state keys the canon lane just minted; re-run the defeat loop at HEAD; land the ability sound import that already exists in canon. None of these needs a new asset class, and the canon half of the contract work closed while this board was being written.

Shortest path to AAAAA: Two of the five asset classes have now produced something and neither has produced a RATE. What remains for this chapter is still ASSET work: seven creature meshes plus rigs and real texture for thirteen, authored texture for the character body, an authored hit-reaction set, a judged pass over the ten master systems that now exist, and a region theme that clears a bar the cohort's best composition currently misses on three of seven axes.

SPOTLIGHT: Chapter 3

Chapter 3 has the richest authored content in the slice and the thinnest proof that any of it works.

domaintierremaining items
CANONCONTENT-COMPLETE3
WORLDITERATION3
PLAYGREYBOX4
ARTITERATION3
AUDIOITERATION4

What is true

What is not true yet

Shortest path to GREYBOX WITH PROOF: Write one loop-QA script and run it in the client. That single act converts this chapter from asserted-to-work into measured, and it is the cheapest tier-raising action on the entire board.

Shortest path to CONTENT COMPLETE: The grass-exclusion layer (without it the settlement does not exist at eye level), the seven anchored sound rows, and the state-writing half of the dialogue system.

Every cell, with its evidence

Prologue -- the other realm

*Scheduled LAST by the slice ruling: the realm is designed at slice-end on the matured concept-art pipeline. Its low cells are SEQUENCING, not slippage.*

CANON: GREYBOX

WORLD: ITERATION

PLAY: ITERATION

ART: ITERATION

AUDIO: ITERATION

Chapter 1 -- the other realm

*Same sequencing ruling as the Prologue.*

CANON: GREYBOX

WORLD: ITERATION

PLAY: ITERATION

ART: ITERATION

AUDIO: ITERATION

Chapter 2 -- Flores

*The most-built chapter in the game and the only one with -game input proof.*

CANON: CONTENT-COMPLETE

WORLD: GREYBOX

PLAY: GREYBOX

ART: ITERATION

AUDIO: GREYBOX

Chapter 3 -- Flores

*Shares the dressed island with Ch 2 -- and its own staged content is previz massing.*

CANON: CONTENT-COMPLETE

WORLD: ITERATION

PLAY: GREYBOX

ART: ITERATION

AUDIO: ITERATION

Chapter 4 -- Bali

CANON: CONTENT-COMPLETE

WORLD: ITERATION

PLAY: GREYBOX

ART: ITERATION

AUDIO: ITERATION

Chapter 5 -- Sumatra / Java / Khmer

CANON: CONTENT-COMPLETE

WORLD: ITERATION

PLAY: GREYBOX

ART: ITERATION

AUDIO: ITERATION

Chapter 6 -- Sri Lanka

CANON: CONTENT-COMPLETE

WORLD: ITERATION

PLAY: ITERATION

ART: ITERATION

AUDIO: ITERATION

Chapter 7 -- South India

CANON: CONTENT-COMPLETE

WORLD: ITERATION

PLAY: ITERATION

ART: ITERATION

AUDIO: ITERATION

Chapter 8 -- Swahili Coast

CANON: CONTENT-COMPLETE

WORLD: ITERATION

PLAY: ITERATION

ART: ITERATION

AUDIO: ITERATION

Chapter 9 -- Ethiopia

CANON: CONTENT-COMPLETE

WORLD: ITERATION

PLAY: ITERATION

ART: ITERATION

AUDIO: ITERATION

Chapter 10 -- Rift Valley

CANON: CONTENT-COMPLETE

WORLD: ITERATION

PLAY: ITERATION

ART: ITERATION

AUDIO: ITERATION

Chapter 11 -- Congo Basin

CANON: CONTENT-COMPLETE

WORLD: ITERATION

PLAY: ITERATION

ART: ITERATION

AUDIO: ITERATION

Chapter 12 -- West Africa

CANON: CONTENT-COMPLETE

WORLD: ITERATION

PLAY: ITERATION

ART: ITERATION

AUDIO: ITERATION

Chapter 13 -- South Africa

*THE SLICE TERMINUS -- the healer's child joins and the departure closes the slice.*

CANON: CONTENT-COMPLETE

WORLD: ITERATION

PLAY: ITERATION

ART: ITERATION

AUDIO: ITERATION

The burn-down, in numbers

35 tracked lines. 20 have a demonstrated throughput rate and are therefore schedulable; 13 have NO demonstrated rate at all -- those are the lines that make a date impossible to give honestly.

iddomainitemhaveneedremainingrate
BD-01playSlice chapters with ANY playable content in the engine41410demonstrated
BD-02playSlice chapters with -game INPUT PROOF11413demonstrated
BD-03artFamily master Niagara systems10100demonstrated -- ten masters in one 13-second headless commandlet
BD-04artAbility variant keys needing an authored read0114114NONE DEMONSTRATED
BD-05artCreature meshes for the slice6152146geometry demonstrated / quality NONE
BD-06artCreature assets that can deform or animate0152152NONE DEMONSTRATED
BD-07artCreature texture sets at authored PBR0152152NONE DEMONSTRATED
BD-08artNamed slice characters with a character asset1103102NONE DEMONSTRATED
BD-09artAuthored hit-reaction / flinch / stagger clips0the setthe whole setNONE DEMONSTRATED
BD-10artAuthored attack montages for the game's own moveset4the moveset0 bespoke clips against 72 canon weapons, 185 abilities and 10 tradesNONE DEMONSTRATED
BD-11artCreature attack animation0every creature telegraphall of itNONE DEMONSTRATED
BD-12artLocomotion foot-plant bands inside the armed band044n/a
BD-13worldSlice chapters with a level41410demonstrated -- six landscapes landed in a single commit
BD-14worldLevels with a dressing pass165demonstrated -- 1 map over 3 look waves
BD-15worldMaps with encounter ground on the combat bar264demonstrated
BD-16worldCultural architecture assets1every attested structure in the sliceall but one massing meshNONE DEMONSTRATED
BD-17worldOpen engine-visual defects505demonstrated
BD-18worldSubject stations inside the readable contrast band242n/a
BD-19playCanon systems with a runtime consumer112312demonstrated
BD-20playSlice boss rows with the engine-consumed columns filledwin_condition_reward_counters 49; has_nonkill_path 23; pip_count 13; hitzone_parts 1; phase_trigger 0; signature_counters 04926demonstrated -- a whole chapter's encounter rows have landed in one commit
BD-21playDrop rows carrying a rate0157157NONE DEMONSTRATED for the rates themselves
BD-22playChapter seams built31310demonstrated
BD-23playChapters with gather / trade / exploration stations11413demonstrated
BD-24playDialogue options that write world state0the consequence layerall of itdemonstrated
BD-25audioThemes passing all seven axes of the composition rubric01414NONE DEMONSTRATED for a PASSING theme -- but the bar is now measurable, which it was not this morning
BD-26audioThemes composed at any tier143824partially demonstrated
BD-27audioRegion cells composed (the per-chapter musical identity)01212NONE DEMONSTRATED
BD-28audioRegistry sound rows the engine can resolve and play38680642demonstrated
BD-29audioAbilities with their own sound0185185demonstrated
BD-30audioRecorded voice lines0427427NONE DEMONSTRATED
BD-31audioA music playback path in the engine011NONE DEMONSTRATED
BD-32canonSlice nodes with a region page12142demonstrated
BD-33canonSlice nodes with field-sense clue rows11413demonstrated
BD-34canonQuest definitions landing inside the slice0the slice's own questsall of themdemonstrated
BD-35canonOpen canon contract asks refusing to invent330demonstrated

BD-01 -- Slice chapters with ANY playable content in the engine

BD-02 -- Slice chapters with -game INPUT PROOF

BD-03 -- Family master Niagara systems

BD-04 -- Ability variant keys needing an authored read

BD-05 -- Creature meshes for the slice

BD-06 -- Creature assets that can deform or animate

BD-07 -- Creature texture sets at authored PBR

BD-08 -- Named slice characters with a character asset

BD-09 -- Authored hit-reaction / flinch / stagger clips

BD-10 -- Authored attack montages for the game's own moveset

BD-11 -- Creature attack animation

BD-12 -- Locomotion foot-plant bands inside the armed band

BD-13 -- Slice chapters with a level

BD-14 -- Levels with a dressing pass

BD-15 -- Maps with encounter ground on the combat bar

BD-16 -- Cultural architecture assets

BD-17 -- Open engine-visual defects

BD-18 -- Subject stations inside the readable contrast band

BD-19 -- Canon systems with a runtime consumer

BD-20 -- Slice boss rows with the engine-consumed columns filled

BD-21 -- Drop rows carrying a rate

BD-22 -- Chapter seams built

BD-23 -- Chapters with gather / trade / exploration stations

BD-24 -- Dialogue options that write world state

BD-25 -- Themes passing all seven axes of the composition rubric

BD-26 -- Themes composed at any tier

BD-27 -- Region cells composed (the per-chapter musical identity)

BD-28 -- Registry sound rows the engine can resolve and play

BD-29 -- Abilities with their own sound

BD-30 -- Recorded voice lines

BD-31 -- A music playback path in the engine

BD-32 -- Slice nodes with a region page

BD-33 -- Slice nodes with field-sense clue rows

BD-34 -- Quest definitions landing inside the slice

BD-35 -- Open canon contract asks refusing to invent

The critical path, dependency-ordered

Read this as a chain, not a list: each step names what it UNLOCKS, so a step taken out of order buys nothing.

1. CP-1 -- The ability-VFX master systems -- CLOSED, and never attended

2. CP-2 -- The creature-rim A/B -- RUN, and the lever is refuted

3. CP-3 -- Import the ability sound rows that already exist in canon

4. CP-4 -- One loop-QA script each for Chapters 3, 4 and 5

5. CP-5 -- Fight Chapter 2's main boss by input, at the canon sites

6. CP-6 -- The canon engine-column pass

7. CP-7 -- Dialogue for the chapters that have none

8. CP-8 -- The world chain for the chapters that have no level

9. CP-9 -- The creature asset chain

10. CP-10 -- The character asset chain

11. CP-11 -- The reaction-asset acquisition

12. CP-12 -- The music chain, whose two front-blockers just became one

13. CP-13 -- The realm chapters

WHEN

NO DATE APPEARS ON THIS BOARD, and that is a finding rather than a hedge. No artifact in either repository -- no plan, ledger, queue or board -- carries a measured or estimated date for AAAAA on any chapter. Everything below is DERIVED from demonstrated throughput against counted remaining work, and every derivation names the assumption that would break it.

*The factory's own unit is the WAVE, not the day. A wave is one recorded engine cycle: build, measure, record, commit.*

Demonstrated throughput

metricmeasuredwhat it derives
engine waves landed8 waves (the sixth through the fourteenth) between 08-04 21:24 and 08-05 05:39one wave per ~62 minutes of active factory time
the tightest measured runwaves 9 through 13 in 4 h 37 mone wave per ~69 minutes
commits per day60 on 08-04, 26 by 05:39 on 08-05the factory's peak day is ~60 commits
chapters reaching engine presence4 of 14, across the whole life of the buildCHAPTER throughput is NOT wave throughput and is far thinner -- this is the number that matters for the slice
levels dressed1 of 6, across 3 look waves~3 waves per map dressed
asset classes that have produced a unit2 of 5 (ability-VFX masters 10/10; character assets 1 of 103)the POLISH gate is no longer five-of-five at zero -- and two units and ten assets are still not a rate, so no range moves

Ranges, with the assumption that breaks each one

Chapter 2 -> CONTENT-COMPLETE on PLAY -- 1-3 waves (confidence: HIGH -- every remaining item has a demonstrated rate)

Chapters 3, 4 and 5 -> GREYBOX WITH PROOF -- 1-2 waves (confidence: HIGH)

The canon engine-column pass across the whole slice -- 2-5 canon waves (confidence: HIGH -- zero GPU, zero engine dependency)

Chapters 6-13 -> GREYBOX (level + staging + proof, undressed) -- 8-16 waves (confidence: MEDIUM)

All six existing maps -> DRESSED -- 12-20 waves (confidence: LOW-MEDIUM)

ANY chapter -> POLISH -- UNKNOWN -- NO RANGE CAN BE HONESTLY GIVEN (confidence: n/a)

ANY chapter -> AAAAA-VERIFIED -- UNKNOWN, AND FURTHER OUT THAN POLISH (confidence: n/a)

The honest sentence

Chapter 2 can be CONTENT-COMPLETE on what the player DOES within a few waves, and three more chapters can be measured rather than assumed in about the same time. Nothing in the slice can be POLISHED, let alone AAAAA-VERIFIED, until the asset classes that gate it start producing at a RATE -- and the L23 close changed that sentence in exactly one way: the class this board named as the front of the critical path produced all ten of its units in a single headless commandlet, having been recorded for two waves as blocked on an attended session that turned out not to be needed. Two classes have now produced something, three have produced nothing, and none has produced a rate.

Decisions this board surfaces

DEC-1 (the director) -- Whether this board deploys to the public review site

DEC-2 (the canon lane) -- Four open asks where the engine is correctly refusing to invent

DEC-3 (the director) -- The unanswered site-rights question behind three of five structures

DEC-4 (the audio lane) -- The composition bar HAS a ruler now -- and the recompose has a measured target

What this board does NOT know

Generated by harness/site/structure_site.py — the URL path is the repo path. review root