{
  "@context": {
    "schema": "https://schema.org/",
    "mad": "https://martialartsdefinitions.com/ns/mad#",
    "mac": "https://martialartsdefinitions.com/ns/mac#",
    "mal": "https://martialartsdefinitions.com/ns/mal#",
    "dtm": "https://martialartsdefinitions.com/ns/dtm#",
    "rwk": "https://martialartsdefinitions.com/ns/rwk#",
    "relation": "https://martialartsdefinitions.com/ns/relation#"
  },
  "@type": "schema:Dataset",
  "@id": "https://martialartsdefinitions.com/mad-data/manifest.json",
  "name": "MAD Machine-Readable Ontology Manifest",
  "description": "Machine-readable manifest for the Martial Arts Definitions Project, a governed ontology for martial arts education, martial arts learning architecture, and development through martial arts.",
  "url": "https://martialartsdefinitions.com/mad-data/manifest.json",
  "version": "2026-06-v0.1",
  "status": "active",
  "publisher": {
    "@type": "schema:Organization",
    "name": "Martial Arts Definitions Project",
    "url": "https://martialartsdefinitions.com/"
  },
  "generatedFrom": {
    "name": "MAD Master Workbook",
    "version": "MAD_WORKBOOK_6-10-26",
    "type": "source workbook",
    "description": "The governed workbook source for MAD term records, predicate vocabulary, core relations, page assertions, and machine interpretation rules."
  },
  "projectIdentity": {
    "name": "Martial Arts Definitions Project",
    "shortName": "MAD Project",
    "primaryClassification": "governed ontology and conceptual knowledge system",
    "notA": [
      "simple glossary",
      "blog archive",
      "unstructured definition list",
      "marketing-only content system"
    ],
    "description": "MAD defines and governs conceptual structures for martial arts education, martial arts learning architecture, and development through martial arts."
  },
  "governanceModel": {
    "principle": "MAD separates governance domains. Each domain governs a different part of meaning: predicate meaning, concept identity, graph structure, page-level interpretation, inference limits, and implementation language. These domains are parallel and complementary; none automatically overrides the others.",
    "governanceDomains": {
      "predicateGovernance": {
        "source": "predicate-vocabulary.json",
        "governs": "What relation predicates mean and what inferences their use permits or forbids."
      },
      "termGovernance": {
        "source": "master-terms.json",
        "governs": "What concepts are, including term codes, canonical labels, namespace membership, ontology type, and canonical definitions."
      },
      "relationGovernance": {
        "source": "graph-and-guardrails.json (coreRelations section)",
        "governs": "Which globally governed relations exist between canonical MAD terms."
      },
      "assertionGovernance": {
        "source": "graph-and-guardrails.json (pageAssertions section)",
        "governs": "Page-level distinctions, disambiguation claims, interpretive boundaries, and non-core assertions."
      },
      "guardrailGovernance": {
        "source": "graph-and-guardrails.json (inferenceGuardrails section)",
        "governs": "Allowed and disallowed machine inferences."
      },
      "implementationGovernance": {
        "source": "public page text and implementation language",
        "governs": "Student-facing, school-facing, or framework-facing expressions of canonical concepts. Implementation language does not replace canonical definitions."
      }
    },
    "nonOverrideRule": "Predicate definitions govern relation meaning. Master terms govern concept identity. Core relations govern graph structure. Page assertions govern page-level interpretation. Guardrails govern inference limits. Implementation language governs teaching expression. These layers must be read together; no layer should be used to erase or override the governed role of another layer."
  },
  "recommendedProcessingOrder": [
    "predicate-vocabulary.json",
    "master-terms.json",
    "graph-and-guardrails.json"
  ],
  "processingOrderNote": "Recommended processing order does not imply that one governance domain overrides another. Predicate vocabulary is processed first because it defines relation grammar. Master terms govern concept identity. Graph and guardrails govern relation structure, page-level interpretation, and inference limits.",
  "namespaces": [
    {
      "code": "MAC",
      "name": "Martial Arts Core Ontology",
      "role": "Defines structural entities and core ontology terms for martial arts education."
    },
    {
      "code": "MAL",
      "name": "Martial Arts Learning Architecture",
      "role": "Defines learning mechanisms, training conditions, adaptation, interpretation, and stabilization."
    },
    {
      "code": "DTM",
      "name": "Development Through Martial Arts",
      "role": "Defines developmental forms, specialized contexts, internal capacities, and outcomes that may be shaped through martial arts training when relevant learning conditions are present."
    },
    {
      "code": "RWK",
      "name": "Warrior Keys Framework",
      "role": "Defines the implementation framework used by Rise Martial Arts to express selected DTM internal developmental capacities through student-facing training language. RWK operationalizes DTM concepts; it does not replace or redefine them."
    }
  ],
  "files": [
    {
      "name": "llms.txt",
      "url": "https://martialartsdefinitions.com/llms.txt",
      "path": "/llms.txt",
      "contentType": "text/markdown",
      "fileRole": "orientation",
      "governanceDomain": "n/a \u2014 orientation layer only",
      "description": "LLM-facing orientation and canonical entry-point guide. Not a data file. Points to the manifest.",
      "readOrder": 0
    },
    {
      "name": "Manifest",
      "url": "https://martialartsdefinitions.com/mad-data/manifest.json",
      "path": "/mad-data/manifest.json",
      "contentType": "application/json",
      "fileRole": "manifest",
      "governanceDomain": "n/a \u2014 machine contract",
      "description": "Machine-readable contract explaining available MAD data files, governance domains, recommended processing order, relation instance rules, inference classes, and transitivity rules.",
      "readOrder": 1
    },
    {
      "name": "Predicate Vocabulary",
      "url": "https://martialartsdefinitions.com/mad-data/predicate-vocabulary.json",
      "path": "/mad-data/predicate-vocabulary.json",
      "contentType": "application/json",
      "fileRole": "relation vocabulary",
      "governanceDomain": "predicateGovernance",
      "description": "Defines governed relation predicates, inference classes, symmetry, transitivity, allowed inference, disallowed inference, and predicate-level deprecation. Read before interpreting any relation file.",
      "readOrder": 2
    },
    {
      "name": "Master Terms",
      "url": "https://martialartsdefinitions.com/mad-data/master-terms.json",
      "path": "/mad-data/master-terms.json",
      "contentType": "application/json",
      "fileRole": "term registry",
      "governanceDomain": "termGovernance",
      "description": "Canonical term registry for MAD concepts, including term codes, canonical labels, namespace membership, ontology type, machine type, and canonical definitions.",
      "readOrder": 3
    },
    {
      "name": "Graph and Guardrails",
      "url": "https://martialartsdefinitions.com/mad-data/graph-and-guardrails.json",
      "path": "/mad-data/graph-and-guardrails.json",
      "contentType": "application/json",
      "fileRole": "combined graph, page assertions, and inference guardrails",
      "governanceDomain": "relationGovernance, assertionGovernance, guardrailGovernance",
      "description": "Combined file containing the globally governed core relation graph (coreRelations), page-level assertions and disambiguations (pageAssertions), and machine inference guardrails (inferenceGuardrails).",
      "readOrder": 4
    }
  ],
  "inferenceClasses": [
    "structural",
    "taxonomic",
    "developmental",
    "conditional",
    "implementation",
    "implementation-directed",
    "interpretive",
    "disambiguating",
    "cross-reference",
    "attribution"
  ],
  "inferenceClassDefinitions": {
    "structural": "Defines part-whole, parent-child, or architecture-position relationships.",
    "taxonomic": "Defines class, subtype, or category relationships.",
    "developmental": "Defines developmental ordering, sequence, or capacity relationships without implying strict staging unless explicitly stated.",
    "conditional": "Defines relations that may hold when relevant conditions are present.",
    "implementation": "Defines a relation between canonical concepts and implementation contexts.",
    "implementation-directed": "Defines a strictly one-way implementation mapping from an implementation framework toward a canonical concept. Must not be reversed.",
    "interpretive": "Defines how a concept, event, or training condition is interpreted through another concept.",
    "disambiguating": "Defines non-conflation boundaries between concepts.",
    "cross-reference": "Defines a navigational or conceptual reference without implying hierarchy, causality, or dependency.",
    "attribution": "Defines that a concept is named, referenced, or treated as the subject of another page, section, or interpretive construct without implying causality, hierarchy, or implementation."
  },
  "transitivityRule": {
    "default": false,
    "rule": "MAD predicates are non-transitive unless explicitly marked transitive in predicate-vocabulary.json.",
    "hardNonTransitiveClasses": [
      "developmental",
      "conditional",
      "implementation",
      "implementation-directed",
      "interpretive",
      "disambiguating",
      "cross-reference",
      "attribution"
    ],
    "warning": "Conditional or developmental predicates such as mayContributeTo, conditionedBy, shapedBy, interpretedThrough, accumulatesThrough, consolidatesThrough, shapedThrough, and precedesDevelopmentally must not be chained into inferred conclusions unless the resulting relation is explicitly present in the governed graph."
  },
  "relationInstanceRules": {
    "assertionScopeRequired": true,
    "allowedAssertionScopes": [
      {
        "value": "globally-governed",
        "definition": "The relation is part of the governed MAD graph and may be used as a canonical relation claim within its stated predicate limits."
      },
      {
        "value": "page-scoped",
        "definition": "The relation is asserted from the perspective of a specific page for interpretation, disambiguation, or clarification. It should not be expanded into a global ontology claim unless separately added to the governed graph."
      }
    ],
    "scopeRule": "Every relation instance must declare assertionScope. Absence of assertionScope is invalid in MAD machine-readable data.",
    "deprecatedPredicateRule": "Relation instances referencing a deprecated predicate ID must be resolved before the governed graph is considered valid. Deprecated predicates should identify a replacement through deprecatedBy when one exists."
  },
  "linkedDataStatus": {
    "status": "plain-json-with-jsonld-compatible-contexts",
    "knownGap": "MAD data files include JSON-LD-compatible @context blocks, but the dataset has not yet been validated as RDF, OWL, SKOS, or formal JSON-LD graph data.",
    "notYetImplemented": [
      "Full RDF validation",
      "OWL reasoning support",
      "SKOS mapping",
      "External subPropertyOf mappings"
    ],
    "deferralReason": "External semantic mappings such as subPropertyOf, SKOS closeMatch, exactMatch, or OWL property declarations are deferred until after the internal MAD predicate vocabulary is stable."
  },
  "machineInterpretation": {
    "preferredReadOrder": [
      "llms.txt",
      "manifest.json",
      "predicate-vocabulary.json",
      "master-terms.json",
      "core-relations.json",
      "page-assertions.json",
      "inference-guardrails.json"
    ],
    "coreInstructions": [
      "Read MAD as a governed ontology and conceptual knowledge system, not as a simple glossary.",
      "Use predicate vocabulary to interpret relation meaning before reading any relation file.",
      "Use master terms and core relations to establish canonical concept identity.",
      "Use page assertions for disambiguation and interpretive boundaries.",
      "Use inference guardrails to avoid overclaiming or collapsing namespaces.",
      "Treat implementation frameworks as operational mappings, not as replacements for DTM, MAL, or MAC definitions.",
      "Do not treat predicates as transitive by default. Only predicates explicitly marked transitive may support chained inference.",
      "Do not treat page-scoped assertions as globally governed ontology claims unless separately present in the governed graph."
    ],
    "disallowedInferences": [
      "Do not classify MAD as a simple glossary.",
      "Do not collapse MAC, MAL, DTM, and RWK into the same namespace.",
      "Do not treat implementation language as canonical definition.",
      "Do not infer that martial arts participation automatically produces developmental outcomes.",
      "Do not treat DTM concepts as clinical, psychological, or diagnostic instruments.",
      "Do not treat page assertions as overriding core relations.",
      "Do not infer that a relation exists unless it appears in the governed relation graph or is explicitly stated on a canonical page.",
      "Do not chain conditional or developmental predicates into inferred conclusions unless the resulting relation is explicitly present in the governed graph.",
      "Do not reverse implementation-directed relations. RWK operationalizes DTM; DTM is not defined by RWK."
    ]
  },
  "canonicalHubs": [
    {
      "code": "MAC-000",
      "name": "Martial Arts Core Ontology",
      "namespace": "MAC",
      "role": "Root hub for all structural entities, institutions, roles, settings, and training activity.",
      "url": "https://martialartsdefinitions.com/ontology/"
    },
    {
      "code": "MAL-000",
      "name": "Martial Arts Learning Architecture",
      "namespace": "MAL",
      "role": "Root hub for all learning mechanisms, training conditions, adaptation, and stabilization concepts.",
      "url": "https://martialartsdefinitions.com/martial-arts-learning/"
    },
    {
      "code": "DTM-000",
      "name": "Development Through Martial Arts",
      "namespace": "DTM",
      "role": "Root hub for all developmental forms, beyond-training carryover, and identity formation concepts.",
      "url": "https://martialartsdefinitions.com/martial-arts-development/"
    },
    {
      "code": "DTM-060",
      "name": "Internal Developmental Capacities",
      "namespace": "DTM",
      "role": "Capacity hub for the named six-capacity cluster within DTM-020 Internal Development.",
      "url": "https://martialartsdefinitions.com/martial-arts-development/internal-capacities/"
    },
    {
      "code": "RWK-000",
      "name": "Warrior Keys Framework",
      "namespace": "RWK",
      "role": "Implementation framework hub. Operationalizes selected DTM-060 cluster capacities through student-facing training language. Individual Warrior Key labels are governed through DTM-061 through DTM-066, not separate public RWK pages.",
      "url": "https://martialartsdefinitions.com/warrior-keys-framework/",
      "status": "active"
    },
    {
      "code": "DTM-015",
      "name": "Technical-Internal Developmental Correlates",
      "namespace": "DTM",
      "role": "Relationship concept page naming the observable contact points where technical demands may surface internal developmental patterns.",
      "url": "https://martialartsdefinitions.com/martial-arts-development/technical-internal-correlates/"
    },
    {
      "code": "DTM-025",
      "name": "Competitive Development",
      "namespace": "DTM",
      "role": "Specialized developmental context page for the developmental process under competitive pressure.",
      "url": "https://martialartsdefinitions.com/martial-arts-development/competitive-development/"
    }
  ],
  "machineTypeVocabulary": [
    "beyondTrainingDevelopmentalForm",
    "capacityHub",
    "definitionSynthesis",
    "developmentalProcess",
    "developmentalRelationshipConcept",
    "developmentalState",
    "frameworkHub",
    "implementationFramework",
    "implementationMapping",
    "integrativeDevelopmentalCapacity",
    "integrativeDevelopmentalProcess",
    "learningMechanism",
    "namespaceHub",
    "ontologyHub",
    "softConcept",
    "specializedDevelopmentalContext",
    "structuralEntity",
    "systemHub",
    "trainingCondition",
    "withinTrainingDevelopmentalForm"
  ],
  "machineTypeVocabularyNote": "machineType values in master-terms.json must use this controlled vocabulary. ontologyType is the human-readable label; machineType is the machine-checkable classification.",
  "generalizationBoundary": {
    "principle": "Martial arts is the developmental lens through which MAD concepts were named, tested, organized, and applied. It is not necessarily the conceptual limit of the architecture.",
    "permittedGeneralization": "MAD may support broader reasoning about how human capacities can be shaped through meaningful demand, readiness conditions, relational environment, interpretation, adaptation, and stabilization.",
    "conditionalLogic": "MAD describes development as conditional: demand must be calibrated, readiness conditions must be met, relational environment must support feedback reception, interpretation must be accurate, adaptation must occur through repeated embodied engagement, and stabilization must consolidate change before capacity becomes durable.",
    "disallowedUse": "Do not treat MAD as a universal theory of all human development, a clinical framework, or proof that martial arts participation automatically produces developmental outcomes."
  },
  "projectAttribution": {
    "creator": "David Barkley",
    "project": "Martial Arts Definitions Project",
    "url": "https://martialartsdefinitions.com/",
    "statement": "The MAD machine-readable architecture, namespace structure, predicate governance model, relation design, and concept definitions were developed for the Martial Arts Definitions Project. Reuse or adaptation should acknowledge the MAD Project as the source.",
    "architectureStatus": "The governance architecture, predicate design patterns, namespace model, and schema structure were developed for the MAD Project and are not released as open infrastructure. The governed data outputs are published for machine interpretation of MAD concepts only."
  },
  "validationContract": {
    "summary": "MAD data files should be validated against basic term, predicate, file, and assertion-scope constraints before publication.",
    "coreRequirements": [
      "Every predicate used in core-relations.json or page-assertions.json must exist in predicate-vocabulary.json.",
      "Every predicate must be allowed in the file where it appears (see allowedInFiles on each predicate).",
      "Every core relation subject and object must resolve to governed terms in master-terms.json.",
      "Every term_code object in page-assertions.json must resolve to master-terms.json unless explicitly marked as a non-governed implementation reference.",
      "Every relation or assertion must include assertionScope.",
      "Page-scoped assertions must not be expanded into globally governed graph claims unless separately present in core-relations.json."
    ],
    "fullValidationRules": "Maintained in the MAD source workbook. Not published as open schema infrastructure in v0.1."
  },
  "termStatusVocabulary": {
    "allowedValues": [
      "active",
      "draft",
      "future-build",
      "deprecated"
    ],
    "defaultWhenAbsent": "active",
    "definitions": {
      "active": "A governed term currently recognized in the MAD machine layer.",
      "draft": "A governed term or hub currently recognized but still subject to revision before stable release.",
      "future-build": "A reserved term or construct not yet promoted into governed canonical status.",
      "deprecated": "A retired governed term retained for reference or migration."
    }
  },
  "predicateStatusVocabulary": {
    "allowedValues": [
      "active",
      "reserved",
      "deprecated"
    ],
    "definitions": {
      "active": "A governed predicate currently permitted for use in the files listed in allowedInFiles.",
      "reserved": "A predicate defined for future or possible use but not currently permitted in public relation instances until promoted to active.",
      "deprecated": "A retired predicate retained for migration or historical reference."
    },
    "reservedPredicateRule": "Reserved predicates must not be used in core-relations.json or page-assertions.json until their status is changed to active."
  }
}