Open Availability¶

Make a knowledge resource reachable by anyone under explicit, non-restrictive, machine-operative terms so that reuse shifts from negotiate-per-use to consult-the-license, unlocking combinatorial composition across an ecosystem.

Core Idea¶

Open availability is the governance posture in which a knowledge resource — an ontology, a dataset, a software package, a specification, a publication — is made accessible to any user under explicit and non-restrictive use conditions, converting the resource from a gatekept or implicitly-available asset into one with known, permissive terms that support downstream reuse, redistribution, and combination without per-use negotiation.

The pattern has four commitments that travel together. Findability means the resource can be discovered through a public lookup mechanism — a registry, a repository, a search index — without requiring prior knowledge of its existence or a relationship with the publishing group. Accessibility means the resource can be retrieved by any interested party without submitting a separate permission request for each use: the bits are reachable through an open channel. Explicit use terms means a license or open-access declaration accompanies the resource, specifying what holders of the resource are and are not permitted to do with it — and making that specification machine-readable and legally operative rather than implied or informal. Non-restrictiveness means the terms actually permit substantive reuse: machine reading, redistribution, modification, and incorporation into derivative works. The first three commitments without the fourth produce nominal openness; a resource that exists in a public repository under a license that prohibits most reuse is technically findable and accessible but not openly available in the sense that matters for downstream composition.

The pattern is operationalised across several knowledge-resource governance regimes that converge on the same four-part architecture for different substrates. The OBO Foundry's open-availability principle requires biomedical ontologies to carry explicit licenses permitting cross-ontology composition. The FAIR data principles (Findable, Accessible, Interoperable, Reusable) formalise three of the four commitments for research datasets. The Open Source Initiative's Open Source Definition codifies them for software. The Budapest, Bethesda, and Berlin declarations operationalise them for research publications. The Creative Commons license family was explicitly designed to port the GPL-style open-software architecture into other knowledge-resource media.

What these instantiations share structurally is the move from negotiate-per-use coordination to consult-the-license coordination. In a closed or ambiguously-licensed resource ecosystem, every potential reuse requires a transaction with the rights holder: identifying who holds the rights, reaching them, describing the intended use, awaiting permission, and absorbing any conditions imposed. At population scale — thousands of researchers, dozens of ontologies, millions of datasets — this per-use transaction cost is prohibitive and combinatorial reuse becomes effectively impossible. Explicit permissive licensing pre-authorises the full class of non-commercial or modification uses, reducing per-use coordination cost to near zero. The network consequence is that ecosystems of openly available resources can develop combinatorial compositions — ontologies that import other ontologies, datasets that join other datasets, tools that build on other tools — that closed ecosystems cannot, because the licensing is compatible and the permission is already granted.

The recurring failure mode the pattern guards against is nominal availability without substantive openness: a resource published in a public location under terms so vague, restrictive, or incompatible with other resources that practical reuse is blocked. OBO Foundry curation practice names this explicitly, requiring not just that terms exist but that they are unambiguous and permissive enough to enable the downstream composition the resource is intended to support.

Structural Signature¶

Sig role-phrases:

the knowledge resource — the ontology, dataset, software package, specification, or publication whose governance is at issue
the findability commitment — discoverability through a public lookup (registry, repository, index) without prior knowledge or a relationship with the publisher
the accessibility commitment — retrievability through an open channel without a separate per-use permission request
the explicit-terms commitment — a machine-readable, legally operative license or open-access declaration stating what holders may and may not do, rather than implied or informal terms
the non-restrictiveness commitment — terms that actually permit substantive reuse (machine reading, redistribution, modification, derivative works), the fourth commitment without which the first three yield only nominal openness
the three-layer stack — the technical (where the bits live), legal (what the license permits), and social (whether the community treats it as usable) layers a breakdown localizes to
the consult-the-license coordination move — the engineered payoff: pre-authorizing the whole class of intended uses converts negotiate-per-use into consult-the-license, dropping per-use cost toward zero
the combinatorial reach versus enclosure risk — the population-scale consequence: compatibly licensed resources compose (ontologies importing ontologies, datasets joining datasets), against the standing risk that re-closure breaks everything built atop a resource

