About Cuddler

Applications should not have to handle a different AI response shape every time. Cuddler makes the expected fields, data types, and validation rules explicit before generation.

The Artifact Specification governs how an Artifact Definition is built; its exact Data Schema tells the downstream agent what JSON to return and lets the consuming application validate it before use.

Built for engineers who need useful failure boundaries

Why the publication surface makes document intent inspectable

Cuddler connects technical causality to practical control: publish the rule, preserve the exact version, validate the responsible layer, and retain evidence another engineer can inspect.

Visible intent

Required structure and property-level guidance move document rules out of prompts and into an inspectable contract.

Failure boundary

Independent Data and Template validation points a mismatch to the layer responsible before rendering.

Reproducible handoff

Exact schema identities, versions, examples, and publication inventories let another compatible workflow follow the same contract.

Inspectable proof

Canonical pages, published JSON, validation paths, and source notes show where each technical or narrative claim comes from.

TrackThat and Cuddler

The company behind the public technology specification

Cuddler is owned and published by TrackThat Inc.

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

TrackThat Inc. is the corporate owner and accountable publisher of Cuddler. TrackThat maintains the standards, governed releases, controlled brand assets, and public publication system while Cuddler remains the technology specification that people and compatible tools implement.

Visit TrackThat

TrackThat Inc. ownership gives the specification an accountable steward. TrackThat governs the maintained releases and public source of truth; Cuddler is the technology contract that compatible people, agents, and tools implement.

This separation keeps accountability clear without creating lock-in. Engineers can inspect a canonical release, implement the contract independently, and trace a document back to known standards, schemas, and validation results.

What TrackThat is accountable for

TrackThat maintains the corporate ownership, publication governance, controlled brand system, and evidence boundaries behind Cuddler. The relationship stays explicit on the About page and in the global footer.

  • TrackThat is the corporate owner; Cuddler is the technology specification
  • TrackThat maintains the public standards and governed releases
  • Published versions and controlled assets create an inspectable source of truth
  • Compatible tools may implement Cuddler without becoming TrackThat products
  • Claims, changes, and publication decisions remain evidence-aware

Who the approach is built for

Teams in regulated, audit-facing, or operationally sensitive environments where AI output still needs a durable publishing contract and a real review path.

See the case studies

Cuddler takes a different approach

The document contract is designed for both humans and AI assistants

Embedded AI instructions at the property level

A conforming Cuddler Data Schema does more than validate shape. Every instance-visible property is expected to carry generator-readable `for-ai` guidance in Alpaca format so assistants know what the field means, what they should write there, how specific it should be, and what constraints or exclusions matter.

Validation before rendering

Cuddler separates the data contract from the rendering contract. Data JSON is validated first, markdown-compliant template-document JSON is validated second, and rendering only happens after both pass and stay version-aligned.

Guidance, schemas, and outputs stay in lockstep

The public site publishes versioned Document Role, the shared Artifact Specification, Artifact Definitions, and aligned examples together. Assistant guidance stays embedded directly in specification and schema `for-ai` properties, so teams and tools can work from one versioned release family instead of separate prompt files.

Implementation stories with visible evidence boundaries

Sponsor stories connect an operating pressure to the Cuddler mechanism used to address it. Each page identifies its source context so readers can separate the described implementation pattern from measured performance evidence.

Inspect the public surfaces

Choose the contract, library, or implementation path responsible for your next decision

Document Role

Canonical role-specific contracts for Cuddler Data, Template, and Process artifacts.

Open Document Role

Artifact Specification

Cuddler's flagship shared authoring standard: the metadata, conformance, machine-guidance, attribution, and publication contract every public Artifact Definition follows.

Open Artifact Specification

Artifact Definitions

A public library of specific artifact-type contracts, exact versions, and aligned examples ready to inspect, try, or download.

Open Artifact Definitions

Field-Level Instructions Matter

The differentiator is not just validation. It is instruction quality inside the schema itself.

Cuddler was built for engineers and teams that want AI output their software can use without writing a new parser for every response. A fast draft is not enough when an application expects exact fields and data types, another engineer must reproduce the result, or a failed output must point back to the responsible layer. The Artifact Specification makes that contract explicit.

The public Document Role and Artifact Specification surfaces work together. A Document Role defines the artifact’s job; the Artifact Specification defines the shared authoring rules. The resulting schema is both a validator and a readable contract. Its exact constraints and property-level guidance let compatible assistants act without guessing what belongs in a field, how specific it should be, or what must be excluded.

That technical confidence has an accountable source. TrackThat Inc. owns and publishes Cuddler, maintains the governed releases and public standards surface, and remains answerable for the specification’s direction. Compatible tools, AI agents, and document workflows can implement Cuddler without confusing the technology contract with its corporate owner.

The strict rule matters because it localizes ambiguity where AI systems usually drift. Instead of asking an assistant to infer purpose from a property name or type, Cuddler keeps the instruction beside the schema constraint. Reviewers can inspect both before generation.

The intended consequence is practical: clearer inputs, earlier validation, and output that another engineer can reproduce from the same contract. The implementation stories show how that pattern was applied; their source notes state the evidence boundary.

Inspect the contract or follow an implementation story

Use Standards when a rule must be canonical. Use the implementation stories when you want to see an engineering pressure, the Cuddler mechanism applied to it, and the stated evidence boundary.

Inspect the Standards DirectoryInspect implementation stories

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

Explore

Standards

Learn