3.3 KiB
Current checker protocol — repair22
Source preparation, NOT RUN. ORDER_AUDIT.md and order-audit.json are the single current seven-domain table. REPAIR17–21 remain untouched historical records; their current-status and B1 power-credit claims are superseded.
The registry remains exactly15 conditions + EV. No accepted originals, counts, CurrentAlphaScope, three safety outcomes or30/88 denominator change. Original 13/88 gains no credit. P04 main9b stays frozen; no integration is claimed.
C's NATIVE_RUNS / native_ownership / verify_native block is unchanged. C25 and all existing fixture cases remain. R's verify_shift_completion derives three distinct process IDs from the existing raw start/process/end joins, with all end flags, exit0 and complete SHA checks retained. The one1080 SALE joins the original serviceID and priceSnapshot via service.payment., actual receipt entries and idempotency transaction ID; no fixed PID or ledger number.
S1 uses the full existing writer--observations Variant data in B/p04-s1-native-r02. The pre-travel ACTIVE reservation, requester/task, assigned staff and original staff_cell join the later boarded task and trip. Reserve exhaustion is measured before the normal tick, and depleted raw must show mana0 and the actual elevator unpowered. JSON summaries do not replace typed raw.
S3 B1 remains a combined dependency/closure diagnostic. Its actual interruption reason is RELATED_FACILITY_INACTIVE. It supplies no power_stop evidence and no priority approval. The strict power-vs-closure order is D05 pending/unknown.
Only S4 supplies power_stop. The new verifier requires source-pinned native ownership, complete product1338 + sole QA override, three whole4-member formal packages per process, separate Writer/Reader, exact Runtime typed restoration and full typed replay. Actual NO_POWER, operating dependency, powered/ACTIVE kitchen, positive mana and open operator are mandatory. Raw graph edges and revision prove the isolated consumer and exact reconnect; source-derived evaluation/hold determines recovery. Duration−1, zero stopped charges, original service/reservation identity, one SALE and unchanged replay are joined from raw. Every intervening held minute is retained and checked. No normalization or dropped Runtime fields is allowed. S4 is pending Root execution, not accepted.
checker_join_fixtures retains every previous case and adds rejection controls for B1 masquerading as power, dependency false, kitchen unpowered, closure, pre-travel mismatch, absent outage, wrong PID and transaction join. Consistently renamed dynamic PID/transaction/service IDs are positive controls. These fixtures have NOT RUN. They require actual S4 raw for the S4 positive control.
The fresh R collection is B/audit-support/p04-raw-collect-r22. It re-reads existing C/S1/S2a/S2b/S3 without native reruns and newly collected S4; no result scalar is authority. It binds the current verifier hash. The old r17/r20 collection and 21615-check proof remain immutable. New checker bytes differ; no1339 identity claim. Missing raw, changed pins, mandatory undefined rules or unsupported joins must fail. Final index/applicability, registered validation, support53cb registered rebind, independent review, normal integration and individual nativeWindows obligations remain Root work. No final acceptance is asserted.