What It Is Not¶

Not mere availability. "The resource exists somewhere a user could reach it" is exactly what open availability is not: the concept exists to separate availability from reachability-by-anyone-under-explicit-non-restrictive-terms. A maintainer who posts an ontology at a public URL and declares it "available" has not achieved open availability if downstream composition fails for want of operative, permissive terms — the failure mode the concept names nominal availability without substantive openness.
Not "free of charge." The pattern is about use terms, not price: the load-bearing question is whether holders may machine-read, redistribute, modify, and incorporate the resource, not whether they paid for it. A paywall is one access barrier, but a gratis resource under terms that forbid reuse is still not openly available, and a priced resource is a separate axis from the licensing posture the concept governs.
Not satisfied by findability, accessibility, and a license alone. The first three commitments without the fourth — non-restrictiveness — produce only nominal openness: a resource that is discoverable, retrievable, and licensed, but under terms prohibiting substantive reuse, is technically findable yet useless for composition. The fourth commitment, that the terms actually permit reuse, is what makes openness substantive rather than apparent.
Not the same as transparency. Transparency concerns disclosure — the visibility of processes and decisions to stakeholders; open availability concerns accessibility-for-use of a resource under explicit terms. The two often co-occur, but their structural commitments differ: a resource can be fully disclosed yet encumbered by a license that blocks reuse, so transparency does not entail composability.
Not "open access" to a commons. "Open access to a forest" or "to the airwaves" is a different problem entirely: those are commons-management situations governed by commons and tragedy_of_the_commons, where the resource is rivalrous and the failure mode is overuse. Open availability concerns non-rivalrous knowledge resources whose failure mode is gated reuse; the shared word "open" hides that the two belong to different prime families.

Scope of Application¶

Open availability lives within knowledge-resource governance; its reach is bounded to that domain, because its substance is one coordination posture applied to non-rivalrous knowledge resources, and the commons cases that share the word "open" (a forest, the airwaves) belong to a different prime family (commons, tragedy_of_the_commons) where the resource is rivalrous and the failure mode is overuse, not gated reuse. The exportable coordination move (license_as_coordination) is the parent's to carry. Within the domain the identical four-part architecture is instantiated across these substrates.

Biomedical ontologies — the OBO Foundry open-availability principle requires ontologies to carry explicit licenses permitting cross-ontology composition and downstream tool development (Gene Ontology, Human Phenotype Ontology).
Research data — the FAIR principles (Findable, Accessible, Interoperable, Reusable) formalize three of the four commitments for scientific datasets.
Open-source software — the OSI Open Source Definition codifies the use-terms commitment, with source-code availability formalizing retrieval.
Open-access publishing — the Budapest, Bethesda, and Berlin declarations operationalize the architecture for research publications.
Open standards — W3C, IETF, and ISO open-standards practice opens specification documents and reference implementations to public use.
Open government data — public-data portals (data.gov, the EU Open Data Portal) extend the posture to administrative records.

Clarity¶

Naming open availability separates two things that "the resource is available" silently fuses: availability (the resource exists somewhere a user could in principle reach) from open availability (it is reachable by anyone under explicit, non-restrictive terms). Without the distinction, a knowledge-resource maintainer can announce that an ontology or dataset is "available," point to a public URL, and believe the coordination job is done — while downstream composition quietly fails because the terms are vague, the license is incompatible, or reuse demands a permission request the maintainer never anticipated. The concept makes the failure mode visible and gives it a name: nominal availability without substantive openness, the resource that sits in a public repository under terms that block the very reuse it was meant to enable. The sharper question a curator can now ask is not "is this published?" but "is this composable — can a stranger machine-read it, redistribute it, and fold it into a derivative work without negotiating with me first?"

