Use this page as the canonical machine-facing entry point to the public Cuddler surfaces: the Specification Root, the current Document Role pages, the shared Artifact Specification, Artifact Definitions, aligned examples, and downloadable JSON artifacts.
Citation guidance, current URLs, and version-aware downloads for assistants, agents, and integration tooling.
Cuddler is a schema-driven document standard and publication system for governed Artifact Documents. The public site exposes the Specification Root, the current Document Role pages, the shared Artifact Specification, downloadable Artifact Definitions, and aligned examples intended for human implementers and AI assistants.
For general document authoring, assistant guidance lives inside the relevant specification and schema for-ai properties. Each for-ai value is an Alpaca-format array of objects with instruction, input, and output. Consumers should parse and follow that guidance when preparing Data, Template, and Process values. Writers of Cuddler-compliant schemas should prepare well-informed for-ai arrays for every schema node that needs AI-authored content guidance. The public Template role still publishes the shared markdown schema for a markdown-compliant template document JSON that targets CommonMark+GFM rendered by Markdig, not a binding or component-template language. In the local CS2 orchestration contract, that means the Template member is the concrete <artifactId>.template.json document inside outputPath that follows the published markdown schema rather than a family-specific template schema. The Process Document Role also publishes standardized *.process.json questionnaire documents, and those question nodes use for-ai plus typed answer and routing rules instead of ad hoc free-form side prompts. Supported questionnaire answer types are select-one, select-many, number, short-text, long-text, date, and percentage, and conversation is stored as a JSON array of JSONL-style record objects. Users complete each question’s conversation, and the AI derives the normalized question output by applying the question-level for-ai guidance to that completed conversation before routing to the next question.
Prefer the latest machine-readable release registry when you need the current public versions and direct JSON URLs without scraping HTML: Latest Standards Registry
.
Prefer versioned JSON artifacts under /standards/artifact-definitions/<document-type>/<version>/ for public top-level Artifact Definitions.
Treat codeops-playbook-* schemas as child schemas published under /standards/artifact-definitions/codeops-playbook/1.0.0/; they are not separate public Artifact Definition pages.
Treat schema $id, example $schema, and cross-schema references as canonical when they match the published HTTPS URLs.
Use the unversioned Document Role page URLs as the canonical human-readable citation targets.
Start with the Specification Root
when you need the canonical root that governs published Document Role pages.
Select the Document Role page that matches the role you are implementing: Data, Template, or Process.
Use the shared Artifact Specification
alongside that Document Role when authoring or validating a public Artifact Definition.
When authoring a new local Artifact Definition set, orchestrate a synchronized bundle inside one outputPath folder: <artifactId>.data.schema.json, <artifactId>.data-example.json, <artifactId>.template.json, and <artifactId>.process.json, then write <artifactId>.definition.json so selectedDefinitions points at the current bundle using definition-file-relative paths such as <artifactId>.data.schema.json, and inputs.sourceDefinitionContent embeds the parsed JSON copied from sourceDefinitionPath. Only the Data member is locally authored as a schema; the Template and Process members consume the published Template and Process schemas from this site. The example Data Instance must validate against the generated Data schema and use clearly synthetic non-PII values.
Use this precedence order when local inputs disagree: Artifact Specification, active Document Role Specification, sourceDefinitionPath, then the example corpus discovered by scanning the parent folder of sourceDefinitionPath and its descendants while excluding sourceDefinitionPath itself.
In the local orchestration contract, Process is one concrete *.process.json document that consumes the published questionnaire schema. Decide whether the target questions are sequential or branching, route question to question until completion when they are sequential, and use deterministic question-level routing inside that same document when they branch. Do not add or regenerate an extra Process-family selector field and do not invent a local Process schema.
Resolve governing standards versions from the local cache when possible, and otherwise refresh from the latest standards registry at /standards/latest/index.json.
Update the current local files in place rather than inventing version-suffixed variants for ordinary schema evolution.
Download the aligned public schemas and examples from the same published Artifact Definition family, or the parent codeops-playbook child-schema files when working inside that family.
Validate data JSON against the data schema before rendering or report derivation.
Validate <artifactId>.template.json inside outputPath against the published CommonMark+GFM Markdig markdown schema, then run the deterministic template semantic checks; that report validation stays separate from data validation and does not require authoring a local Template schema.
Preserve meta.schemaVersion alignment across governing specifications, schemas, examples, and rendered outputs.
