LOOM.
PUBLIC RESEARCH DOCUMENT · ONTOLOGY · v1.0

Project Loom Ontology

The core concepts Loom uses to study the gap between policy decisions and outcomes, including concept maturity and the rules for promotion.

Source: ONTOLOGY.mdRendered from the current repository document

Project Loom Ontology

Version: 1.0
Status: Working public reference
Purpose: Define the smallest necessary shared vocabulary for examining the gap between policy decisions and real-world outcomes.

Why an ontology?

Loom needs stable meanings for its central concepts. Without them, researchers may use the same word to describe different things, or treat different mechanisms as though they were the same. The ontology is a set of concepts and relationships to test against cases—not a claim that every concept is already empirically established.

The conceptual rule is: define the mechanism first, then examine whether the evidence in a case supports using that concept.

The core chain

Policy → Governance → Implementation → Outcome

The chain is an analytical guide, not a claim that governance is always linear. Feedback, legal challenge, institutional conflict, funding changes, and changing conditions can alter the pathway at multiple points.

Canonical concepts

The following six concepts form Loom's current core vocabulary.

CON-001 — Policy

A formal decision or directive by an authorized actor that states an intended course of action or outcome. A policy declaration is not the same as the work needed to carry it out.

Question: What was formally decided, by whom, and through which instrument?

CON-002 — Governance

The institutions, authorities, processes, rules, resources, and relationships through which collective decisions are made, implemented, monitored, and corrected.

Question: Which actors and institutions had authority, obligations, information, and decision rights?

CON-003 — Implementation

The administrative, legal, fiscal, technical, and human work required to turn a policy into operational reality. It includes procurement, staffing, rulemaking, delivery, enforcement, monitoring, and adaptation.

Question: What had to happen after the decision for the intended outcome to occur?

CON-004 — Governance Capacity

The ability of an institution or system to formulate, implement, administer, monitor, adapt, and sustain policy. Capacity varies by domain, institution, and time; it is not a simple yes/no property.

Question: Did the relevant institutions have the authority, skills, staffing, resources, information, and adaptive ability required?

CON-005 — Implementation Debt

The accumulated gap between the commitments a policy creates and the resources, capabilities, decisions, dependencies, or operational work needed to fulfill them. Debt may remain hidden until a deadline, shock, or implementation bottleneck exposes it.

Question: What necessary work or capacity was assumed, deferred, unfunded, or left unresolved?

CON-006 — Dependency Chains

The sequence of actors, decisions, resources, systems, permissions, and conditions that must connect for implementation to proceed. A blocked or fragile dependency can prevent later steps even when the policy itself remains formally in force.

Question: What must happen first, who controls it, and what happens if that link fails?

Supported concepts and working candidates

Loom distinguishes a concept's place in the ontology from how much empirical support it has.

Supported concepts currently include:

These are working classifications, not universal laws. Their scope and evidence should be examined in each case.

Candidate concepts remain hypotheses or developing analytical distinctions, including:

Candidate status means “worth investigating,” not “established fact.”

Concept promotion rules

Concept maturity must follow accumulated research rather than rhetorical confidence:

  1. Observation: a pattern or distinction is noticed and recorded.
  2. Candidate: a concept is defined clearly enough to test in at least one case.
  3. Supported: evidence from at least three diverse cases supports its usefulness and boundaries.
  4. Canonical: evidence spans at least five cases and three domains, with peer review and demonstrated predictive value under the current promotion rule.

A concept should not be promoted solely because it is intuitive, appears in many notes, or has been used in a public explanation. Negative cases and alternative explanations matter.

How concepts are used in a case

For each proposed concept, a researcher should record:

The concept should be revised or rejected if case evidence repeatedly fails to distinguish it from neighboring concepts or if its explanatory value does not survive comparison.

What this ontology does not claim

The ontology does not, by itself, prove a causal explanation, score a government, or establish that a policy failed. It supplies shared terms for research. Claims about a real case require retrieved evidence, scoped statements, contradiction analysis, and review under Loom's research protocol.

The detailed working ontology remains versioned in the repository. This public page presents the current core vocabulary and its maturity rules in a form readers can inspect without navigating internal research notes.