FOLD_REPORT_P1C.md

pipelines/FOLD_REPORT_P1C.md

FOLD REPORT — P1-C wave, 2026-07-28

Inputs: 4 audit drafts + 4 fresh-context refutation critics under scratchpad/lens_wave/, plus the

20 binding rulings in scratchpad/lens_wave/DIRECTOR_ADJUDICATIONS_28.md (Addendum 2, items 15-20,

is the P1-C set). Output: scratchpad/lens_wave/REGISTER_V14_FOLD.md — 39 new register entries,

94-132, plus six amendments to existing entries, a DR-2 freeze-consequence statement, the claim-board

flip block, the kill ledger and a four-item Josh brief queue.

Per-unit counts, from the critic closing blocks

Arithmetic notes. The knowledge-progression critic's headline reads "Killed: 2" but both kills are

LIMBS, not findings: KPD-3 splits into 3a (survives, land the gate) and 3b (re-classed

blocked-on-a-ruling) with its recommendation struck, and KPD-6 is re-classed and narrowed rather than

removed. Counted honestly in whole-finding terms, only the two hades findings die outright, and both

die with a preserved crumb routed elsewhere (HD-14 to entry 73, HD-20 to entry 9). Presentation is

the cleanest unit in the program to date — zero findings die across sixteen, with the critic

independently re-running every count and confirming exact reproduction on 12 of 19 measurements and

holding controls on the rest.

Register selection: 39 of 58 survivors earned a row (HIGH-priority, schema-freeze-relevant or

slice-relevant); the remaining 19 are captured in four per-lens roll-up lines naming their draft as

the record, and one survivor (PC-16) enters as an amendment to existing entry 4 rather than a new

number, per adjudication 20.

Unresolved

Zero items are unresolved in the sense of blocking the fold. Everything either landed at its amended

verdict, landed CONTESTED-CARRIED at a stated position with both readings recorded, or routed to the

Josh brief queue without being applied. Four things the director should know are OPEN rather than

undecided:

• The DECAY law (v1.3 entry 92) was in this lens's declared scope and produced no clause. It is

recorded as a named debt on DR-2 open item 6, not silently dropped. This is the one place the wave

did not fully discharge what the claim board assigned it.

• Four Josh briefs are queued and none is applied: the band collapse (entry 97), the cross-cultural

reward taxonomy (entry 129), player-initiated bond investment (entry 119), wrong-link cost (entry

127).

• Six items are CONTESTED-CARRIED to the director by design: entry 110's bounded-persistence

question, entry 115's scope against 47/48, the pop-up-rift density band, entry 117's class split,

the sink-ladder class, and the T3 roster count currency (routed as a director apply, but

numeric-canon adjacent — confirm the reading first).

• One process defect propagates OUTSIDE this fold: the wave spec's own divergence guard carries a

wrong CVD anchor for the ratified minigame-completion promise. Substance true, anchor wrong, and

every lens in the wave that touched the no-scoreboard guard may have inherited it. Fix at the wave

spec so the roster re-anchors.

Landing checklist for the director

Ordered so nothing writes a file another step is reading, and so anything that must precede a

scheduled freeze or an in-flight wave lands first.

1. THE DR-2 CLAUSE, first, because the freeze is what this wave ran ahead of.

docs/ASSET_DROPIN_CONTRACT.md §7 gains open item 6: the seven-clause realm-tier reservation

(entry 95), the presentation_tier_ref rail and id-plus-tier fallback rule (entry 94), the

two-name ratification presentation_tier_ref versus generation_tier (entry 96), the closed cue

parameter set (entry 100), the explicit generation_tier='realm' selector write (entry 105 clause

4), and the DECAY law carried from v1.3 entry 92. Reserve presentation_tier_ref as an OPAQUE key

and ratify its value domain separately, so the freeze does not wait on the entry-97 Josh brief.

§2's VFX row gains the tier and variant treatment in the same commit. NO registry touch in this

step.

2. docs/DESIGN_GAP_REGISTER.md — append REGISTER_V14_FOLD.md verbatim as the new §v1.4 section

after §v1.3. Then, IN PLACE in §v1.2: cells 1, 2, 11, 12, 13 to CLAIMED-RUN; cell 14a from

CLAIMED-RUN-in-part to CLAIMED-RUN; cell 14b and cell 24 gaining their recorded notes; the

