Independent QC: Separate Implementation from Verification
When implementation and review happen inside the same runtime and context, the review can inherit the same assumptions and omissions as the implementation. Netsujo separates the implementation runtime from the QC runtime and checks the same exact target from a fresh context.
Independent QC is a Netsujo operating term. It does not refer to a specific industry certification or external standard.
Two runtimes with different responsibilities
- Implementation runtime
- Changes code, adds tests, fixes defects, and updates the pull request. It can explain its own work, but that explanation is not independent acceptance evidence.
- QC runtime
- Reads the target version and its evidence from a separate context, with read-only verification preferred wherever possible.
Four acceptance conditions
- The QC target identifier matches the implementation acceptance target: commit SHA, immutable artifact digest or ID, deployment ID, or another exact identifier.
- The QC runtime and context are independent from the implementation runtime.
- The reviewer reads checkable evidence such as the diff, CI result, logs, or production readback rather than relying only on a report that says tests passed.
- When the target HEAD changes after review, the previous PASS is not silently reused for the new version.
Fix the Exact HEAD
A pull request number does not uniquely identify the code under review. Netsujo fixes the HEAD SHA at review time and binds CI and review evidence to that SHA. A later fix commit creates a new target that must satisfy the acceptance conditions again.
Field note: exact-SHA verification
CI, Independent QC, and production acceptance have different jobs
| Layer | What it proves | What it does not prove by itself |
|---|---|---|
| CI | Defined automated checks passed for a particular target | That design, operating boundaries, or production behavior are correct |
| Independent QC | A separate runtime and context accepted the target and evidence | That it has deployment or publication authority |
| Production acceptance | The deployed system is serving and behaving as observed | That CI or independent QC can be skipped |
Field note: role-separated development with ChatGPT, Claude Code, and Codex