RankWithMe.ai

◈ ROOT-LD SPECIFICATION — IMMUTABLE DOCUMENT

Root-LD — Federated Semantic Linked Data Specification

Version1.0

StatusPUBLISHED

Authored2026-02-28

Homeroot-ld.org

Domains5 Registered

Entity Classes15 Defined

Edge Types20+

Root-LD is a federated semantic linked data specification for organizing, anchoring, and connecting machine-readable knowledge across multiple domains. It is designed to function the way biological cognition functions — not through a single centralized intelligence but through distributed processing units synchronized to a shared anchor frequency.

Every entity in a Root-LD federation carries the same root wrapper regardless of domain, type, or content. The root never changes. The content beneath it does. The edges between entities emerge from the data over time through deterministic, lexical, and semantic passes.

The result is a knowledge graph that grows more intelligent as it grows larger — because every new entity added to any domain in the federation immediately becomes available for edge-building against every existing entity across all domains.

Root-LD is a semantic architecture for federated knowledge. It is not a content management system. It is not a database schema. It is not an SEO framework. It produces all three as byproducts of the architecture.

§1 The Three Layers #part-one

Every Root-LD entity consists of exactly three layers stacked in fixed order. The layers never reorder. The layers never merge. Each layer has a specific function and a specific set of fields. Fields are defined at the specification level and populated from data. None are invented at the entity level.

ANCHOR — Root-LD Identity

Identity and provenance · Fixed across all entities, all domains, all time

FIXED UNIVERSAL IMMUTABLE FIELDS

BODY — Content Layer

Domain-specific · Entity-class-specific · Populated from data

DOMAIN-SPECIFIC CLASS-SPECIFIC VERSIONED

RECURSIVE — Edge Layer

Edges and semantic relationships · Not populated at ingestion · Grows over time

ACCUMULATIVE BUILT BY PASSES COMPOUNDS

A consuming system — a crawler, a language model, an API client — enters an entity and finds three distinct zones. The anchor tells it who this entity is and where it came from. The body tells it what this entity contains. The recursive layer tells it how this entity relates to every other entity in the federation that has been connected to it through confirmed semantic passes.

The recursive layer does not exist at ingestion. It is earned. An entity minted today has an empty recursive layer. An entity that has been in the federation through multiple pass cycles has a recursive layer dense with confirmed cross-domain edges. That difference is the compounding.

§2 Layer One — Anchor #anchor-layer

The anchor layer is fixed across all entities, all domains, all time. Its purpose is to make every entity in the federation uniquely identifiable, verifiable, traceable to its primary source, and locatable within the federation hierarchy. The only field that varies between domains is the domain signature. Every other field is universal or derived deterministically from the entity's properties at ingestion.