The concept also pulls apart three layers that ambiguous practice runs together: the technical layer (where the bits live and how they are served), the legal layer (what the license actually permits a holder to do), and the social layer (whether the community treats the resource as freely usable in practice). A resource can pass on one and fail on another — served from an open endpoint but encumbered by an incompatible license, or permissively licensed but undiscoverable for want of a registry entry — and localizing the breakdown to the right layer tells the maintainer which fix moves the needle, since a better server cannot cure a restrictive license and a permissive license cannot cure a missing lookup mechanism. Most pointedly, it reframes licensing from boilerplate into a coordination instrument: by reading "explicit permissive terms" as the move from negotiate-per-use to consult-the-license, the curator can see why combinatorial reuse at population scale stands or falls on whether the fourth commitment — non-restrictiveness — is actually met, not merely whether the first three create the appearance of openness.

Manages Complexity¶

A reuse decision in a closed resource ecosystem is, in full, a thicket of bespoke transactions: for every ontology, dataset, or package a stranger might fold into a derivative, identify the rights holder, reach them, describe the use, await terms, and absorb conditions — a per-pair cost that grows combinatorially as the ecosystem scales to thousands of resources and users. Open availability collapses that thicket onto the license. Once a resource carries explicit, permissive terms, the entire class of intended uses is pre-authorised, so the cost of any given reuse drops to "consult the license" and the curator no longer reasons resource-by-resource and holder-by-holder. The whole posture reduces to four readable commitments — findability, accessibility, explicit terms, non-restrictiveness — checked once per resource; whether combinatorial composition is feasible across a population of resources then follows almost entirely from whether their licenses are present and compatible, not from re-litigating each pairing. A maintainer asking "will a stranger be able to build on this?" reads the answer off those four checks plus license compatibility, and a curator diagnosing a stalled composition localizes the break to the technical, legal, or social layer rather than auditing every downstream attempt. A coordination problem that is in principle quadratic in the number of resources is thereby compressed into a small per-resource checklist whose outcome predicts the ecosystem's combinatorial reach.

Abstract Reasoning¶

Reduced to a four-commitment checklist over a three-layer stack, open availability licenses the inferences a curator or resource maintainer draws when reasoning about reuse, all turning on the gap between nominal and substantive openness.

Diagnostic — localize a stalled composition to a failed commitment or layer. When a downstream composition fails — a stranger cannot fold an ontology into a derivative, a dataset will not join another, a tool cannot build on a library — the curator does not treat it as a generic "it didn't work" but infers which of the four commitments is missing and which layer it lives on. A resource that is reachable and licensed but absent from any registry has failed findability at the technical/social layer; one that is discoverable but demands a per-use permission request has failed accessibility; one that is served openly but carries no operative license has failed explicit terms at the legal layer; one that has all three yet sits under terms that forbid machine reading, redistribution, or modification has failed non-restrictiveness — the signature of nominal availability without substantive openness. The inference runs from the surface symptom (composition blocked) to the precise hidden defect, and it is sharp because the four commitments fail independently and a resource can pass three while silently failing the fourth.

Interventionist — fix the layer that is actually broken, predict the change in reach. Because the breakdown is localized, the remedy is too, and the concept predicts that a fix aimed at the wrong layer moves nothing. A better server or faster endpoint cannot cure a restrictive license; a permissive license cannot cure a missing registry entry; relicensing to permit modification and redistribution is predicted to unlock the class of compositions that the old terms foreclosed, while merely re-hosting it is not. The high-leverage intervention is therefore on the fourth commitment — converting terms from gatekept or ambiguous to explicit-and-permissive pre-authorises the whole class of intended uses at once, dropping per-use coordination cost toward zero and predicting a step change in how many strangers can build on the resource without negotiating. Each candidate fix is thus a prediction about combinatorial reach: relax the binding constraint and the feasible composition space expands; touch a non-binding layer and it does not.

