Requirements Traceability

The normative rules are in SPEC.md. The supporting oaa-1.0.yaml catalog assigns stable requirement IDs; traceability.md maps them to rules and fixtures. The 0.1 catalog remains unchanged for historical use.

Automated rules cover archive/content conditions and explicitly classified processing outcomes. Processing findings (unsupported version, configured capacity, unavailable input) are not archive-invalidity findings. Reader, writer, privacy, and other behavior that cannot be inferred from an archive is tracked separately, with evidence in the release verification scope.

The tests require every automated requirement to have rule and expected-finding fixture coverage, and every finding to reference known requirement IDs. Fixture coverage does not prove another application’s implementation behavior.

Regenerate and check the matrix from a checkout of the validator repository:

python requirements/generate_traceability.py
python requirements/generate_traceability.py --check