META-AIML v3 Documentation Search

Entry point for all META-AIML v3 documentation sections.

Canonical ontology contracts defining entity nature in META-AIML v3.

Canonical archetype contracts defining value-flow topology and role structure.

Mode-grouped list of all 31 entity contracts with canonical links.

Module-family guidance for v3 entity-level module blocks.

Reusable component contracts and canonical component URLs.

Step-by-step onboarding for creating and validating v3 schemas.

Ontology modes, archetypes, capabilities, and structural metadata.

How ontology, archetypes, entities, examples, and validator rules connect.

Legacy base-model migration guidance to v3 ontology/archetype model.

How legacy organization model maps to v3 contracts.

How legacy product offering model maps to ProductEntity and commerce contracts.

How legacy service category maps to v3 entities.

How legacy creative work model maps to digital/event entities.

How legacy community model maps to NetworkGraph entities.

How legacy financial category maps to FinancialEntity contracts.

Reusable address and location structures from components/address_format.json.

Capability group definitions reused by entity contracts.

Shared primitives such as identifiers, contacts, and social profiles.

Extended entity capabilities data contract.

Localized text formats for multi-language fields.

Reusable amount, currency, and pricing structures.

Review and rating source-link structures.

Site-level interaction and automation signals.

Topology, roles, and value-source semantics.

Base ontological schema for software-based digital systems. CRITICAL: (1) No physical locality required; (2) Virtually scalable without geographic constraints; (3) Accessible via digital channels only; (4) Can combine with any archetype.

Base ontological schema for temporal events and experiences. CRITICAL: (1) Events are temporally bounded; (2) Have discrete start/end time; (3) Can be recurring or one-time; (4) Location can be physical, virtual, or hybrid.

Base ontological schema for regulated financial systems. CRITICAL: (1) Manages money or regulated financial assets; (2) Must be licensed/regulated; (3) Limited to DirectService or ProtocolSystem archetypes ONLY; (4) Requires compliance framework.

Base ontological schema for entities with tangible, geographic presence. CRITICAL CONSTRAINTS: (1) Must require 'location' module; (2) Must include 'PhysicalLocation' in deliveryFormat; (3) No behavioral/operational flags—only structural guarantees.

Base ontological schema for tangible/digital products and goods. CRITICAL: (1) Products are ITEMS, not platforms; (2) NO interaction archetypes allowed; (3) Has inventory/version lifecycle; (4) Distinct from ProductEntity-hosting-platform (which would be DigitalEntity+archetype).

Platform publishes content to broad audience (hub-and-spoke, one-to-many model). Publisher creates/curates content; audience consumes passively or with minimal interaction. Content is the primary product. Economics driven by reach, not transaction volume.

Platform provides value directly to user/consumer (1:1 or 1:many relationship). Platform creates, owns, or curates value; users consume directly. No intermediation, no peer-to-peer. This is the most common archetype used by physical businesses, SaaS tools, utilities, and any platform where the value proposition IS the platform itself.

Archetype for transaction mediation where a platform orchestrates exchanges between distinct participant roles, controls matching and settlement flow, and enforces trust mechanisms such as escrow and dispute handling.

Archetype for peer-centric graph systems where users are the primary value source, user-to-user relationships drive engagement growth, and the platform acts as infrastructure for discovery, communication, and community moderation.

Archetype for autonomous protocol-driven systems that execute deterministic rules without central operator mediation, relying on formal governance, cryptographic trust assumptions, and machine-enforced transaction semantics.

Authentication and identity flow patterns.

Regulatory and policy controls.

Advanced identity patterns (MFA, enterprise auth).

Address, coordinates, and geospatial context.

Fulfillment and operational movement data.

Localization support for content and UI.

Real-time and async event messaging.

Payment orchestration and settlement behavior.

Personalization and ranking behavior.

Discovery, filtering, and query interfaces.

Security posture and protection controls.

Media stream delivery and live transport features.

