Document Templates

The Cuddler Schema Catalog is the source of truth for published document contracts. In v1.0.0-draft.6, each catalog entry defines the document template identifier, compatible schema version, and the artifacts required for generation, validation, and export.

Catalog Access

Browse published schema families by document type.
Review compatibility notes and schema version metadata.
Access full document definitions through an active subscription.
Use the catalog as the starting point for MCP-driven generation workflows.

Document Types

Catalog Field	Description	Usage
`documentType`	Stable identifier for a schema family.	Used to select the correct generation and rendering contract.
`schemaVersion`	Contract compatibility boundary.	Must align with data and template schemas used at runtime.
`artifacts`	Links to data and template schema assets.	Consumed by validation and render workflows.

Subscription Model

Public view: high-level document type listings and metadata.
Subscriber view: full document definitions and implementation detail.
Schema updates are published with explicit compatibility notes.

Versioning Rules

Each entry maps directly to a versioned schema contract.
Draft alignment is explicit: this page tracks Cuddler v1.0.0-draft.6.
Data schema and template schema versions move together.
Breaking changes require a new version and migration notes.

Examples

{
  "documentType": "brand-guide",
  "schemaVersion": "1.0.0",
  "artifacts": {
    "dataSchema": "/schemas/brand-guide/1.0.0/data.schema.json",
    "templateSchema": "/schemas/brand-guide/1.0.0/template.schema.json"
  }
}

Catalog Assets

Schema artifacts published through the catalog are designed for deterministic tooling workflows and long-lived compatibility.

Data schema files for strict validation.
Template schema files for rendering behavior.
Example payloads for integration testing.