Policy Engine Vulnerability Data Pipeline
Source-verified against commit
2021a48f6e(2026-10-05). Re-verify the named source contracts before applying this description to an installation. Re-verify:git show HEAD:src/Vulnerabilities/__Libraries/StellaOps.Vulnerabilities.Consensus/ConsensusEvaluator.cs.
Policy consumes vulnerability statements from the Vulnerabilities hub through owner APIs. It owns a tenant projection used during release evaluation. Findings owns the operator decisions mirrored into that projection.
Current data flow
Hub statements and provenance -> shared consensus evaluator -> Policy gate projection
Findings tenant decisions ------> retained overlay feed -----^
Release components and scan detail -> Policy findings lookup -> promotion evaluation
Policy effective-status API -------------------------------> Findings display
The projection consumes consensus.changed events and seeds from the hub’s consensus-inputs corpus section. Each issue is evaluated with issuer tiers and the tenant’s live overlays. Distro applicability is retained in release-scoped projection rows.
PostgresFindingsLookup reads Policy’s projection during release evaluation. A projection that cannot answer is handled by the configured unavailable-source policy. A tenant decision reaches the gate only after the overlay consumer applies it.
Ownership and limits
- Vulnerabilities owns global statements, provenance, corpus publication and its event stream.
- Findings owns tenant decisions and publishes their overlay states transactionally.
- Policy owns the materialized gate projection and effective-status read.
- Release Orchestrator owns promotion authorization and release evidence.
- Scanner’s hub-backed matching evaluates statements for the scanned image’s release.
The retired Concelier, Excititor and VexLens services are not hops in this pipeline. PCR weights, calibration manifests and confidence-threshold VEX gates do not decide the current consensus. Reachability and other promotion gates retain their separate contracts.
See Policy architecture, Findings overlay feed, promotion ownership and consensus operations.
The earlier design is frozen history. It does not describe the current runtime.