Recurring billing and plan lifecycle.

Profile, roles, and account lifecycle patterns.

Post-purchase support and guarantee metadata.

v3 schema for outpatient clinics and ambulatory care providers delivering medical services directly to patients at controlled facilities with appointment and care coordination workflows.

v3 schema for accommodation providers delivering lodging services directly to guests at physical properties with reservation, stay, and guest service operations.

v3 schema for restaurants as static website intelligence profile: stable business metadata + external source links for dynamic data (menu/reviews), so AI can fetch fresh values without manual schema rewrites.

v3 schema for physical retail stores as static website intelligence profile: durable store metadata plus external source links for dynamic catalog/review data.

v3 schema for digital B2B service platforms that provide operational business workflows directly to organizations through managed software and process automation.

v3 schema for first-party ecommerce stores as static website intelligence profile: stable commerce metadata plus external source links for dynamic catalog/pricing/review data.

v3 schema for digital marketplaces mediating transactions between buyers and sellers through listing, matching, payment orchestration, and trust workflows.

v3 schema for digital education platforms delivering learning content, assessments, and progress tracking directly to learners and organizations.

v3 schema for subscription and ad-supported streaming platforms where the primary value is curated audiovisual content broadcast to audience segments.

v3 schema for platforms that host virtual events and conferences, providing registration, session delivery, audience engagement, and sponsor workflows directly to participants.

v3 schema for digital fitness platforms that deliver training plans, workout experiences, and wellness tracking directly to users.

v3 schema for digital gaming platforms delivering gameplay, progression systems, and player services directly through managed game infrastructure.

v3 schema for telemedicine service platforms that deliver remote care workflows directly to patients through digital consultation, scheduling, and clinical coordination tools.

v3 schema for editorial blog platforms where value is created by publisher-authored articles and distributed to a broad audience via web and feed channels.

v3 schema for digital news publishing platforms where the primary value is editorial content distributed from publisher to broad audience.

v3 schema for image hosting platforms that provide upload, organization, sharing, and delivery of photos directly to users and teams.

v3 schema for video hosting services that provide upload, processing, storage, and controlled playback delivery directly to customers.

v3 schema for personal websites focused on publishing identity, portfolio, and creator content from an individual publisher to an audience.

v3 schema for productivity platforms that provide task planning, collaboration workflows, and execution tracking directly to users and teams.

v3 schema for digital real estate platforms that mediate transactions and lead flows between property seekers, listing providers, and real estate professionals.

v3 schema for social dating platforms where graph-based user interactions are primary, with optional monetization layers for boosts and premium matchmaking features.

v3 schema for social networking platforms where the primary value source is user-generated content and graph interactions among participants.

v3 schema for cloud file hosting platforms that provide storage, sharing, synchronization, and file lifecycle control directly to users and organizations.

v3 schema for generative AI service platforms that provide model inference, content generation, and applied AI workflows directly to end users and enterprise teams.

v3 schema for generic web application products that provide software capabilities directly to users through browser-native and API-enabled interfaces.

v3 schema for managed website operations services that provide hosting, maintenance, security, and performance optimization directly to business customers.

v3 schema for ride-hailing and ridesharing platforms that mediate transportation transactions between riders and drivers through real-time dispatch and pricing systems.

v3 schema for time-bounded events delivered directly to participants, including registration, scheduling, venue coordination, and attendee engagement workflows.

v3 schema for regulated online banking systems delivering account, payment, and money movement services directly to customers under financial compliance controls.

v3 schema for standalone product artifacts represented as ProductEntity without interaction archetypes, covering physical or digital sellable items and inventory lifecycle.

v3 schema for software products as product artifacts (not services), including packaging, licensing, release lifecycle, and inventory characteristics.

Interactive schema validation UI using synced browser validator adapter.

Validator SDK usage, score model, and CLI integration.

Filled v3 examples for all canonical entities.

Browse schema families from the website.