◈ Root-LD Federation Document

The Federation

Registered domains, entity classes, and cross-domain intelligence

Spec Version
1.0
Domains
5 Registered
Entity Classes
15 Defined
Status
ACTIVE
§ 1

What Is The Federation

#what-is-federation

The Federation is the full connected graph across all Root-LD registered domains. It is not a single database. It is not a centralized system. It is a collection of independently operated domains that conform to a shared specification — the Root-LD Specification v1.0 — and produce entities that are structurally compatible, semantically linkable, and permanently identifiable across domain boundaries.

Every entity minted in any registered domain carries the same anchor layer. Every anchor layer points back to root-ld.org as the governing specification. Every edge in the Recursive layer can cross domain boundaries because every entity shares the same federationId format, the same entityClass taxonomy, and the same edge taxonomy.

When the federation is mature — when the corpus is large, the lexicon is rich, and the passes have run multiple times — what exists is a machine-readable map of American public infrastructure, law, economics, business, and procurement, organized by a proprietary schema, connected by semantically-confirmed edges, navigable by any crawler, and reasoned about by a model fine-tuned specifically on the relationships within it. That is not a collection of websites. That is infrastructure.

Registered Domains
5
Founding federation members. Each conforms to Root-LD v1.0.
Entity Classes
15
Defined at the federation level. New classes require spec amendment.
Edge Taxonomy
20
Defined relationship types spanning all domains and all entity classes.
§ 2

Registered Domains

#registered-domains

Each registered domain has a profile defining its primary entity classes, its lexicon contribution, its schema extensions, and its relationship to all other domains in the federation. Domains are registered at the federation level — at root-ld.org — before any entities are minted under them.

oakmorel.com Primary Member
Focus Forensic intelligence, procurement forensics, platform integrity, public infrastructure data
Lexicon Procurement terminology, forensic methodology, legal citations, government entity hierarchy
Domain Code OM
Primary Classes
STATUTE REGULATION BID CONTRACT ENTITY ECONOMIC PERSON ORGANIZATION
rankwithme.ai Primary Member
Focus Semantic search, entity-first business profiles, knowledge graph construction, AI-assisted content intelligence
Lexicon Search terminology, schema vocabulary, AI methodology, local business taxonomy, SEO technical vocabulary
Domain Code RW
Primary Classes
WEBPAGE RESEARCH DEFINITION DATASET ORGANIZATION PERSON
recursiveengineoptimization.com Primary Member
Focus Recursive reasoning, knowledge graph theory, LLM methodology, AI epistemology
Lexicon AI/ML terminology, graph theory, epistemology, model architecture vocabulary
Domain Code REO
Primary Classes
RESEARCH DEFINITION WEBPAGE DATASET
franklinsledger.com Primary Member
Focus Financial intelligence, economic data, fiscal analysis, public spending records
Lexicon Financial terminology, accounting vocabulary, economic indicators, fiscal period taxonomy
Domain Code FL
Primary Classes
ECONOMIC DATASET ORGANIZATION EVENT
root-ld.org ◈ Specification Home
Focus The specification itself. The authoritative home of the Root-LD standard. Every other domain references root-ld.org as the governing specification source.
Lexicon The federation lexicon lives here. All domain lexicon contributions are reviewed and published at root-ld.org before becoming active in cross-domain edge-building.
Domain Code RLD
Primary Classes
DEFINITION RESEARCH
§ 3

Entity Classes

#entity-classes

Entity classes are defined at the federation level. Every entity minted in any domain must declare one of these classes. The class determines which body fields are required, which edge types apply, and how the entity participates in federation passes. New classes require a specification amendment — they cannot be invented at the domain level.

Class Registry — v1.0

15 DEFINED CLASSES
Class
Domains
Description
STATUTE
OM
Federal and state legislation. Includes USC, CFR, state codes, and constitutional provisions. Requires citationFormal, bodyText, regulatoryAuthority.
REGULATION
OM
Agency rules, federal register entries, state regulatory guidance. Same schema as STATUTE with regulatoryAuthority required.
BID
OM
Public procurement solicitations. Requires solicitationNumber, issuingAgency (federationId), naicsCode, responseDeadline, estimatedValue.
CONTRACT
OM
Awarded procurement contracts. Extends BID schema with awardedTo (federationId), awardAmount, contractType.
ENTITY
OM
Government agencies, departments, districts, and public bodies. Hierarchical — parentEntity and childEntities are federationIds enabling the full government org chart.
ECONOMIC
OM FL
Economic indicators, public spending data, fiscal period statistics. Requires indicatorCode, issuingAgency, reportingPeriod, value, unit.
WEBPAGE
RW REO
Structured representations of web entities. Includes business profiles, service pages, and content entities with full schema.org compatibility.
RESEARCH
RW REO
Academic papers, technical reports, methodology documents, and structured analysis. Requires primarySource, authors, publicationDate.
CASE
OM
Legal cases, court decisions, administrative rulings. Requires bodyText (full decision text), citationFormal, jurisdiction, court name.
DEFINITION
RW REO RLD
Canonical term definitions drawn from the federation lexicon. The lexicon itself is a collection of DEFINITION entities. Includes the term, its definition, its domain of origin, and all federation contexts in which it appears.
PERSON
OM RW
Named individuals in a federation context — government officials, business principals, signatories. Linked to ORGANIZATION entities via federationId.
ORGANIZATION
OM RW FL
Private companies, nonprofits, and business entities. Distinct from ENTITY (public bodies). Includes EIN, UEI, DUNS for cross-system deduplication. Used for business profiles in rankwithme.ai.
JURISDICTION
OM
Geographic and legal jurisdictions. Federal, state, county, municipal. Normalized across the federation so all entities can share jurisdiction edges without custom mapping.
DATASET
RW REO FL
Structured data collections. Government open data releases, research datasets, economic data series. Requires schema describing the data structure, source, and update frequency.
EVENT
FL
Time-bounded occurrences — fiscal year closings, regulatory deadlines, procurement cycles, economic reporting periods. Linked to affected ENTITY, STATUTE, and ECONOMIC entities.
§ 4

