# Requirement Origin

## Context

Most requirements name neither a carrying feature nor a basis, while every enforced Intent check passes.

## Decision

Every requirement names its parent: a carrying `feature`, including a shipped feature, or a constraint or research in `basedOn`, or a decision that names it in `decides`, in that precedence.

## Evidence with Confidence

`research/intent-hierarchy-evidence` and `research/cross-layer-trace-evidence` are measured over the largest consumer on 2026-10-30, high confidence. `research/established-traceability-practice` carries the stated vendor-restatement limit on the regulated regimes.