The Interdependency is an independent research and software organization building testable systems across agent architecture, formal geometry, measurement, metadata, language representation, and cross-domain research.

The work is organized around explicit authority boundaries: repositories own their own claims, implementations, evidence, and limitations. Composition does not silently transfer proof, empirical validity, security standing, or semantic authority.

• a0 — persistent-agent and multi-model research instrument.
• skill-lib — reusable agent skills and MSDMD native-first metadata tooling.
• stack — composition forge for pinned repositories, cross-system research, falsification, and project graduation.
• UCNS — exact geometric constructions, including Public Gonol carriers and framed Möbius motion.
• EDCM — measurement and evaluation research with provenance-preserving result contracts.
• EPAC — elementary/particle-scale energy-and-arity coupling research with explicit falsification boundaries.
• METAPAT — semantic authority for cross-domain structural comparison and constrained terminology transfer.
• UCHC — Unit Circle Hyperspace Constructs for human and programming-language representations.
• interdependentway.org — public-facing doctrine, research, projects, and builder-maintained documentation.

No repository is authoritative merely because another repository consumes it.

• METAPAT owns its semantic framework.
• UCNS owns its geometric constructions and their proof/status boundaries.
• EDCM owns measurement and evaluation contracts.
• skill-lib owns reusable agent/build/evidence procedures.
• Stack composes exact pinned views for cross-repository research without taking over their authority.
• Independent projects graduate from research only when their own repository, verification, release, and reconsumption boundaries are established.

The repository README is the first authority for the current scope and status of each project.

Research and software are developed with:

• explicit assumptions and nonclaims;
• reproducible tests, receipts, and provenance where available;
• preservation of negative results;
• separation of implemented behavior from demonstrated usefulness;
• separation of mathematical construction from empirical validation;
• explicit hmmm boundaries where evidence or authority remains unresolved.

Multiple AI systems may participate as computational, drafting, adversarial, and review tools. They do not become source authority by participation.

Before depending on a repository:

1. read its current README.md and governing instructions;
2. check its license and release status;
3. distinguish stable implementation from research candidates;
4. inspect the tests or evidence that support the claim you care about; and
5. preserve any stated nonclaims or unresolved boundaries.

Forks, archives, experiments, and historical repositories remain visible when they carry useful provenance. Their presence does not make them canonical.

The Interdependency is founded and built by Erin Spencer.

The public map is intentionally an entrance, not a dump of the entire working graph.