Boundary-drawing — decide whether a resource is composable, and whether two are combinable. The concept gates a class of reuse inferences. A resource that passes all four checks may be treated as composable — a stranger can machine-read, redistribute, and incorporate it without per-use negotiation — and may be planned into derivative work; one that fails any check cannot be, and a maintainer's announcement that it is "available" does not license the assumption. A second, pairwise boundary governs combination: even two individually open resources compose only if their licenses are mutually compatible, so the curator reasons not just per-resource but per-pair, and an incompatible-license verdict forecloses the join regardless of each resource's standalone openness. The judgment "is this published?" is replaced by the operative "is this composable, and compatible with what I want to combine it with?"

Predictive — combinatorial reach and enclosure risk at population scale. From the per-resource checklist plus license compatibility, the curator predicts ecosystem-level outcomes no single resource exposes: ecosystems of openly available, compatibly licensed resources will develop combinatorial compositions — ontologies importing ontologies, datasets joining datasets, tools stacking on tools — that closed or incompatibly licensed ecosystems cannot, because the per-use permission is already granted and the cost is near zero. The same frame names the standing downside risk — enclosure: an openly available resource can later be re-closed, and because downstream compositions depend on its terms holding, the curator treats the durability of the open terms (and the social and legal machinery that resists re-closure) as load-bearing, predicting that re-enclosure of a widely-composed-upon resource propagates breakage through everything built on it.

Knowledge Transfer¶

Within knowledge-resource governance — the home domain — open availability transfers as mechanism across substrates that share the four-part architecture, because the cargo is one coordination move: convert negotiate-per-use into consult-the-license by attaching explicit, non-restrictive, machine-operative terms to a findable, retrievable resource. It is instantiated, with the same skeleton, across biomedical ontologies (the OBO Foundry open-availability principle requiring licenses that permit cross-ontology composition), research data (the FAIR principles formalizing three of the four commitments), software (the OSI Open Source Definition codifying them), research publications (the Budapest/Bethesda/Berlin declarations), open standards (W3C/IETF/ISO practice), and open government data (public-data portals). The transfer here is unusually literal and historically documented: open-source licensing discipline ported almost without modification into open-access publishing and open-data practice, and the Creative Commons family was explicitly designed to carry the GPL-style architecture into other media. Across all of these the full apparatus carries without translation — the nominal-versus-substantive-openness diagnostic, the technical/legal/social three-layer localization, the per-resource four-commitment checklist plus pairwise license-compatibility, and the enclosure-risk and combinatorial-reach predictions — because every case is the same governance posture applied to a different knowledge-resource medium.

Beyond knowledge resources the named posture does not extend in a structurally non-trivial way, and the honest reading separates a different prime family from a genuinely portable parent. The tempting extensions — "open access to a forest," "open access to the airwaves" — are not instances of open availability at all; they are commons-management problems governed by their own structural primes (commons, tragedy_of_the_commons), where the resource is rivalrous and the failure mode is overuse, not gated reuse. Confusing the two would be an (A) miscategorization on the shared word "open," and it should be marked off. What does generalize is the (B) case: the substantive structural content of open availability is largely the union of parents already in the catalogue — transparency (extended to knowledge resources) for the disclosure component, mediator_availability_constraint for the access-architecture component, and the governance prime family for the licensing component — and the one sharp move beyond that union is explicit-license-as-coordination-mechanism: a pre-authorization that lets strangers combine resources without per-pair negotiation, dropping coordination cost toward zero and unlocking combinatorial composition. That coordination move, now carried by the parent prime license_as_coordination, is the portable core, and it is what a cross-domain lesson should carry — wherever pre-declared permissive terms replace per-use negotiation to enable population-scale recombination. Stripped of jargon, "open availability" itself reduces toward a normative policy posture ("make knowledge available under explicit permissive terms") rather than a substrate-independent mechanism, which is exactly why its reach stays inside knowledge-resource governance and the exportable structure is the coordination move it instantiates, not the posture as named. See Structural Core vs. Domain Accent.