FIELD	REQ	MUTABILITY	DESCRIPTION
specVersion	REQUIRED	IMMUTABLE	Root-LD spec version this entity was generated under. Current value: 1.0. Allows future parsers to correctly interpret historical entities.
federationId	REQUIRED	IMMUTABLE	Globally unique identifier across the entire federation. Format: {domainCode}-{entityClass}-{hash}. Example: OM-STATUTE-7x9k2m. Generated at ingestion. Never changes.
domainSignature	REQUIRED	IMMUTABLE	The registered domain this entity belongs to. The one anchor field that varies between entities across different domains. New domains registered at federation level before any entities are minted.
entityClass	REQUIRED	FIXED	Broad entity category defined at federation level. 15 defined classes. New classes require specification amendment. Values: STATUTE · REGULATION · BID · CONTRACT · ENTITY · ECONOMIC · WEBPAGE · RESEARCH · CASE · DEFINITION · PERSON · ORGANIZATION · JURISDICTION · DATASET · EVENT
entitySubclass	REQUIRED	FIXED	Domain-specific subtype. Allows domain granularity without polluting the federation-level class taxonomy. Example under STATUTE: FEDERAL-USC · FEDERAL-CFR · STATE-CODE
primarySource	REQUIRED	IMMUTABLE	Canonical URL of the original source document. Must be public, verifiable, and persistent. An entity without a verifiable primary source cannot be minted.
sourceVerified	REQUIRED	MUTABLE	Boolean. Primary source verified at ingestion. Entities with sourceVerified: false are excluded from edge-building passes until verified.
dateIngested	REQUIRED	IMMUTABLE	ISO 8601. When this entity was first created in the federation. A permanent historical fact.
dateLastVerified	REQUIRED	MUTABLE	ISO 8601. When the primary source was last successfully fetched and content confirmed. Updated by cron.
dateModified	REQUIRED	MUTABLE	ISO 8601. When the underlying source content last changed. This is not when the publishing domain updated the page — this is when the source changed.
contentHash	REQUIRED	MUTABLE	Hash of body content at last verification. Detects changes between cron runs without full content fetch. Hash change triggers entity flagging for regeneration.
humanVerified	REQUIRED	MUTABLE	Boolean. Has a human reviewed and confirmed this entity. False by default. High-stakes classes — STATUTE, REGULATION, CASE — prioritized for human verification.
generationMethod	REQUIRED	IMMUTABLE	How body content was produced. Values: DETERMINISTIC · LLM-ASSISTED · LLM-GENERATED · HUMAN-AUTHORED. Critical for trust scoring and disclosure.
disclosureStatement	CONDITIONAL	FIXED	Plain-language statement of how this entity was produced. Required when generationMethod is LLM-ASSISTED or LLM-GENERATED. Null for HUMAN-AUTHORED and DETERMINISTIC.

ANCHOR EXAMPLE — JSON

◈ LAYER ONE — ANCHOR — OM-STATUTE-7x9k2m

// Root-LD Anchor — Layer One
"specVersion":         "1.0",
"federationId":        "OM-STATUTE-7x9k2m",
"domainSignature":     "oakmorel.com",
"entityClass":         "STATUTE",
"entitySubclass":      "FEDERAL-USC",
"primarySource":       "https://uscode.house.gov/view.xhtml?req=15+U.S.C.+1",
"sourceVerified":      true,
"dateIngested":        "2026-02-28T00:00:00Z",
"dateLastVerified":    "2026-02-28T12:00:00Z",
"dateModified":        "1890-07-02T00:00:00Z",
"contentHash":         "sha256:a1b2c3d4e5f6...",
"humanVerified":       false,
"generationMethod":    "LLM-ASSISTED",
"disclosureStatement": "This summary was generated by an automated
                         machine intelligence system. It is not a legal
                         interpretation. The original source text is
                         preserved verbatim below."

§3 Layer Two — Body #body-layer

The body layer is domain-specific and entity-class-specific. This is where the actual data lives. Body schemas are defined per entity class at the domain level but must conform to federation-level field naming conventions — so cross-domain edge-building can operate on shared field names without custom parsers for every domain.

UNIVERSAL BODY FIELDS — ALL ENTITIES

FIELD	REQ	DESCRIPTION
name	REQUIRED	Canonical human-readable name. The official title — not a description of the content.
description	REQUIRED	Concise machine-readable description of what this entity is. A description of the entity itself. "The First Amendment to the United States Constitution." — not a summary of what it says.
summary	CONDITIONAL	Plain English summary. Required for STATUTE and REGULATION. When present must be accompanied by disclosureStatement in the anchor layer.
bodyText	CONDITIONAL	Verbatim source text. Required for STATUTE, REGULATION, CASE, DEFINITION. Never modified by LLM passes. Does not change unless the primary source changes.
jurisdiction	REQUIRED	Legal or administrative jurisdiction. Hierarchical — Federal, State, County, Municipal. Normalized across the federation for cross-domain jurisdiction edges without custom mapping.
effectiveDate	REQUIRED	ISO 8601. When this entity became effective.
expirationDate	OPTIONAL	ISO 8601. When this entity expires or is superseded. Null for permanent entities.
status	REQUIRED	Current status updated by cron. Values: ACTIVE · SUPERSEDED · EXPIRED · PENDING · REPEALED · DRAFT
identifiers	REQUIRED	Array of all known identifiers across different systems. Enables cross-system deduplication. For statutes: USC citation, Public Law number, Statutes at Large citation.
tags	REQUIRED	Array of controlled vocabulary terms from the federation lexicon. Shared tags across entities are candidates for lexical edges in Pass Two.

