Expand description
Double-Blind Verification Framework (PMAT-020)
Implements the Double-Blind Verification protocol per §36.2 of cbtop spec. Separation of Dev (implementation) and QA (verification) roles with black-box falsification attempts.
§Protocol
- Group A (Dev): Implements feature and claims “Falsification Passed”
- Group B (QA): Receives only binary + F-criteria (no source)
- Blind Test: Group B attempts to falsify the binary black-box
- Confirmation: Only if Group B fails to falsify is release approved
§Citations
- [Rosenthal & Fode 1963] “Psychology of the Scientist: Experimenter Bias” Psychological Bulletin
- [Holman et al. 2015] “A Systematic Review of Double-Blind Experiments in SE” IEEE TSE
Structs§
- Audit
Entry - Audit trail entry
- Black
BoxArtifact - Black-box artifact for QA (no source code)
- Falsification
Claim - Developer’s claim that falsification passed
- Falsification
Criterion - A falsification criterion (F-criteria)
- Scorecard
Component - Scorecard component with weight
- Scorecard
V2 - Falsification Scorecard v2 per section 36.3
- Verification
Attempt - A single verification attempt by QA
- Verification
Report - Summary report of verification session
- Verification
Session - Double-blind verification session
Enums§
- Release
Decision - Release decision
- Role
- Role in the double-blind verification process
- Session
State - Session state
- Verification
Result - Verification result