Package-level declarations
Types
Runs even when the element has no Requirements work product.
Requirements registration of the shared string-value check.
HIGH: Each entry of Requirement.allocatedTo must be a direct child of the requirement's subject (element), expressing "this requirement, which is about the subject, is realised by the following sub-elements of it." A requirement cannot allocate outside its own subject.
HIGH: Requirement shall be allocated to an element.
HIGH: ASIL of a requirement shall be >= max(ASIL of all parent requirements).
HIGH: Requirements shall fit their subject element's ASIL and agree with its declared allocatedAsil.
INFO on a derived requirement above every classified parent requirement.
HIGH: A requirement cannot derive from a parent requirement that does not actually allocate to this requirement's subject. For each parent in r.derivedFrom, if parent.allocatedTo is non-empty, then r.element (the subject) must appear in parent.allocatedTo.
MODERATE: Requirement text shall contain a recognized normative modal.
Review actual inventory requirements, including declarations without their required container. Individual findings cite direct evidence; RequirementSetSemanticRule carries the shared comparison inventory instead of duplicating it for every requirement and semantic rule.
One review obligation per root Requirements document. Every loaded requirement remains comparison evidence: the reviewer uses actual hierarchy and overlapping applicability, not filenames or equal coarse level numbers. This preserves cross-container and cross-element comparisons.
MODERATE: Requirement description shall mention the element name (subject) before the modal.