CLASS-SPECIFIC BODY FIELDS — SELECTED CLASSES

◈ STATUTE / REGULATION

"citationFormal":       "15 U.S.C. § 1",
"citationInformal":     "Sherman Antitrust Act Section 1",
"amendmentHistory":     [ array of dates and descriptions ],
"relatedStatutes":      [ array of federationIds ],
"regulatoryAuthority":  "Federal Trade Commission",
"penaltyProvisions":    true,
"procurementRelevance": false

◈ BID / CONTRACT

"solicitationNumber":   "FA8501-26-R-0001",
"issuingAgency":        "OM-ENTITY-af7b2c",   ← federationId
"naicsCode":            "541330",
"setAsideType":         "SDVOSB",
"estimatedValue":       4200000,
"responseDeadline":     "2026-04-15T17:00:00Z",
"awardedTo":            null,
"awardAmount":          null,
"contractType":         "FIXED-PRICE"

◈ ENTITY — GOVERNMENT AGENCY

"entityType":           "Federal Agency",
"parentEntity":         "OM-ENTITY-...",     ← federationId
"childEntities":        [ array of federationIds ],
"geographicScope":      "National",
"budgetAuthority":      120000000000,
"programAreas":         [ array ],
"procurementHistory":   [ array of federationIds ]

◈ ECONOMIC

"indicatorName":        "Consumer Price Index — All Urban Consumers",
"indicatorCode":        "CUUR0000SA0",
"issuingAgency":        "U.S. Bureau of Labor Statistics",
"reportingPeriod":      "2026-01",
"value":                315.8,
"unit":                 "Index (1982-84=100)",
"priorPeriodValue":     314.2,
"methodology":          "https://www.bls.gov/cpi/methodology.htm"

§4 Layer Three — Recursive #recursive-layer

The edge layer. Recursive-LD is not populated at ingestion. It grows over time through four sequential passes run against the full corpus. It is called Recursive-LD because each pass uses the output of prior passes as input — the graph reasons about itself using its own accumulated confirmed relationships as context.

The full Recursive-LD specification — covering the two-mode architecture for Entity Intelligence and Cognitive Telemetry, the complete field schema, and the Escher Defense research pipeline — is published at recursive-ld.org.

EDGE OBJECT STRUCTURE

FIELD	TYPE	DESCRIPTION
targetId	string	The federationId of the entity this edge points to.
targetDomain	string	The domain signature of the target entity.
edgeType	string	The type of relationship. Drawn from the federation edge taxonomy.
confidence	float	0.0 to 1.0. Confidence in this relationship. Deterministic edges are always 1.0.
confirmationMethod	string	Values: DETERMINISTIC · LEXICAL · SEMANTIC-LLM · SEMANTIC-FINETUNED · HUMAN-CONFIRMED
dateEstablished	ISO 8601	When this edge was first recorded.
dateLastConfirmed	ISO 8601	When this edge was last validated.
bidirectional	boolean	Does the target entity carry a corresponding edge back to this entity.
weight	float	Relative strength of this relationship against other edges from this entity. Updated as new edges are added.

THREE-LAYER ENTITY DOCUMENT — JSON-LD

◈ COMPLETE ENTITY DOCUMENT — THREE-LAYER @GRAPH