Examples¶

Canonical¶

The Gene Ontology (GO) is the defining instance in its home domain. GO is registered in the OBO Foundry and downloadable from a public endpoint (findability and accessibility); it is released under a Creative Commons Attribution (CC BY 4.0) license that permits redistribution, modification, and incorporation into derivative works with only an attribution requirement (explicit, non-restrictive terms); and it is published in machine-operative formats (OBO, OWL) that other ontologies and software consume directly. Because the license pre-authorises reuse, thousands of research groups annotate genomes with GO terms and hundreds of tools and ontologies import it without ever contacting the maintainers — the coordination cost of any given reuse is "read the license," not "negotiate a permission." That pre-authorisation is exactly what lets the biomedical-ontology ecosystem compose combinatorially.

Mapped back: GO is the knowledge resource; its OBO Foundry registration and open endpoint satisfy the findability and accessibility commitments, and CC BY 4.0 satisfies the explicit-terms and non-restrictiveness commitments. Reuse-without-contact is the consult-the-license coordination move, and the ontologies-importing-ontologies pattern is the combinatorial reach it unlocks.

Applied / In Practice¶

The August 2023 relicensing of Terraform shows both the coordination payoff and the enclosure risk the concept predicts. Terraform, HashiCorp's infrastructure-as-code tool, had for years been distributed under the permissive open-source Mozilla Public License; an ecosystem of providers, modules, and downstream tools composed on top of it precisely because the terms pre-authorised reuse. HashiCorp then re-closed it, switching to the restrictive Business Source License, which forbids competing commercial use. Because thousands of downstream projects depended on the open terms holding, the re-enclosure threatened to break what had been built atop it — and the community responded by forking the last open version as OpenTofu, moved under the Linux Foundation to make the open terms durable. The episode is the concept's enclosure prediction in miniature: composability is only as stable as the non-restrictiveness commitment.

Mapped back: The permissive MPL supplied the explicit-terms and non-restrictiveness commitments that powered the consult-the-license coordination move and Terraform's combinatorial reach. The switch to the Business Source License is the enclosure risk realised — re-closing a widely-composed-upon resource propagates breakage downstream — and the OpenTofu fork is the ecosystem defending the durability of those terms.

Structural Tensions¶

T1: Nominal versus substantive openness (three commitments look open without being so). The concept's sharpest boundary is that findability, accessibility, and an explicit license — the first three commitments — produce only nominal openness without the fourth: a resource that is discoverable, retrievable, and licensed, yet under terms that forbid machine reading, redistribution, or modification, is technically "available" and useless for composition. This is the failure mode the concept exists to name, and it is treacherous precisely because the appearance of openness (a public URL, a license file) is fully compatible with substantive closure. A maintainer can honestly believe the coordination job is done while downstream reuse quietly fails. The gap between looking open and being composable is exactly where nominal availability hides. Diagnostic: Do the terms actually permit reuse — machine reading, redistribution, modification, derivative works — or only the appearance of openness (findable, retrievable, licensed, but non-reusable)?

T2: Composability unlocked versus enclosure exposure (openness creates the dependency it can betray). Permissive terms pre-authorize reuse and unlock combinatorial composition — ontologies importing ontologies, tools stacking on tools — which is the whole payoff. But that same success builds a dependency: everything composed atop a resource depends on its open terms continuing to hold, so an openly available resource that is later re-closed propagates breakage through everything built on it. The openness that invites composition is the openness that, when withdrawn, does the most damage, and the more widely a resource is composed upon the more catastrophic its re-enclosure. Composability and enclosure-exposure are the same coin: durability of the terms becomes load-bearing exactly to the degree the resource succeeded. Diagnostic: How much downstream composition depends on these terms holding, and what social or legal machinery makes their openness durable against re-closure?

