Store one canonical relationship assertion
Answers Metaphysics · Topology · Identity · Derivation · Epistemology · Nomenclature
Store a relationship once in its canonical direction and generate the named inverse for reading. Provenance, source linkage, and implementation status must be explicit rather than duplicated as a second fact.
What goes wrong without it
A relationship written twice, once in each direction, is two facts that can disagree. The moment one is updated and the other is not, the graph holds a contradiction in which both readings look equally authoritative, and no reader can tell which was meant. Asserting one direction and inferring the other is what keeps a structure consistent as it grows.
What proves it — 1
Each is a gate the build runs: a check inside a ring, a whole ring, or an eval beside them. A build stops at the first that refuses.
- registry integritycanonical graph integrity
Endpoints resolve, relationship triples are unique, and compositions remain acyclic where the model requires it.
Derived from — 1
Relationships it licenses
takes as numerator · takes as denominator · parent campaign
Where this model stands
Each relationship is asserted once, and a duplicate or an endpoint of the wrong kind is not admitted.
The reverse reading is taken from the named inverse rather than stored as a second assertion.
A relationship that can point at its own kind declares itself acyclic, and every such relationship is walked for a cycle.
RUL-003