Relations & conflicts
Typed links between records, conflicts and replacements.
A record on its own rarely tells the whole story. Relations connect records so that an agent can see why a requirement exists (the objective it refines), how it is achieved (the technical requirement that realises it) and what limits it (the constraints on it). Corpole uses a small set of typed relations and allows each only between the types where it makes sense.
Relations also catch contradictions. When two records cannot both hold, a “conflicts with” relation marks them, and an open conflict stops either from becoming Authority. Agents are instructed to stop at a conflict and show both codes rather than choose a winner, because choosing is a judgement that belongs to the people accountable for it.
The articles here explain which relation to use when, why a record may be refused when you try to make it Authority, and what to do when two binding records disagree. The reference page lists every relation with its meaning and what agents do with it.
Articles in Relations & conflicts
- ConceptRelations: when to use whichTyped links tell an agent why a requirement exists, how it is achieved and what limits it.
- TroubleshootingWhy a record cannot become AuthorityTwo rules block it: a requirement without acceptance criteria, and an open conflict.
- CaseTwo binding records disagreeThe agent stops and shows both codes. It does not pick a winner; a person does.