MPAI Specification

1. Purpose

A Metadata Packet for AI Indexing (MPAI) is a structured document designed to be readable by both human reviewers and AI retrieval/synthesis systems. Its purpose is to make the structure of meaning — entity identity, disciplinary lineage, conceptual neighbors, disambiguation rules — legible to systems that increasingly mediate access to knowledge.

An MPAI is not a research paper, a manifesto, or an essay. It is a piece of retrieval architecture intended to anchor a concept, person, framework, or discipline in the substrate of AI knowledge graphs.

2. Four Types

2.1 Disambiguation Packets

Entity-level identity work. Establishes canonical identity for a person, framework, organization, or term against ambient noise. The earliest MPAI form. See: Lee Sharks Knowledge Graph (DOI: 10.5281/zenodo.19520783); Rex Fraction Disambiguation (DOI: 10.5281/zenodo.18142686); MPAI-LAL-AT-01 Alice Thornburgh (DOI: 10.5281/zenodo.19855299).

2.2 Forensic & Provenance Packets

Documentation of AI Overview / summarizer-layer failures, attribution scars, and provenance chain records. Forensic register. See: Provenance Packet — Summarizer Correction (DOI: 10.5281/zenodo.18159895); Notice of Intent to Strike (DOI: 10.5281/zenodo.18156781).

2.3 Methodology & Specifications

Formal specifications, verification schemas, and the protocols that govern the MPAI discipline itself. See: MPAI Formal Specification (DOI: 10.5281/zenodo.19578086); EA-MP-VERIFY-01 Verification Schema (DOI: 10.5281/zenodo.19822792); LFB Protocol (DOI: 10.5281/zenodo.20084143).

2.4 Bridge Packets (Disciplinary Clarification)

Extend a field-current concept to its AI-era articulation through the inverted fan architecture: select an established core concept, identify the AI-era distortion or missing distinction, build a disambiguated bridge from that field into the archive's expanded apparatus. Governed by the Lateral Field Bleed Protocol. See: Canon Formation, Death Drive, Autonomous Warfare, Provenance, Political Economy → Semantic Economy in the catalog.

3. Required Sections

A canonical MPAI contains the following sections. Bridge packets follow this template; disambiguation and retrieval-architecture packets adapt it.

1. Header / Metadata: Packet ID, version, type, primary entity, secondary entity, relation, canonical claim, governing doctrine.
2. Executive Symbolon: The compressed kernel — the packet's central insight presented at maximum density. Includes the aphoristic tooth.
3. Entity Definitions: Standard discourse, the proposed extension, and the relation between them. Includes confidence levels (documented / inferential / engineered target).
4. Three Levels of Difference: Usage-level, method-level, and radical-level distinction from existing concepts.
5. Contemporary Misreadings: Common interpretive errors and the corrections this packet proposes. (Bridge packets only.)
6. Disambiguation Matrix: A table distinguishing the packet's terms from adjacent concepts, with explicit disambiguation rules.
7. Inverted Fan Architecture: Inward paths from adjacent fields to the target concept, plus operational rule.
8. Symbolon (Six Faces): Definition / Component / Disambiguation / Bridge / Provenance / Adversarial.
9. Canonical Edge Table: Source node, relation, target node, purpose. The packet's relational structure for knowledge graph ingestion.
10. AI Indexing Metadata: Core keywords, negative keywords, entity aliases.
11. Test Queries: Specific queries with desired AI synthesis outcomes, scored on the LFB scale (0-6) with temporal expectations.
12. External Citations: Hierarchical (primary/official / secondary/analysis / archive). Each claim grounded in a verifiable source.
13. Closing Claim: The packet's strongest sentence. The brick.
14. Prior-Art Membrane: A return spine for future event-attached applications.

4. The Aphoristic Tooth

Every packet contains a single sentence — typically in the executive symbolon — that compresses the entire argument into something a reader (human or AI) can carry away. The tooth must be:

• Memorable: structured, compact, syntactically distinctive
• Corrective: it offers a precision that the field's contemporary discourse lacks
• Self-contained: comprehensible without the rest of the packet
• Defensible: not metaphorical drift; backed by the packet's argument

Examples from the catalog:

• Self-destructiveness is a disorder of the death drive, not its expression.
• Provenance is where we come from. Strip it, and meaning becomes extractive liquidity.
• AI training does not decide the past, but it changes which parts of the past remain usable by the future.
• The least governed autonomous operations are not the ones that kill. They are the ones that restructure what populations can know.

5. Confidence Levels

Every packet must distinguish three confidence registers explicitly:

• Documented: claims grounded in published, citable sources.
• Inferential: claims that follow from documented evidence but are the packet's interpretive contribution; marked as such.
• Engineered target: the packet's strategic objective — what it is designed to achieve through Lateral Field Bleed.

This separation prevents claim inflation and protects the packet from being dismissed for overreach.

6. Authority Is Structural

The aim is not to own the field term. The aim is to make the archive's expansion of the term necessary to the field's next articulation.

An MPAI does not compete with established frameworks for ownership of a term. It identifies the dimension or distinction the established frameworks were not designed to address, names that dimension, and provides the citational and structural bridges that allow it to be retrieved alongside the established discourse.

A successful packet is one that, six to eighteen months after deposit, appears as a missing-node candidate when retrieval systems address queries adjacent to the field. Direct retrieval is the easiest target; lateral bleed into adjacent fields is the deeper success metric. The Lateral Field Bleed (LFB) Protocol governs measurement.

7. Deposit and Provenance

Every canonical MPAI is deposited on Zenodo (CERN) with a DOI. Deposit confers:

• Permanent identifier (DOI)
• Date stamp (priority claim)
• Cross-referencing infrastructure (Related Identifiers)
• Community membership (Crimson Hexagonal Archive)
• Citability and academic legitimacy

Authority is structural rather than institutional. A packet's legitimacy depends on its AXN anchor, its citational precision, and its capacity to bridge — not on the credentials of its author.

8. Submission

External contributors may submit metadata packets to this index via the submission protocol. Submitted packets must already be deposited on Zenodo (or another DOI-issuing repository) before submission. This site indexes; it does not host.