T3: Three-layer localization versus the requirement that all hold (fixing the wrong layer moves nothing). Separating the technical (where the bits live), legal (what the license permits), and social (whether the community treats it as usable) layers lets a curator localize a stalled composition to the layer that actually broke — powerful, because a better server cannot cure a restrictive license and a permissive license cannot cure a missing registry entry. But the flip side is that openness requires all three to hold at once, and passing two while failing one still blocks reuse. The localization that tells you which fix moves the needle also means no single layer's success is sufficient, and a maintainer who invests in the wrong (non-binding) layer sees no change in composability. Diagnostic precision and conjunctive fragility are the same structure. Diagnostic: Which layer is the binding constraint on this stalled reuse — technical, legal, or social — and is the proposed fix aimed at that layer rather than an already-passing one?

T4: Non-rivalrous openness versus rivalrous commons (the shared word hides different prime families). "Open" tempts a conflation the concept must actively resist: open availability governs non-rivalrous knowledge resources whose failure mode is gated reuse, whereas "open access to a forest" or "to the airwaves" is a commons-management problem governed by commons and tragedy_of_the_commons, where the resource is rivalrous and the failure mode is overuse. The two are opposite in structure — one wants more reuse (which costs nothing extra), the other wants less (because use depletes) — yet the shared word invites importing the wrong toolkit, applying enclosure-and-composition logic to a depletable resource or overuse-restriction logic to an infinitely copyable one. The concept's reach ends exactly where rivalry begins, and the word "open" is the trap at that boundary. Diagnostic: Is the resource non-rivalrous (copying it costs nothing, failure is gated reuse — open availability) or rivalrous (use depletes it, failure is overuse — a commons problem)?

T5: Autonomy versus reduction (a governance posture or the license-as-coordination parent). Within knowledge-resource governance, open availability transfers as mechanism across substrates that share the four-part architecture — biomedical ontologies, research data, software, publications, standards, government data — and the transfer is unusually literal and historically documented (open-source discipline ported into open-access and open-data; Creative Commons designed to carry the GPL architecture into new media). But stripped of jargon the named posture reduces toward a normative policy stance ("make knowledge available under explicit permissive terms") rather than a substrate-independent mechanism, and its substantive content is largely the union of catalogue parents — transparency for disclosure, mediator_availability_constraint for access, the governance family for licensing. The one sharp exportable move is license_as_coordination: pre-declared permissive terms replacing per-use negotiation to enable population-scale recombination. The tension is between a richly instantiated governance posture and the recognition that its portable core is that coordination move. Diagnostic: Resolve toward license_as_coordination (with transparency and access parents) when the lesson is "pre-declared terms replace per-use negotiation"; toward open availability when the four-commitment architecture over knowledge resources is the subject.

Structural–Framed Character¶

Open availability sits at the framed end of the structural–framed spectrum — framed-leaning: a knowledge-resource governance posture, mildly normative and constituted by a licensing practice, that the entry itself concedes reduces toward a policy stance rather than a substrate-independent mechanism. On evaluative_weight it carries a normative tilt: stripped of jargon the posture is "make knowledge available under explicit permissive terms," a recommendation with a value orientation (openness as the composability-enabling good), so it sits above a purely neutral mechanism while short of a censure. On human_practice_bound it is high: the posture is constituted by the practice of governing a knowledge resource's licensing perimeter and dissolves without it — with no rights holder, no license, and no reuse to pre-authorize, there is only a resource sitting somewhere, nothing being "openly available." Institutional_origin is pronounced: the four-commitment architecture is codified furniture of specific governance regimes — the OBO Foundry principle, the FAIR data principles, the OSI Open Source Definition, the Budapest/Bethesda/Berlin declarations, the Creative Commons family — a set of institutional artifacts, not a fact of nature. On vocab_travels it scores low: the licensing-and-registry idiom is pinned to knowledge-resource governance. And on import_vs_recognize the transfer is layered — within knowledge-resource governance it ports as mechanism (unusually literally and historically documented, open-source discipline porting into open-access and open-data), but "open access to a forest" is a different prime family (commons, tragedy_of_the_commons) entirely, not an import of "open availability."