{
  "@context": "https://root-ld.org/context.jsonld",
  "@graph": [
    {
      // Layer One — Anchor-LD (immutable)
      "@type":              "rld:AnchorEntity",
      "rld:specVersion":    "1.0",
      "rld:federationId":   "RW-ORGANIZATION-9c2d4e",
      "rld:domainSignature":"rankwithme.ai",
      "rld:entityClass":    "ORGANIZATION",
      "rld:dateIngested":   "2026-03-01T00:00:00Z"
    },
    {
      // Layer Two — Body-LD (versioned)
      "@type":              "rld:BodyEntity",
      "schema:name":        "Barbara's Bakery",
      "schema:description": "Independent artisan bakery in San Diego, CA.",
      "schema:url":         "https://barbarasbakery.com"
    },
    {
      // Layer Three — Recursive-LD (accumulative)
      "@type":              "rld:RecursiveEdge",
      "rld:edgeType":       "MEMBER_OF",
      "rld:targetId":       "RLD-DEFINITION-federation",
      "rld:targetDomain":   "root-ld.org",
      "rld:confidence":     1.0,
      "rld:pass":           "deterministic",
      "rld:timestamp":      "2026-03-01T00:00:00Z"
    }
  ]
}

§5 The Four Passes #federation-passes

Edges in the recursive layer are built by four sequential passes. The passes are additive — later passes build on earlier ones but do not replace them. Confidence scores are written per edge per pass. The four-pass model is not sequential ranking. It is layered epistemic resolution. A deterministic edge and a fine-tuned semantic edge can coexist on the same entity pair with different confidence scores and different edge types. The graph holds them both.

PASS	METHOD + CONFIDENCE	DESCRIPTION
01	Deterministic CONF: 1.0	Exact identifier matches. If a bid's issuingAgency matches a directory entity's federationId, an ISSUED-BY edge is created at confidence 1.0. No LLM. No ambiguity. Pure data. Runs at ingestion for every new entity.
02	Lexical CONF: 0.70–0.90	The federation lexicon runs against every entity's bodyText and summary. Shared vocabulary density above threshold creates LEXICALLY-RELATED edges at confidence proportional to density. A bakery with health code references and supplier relationships receives lexical edges to regulatory entities on OakMorel. Language carries the signal. The lexicon reads it.
03	Semantic-LLM CONF: 0.50–0.85	Entity pairs above the lexical threshold but below confidence 0.70 go to local LLM inference. Entity summaries and proposed edge type go in. Confidence and rationale come out. Above 0.70 the edge is recorded with rationale stored as metadata. Every confirmed rationale becomes training data for Pass Four.
04	Semantic-Finetuned CONF: 0.75–0.95	Same architecture as Pass Three on a model fine-tuned on confirmed edges and rationales from all prior passes. Runs quarterly as corpus reaches training density. Finds relationships the base model misses — specific to the federation's domain vocabulary and conceptual structure. Final authority on contested edges. The pass that makes the graph proprietary.

§6 Edge Taxonomy #edge-taxonomy

The full set of defined relationship types across the federation. Edge types outside this taxonomy cannot be created without a specification amendment. New edge types require declaration of domain, minimum confidence, and directionality.

UNIVERSAL EDGE TYPES — ALL DOMAINS

EDGE TYPE	DIRECTION	MIN CONF	DESCRIPTION
PARENT_OF	DIRECTED	0.90	Hierarchical containment. Source structurally contains or governs target.
CHILD_OF	DIRECTED	0.90	Inverse of PARENT_OF.
MEMBER_OF	DIRECTED	0.95	Federation membership or group affiliation. Source belongs to target collective.
COMPOSED_OF	DIRECTED	0.85	Component composition. Target entities are constituent parts of source.
REFERENCES	DIRECTED	0.80	Source explicitly references or cites target.
CITED_BY	DIRECTED	0.80	Inverse of REFERENCES.
COEXISTS_WITH	UNDIRECTED	0.65	Entities occupy the same ecosystem layer without hierarchical relationship.
COMPLEMENTS	UNDIRECTED	0.65	Entities are functionally additive — each extends the value of the other.
GROUNDS	DIRECTED	0.75	Source provides epistemic foundation or evidentiary basis for target's claims.
EXTENDS	DIRECTED	0.70	Source builds on and expands the knowledge scope of target.
INSTANTIATES	DIRECTED	0.80	Source is a concrete instance or implementation of the abstract target.
PRECEDES	DIRECTED	0.85	Source chronologically or logically precedes target.
SUCCEEDS	DIRECTED	0.85	Source follows from target temporally or causally.
EVOLVES_FROM	DIRECTED	0.75	Source is a transformed version of target over time.
RECORDS	DIRECTED	0.80	Source is a temporal log or persistent record of target's state.
TOPICALLY-RELATED	UNDIRECTED	0.70	Significant topical overlap confirmed by semantic pass.
LEXICALLY-RELATED	UNDIRECTED	0.65	Significant shared vocabulary from the federation lexicon.

