Skip to content

Change-risk hotspots in core loading and mapping modules #1140

@ahouseholder

Description

@ahouseholder

Summary

Several modules are identified as high-churn hotspots whose modification affects nearly all runtime loading, mapping generation, or documentation/data generation: the package initializer, registry mixins, decision-table base, topological sort, and the docs/data pipeline. Changes to any of these areas carry outsized regression risk.

Category

  • Top risk
  • Technical debt
  • Security
  • Performance / scaling
  • Fragile / high-churn area
  • Other

Severity

medium

Evidence

  • src/ssvc/__init__.py
  • src/ssvc/registry/
  • src/ssvc/_mixins.py
  • src/ssvc/decision_tables/base.py
  • src/ssvc/utils/toposort.py
  • src/ssvc/doctools.py
  • mkdocs.yml
  • metadata/specs/

Impact if Ignored

Without explicit awareness of these hotspots, contributors may make changes that inadvertently break runtime loading, mapping semantics, or documentation generation with no immediate visible failure.

Suggested Action

Add targeted integration tests or regression guards for each hotspot. Document which modules are high-churn in CONTRIBUTING.md. Consider enforcing broader test coverage thresholds on these specific files in CI.

Metadata

Metadata

Assignees

No one assigned

    Labels

    concernTechnical risk, debt, or fragile areagroup:unscheduledNot yet scheduled in PRIORITIES.md
    No fields configured for Concern.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions