Clarify evidence tier authority and proof-of-concept approval gate
This commit is contained in:
@@ -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.
|
||||
|
||||
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.
|
||||
Reference in New Issue
Block a user