Finding Reconciliation Board¶
Reconciliation workflow — instantiates Parallel Independent Inspection Design
The post-discovery workflow that deduplicates, adjudicates, severity-triages, and routes independent findings while keeping minority signals alive until resolved.
The Finding Reconciliation Board is the post-discovery engine. It discovers nothing itself; it takes the raw findings that independent inspectors have already produced and runs them through a structured workflow — deduplicate identical findings, adjudicate disagreements, triage by severity, route each item to fix, accept-as-residual-risk, or reject, verify that a fix actually closed its finding, and, crucially, keep a lone minority finding alive until it is explicitly resolved rather than dropped for lack of a second voter. Its defining idea is that it is a workflow over a many-source finding set in which unanimity is treated as suspicious rather than as the only evidence that counts.
Example¶
A notified body has three independent assessors review a new infusion-pump submission — one on electrical safety, one on embedded software, one on clinical evidence — each producing a findings list. The reconciliation board convenes afterward. It merges the two assessors who both flagged the same alarm-latency issue into one finding (deduplication). It adjudicates a disagreement where the software assessor rates a logging gap "major" and the clinical assessor rates it "minor," holding it at major pending the manufacturer's response (severity triage). And it refuses to drop the electrical assessor's lone concern about a capacitor's derating just because no one else raised it — the concern is logged, routed to the manufacturer, and closed only once a test report verifies the change (minority preservation and fix verification). The board's product is a single reconciled finding register with dispositions and a residual-risk statement, not any new finding of its own.
How it works¶
Findings arrive from every pass on a common schema. The board deduplicates by location and type, adjudicates disagreements under a defined authority and rule, and triages severity against a release threshold. Each surviving finding is routed to fix, accept, or reject; routed fixes are verified to have closed the finding; and defects that escaped the inspection feed back into the register and the inspection design. A standing minority-preservation rule guarantees that a single-reviewer finding gets a disposition, never a silent deletion.
Tuning parameters¶
- Adjudication authority — a single chair, a panel, or a vote; concentrated authority is fast but bias-prone, distributed authority is slower but more robust.
- Release-hold severity threshold — how severe a finding must be to block release; strict thresholds catch more but stall more.
- Minority-preservation strictness — how much corroboration a finding needs before it can be closed as noise; stricter keeps rare-but-real findings alive longer at the cost of a fatter queue.
- Closure-verification depth — how thoroughly a claimed fix is re-checked before the finding is closed.
- Escape-feedback loop — whether and how escaped defects revise the inspection design, not just the register.
When it helps, and when it misleads¶
Its strength is turning a pile of scattered independent findings into one actionable register without erasing corroboration or quietly deleting the minority.
Its characteristic failure is false confidence from unanimity: a board that closes anything all reviewers agreed on and drops anything only one reviewer raised will systematically bury the rare-but-real. Perfect agreement among reviewers who share training is often evidence of a shared blind spot, not of correctness — the paradox that too-unanimous a result should lower, not raise, confidence.[n1] The guarding discipline is to enforce the minority rule and require an explicit disposition — fixed, accepted, or rejected with reason — for every finding, so silence is never a resolution.
How it implements the components¶
reconciliation_and_adjudication_loop— its core: deduplicate, adjudicate disagreements, triage severity, and route each finding.minority_signal_preservation_rule— a lone finding always earns a disposition and never a silent drop; unanimity is not the bar for keeping a concern alive.fix_verification_and_escape_feedback— each routed fix is verified to have closed its finding, and defects that escaped feed back into both the register and the inspection design.
The board runs no inspection passes and plans no coverage, so it does not implement independence_protocol or overlap_coverage_plan — that independent discovery is done upstream by Dual or Triple Diagnostic Read and Parallel Code Review Round. Its fix-verification acts on a single artifact's findings, unlike the physical-unit rework loop of Multi-Inspector Manufacturing Sort.
Related¶
- Instantiates: Parallel Independent Inspection Design — the reconciliation layer that turns separate discoveries into a corrected artifact and a residual-risk record.
- Consumes: the discovery mechanisms whose findings it reconciles — Dual or Triple Diagnostic Read, Parallel Code Review Round, Independent Security Review Lenses, Blind Document Proofing Passes.
- Sibling mechanisms: Capture-Recapture Defect Estimation · Independent Checklist Variant Rounds · Multi-Inspector Manufacturing Sort · Overlap Heatmap · Seeded Defect Calibration Exercise
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: For each independent finding, the mechanism makes bounded duplicate, validity, severity, and routing dispositions while preserving unresolved minority signals.
Nearest alternative: Protocol, Workflow & Routine — Findings pass through a reconciliation workflow, but the defining outputs are their case-specific adjudications and routes.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Accounting & Auditing
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Reconciling independent findings while preserving an audit trail has a strong lineage in audit and assurance practice.
Related originating lineages:
- Engineering & Design — Independent verification, severity triage, and defect disposition materially shape safety and quality boards.
- Medicine & Healthcare — Clinical review boards provide a professional model for multidisciplinary finding adjudication.
- Organizational & Management Science — Cross-functional review boards supply the institutional adjudication and routing format.
Review resolution: Both reviewers agree that accounting_auditing is primary. I retain engineering_design, organizational_management, medicine_healthcare only as formative origin lineage(s), without treating every later application as an origin. cross_disciplinary_synthesis is appropriate because the exact artifact combines contributions from multiple professional lineages. Reach is multi_domain as a separate applicability judgment: it does not widen or narrow the recorded provenance. Encyclopedia synthesis is true because the exact generalized artifact is an encyclopedia-authored combination or refinement. The secondary differences are reconciled with no unresolved primary-provenance ambiguity.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] The paradox of unanimity is the observation that beyond a point, more perfect agreement among independent judges reduces confidence, because it more likely reflects a shared bias or process failure than genuinely convergent evidence. It is the formal reason a reconciliation board must protect minority findings rather than reward consensus. ↩