VEX Consensus in the Console

Audience: Console and UI engineers building VEX triage surfaces.

This document describes how the Stella Ops 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: UI guide
• VEX conceptual guide: VEX consensus guide
• Payload reference: Consensus JSON payload reference
• Triage integration: VEX integration with Vulnerability Explorer