DOMAIN-SPECIFIC EDGE TYPES — OM (oakmorel.com)

EDGE TYPE	DOMAIN	DESCRIPTION
GOVERNS	OM	A statute or regulation governs an entity, process, or procurement type.
GOVERNS-INVERSE	OM	A process or entity is governed by a statute.
ISSUED-BY	OM	A bid or contract was issued by a government entity.
ISSUED-BY-INVERSE	OM	A government entity issued this bid or contract.
SUPERSEDES	OM	This entity replaces a prior entity.
SUPERSEDED-BY	OM	This entity was replaced by a newer entity.
AMENDS	OM	This entity modifies another entity.
AMENDED-BY	OM	This entity was modified by another entity.
ENFORCED-BY	OM	This statute or regulation is enforced by this agency.
ENFORCES	OM	This agency enforces this statute or regulation.
FUNDS	OM	This economic data or budget line funds this entity or program.
FUNDED-BY	OM	This entity is funded by this economic allocation.
JURISDICTIONALLY-RELATED	OM	Two entities share a jurisdiction.
FORENSICALLY-RELEVANT	OM	Connects public law and procurement data to forensic intelligence service relevance.
CITED-IN	OM	This statute or case is cited in this document.
CITES	OM	This document cites this statute or case.

CROSS-DOMAIN EDGE EXAMPLE

◈ FIVE ENTITIES · FOUR DOMAINS · FIVE CONFIRMED EDGE TYPES

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

Four entities. Four domains. Five confirmed edge types. One traversal path connecting a statute to a procurement contract to a business profile to a federal agency to an economic indicator — all through edges confirmed by the federation passes, all navigable by any crawler, all available to any AI system reasoning about procurement, compliance, or federal contracting.

§7 Federation Architecture #part-two

REGISTERED DOMAINS — v1.0

CODE	DOMAIN + ROLE	PRIMARY CLASSES
RLD	root-ld.org Specification authority. Governing document, lexicon, and domain registry.	DEFINITIONRESEARCH
OM	oakmorel.com Forensic intelligence. Government, law, procurement, public infrastructure.	STATUTEREGULATIONBIDCONTRACTENTITYECONOMIC
RW	rankwithme.ai Semantic search. Entity-first business profiles. Knowledge graph construction.	WEBPAGERESEARCHDEFINITIONDATASETORGANIZATION
REO	recursiveengineoptimization.com Recursive reasoning. Knowledge graph theory. Layer Three specification home.	RESEARCHDEFINITIONWEBPAGE
FL	franklinsledger.com Financial intelligence. Economic data. Fiscal analysis.	ECONOMICDATASETORGANIZATION

ENTITY CLASS REGISTRY — 15 DEFINED CLASSES

STATUTE

Federal and state legislation. Requires citationFormal, bodyText, regulatoryAuthority.

REGULATION

Agency rules and federal register entries. Same schema as STATUTE.

BID

Public procurement solicitations. Requires solicitationNumber, issuingAgency, estimatedValue.

CONTRACT

Awarded procurement contracts. Extends BID with awardedTo, awardAmount, contractType.

ENTITY

Government agencies, departments, districts. Hierarchical via parentEntity and childEntities.

ECONOMIC

OM · FL

Economic indicators and public spending data. Requires indicatorCode, value, unit.

WEBPAGE

RW · REO

Structured web entity representations with full schema.org compatibility.

RESEARCH

RW · REO

Academic papers, technical reports, methodology documents.

CASE

Legal cases, court decisions, administrative rulings. Requires full decision bodyText.

