ORGANIC REVISION 01 — EXPERIMENTAL RELATION LAYER
2 October 2026

These labels describe proposed relationships between the pinned definitions.
They are local review conventions, not a new standardized logical calculus.
No claim is licensed merely by the presence of a coloured line on the map.

related (symmetric navigation)
  A stated topical or methodological association worth inspecting. It does not
  assert equivalence, entailment, causation, approval or shared authority.

contrast (symmetric navigation)
  A specific distinction or tension worth retaining. It need not be a formal
  contradiction, exhaustive opposition or claim that the concepts cannot coexist.

analogy (symmetric navigation)
  A qualified resemblance of structure, role or pattern across contexts. The
  qualification identifies boundaries; similarity does not transfer source
  authority, historical evidence or every property of either endpoint.

specializes (directional: source → target)
  The source is proposed as a more specific instance or bounded form of the
  target meaning. The warrant must be narrower scope, not merely a familiar
  word or shared topic. This release does not compute transitive closure.

operationalizes (directional: source → target)
  The source gives a proposed practice, mechanism or concrete support for the
  target under the stated conditions. It need not be necessary, sufficient or
  the only way to implement that target. A merely suggestive similarity should
  use related or analogy instead.

REQUIRED EVIDENCE
Every proposal records source and target IDs, exact excerpts of both definitions,
its type, rationale, qualification, AI author status and review origin. The
enclosing graph pins the definitions' checked snapshot and hashes the entire
proposal set. A decision must match both pins and an exact proposal ID.

NAVIGATION AND STATE PROJECTION
All edge types can be followed either way in the path finder. Doing so does not
reverse their semantic assertion. The UI displays source → target for directional
claims even when the reader enters from the target.

The original Carrier relations array has no per-edge type field. For the local
exploratory edition, related/contrast/analogy add navigation references at both
endpoints; specializes/operationalizes add only source → target. Type and review
status remain in each changed record's provenance and in typed-links.json.

Existing links are not reclassified by inference. No transitive links are
automatically added. No new colour, concept ID or approved claim is inferred.
Two different types can describe the same pair when their qualifications are
compatible; they remain separate claims and separate review decisions.

Recorded “Referenced by” is an exact reverse index of stored references. It is
not a claim that the referenced concept endorses the referring concept. Proposed
incoming relations are displayed separately and retain their proposed status.

Threads are authored reading itineraries. A step may use a recorded reference,
a proposed reference or an explicit juxtaposition with no graph edge. None of
these by itself makes the whole itinerary a deductive argument.

Definitions retain their prior checked status in a proposed linked snapshot.
That marker does not certify the new links. Changes to the checked file produce
a new head; the original snapshot remains available for existing expression pins.
