Standards

Use Cuddler's standards directory when a hidden document rule needs one canonical answer, exact scope, and an inspectable published version.

Resolve the authoring rule at its source

The Artifact Specification makes metadata, exact constraints, machine guidance, conformance, attribution, and publication requirements inspectable before a definition-building agent turns them into a public Artifact Definition.

Find the contract responsible for the decision

Read from the top-level authority down to the concrete artifact type. Each detail page exposes the exact scope, release identity, rules, and machine-readable publication artifacts you can use as proof.

Top-level contract

Specification Root

The Specification Root is the topmost canonical node for the Cuddler standards hierarchy. It explains how Document Roles comply with the root and how Artifact Definitions are governed alongside the shared Artifact Specification.

Current release: Version 1.0.0

Role standards

Document Role

Choose the document role that matches what your artifact is supposed to do: store data, define a template, or drive a process.

Current role documents: Data, Template, and Process.

Shared authoring rules

Artifact Specification

Cuddler's flagship shared authoring standard for building Artifact Definitions whose exact Data Schemas make AI-generated JSON predictable and validatable.

Current release: Version 1.0.0

Concrete artifact types

Artifact Definition Library

Start from Cuddler's public library of inspectable Artifact Definitions instead of redefining a document type from scratch.

Review And Publication

Every public standards release is reviewed before publication. The goal is not only readable prose. The review checks that each page, its machine-readable artifacts, and its publication metadata all agree closely enough to be cited, implemented, validated, and reused as a dependable public contract.

What The Review Protects

The publication process is designed to stop a standard from going live while key governance issues remain unresolved.

  • Terminology discipline so Document Roles, Artifact Specifications, Artifact Definitions, and Artifact Documents are not blurred together.
  • Normative clarity so requirement language can be applied by implementers, reviewers, validators, and AI systems without hidden assumptions.
  • Evidence alignment so canonical URLs, JSON artifacts, fixtures, and supporting files tell the same story as the detail page.
  • Publication readiness so version framing, status language, attribution, and release signals are complete before the public release.
The same review expectation applies across the full public stack: the Specification Root, published Document Roles, the shared Artifact Specification, and public Artifact Definitions.

How A Standard Moves To Release

  1. Stage 1

    Scope and terminology review

    Reviewers confirm that the draft stays inside its layer in the standards hierarchy and uses the canonical Cuddler terms consistently.

  2. Stage 2

    Normative and conformance review

    Requirement language, conformance statements, and implementation expectations are checked for ambiguity before publication is allowed to proceed.

  3. Stage 3

    Artifact and evidence alignment review

    The page is compared against its JSON sources, schema identifiers, fixtures, examples, and supporting files so the public evidence remains aligned.

  4. Stage 4

    Publication readiness review

    Version framing, status, attribution, and release details are checked before the draft is approved or returned for revision.

Cuddler publishes document contracts that give AI an exact Data Schema and give applications predictable, validatable JSON.

TrackThat Inc. is the corporate owner and accountable publisher of the Cuddler technology specification.

Visit TrackThat