Coordination value

Type: kb/types/definition.md · Tags: document-system

Coordination value is the worth a structure has because every artifact, tool, or agent adopts the same one — a shared schema field, link label, routing key, protocol, or convention. It is created by the shared commitment, not discovered as a property of the particular choice. Because the value lives in the sharedness rather than in which option was picked, a better-in-principle alternative does not increase it, and defection from the shared choice destroys it.

Scope

Use coordination value to explain why a shared convention resists replacement by a marginally better rival, and why committing to a standard can be right before any evidence that the standard transfers. It answers a warrant question — why a structure is worth committing to and keeping — on the value-source axis, alongside reach (value discovered by testing whether a claim keeps working past its origin cases) and inherited constraint (value forced by a boundary commitment).

The maintenance consequence is worked out in a knowledge base holds theories, descriptions, and prescriptions with asymmetric linking: a structure carrying coordination value has operational authority with no rests-on edge to an upstream theory, so a theory proposing a better option does not trigger its revision. Only a theory showing the coordination itself is net-negative fires a change, and even then re-coordination carries a switching cost.

Exclusions

Coordination value is not behavioral authority. Behavioral authority records the force a structure exerts when consumed — enforcement, routing, instruction; coordination value records why the structure is worth committing to. A structure with coordination value is usually consumed with binding force, but the value-source and the force are different axes.

It is not reach. Reach is a standing property discovered by testing transfer, present whether or not anyone commits; coordination value is absent until the commitment and scoped to its adopters. One structure can carry both — a shared schema can be a good design and the one everyone uses — but the two warrants are earned and defended differently.

It is not the runtime coordination of agent orchestration, which concerns executing agents staying consistent during a run rather than the shared adoption of a retained structure.

Misuse Cases

  • Switching a shared convention to a marginally better alternative, ignoring that the value is the sharedness and re-coordination has a switching cost.
  • Attributing coordination value to every enforced structure. A schema derived from a theory has its warrant in that theory, not in shared adoption; if the theory changes the schema should change, governed by its authored rests-on edge.
  • Committing to a shared convention purely to anticipate coordination that no adopter yet needs, hardening vocabulary before the need is demonstrated.

Relevant Notes: