KB-494E

C1 Staging Codex R4 — P6 Independent Verification Review

2 min read Revision 1
c1stagingcodex-r4read-only2026-06-23

04 — P6 INDEPENDENT VERIFICATION REVIEW

Checks present and accepted

P6 independently checks:

  • count=3, no unexpected code, no missing code;
  • all three rows validated;
  • non-empty title, valid group, array/non-empty input-output-mode fields;
  • allowed-mode membership;
  • exactly nine P5 rows, accepted=0;
  • its own nine-case oracle, joined_n=9, indep_pass=9, pass_disagree=0;
  • case 8 rejected with SQLSTATE 42P01;
  • zero unregistered public tables/functions/triggers.

This closes the R3 count-only/wrong-set and stored-pass false-PASS paths.

Blocking gaps

Current-run stamp binding

Actual code:

SELECT EXISTS(... WHERE op='c1_vocab_build') INTO p3;
...
WHERE l.op IN (...)
  AND l.sandbox_id NOT IN (SELECT sandbox_id FROM sbx_meta.birth_certificate);

This is not equality with the current sandbox/run. birth_certificate has only a primary key on sandbox_id, not a singleton constraint. An additional birth row makes a foreign stamp acceptable.

P4 evidence proof

P6 includes evidence::text in the digest but never gates on evidence->'verify'. A row can remain correctly shaped and validated while its P4 evidence is {} or inconsistent; P6 will hash that value and PASS.

Verdict

Exact canonical and P5 fact verification: safe. Full P4 evidence and current-run DOT-stamp verification: unsafe/incomplete.

Back to Knowledge Hub knowledge/dev/laws-new/reports/c1-staging-codex-r4-final-review-before-dry-run/04-p6-independent-verification-review.md