Tony_tech/veripath
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify evidence tier authority and proof-of-concept approval gate

Browse Source
This commit is contained in:
Leonard
2026-07-24 04:37:16 +00:00
parent 63ae28c7ed
commit 15812d2b04
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/architecture/architectural-principles.md
+6
View File
@@ -45,3 +45,9 @@ Verified defects may be presented as confirmed issues when supported by concrete
Indicative risks must be presented as directional evidence, not proven customer loss. Indicative risks must be presented as directional evidence, not proven customer loss.
This distinction protects client trust, prevents overclaiming, and keeps reports credible. This distinction protects client trust, prevents overclaiming, and keeps reports credible.
Agents may propose evidence classifications, but humans approve final evidence tiers before client-facing use during Version 1.
Ambiguous findings default to Indicative Evidence unless upgraded by human review.
Rejected Verified Evidence classifications default to Indicative Evidence unless the reviewer discards the finding or requests additional evidence.