Relation types
The typed links between records, what each means and what agents do with it.
For: Product owner, Project lead
Relations
| Relation | Meaning | For agents |
|---|---|---|
| Refines | The source details the target one level down the "why" chain: objective → business → stakeholder → functional / non-functional. | Read the chain upwards to understand why a requirement exists before implementing it. |
| Realizes | A technical requirement states how a functional or non-functional requirement is achieved. | Use the realizing technical requirements when implementing the functional or quality requirement. |
| Constrains | A constraint limits specific requirements. A constraint without any constrains link applies to the whole project. | Respect every linked constraint and every project-wide constraint. |
| Depends on | The source can only be implemented or hold once the target does; both are requirements of the same type. | Implement or verify the dependency first; flag it if it is missing. |
| Replaces | The source takes the place of an older record of the same type, which should be Retired. | Follow the replacing record; never implement the replaced one. |
| Conflicts with | The two records cannot both hold. While the conflict is open neither can become Authority. | Stop and surface the conflict with both codes; do not pick a side. |
| Relates to | Informational link only. | Background only; draw no conclusions from it. |