arcodange-org/factory
1
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

docs(prd): cross-family verification rule + STATUS truth-pass (erp#56/#63/#39)

Browse Source 
- qa-strategy › Independent verification: with Mistral (vibe -p,
  mistral-medium-3.5) and Ornith 35B admitted to verifier duty by verdict
  parity (erp#63 evidence, blind-judged), the independent verifier SHOULD be
  a different model family than the builder; journal records which family
  verified what.
- STATUS: #63 ✅ (PR erp#69, harness home erp:fleet/harness/), #56 ✅
  (PR erp#68, authored by the Mistral builder bench), #39 built on local
  branch (push+PR = operator step), PR-log rows, P3 flipped to in-progress.

Paired with erp#69 (Closes erp#63).

Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01VRShc4QhLLU73FLHx9vskh
This commit is contained in:
arcodange
2026-07-18 20:21:55 +02:00
co-authored by Claude Fable 5
parent a4be009e3e
commit c55714d892
2 changed files with 9 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
vibe/PRD/ai-back-office/qa-strategy.md
+2
View File
@@ -58,6 +58,8 @@ Per atom, mechanical, recorded in the registry ([ladder](README.md#the-autonomy-
Work is never attested by the session that produced it. **Milestone closures** ([closure protocol](STATUS.md#closure-protocol--per-milestone)), **POC exit gates**, and **autonomy promotions** are verified by a *context-free subagent prompted to refute* ("find why this is NOT done / NOT at the bar"), whose only inputs are the repo, the issues, and the run journals — never the author's conversation. A refutation the author cannot resolve with evidence blocks the gate; the verifier's verdict is attached to the artifact it gates (milestone, registry autonomy field, POC record). This extends to the process level the principle the pipelines already run at the data level (dual independent extraction, seeded-wrong fixtures that must FAIL) and that the PRD itself was built with (fresh-reader review before first publication).
**Cross-family verification.** The harness runs on more than one model family ([model-fleet › harness portability](model-fleet.md#harness-portability)); a runtime is admitted to verifier duty by verdict parity with the Claude baseline on the two canonical verifier tests (locate-test + cold-reader backlog audit — [erp#63](https://gitea.arcodange.lab/arcodange-org/erp/issues/63), harness home `erp:fleet/harness/`). Once at least one non-Claude verifier is admitted, **the independent verifier SHOULD be a different model family than the builder** — a foreign family refuting the builder is stronger evidence than the builder's family agreeing with itself. Same-family verification stays acceptable when no admitted cross-family verifier fits the role, and the run journal records which family verified what.
## Evidence trail
Every month yields an audit pack: the coherence audit ([T15](task-inventory.md#t15--monthly-coherence-audit)), the month's run journals, snapshot content-hashes, approval-card decisions, and fiscal sheets — archived in git + GED. This pack is deliberately shaped as the documented-control set of the **piste d'audit fiable** (CGI art. 289 VII — [compliance](compliance.md#obligations--fleet-mechanisms)): the invoice ↔ service ↔ payment linkage is evidenced continuously, not reconstructed under audit. The pack is written for a third party (expert-comptable, auditor, or a future operator): it must let them reconstruct *what the fleet did and why* without access to this PRD or any chat history. A distilled summary of each pack also lands in the second brain ([T17](task-inventory.md#t17--knowledge-capture--retrieval-second-brain)), so institutional memory outlives both chat logs and this repo.