confidence-check

Validation checks duplicate work, architecture alignment, official documentation, working OSS references, and root causes using a weighted 5-check algorithm. Scores ≥90% proceed, 70-89% clarify concerns, below 70% stop and reassess to prevent wrong-direction effort.

Architecture checks evaluate whether your proposed change aligns with existing system design patterns and constraints. This 25%-weighted check prevents decisions that conflict with established technical direction and increases implementation confidence.

Yes, the 5-check framework applies across software projects from baseline through refactor phases. It guides decision-making on any feature by requiring evidence across duplicates, architecture, docs, OSS patterns, and root-cause analysis before proceeding.

Anti-rationalization guidance enforces the threshold-driven scoring system objectively. The algorithm requires all five checks to reach confidence thresholds—no override flags bypass the validation gates, ensuring consistent rigor regardless of pressure.

Duplicate verification and architecture each count 25%, official docs 20%, working OSS references 15%, and root-cause analysis 15%. This weighting balances existing work awareness with design fit, documentation grounding, and proven patterns to produce a deterministic confidence score.

Scores between 70-89% signal clarify mode: the change shows promise but gaps remain. Use this threshold when you need to address specific concerns through documentation, stakeholder review, or design iteration before committing to implementation.