META-AIML v3.0.0
50 canonical contracts
31 filled examples
15 module guidance pages

Ontology-driven schemas for AI-readable websites.

META-AIML v3.0.0 publishes a canonical schema system built from ontology, interaction archetypes, shared components, entity contracts, filled examples, and a validator SDK with explicit score gates.

Release facts
Counts are derived from the current `www/public` registry plus module guide metadata.

50

Canonical contracts

31

Filled examples

31

Entity schemas

15

Module guides

Static contract, live sources

v3 is designed for one stable JSON-LD object in the site head, while fast-changing data stays behind declared source URLs.

Published schema sets

v3 separates foundational contracts from filled instances. That keeps composition predictable and makes validation rules explicit.

5
Ontology
Five ontological modes define what an entity fundamentally is.
5
Archetypes
Five interaction archetypes define how value is created or delivered.
31
Entity Contracts
Thirty-one canonical entity schemas cover the current v3 release set.
9
Shared Components
Reusable v3 building blocks for addresses, capabilities, ratings, and structure.

Operational model

The v3 architecture is optimized for publish-once schemas that remain stable while AI agents fetch fresh operational data from declared sources.

1

Choose the contract

Start from the correct ontology mode, archetype, and entity schema before filling business data.

2

Keep dynamic data external

Menus, catalogs, prices, and ratings should be linked as live sources instead of hard-coded snapshots.

3

Validate before publish

The SDK validator and Playground share the same validation core and score semantics.

Menu feeds, product catalogs, and review data are modeled as source descriptors, not as embedded snapshots. This reduces manual maintenance and lets downstream agents fetch current values.

Canonical v3 instance pattern
Minimal valid WebApp instance used for bootstrap validation, showing the smallest required v3 shape.
{
  "@context": ["https://schemas.meta-aiml.org/v3.0.0/context.jsonld"],
  "@id": "https://example.com/meta-aiml-v3/minimal",
  "@type": "WebApp",
  "schemaVersion": "3.0.0",
  "aimlVersion": "3.0.0",
  "ontologicalMode": "DigitalEntity",
  "interactionArchetype": ["DirectService"],
  "domain": "Technology",
  "deliveryFormat": ["WebApp"],
  "name": {
    "en": "Minimal App"
  },
  "description": {
    "en": "Minimal valid META-AIML v3 example instance for playground bootstrap."
  },
  "shortDescription": "Minimal v3 example.",
  "url": "https://example.com",
  "modules": {
    "core": {
      "enabled": true
    }
  },
  "capabilities": {
    "interaction": {
      "features": ["notifications"],
      "interactionMethods": ["online_form"],
      "availableActions": ["open_app"]
    }
  },
  "structuralMetadata": {
    "topology": "binary",
    "roles": ["user", "platform"],
    "valueSource": "platform_provided",
    "transactionFlow": "direct",
    "networkEffects": "none"
  },
  "examples": [
    {
      "scenario": "Quick validation",
      "note": "Minimal baseline for parser boot."
    },
    {
      "scenario": "Template fallback",
      "note": "Used when network loading fails."
    }
  ]
}

Core tooling

The website, public schema host, and validator distribution now point to the same v3 contract family.

Documentation
Architecture, entity contracts, ontology, archetypes, and implementation rules.
Schema Reference
Canonical v3 paths for ontology, archetypes, components, entities, examples, and SDK.
Playground
Paste a schema, run the validator, inspect score, and review normalized output.
SDK
CLI and runtime validator with critical blockers, warning tiers, and score zones.