Concrete checks for the requirement.
Actor names referenced by this requirement.
Business concepts referenced by this requirement.
Stable requirement id.
Requirement category.
Whether downstream phases must implement, ask, exclude, or treat as default.
Product priority within the SRS.
OptionalsectionRendered-section locator when the requirement came from a generated section.
Evidence and generated locations supporting this requirement.
Single atomic requirement statement.
Requirement lifecycle status.
How this requirement is supported.
Short business title.
Verification method best suited for this requirement.
Atomic SRS requirement used as analyze's machine-readable contract registry.
Final markdown remains the human-readable document, but downstream phases should prefer this registry when deciding which analyzed requirements are implementation contracts.