DEFINITION

RW · REO · RLD

Canonical term definitions from the federation lexicon.

PERSON

OM · RW

Named individuals — officials, business principals, signatories.

ORGANIZATION

OM · RW · FL

Private companies, nonprofits, business entities. Includes EIN, UEI, DUNS.

JURISDICTION

Geographic and legal jurisdictions normalized across the federation.

DATASET

RW · REO · FL

Structured data collections with schema describing structure, source, update frequency.

EVENT

Time-bounded occurrences — fiscal closings, regulatory deadlines, procurement cycles.

§8 Governance #part-three

IMMUTABILITY — FOUR FIELDS · NON-NEGOTIABLE

federationIdThe entity's permanent identity in the graph. Cannot be changed under any circumstance. An entity requiring a different identifier must be deprecated and a new entity minted. This ensures any external system that has recorded a federationId can always resolve it and trust what it finds.

dateIngestedThe moment of creation in the federation is a permanent historical fact. Immutable.

domainSignatureAn entity's domain cannot change after minting.

primarySourceThe source document that gave rise to this entity is a permanent fact. Mint a new entity if the source changes.

Deprecation Protocol

Entities are never deleted. They are deprecated. A deprecated entity receives status: SUPERSEDED or status: EXPIRED, a supersededBy field pointing to the new entity's federationId, and is retained in the graph permanently. Any external citation resolves to a page explaining what superseded it and where the current version lives.

Version Control

Spec version recorded in every entity's anchor layer. Existing entities retain their original spec version. Forward compatibility: a parser for v2.0 reads a v1.0 entity without modification. Unknown fields: a v1.0 parser ignores fields it does not recognize in a v2.0 entity.

The Lexicon

Living document maintained at root-ld.org. Shared vocabulary across all domains — the bridge that makes lexical edge-building possible. Every domain contributes terms. Terms reviewed before inclusion. The lexicon is itself a Root-LD entity — a DEFINITION class object with its own federationId, edges, and version history.

New Classes + Edge Types

Entity classes and edge types defined at the federation level cannot be invented at the domain level. New classes require a specification amendment. New edge types require declaration of domain, minimum confidence threshold, and directionality before any edges of that type can be created.

§9 — WHAT THIS PRODUCES

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, 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.

An AI system retrieving from this graph does not find pages. It finds entities with confirmed relationships to other entities across multiple 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.

That is infrastructure.
The specification that defines it is this document.

APP Canonical Naming #appendix

Terms used within the Root-LD specification and across all federation domains. These names are not abbreviated. They are not synonymized.

TERM	DEFINITION
Root-LD	The name of the format and specification.
Anchor	Layer One. Identity and provenance. Fixed across all entities.
Body	Layer Two. Content and domain-specific data.
Recursive	Layer Three. Edges and relationships. Grows over time.
Federation Passes	The four sequential passes that populate the Recursive layer.
The Lexicon Model	The fine-tuned model trained on confirmed federation edges. Runs Pass Four.
The Federation	The full connected graph across all registered domains.
Compound Reasoning	The property where each new entity added to any domain immediately increases the intelligence of the entire graph.

Root-LD Specification Version 1.0 · Authored 2026-02-28 · Published at root-ld.org · All federation domains conform to this specification ◈ IMMUTABLE DOCUMENT

◈ ALL PAGES

ABOUT KANJI LARRYBRIN SCHEMA SPECIFICATION LEXICON AI SAFETY LIVE PROGRESS FEDERATION DIRECTORY KANJI BOT

SYSTEM STATUS

PageSPECIFICATION

DocumentRoot-LD v1.0

StatusPUBLISHED

Authored2026-02-28

Homeroot-ld.org

Layers3

Passes4

Entity Classes15

Edge Types20+

Domains5 Registered

Immutable Fields4

DeletionsNEVER

Backward CompatGUARANTEED

↑↓ : Scroll ENTER : Select ESC : Exit

Build: 2026-PROD Method: ENTITY-FIRST Status: OPERATIONAL

Structure before ads. Always.