The substantive content is largely the union of catalog parents — transparency (extended to knowledge resources) for disclosure, mediator_availability_constraint for access architecture, and the governance family for licensing — with one sharp portable move: license_as_coordination, pre-declared permissive terms replacing per-use negotiation to enable population-scale recombination. That coordination move is genuinely substrate-independent and is the real exportable core. But it does not pull open availability off the framed pole, because license_as_coordination and its co-parents are exactly what the posture instantiates from its umbrellas, not what makes "open availability" itself travel: the cross-domain reach belongs to the coordination move (and transparency/access parents), while the four-commitment architecture, the nominal-versus-substantive-openness diagnostic, and the enclosure-risk vocabulary stay home. Its character: a normative, practice-constituted knowledge-governance posture, structural only in the license-as-coordination move (and the transparency/access/governance parents) it borrows from its umbrellas — a policy stance that reduces toward those primitives rather than a mechanism of its own.

Structural Core vs. Domain Accent¶

This section decides why open availability is a domain-specific abstraction and not a prime — why its exportable core is one coordination move while the posture itself reduces toward policy.

What is skeletal (now lifted to a cross-domain prime). Strip the licensing idiom and a thin relational structure survives: pre-declared permissive terms replace per-use negotiation, so an actor coordinating with a resource consults a standing license instead of transacting with a rights holder — dropping per-use coordination cost toward zero and unlocking population-scale recombination. The portable pieces are abstract: a pre-authorization that covers a whole class of intended uses, a shift from negotiate-per-use to consult-the-license, and the combinatorial reach that follows when compatibly-authorized resources compose freely. This coordination move is now carried by the parent prime license_as_coordination, and the posture's remaining substance is largely the union of parents already in the catalog: transparency (extended to knowledge resources) for disclosure, mediator_availability_constraint for the access-architecture component, and the governance family for licensing. But these are the cores open availability shares, not what makes the posture distinctive.

What is domain-bound. What is distinctive is knowledge-resource-governance furniture and does not survive extraction. The four-commitment architecture (findability, accessibility, explicit terms, non-restrictiveness) and its load-bearing nominal-versus-substantive-openness distinction; the three-layer stack (technical / legal / social) a breakdown localizes to; the machine-operative license requirement (OBO, OWL, CC BY, GPL, the Creative Commons family); the specific codifying regimes (OBO Foundry principle, FAIR data principles, OSI Open Source Definition, Budapest/Bethesda/Berlin declarations); and the enclosure-risk vocabulary of re-closure propagating breakage downstream — these are the codified apparatus of specific governance institutions. The decisive test: open availability governs non-rivalrous knowledge resources whose failure mode is gated reuse, so "open access to a forest" or "to the airwaves" is not an instance at all but a commons-management problem in a different prime family (commons, tragedy_of_the_commons), where the resource is rivalrous and the failure mode is overuse — the shared word "open" hides the boundary. Remove the licensing perimeter and the knowledge-resource medium and there is no open availability, only a resource sitting somewhere.

