Skip to content

License as Coordination

Version
v4 · 2026-09-28 · History
Prime #
1395
Domain group
Professional & Organizational Practice
Origin domain
Law & Governance
Subdomains
Licensing and Coordination, Knowledge Management, Standards Governance → Law & Governance
Also from
Computer Science & Software Engineering
Aliases
License Based Coordination, Standing Permission Terms, Preauthorized Reuse
Related primes
Access Control, Contract, Transaction Costs

Core Idea

License as coordination is the pattern in which a rights holder publishes standing permission terms for a class of actors and uses, replacing repeated bilateral permission requests with a rule that participants can inspect and rely on. The license coordinates by making permitted action predictable before any particular reuse occurs.

How would you explain it like I'm…

The Rules-for-Everyone Sign

Your neighbor puts a sign on her sandbox: "Anyone can play here if you put the toys back." Now you don't have to knock on her door and ask every single time. You just read the sign, follow the rule, and play, and so can all the other kids.

Posted Permission Rules

License as Coordination is when the owner of something writes down the rules for how others may use it, ahead of time, for everyone. Instead of each person asking 'Can I use your song in my video?' and waiting for an answer, they read the license and check whether their use is allowed. That saves a huge amount of asking and answering. It also helps everyone plan, because they can all count on the same written rules. The rules can be generous or strict — what matters is that they are posted and dependable.

Standing Permission as Coordination

License as Coordination is the pattern where a rights holder publishes standing permission terms for a whole class of people and uses, instead of granting permission one request at a time. The shift is from 'negotiate per use' to 'consult the license.' Without a license, every reuse means finding the owner, describing what you want, bargaining, recording the deal, and repeating it for the next person. A license does that work once, in advance: who is covered, which resources, which uses, what obligations, what's excluded, and when permission ends. That makes it a shared planning surface — independent people can coordinate with the owner and with each other just by reading it. Open-source licenses are a familiar example, but a license doesn't have to be open; restrictive or tiered terms coordinate too.

 

License as Coordination is an institutional pattern in which a rights holder publishes standing permission terms covering a class of actors and uses, replacing repeated bilateral permission requests with a rule that participants can inspect, interpret, and rely on before acting. Beyond expressing consent, the license creates a common planning surface: independent actors coordinate both with the rights holder and with one another by checking whether an intended use falls inside the terms. The transformation is from negotiate-per-use to consult-the-license. Per-use negotiation carries recurring transaction costs — identifying the holder, specifying the action, bargaining over conditions, documenting the grant — for every actor and every use; a license amortizes these by declaring in advance the covered actors, resources, uses, obligations, exclusions, and termination conditions. The mechanism accommodates open reuse, restricted reuse, reciprocal (e.g., copyleft) obligations, field-of-use limits, and tiered permissions. Openness is therefore not constitutive; what matters is that a stable permission rule covers a class of future actions and functions as a coordination device participants can rely on.

Broad Use

  • Software and data: open-source, open-data, and shared-dataset licenses.
  • Creative works: public licenses for copying, adaptation, and redistribution.
  • Standards and patents: standardized licensing commitments that reduce implementer uncertainty.
  • Physical resources: standing access, use, or franchise permissions governed through published terms.

Clarity

The abstraction distinguishes the coordination function of licensing from access enforcement and case-by-case contracting. A technical control may grant or deny an action at runtime; a license states the terms under which an action is authorized. A negotiated contract can coordinate one relationship; a standing license coordinates an open or pre-specified class without reopening the bargain each time.

Manages Complexity

Publishing one permission rule can replace a large set of pairwise negotiations. Participants still must determine whether their intended use falls within the terms, but they no longer need to locate and bargain with the rights holder for each instance.

Abstract Reasoning

The central move is to replace ask each time with act under a standing rule. The abstraction helps identify when permission uncertainty, rather than technical incompatibility or scarcity, is the bottleneck to coordination.

Knowledge Transfer

The same design lesson transfers from software ecosystems to data repositories, standards, and shared institutional assets: explicit, class-wide permissions lower search and bargaining costs and allow independently planned actions to compose.

Example

A dataset released under explicit reuse terms can be incorporated by many independent research teams without each team negotiating a separate agreement. They coordinate with the publisher by consulting the same standing rule.

Relationships to Other Abstractions

Local relationship map for License as CoordinationParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.License asCoordinationPRIMEPrime abstraction: Coordination — is a kind ofCoordinationPRIMEPrime abstraction: Open Publication for Interoperability — includesOpen Publicatio…PRIMEDomain-specific abstraction: Open Availability — is a kind ofOpenAvailabilityDOMAIN

Current abstraction License as Coordination Prime

Parents (1) — outgoing typed relations

  • License as Coordination is a kind of Coordination Prime

    License as coordination is coordination specialized to aligning independent actors through standing published permissions.

Children (2) — abstractions linked here by typed relations

  • Open Availability Domain-specific is a kind of License as Coordination

    Open availability is license-as-coordination specialized to openly reusable knowledge resources.

  • Open Publication for Interoperability Prime includes License as Coordination

    Open publication contains a standing reuse license as one of its five defining publication commitments.

Hierarchy paths (5) — routes to 4 parentless roots

Not to Be Confused With

  • Coordination is the wider alignment problem; license as coordination is one institutionally framed mechanism.
  • Access Control technically mediates attempted actions; a license establishes normative or legal permission terms and may exist without automated enforcement.
  • Contract may be individually negotiated and bilateral; a standing license can address an indefinite class of users.
  • Open Availability is a domain-specific knowledge-resource posture that also requires findability, accessibility, and non-restrictive terms.