Requirement
Maintain stable requirement identity, immutable revisions, acceptance criteria, outbound revision-pinned trace links and derived revision-set views.
Bundle → Layer → Finding → Questions Filled
3 bundles · 3 layers · 5 findings · 10 questions
Identity and revisions Which requirement and which version.
Stable identity
One identifier across all revisions.
Requirement identity
The identifier and owner of the requirement.
- What is the requirement's stable identifier, and who owns it?
- Which specification or baseline does it belong to?
Revision
Immutable revisions with their change reasons.
- Which revision is current, and what changed from the previous one?
- Who approved the revision, and when?
Content What is required and how it is accepted.
Statement and criteria
The requirement text and its acceptance criteria.
Statement quality
The text is necessary, unambiguous and verifiable.
- Is the statement singular, unambiguous and verifiable?
- Which type is it, such as functional, performance or constraint?
Acceptance criteria
How satisfaction is judged.
- Which acceptance criteria define when the requirement is met?
- Which verification method is planned: test, analysis, inspection or demonstration?
Traceability Where it comes from and what meets it.
Trace links
Revision-pinned links to sources, designs and tests.
Upstream and downstream
Links to stakeholder needs, design elements and verification.
- Which need, regulation or parent requirement does it derive from?
- Which design elements and tests are linked, and to which revision?
Classifiers Filled
- Family
- World Models
- Category
- Information and virtual systems
- Entry kind
- aggregate
- Navigation path
- NAV.INF.REC.REQ
- Domain
- INF.REC.REQ
- Industry
- Cross-industry
- Tags
- requirementinf.rec.req
What it is Filled
A requirement is a stated need or condition that a system, product or service must meet, kept as a record with a stable identity, immutable revisions, acceptance criteria and trace links to its origin and to what satisfies or verifies it. It is the recorded statement, not the design that answers it or the test that checks it.
In scope
- Identity, content, classification, applicability and immutable revision history
- Local acceptance criteria, qualified assessments and outgoing trace assertions
- Governed local change records, derived revision-set views and exchange reconciliation
Out of scope
- Authoritative baseline approval and master membership
- Rule definitions, tasks, designs, test execution, evidence and decision masters
- Autonomous approval, waiver, legal determination or execution of external operations
Why it exists Filled
Maintain stable requirement identity, immutable revisions, acceptance criteria, outbound revision-pinned trace links and derived revision-set views.
Distinguishing features Filled
- Identity is stable while revisions are immutable, so links can pin the exact text they refer to.
- It carries acceptance criteria that make it verifiable, unlike a goal or wish.
- Trace links point outward to sources, designs and tests, which live in their own records.
- Distinct from a policy rule or constraint, which governs behaviour generally rather than a specific system.
What robots and AI may and may not do Filled
Must not
- Edit an approved revision in place instead of creating a new one.
- Approve or baseline requirements.
- Delete trace links to hide gaps in verification.
- Mark a requirement as verified without linked evidence.
Only with a human decision
- Approving and baselining requirements.
- Accepting changes to requirements under contract or regulation.
- Waiving a requirement or accepting a deviation.
May
- Draft requirements and acceptance criteria for human review.
- Check statements for ambiguity, duplication and missing criteria.
- Report trace coverage and links pinned to outdated revisions.
- Generate test ideas from acceptance criteria.
Moral aspects Filled
- Missing or wrong safety requirements lead to harmful products.
- Requirements decide whose needs are served, so affected users should be represented.
- Traceability supports accountability when things go wrong.
Who is affected
- End users of the system
- Engineering and test teams
- Customers, regulators and certifiers
Owners Filled
Steward
The requirements owner or systems engineer responsible for the specification, under the project's change control.
Roles
- Requirement steward
- Maintains identity, draft content and trace integrity within delegated authority
- Requirements reviewer
- Challenges intent, criteria, ambiguity and affected stakeholder coverage
- Verification assessor
- Records evidence-qualified satisfaction for exact revisions and subject configurations
- Approval authority
- Provides scoped approval or exception decision evidence outside autonomous local functions
- Record custodian
- Enforces access, retention, integrity and lawful disposal
- Baseline authority
- Owns authoritative baseline decisions and membership outside this aggregate
Master systems
- Requirements management tool
- Application lifecycle management system
Links to other meta-models Filled
references
- Authoritative Requirement Baseline - External master pending allocation review. Derived revision-set views cannot approve, mutate or replace baseline membership. Candidate conceptual binding, not ratified executable integration.
- WM-KNW-013 Constraint / Requirement Rule - General rule identity, expression, applicability and lifecycle remain rule-owned; local criteria may pin rule revisions and bind operands. Candidate conceptual binding, not ratified executable integration.
- WM-ACT-006 Task - Task execution remains task-owned and is not proof of requirement satisfaction. Candidate conceptual binding, not ratified executable integration.
- WM-SFT-015 Test Case / Test Result - Tests and results retain external identity and lifecycle; local assessments bind exact results to criteria and subject versions. Candidate conceptual binding, not ratified executable integration.
- WM-KNW-008 Evidence - Evidence stance and provenance remain evidence-owned; this aggregate stores qualified references and assessment rationale. Candidate conceptual binding, not ratified executable integration.
- WM-ACT-024 Decision - Decision occurrence, authority and effect remain external; local disposition is a record of the qualified reference. Candidate conceptual binding, not ratified executable integration.
- Change requests, designs and defects - Inbound candidate references from WM-ACT-032, WM-OBJ-018 and WM-SFT-014 do not transfer their ownership into Requirement. Candidate conceptual binding, not ratified executable integration.
- wm-sft-015-test-case-test-result - Tests verify requirements through trace links.
neighbor
- Authoritative Requirement Baseline - External master pending allocation review. Derived revision-set views cannot approve, mutate or replace baseline membership.
- WM-KNW-013 Constraint / Requirement Rule - General rule identity, expression, applicability and lifecycle remain rule-owned; local criteria may pin rule revisions and bind operands.
- WM-ACT-006 Task - Task execution remains task-owned and is not proof of requirement satisfaction.
- WM-SFT-015 Test Case / Test Result - Tests and results retain external identity and lifecycle; local assessments bind exact results to criteria and subject versions.
- WM-KNW-008 Evidence - Evidence stance and provenance remain evidence-owned; this aggregate stores qualified references and assessment rationale.
- WM-ACT-024 Decision - Decision occurrence, authority and effect remain external; local disposition is a record of the qualified reference.
- Change requests, designs and defects - Inbound candidate references from WM-ACT-032, WM-OBJ-018 and WM-SFT-014 do not transfer their ownership into Requirement.
- wm-knw-013-constraint-requirement-rule - General constraints and rules versus system-specific requirements.
requires
- wm-xct-022-version-change-history - Immutable revisions follow the version history pattern.
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- A requirement is identified by a stable identifier within its specification plus a revision number.
- ReqIF exchange uses identifiers for each specification object.
Direct properties not applicable Not applicable
Not applicable
A requirement is an information record; it may state physical limits but has no physical properties itself.
Recognition optional Filled
- A requirement has an identifier, a shall-type statement, a revision and acceptance criteria.
- Often confused with goals, design decisions, user stories without criteria and test cases.
Capabilities and actions required Filled
- Requirements can be revised, baselined, linked, verified, deferred or retired.
- Revision sets can be derived as views of a specification at a point in time.
Hazards and failure modes required Filled
- Silent changes that break the link between requirement and verification.
- Ambiguous requirements leading to unsafe or disputed outcomes.
Standards and interfaces required Filled
- OMG ReqIF for exchange of requirements between tools.
- OSLC Requirements Management for linking across lifecycle tools.
- ISO/IEC/IEEE 29148 for requirement content and quality.
Context of use required Filled
- Used in systems, software and product engineering and in procurement.
- Regulated sectors such as aviation, medical devices and automotive require traceability.
Sources Filled
- Technical Requirements Definition, section 4.2 - National Aeronautics and Space Administration
- Requirements Management, section 6.2 - National Aeronautics and Space Administration
- Requirements Interchange Format - Object Management Group
- OSLC Requirements Management Part 1: Specification - OASIS Open Projects
- OSLC Configuration Management Part 1: Overview - OASIS Open Projects
- PROV-O: The PROV Ontology - World Wide Web Consortium
- Date and Time on the Internet: Timestamps - Internet Engineering Task Force
- Appendix C: How to Write a Good Requirement - National Aeronautics and Space Administration
- ISO/IEC/IEEE 29148 Systems and software engineering - Requirements engineering (ISO/IEC/IEEE)
- Requirements Interchange Format ReqIF (Object Management Group)
- Guide to Writing Requirements (INCOSE)
Open questions
- Verify source availability, body hashes, immutable release pins and applicable adoption rights outside the sandbox.
- Allocate and review the external authoritative Requirement Baseline boundary without converting derived views into master records.
- Implement nested schemas and conformance fixtures covering stale evidence, divergent revisions, inaccessible links, empty criteria, partial views, redaction and failed concurrent writes.
- Restore independent external review before any canonical or publishable-draft promotion.
- Independent external review is absent; local Codex self-audit cannot replace it
- Direct HTTP statuses and body hashes are unmeasured; coordinator must run check_sources.py
- Immutable OASIS release pins, latest-version status and licensing/adoption review remain open
- Nested instance schemas, controlled state vocabularies, mapping fixtures, concurrency and conformance tests are not implemented
- Domain-specific safety, regulatory and contractual approval profiles are not established; no universal legal obligation is inferred
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-rec-006-requirement/spec.yaml, ver-cy/world-models/card-supplements/wm-rec-006-requirement.json