Why this does not clear the prime bar. A prime's vocabulary travels and its transfer is recognition of the same mechanism, not analogy. Open availability's transfer is bimodal. Within knowledge-resource governance it moves as full mechanism — unusually literally and historically documented, as open-source licensing discipline ported almost without modification into open-access publishing and open-data practice, and the Creative Commons family was explicitly designed to carry the GPL architecture into new media — so the nominal-versus-substantive diagnostic, the three-layer localization, the four-commitment checklist, and the enclosure/combinatorial-reach predictions carry across ontologies, data, software, publications, standards, and government data (recognition, not analogy). Beyond knowledge resources the named posture does not extend structurally: the tempting "open access to a forest" cases are a different prime family (a miscategorization on the shared word "open"), and what genuinely generalizes is the union of parents plus the one sharp move license_as_coordination. Stripped of jargon, "open availability" itself reduces toward a normative policy stance ("make knowledge available under explicit permissive terms") rather than a substrate-independent mechanism — which is exactly why its reach stays inside knowledge-resource governance. So the cross-domain reach belongs to license_as_coordination (with the transparency and mediator_availability_constraint parents); the disciplined move is to carry that coordination move wherever pre-declared permissive terms replace per-use negotiation, and reserve "open availability" for the four-commitment architecture over knowledge resources. It clears the domain-specific bar comfortably for knowledge-resource governance, but its only substrate-spanning content is already carried, in more general form, by the coordination move it instantiates and the parents it composes.

Relationships to Other Abstractions¶

Current abstraction Open Availability Domain-specific

Parents (1) — more general patterns this builds on

Open Availability is a kind of License as Coordination Prime

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

Not to Be Confused With¶

Mere availability. "The resource exists somewhere a user could reach it." This is exactly what open availability is not: a resource posted at a public URL and declared "available" fails the standard if downstream composition breaks for want of operative, permissive terms — the nominal-availability-without-substantive-openness failure mode. Tell: can a stranger machine-read, redistribute, and fold the resource into derivative work without negotiating (open availability), or is it merely posted somewhere (mere availability)?
Free of charge / gratis. A matter of price, not use terms. A gratis resource under a license forbidding reuse is not openly available, and a priced resource under permissive terms can be. The load-bearing question is what holders may do with the resource, not whether they paid. Tell: is the axis the cost of access (gratis) or the permissiveness of the reuse license (open availability)?
Transparency. Disclosure — the visibility of processes and decisions to stakeholders. Open availability concerns accessibility-for-use under explicit terms. A resource can be fully disclosed yet encumbered by a license that blocks reuse, so transparency does not entail composability. (Transparency is also one of the parents the posture composes.) Tell: is the concern making something visible (transparency) or making it reusable under terms (open availability)?
Open access to a commons (a forest, the airwaves). A commons-management problem governed by commons and tragedy_of_the_commons, where the resource is rivalrous and the failure mode is overuse. Open availability concerns non-rivalrous knowledge resources whose failure mode is gated reuse — the opposite structure. The shared word "open" hides that they belong to different prime families. Tell: does use deplete the resource, so the worry is overuse (commons), or is it infinitely copyable, so the worry is blocked reuse (open availability)?
Open source (specifically). The software substrate-instance of open availability, codified by the OSI Open Source Definition. It is one setting of the same four-part architecture, not the whole pattern, which also spans ontologies (OBO Foundry), data (FAIR), publications (Budapest/Bethesda/Berlin), and standards. Tell: is the resource specifically source code under an OSI-conforming license (open source), or the general governance posture across any knowledge-resource medium (open availability)?
License-as-coordination (the exportable parent move). The substrate-general core the posture instantiates — pre-declared permissive terms replacing per-use negotiation, dropping coordination cost toward zero and unlocking population-scale recombination — alongside transparency and mediator_availability_constraint. Open availability is the knowledge-governance realization; the coordination move is what travels. Tell: is the four-commitment architecture over knowledge resources the subject (open availability), or the bare "pre-declared terms replace per-use negotiation" lesson in any substrate (the parent move)? (Treated more fully in Structural Core vs. Domain Accent.)

Neighborhood in Abstraction Space¶

Open Availability sits in a moderately populated region (58^th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Trust Infrastructure for Shared Knowledge (6 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12