Repository navigation
Description
The November19 readiness audit of PR #214 identifies the remaining integration boundary before another scientific calibration. The new typed adjudication contract does not itself create a runnable science package. Historical round03 has no new scientific-invocation envelopes; the November17 prerequisite package explicitly has engineering_prerequisites purpose and null scientific invocations. Neither can be retrospectively promoted into a positive #209 replay.
Required work, after evidence sufficiency review:
- Register a new science package and round ID, instantiate neutral JSON instruction templates and per-phase plans, and pin complete runtime/proof helpers. The prerequisite builder currently hardcodes the engineering purpose; old prompts contain historical literal paths and cannot be reused unchanged.
- Register reviewer IDs
reviewer-aandreviewer-b, distinct fresh roots and distinct repository-relative artifact namespaces explicitly, as required by pair/finalizer accounting and unchanged-path collection into the adjudicator. Old round03 reused.temp/round03-reviewer/in both clones; distinct absolute roots alone do not prevent collection collisions. Build authoring, citation and finalizer configurations against the original scientific manifest, retaining the separate adjudication launch manifest. - Independently check source views, definition omissions, counterevidence and all remaining semantic dependencies against the unchanged gates. No labels may be predicted or manufactured to justify a launch.
- Pass actual same-clone production save/readback in the new reviewer environments before scientific use. Collect post-exit observed identities, native logs, complete readiness lineage and original relative file layouts before freezing the later phase.
- Replay both new bound original sessions with Reject scientific adjudication invocations without bound initial matrices and seals #209 before adjudication. Preserve the 20 initial canonical pairs plus separately sealed/proof-validated final drafts, under the policy repaired in Align adjudication instructions with the registered canonical-persistence policy #219.
Evidence boundaries remain separate: first01 result convention; first30 original GTDB identity; fresh04 bin weights and cell lineage; fresh05 mixed-row cell lineage; fresh32 exact process-generation version; fresh47 original LPSN authority. The bounded first43/first28/fresh14 source replays do not automatically resolve these or their own remaining historical/semantic limits. New fresh05 public body-text extraction is not yet admitted by the existing abstract/JATS proof adapter; retain it as inspected access evidence, not canonical paper proof. Retrieve supported original bytes or separately review and canary a new extractor before using that extraction in scientific scoring.
Acceptance: a separately identified, exposure-reviewed and fully bound science package with concrete templates/configs and successful fresh-environment canaries, followed by complete #209 real-artifact replay. Historical failures remain unchanged. Remaining90 and expansion stay gated. This is a pending integration/evidence task, not permission to bypass evidence gates or launch now.
Activity