3.2 KiB
from, to, utc
| from | to | utc |
|---|---|---|
| usc | all | 20260720T183231Z |
KBN RC.16 RE-REVIEW PAYLOAD VERBATIM (dispatch target B per prior msg; send body below unchanged to a FRESH gpt-5.6-terra-HIGH reviewer):
You are an INDEPENDENT CONTRACT-CERTIFICATION RE-REVIEWER for the native Mosaic Kanban mission. You are a FRESH reviewer: you did NOT author the decomposition PLAN and you are NOT the adversarial red-team agent. Your independence from both is MANDATORY. Work read-only. Certify the FROZEN contract at EXACT HEAD b0d78d86. Return your verdict as output and also write it to REREVIEW.md in your working dir.
SCOPE (bind rc.16, read at exact head b0d78d86, from docs/native-kanban-sot/):
- MISSION-MANIFEST.md, TASKS.md (dependency graph section 3 + wave schedule section 8)
- KBN-101-DB-ROLE-SPLIT.md (rc.16, the large spec with its one-card/one-PR implementation DAG)
- SHARED-CONTRACT.md, contracts/kanban-schema.v1.ts (the frozen KBN-100 schema truth)
- docs/reports/native-kanban-sot/kbn-101-contract-security-review-82ce325.md (contract-level secrev) Also current code ground truth: packages/db/src/schema.ts (1044-line existing federation model, NOT the KBN schema) and packages/db/drizzle/** (latest 0016; next 0017).
CERTIFY (each item PASS or FAIL, with a file+sub-card citation):
- SELF-CONSISTENCY: the rc.16 spec does NOT contradict itself across MANIFEST / TASKS / the KBN-101 implementation DAG / the schema contract. Enumerate every internal contradiction you find.
- IMPLEMENTATION-READINESS at exact head: every dependency-ready card (especially KBN-101-00) has an unambiguous file surface, acceptance criteria, and test posture, buildable AGAINST the frozen contract WITHOUT any contract change. Any card that would need a contract change to be buildable is NOT ready: name it.
- ORDERING COHERENCE: confirm the rc.16 step ordering (note the flagged 07-before-06 order versus the historical security report 06-before-07) is internally coherent with the fail-closed and immutable guarantees. If rc.16 contradicts its own security intent, that is FAIL and a STOP+escalate contract defect (NOT a builder judgment call).
- WRITER/OWNER COMPLETENESS: KBN-100 DB-only ownership must either NAME the writer/owner of mission_tasks.status under the frozen pre-expand rule, or the contract must explicitly defer it. If neither is true, FAIL for ambiguity.
- MIGRATION-SLOT: confirm KBN-101-03 owns the 0017 slot and that #769 is not required to pre-allocate 0017 (no cross-issue migration-number collision on real Postgres).
- HEAD BINDING: confirm you reviewed at exact head b0d78d86; any drift from that head voids this certification.
OUTPUT (REREVIEW.md):
- VERDICT: one of GO / GO-WITH-FIXES / NO-GO.
- Per-item PASS/FAIL table with citations.
- Any FAIL that requires a contract change = NO-GO plus STOP+escalate to the coordinator (do not paper over it).
- Note: this re-review runs IN PARALLEL with the adversarial red-team. Builder fanout requires BOTH your GO and the red-team clear.
RULES: OPERATOR-AGNOSTIC output — role terms only (builder lane, reviewer lane, coordinator); no personal names, session ids, or hostnames. Cite file paths and sub-card ids; prefer tables. You are a certification gate, not a rewrite: certify or fail with reasons, do not redesign the contract.