Cross-Domain Intelligence

#cross-domain

The federation's intelligence does not live in any single domain. It emerges from the edges between domains. A statute on oakmorel.com, a business profile on rankwithme.ai, an economic indicator on franklinsledger.com, and a methodology definition on recursiveengineoptimization.com are four separate entities on four separate domains. When they share lexicon terms, jurisdiction, or confirmed semantic overlap, they become connected — and the connection makes each one more valuable than it was alone.

Edge Density — The Primary Metric

COMPOUNDING

The power of the federation is measured not by the number of entities but by the density of cross-domain edges. Every cron run, every new entity ingested, every pass increases edge density.

Cross-Domain Edge Example

OM-STATUTE-7x9k2m        ───GOVERNS──────────►   OM-BID-3a8f1b
15 U.S.C. § 1                                        FA8501-26-R-0001
Sherman Antitrust Act       ◄──GOVERNS-INVERSE───   Federal Contract
                                                             
        │ TOPICALLY-RELATED                        ISSUED-BY │
                                                             
RW-ORGANIZATION-9c2d4e   ───REFERENCED-BY────►   OM-ENTITY-af7b2c
Business Profile                                     Federal Agency
rankwithme.ai                                         oakmorel.com
        
        │ JURISDICTIONALLY-RELATED
        
FL-ECONOMIC-2b7e9a
Economic Indicator
franklinsledger.com
◈ Edge Density Rule
A graph with 10,000 entities and 1,000 cross-domain edges is less powerful than a graph with 1,000 entities and 10,000 cross-domain edges. Edge density is the metric that matters. The graph compounds.

Compound Reasoning

THE EMERGENT PROPERTY

Compound Reasoning is the property of a mature federation where every new entity added to any domain immediately increases the intelligence of the entire graph. It emerges because the Recursive layer runs across the full corpus — a new entity on rankwithme.ai is immediately available for edge-building against every existing entity across all five domains.

root-ld.org
Spec v1.0 — Anchor for all domains
Specification Layer
oakmorel.com
rankwithme.ai
franklinsledger.com
Cross-Domain Edges
oakmorel.com
recursiveengineoptimization.com
rankwithme.ai
Pass 1 — Deterministic
Pass 2 — Lexical
Pass 3 — Semantic-LLM
Pass 4 — Finetuned
Federation Passes

When an AI system retrieves from this graph it does not find pages. It finds entities with confirmed relationships to other entities across five domains. When it answers a question about procurement fraud it finds the statute that governs it, the agency that enforces it, the bid types it applies to, the economic indicators that correlate with it, and the forensic methodology that detects it — all connected by edges confirmed by a model that understands this specific domain better than any general-purpose model. The fine-tuned model — The Lexicon Model — is the moat.

§ 5

Joining The Federation

#joining

New domains can be registered in the federation. Registration is a federation-level decision made at root-ld.org. A domain that wishes to join must conform to the Root-LD specification in full — there are no partial implementations. The anchor layer is non-negotiable. The immutability rules apply from the first entity minted.

Domain Registration Requirements Required Before First Entity
01
Conform to Root-LD v1.0. The full specification — all three layers, all anchor fields, all governance rules. No partial implementations. No field omissions in the anchor layer.
02
Register a domain code. A short unique identifier used as the prefix in all federationIds minted under this domain. Must not conflict with existing domain codes.
03
Declare primary entity classes. Which of the 15 defined entity classes this domain will mint. Class-specific body fields must be implemented in full for each declared class.
04
Contribute to the lexicon. Submit domain-specific vocabulary terms to the federation lexicon at root-ld.org for review. Approved terms become available for cross-domain lexical edge-building across the full corpus.
05
Reference root-ld.org as the governing specification. Every entity minted in the domain carries specVersion in the anchor layer pointing to the Root-LD version it was generated under. The domain's own documentation must reference root-ld.org as the source specification.
◈ On Adoption
The federation does not need broad external adoption to be valuable. The value is in edge density, not entity count. The founding five domains — operating at scale, running the passes, growing the lexicon, and fine-tuning the Lexicon Model — produce compound reasoning that no external system can replicate. Adoption by adjacent domains becomes inevitable when the federation's intelligence is demonstrably superior to any standalone alternative. The openness of the specification is the invitation. The quality of the graph is the pull.