- Implemented comprehensive tests for verdict artifact generation to ensure deterministic outputs across various scenarios, including identical inputs, parallel execution, and change ordering. - Created helper methods for generating sample verdict inputs and computing canonical hashes. - Added tests to validate the stability of canonical hashes, proof spine ordering, and summary statistics. - Introduced a new PowerShell script to update SHA256 sums for files, ensuring accurate hash generation and file integrity checks.
916 B
916 B
VEX Consensus in the Console
This document describes how the Console should surface VEX evidence and consensus to keep triage explainable.
What the Console Should Show
- Effective VEX status (
affected,not_affected,under_investigation,fixed) with confidence/tier label. - Provenance for each source statement: issuer identity, signature verification state, timestamps, and digests.
- Conflicts as first-class facts (what disagrees, at what trust tier), not hidden UI logic.
- Snapshot identity and staleness budgets when operating against Offline Kit snapshots.
Evidence Linking
Every displayed fact should link back to:
- The raw VEX observation(s)
- Linkset correlation view (what was grouped and why)
- The policy explanation that consumed the evidence (when shown in triage)
References
- Operator guide:
docs/15_UI_GUIDE.md - VEX conceptual guide:
docs/16_VEX_CONSENSUS_GUIDE.md