git.stella-ops.org/docs/dev/normalized_versions_rollout.md

Normalized Versions Rollout Dashboard (Sprint 2 – Feedser)

Status date: 2025-10-12 17:05 UTC

This dashboard tracks connector readiness for emitting AffectedPackage.NormalizedVersions arrays and highlights upcoming coordination checkpoints. Use it alongside:

• src/StellaOps.Feedser.Merge/RANGE_PRIMITIVES_COORDINATION.md for detailed guidance and timelines.
• Feedser SemVer Merge Playbook §8 for persisted Mongo document shapes.
• Normalized Versions Query Guide for index/query validation steps.

Key milestones

• 2025-10-13 – Normalization to finalize SemVerRangeRuleBuilder API contract for review.
• 2025-10-17 – Connector owners to post fixture PRs showing NormalizedVersions arrays (even if feature-flagged).
• 2025-10-18 – Merge cross-connector review to validate consistent field usage before enabling union logic.

Connector readiness matrix

Connector	Owner team	Normalized versions status	Last update	Next action / link
Acsc	BE-Conn-ACSC	❌ Not started – mapper pending	2025-10-11	Design DTOs + mapper with normalized rule array; see src/StellaOps.Feedser.Source.Acsc/TASKS.md.
Cccs	BE-Conn-CCCS	❌ Not started – mapper pending	2025-10-11	Add normalized SemVer array in canonical mapper; coordinate fixtures per TASKS.md.
CertBund	BE-Conn-CERTBUND	❌ Not started – mapper pending	2025-10-11	Capture firmware-style ranges; emit normalized payload; src/StellaOps.Feedser.Source.CertBund/TASKS.md.
CertCc	BE-Conn-CERTCC	⚠️ In progress – fetch pipeline DOING	2025-10-11	Implement VINCE mapper with SemVer/NEVRA rules; unblock snapshot regeneration; src/StellaOps.Feedser.Source.CertCc/TASKS.md.
Kev	BE-Conn-KEV	✅ Normalized catalog/due-date rules verified	2025-10-12	Fixtures reconfirmed via dotnet test src/StellaOps.Feedser.Source.Kev.Tests; src/StellaOps.Feedser.Source.Kev/TASKS.md.
Cve	BE-Conn-CVE	✅ Normalized SemVer rules verified	2025-10-12	Snapshot parity green (dotnet test src/StellaOps.Feedser.Source.Cve.Tests); src/StellaOps.Feedser.Source.Cve/TASKS.md.
Ghsa	BE-Conn-GHSA	⚠️ DOING – normalized rollout task active	2025-10-11 18:45 UTC	Wire SemVerRangeRuleBuilder + refresh fixtures; src/StellaOps.Feedser.Source.Ghsa/TASKS.md.
Osv	BE-Conn-OSV	✅ SemVer mapper & parity fixtures verified	2025-10-12	GHSA parity regression passing (dotnet test src/StellaOps.Feedser.Source.Osv.Tests); src/StellaOps.Feedser.Source.Osv/TASKS.md.
Ics.Cisa	BE-Conn-ICS-CISA	❌ Not started – mapper TODO	2025-10-11	Plan SemVer/firmware scheme selection; src/StellaOps.Feedser.Source.Ics.Cisa/TASKS.md.
Kisa	BE-Conn-KISA	❌ Not started – mapper TODO	2025-10-11	Localisation-aware mapper with normalized rules; src/StellaOps.Feedser.Source.Kisa/TASKS.md.
Ru.Bdu	BE-Conn-BDU	❌ Not started – mapper TODO	2025-10-11	Emit normalized ranges, capture provenance; src/StellaOps.Feedser.Source.Ru.Bdu/TASKS.md.
Ru.Nkcki	BE-Conn-Nkcki	❌ Not started – mapper TODO	2025-10-11	Similar to BDU; ensure Cyrillic provenance preserved; src/StellaOps.Feedser.Source.Ru.Nkcki/TASKS.md.
Vndr.Apple	BE-Conn-Apple	✅ Shipped – emitting normalized arrays	2025-10-11	Continue fixture/tooling work; src/StellaOps.Feedser.Source.Vndr.Apple/TASKS.md.
Vndr.Cisco	BE-Conn-Cisco	❌ Not started – mapper TODO	2025-10-11	Decide on scheme (semver vs custom) before emitting rules; src/StellaOps.Feedser.Source.Vndr.Cisco/TASKS.md.
Vndr.Msrc	BE-Conn-MSRC	❌ Not started – mapper TODO	2025-10-11	Gather samples, define scheme, emit normalized rules; src/StellaOps.Feedser.Source.Vndr.Msrc/TASKS.md.
Nvd	BE-Conn-NVD	⚠️ Needs follow-up – mapper complete but normalized array MR pending	2025-10-11	Align CVE notes + normalized payload flag; src/StellaOps.Feedser.Source.Nvd/TASKS.md.

Legend: ✅ complete, ⚠️ in progress/partial, ❌ not started.

Monitoring

• Merge now emits feedser.merge.normalized_rules (tags: package_type, scheme) and feedser.merge.normalized_rules_missing (tags: package_type). Track these counters to confirm normalized arrays land as connectors roll out.
• Expect normalized_rules_missing to trend toward zero as each connector flips on normalized output. Investigate any sustained counts by checking the corresponding module TASKS.md.

How to use this dashboard

1. Before opening a connector PR, update the module TASKS.md entry and drop a short bullet here (status + timestamp).
2. When a connector lands normalized outputs, flip the status to ✅ and note any rollout toggles (feature flags, fixture regenerations).
3. If a dependency or blocker emerges, add it both in the module TASKS.md and in this matrix so merge/storage can escalate quickly.