non-combat-progression-viability and R-A16 aspect rows marked RUN; and the wave status board's

P1-C line moving RUNNING to RUN with a P1-program-complete line. Apply the entry-4 merge (the

positive/identity half from PC-16) and the entry-9, entry-22, entry-46, entry-53 and entry-73

amendment notes in the same commit. Leave every WIDEN-PENDING and OPEN row untouched. Update the

file's Status line to SYNTHESIS v1.4. NO registry touch.

3. docs/proposals/COMPARATOR_LENS_PROGRAM.md — correct the divergence guard's CVD anchor for the

minigame-completion promise (Layer 2 definition, not the cardinal-numerical section), and add the

two earned method rules: blank counts are computed separately from histograms, and a search that

DID match must be read. Zero-token. NO registry touch.

4. harness/apply_*_columns.py pattern — the region ambient-array populate (entry 104). REGISTRY

TOUCH: T0_Region_Index three array columns across 76 rows. Must key on layering_role, must use

the corrected 10-bed set for the slice region, and must refresh docs/fidelity_baseline.json via

--emit-baseline on registry_fidelity.py in the SAME commit. Deterministic, zero-model, no

authoring judgment — the correct first substantive landing.

5. docs/proposals/REALM_DESIGN_PROGRAM.md Wave-2 mint inputs, before the schema freezes: law_state

and exploit_tier on the metaphysical-laws sub-row (entry 132), the region_id soft-FK plus the

renderable-versus-law ownership split routed in from the killed HD-14 (entry 73 amendment), and

native_hostile_families plus reward_mix_class (entry 117). All are schema text in a

proposal-tier document — NO registry touch yet.

6. _source/01_Tier_1_Foundation/T1_Ability_Tree — the craft law under the existing ladder anchor

(entry 99), director-authored per adjudication 19, fresh critic before it lands. Living-source

edit to a T1 .md; gate-safe, NO registry touch.

7. _source/01_Tier_1_Foundation/T1_Audio_Spec — the two-page delegating authority stub (entry 102).

DIRECTOR-authored work order per adjudication 19, never fanned out. Add its docs/DOC_MAP.md row

in the same commit; a doc is not done until it is listed there. Closes entry 22's audio third.

8. docs/proposals/DIFFICULTY_SYSTEM.md — the defeat paragraph (entry 111) lands WITH the bounded-

persistence invariant (entry 110), never after it, or a tier-scoped bound gets read arc-wide. The

invariant's gate clause waits on the director call recorded as contested.

9. Engine lane, slice-scoped and in this order: the worldstate write at the death call site (entry

108), the attempt index on the payout BEFORE the natural-voice pass touches the 281 strings (entry

109), the retry anchor correction sequenced BEHIND entry 46's column repair (entry 113), and the

fired-clue exempt class with its unfiltered text store (entry 130).

10. harness/check_link_rewards.py plus its gates_config.json row (entry 128) — new gate, modelled

on the existing weave-lifecycle shape, FAIL on the 16 exposed rows and WARN-count on the blanks.

NO registry touch; it reads columns that already exist. Do NOT touch the 122 blanks — they are

the entry-129 Josh brief.

11. The gate-enum change (entry 120) rides a SINGLE commit with its scene-registry and schema edits,

per the never-write-a-gate-enrolled-file-mid-check rule. REGISTRY TOUCH: T0_Scene_Spec_Registry

value set; baseline refresh in the same commit. Entry 121's festival column is a second REGISTRY

TOUCH with the same rule.

12. Ledger entry for this sitting cites the fold's corrections block by name (the wave-spec CVD

anchor, the three histogram-to-blank corrections, the two control-count corrections) rather than

rewriting any earlier headline.

13. Archive: copy the eight P1-C files into docs/pipeline_review/lens_wave_2026-07-28/ alongside

the P1-B and realm-wave set, and confirm the docs/DOC_MAP.md row for that archive directory

covers them.

Registry-touch flags, consolidated: steps 4, 11 (twice) are the only registry writes in this

checklist, and every one of them refreshes docs/fidelity_baseline.json via --emit-baseline in the

same commit or the gates go red. Steps 5, 6, 7 and 8 edit living-source or proposal documents and are

gate-safe. Step 1 edits a contract document and is gate-safe. Nothing in this fold edits the frozen

_source/00 T0 xlsx.

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