tson.io

Revision 34 is a retained revision. It stays published at this address so hash-pinned references keep resolving, but it is no longer the working draft — revision 35 is.

Read this document in revision 35 →Revision 35·All revisions

Specification

The TSON specification, split into two parts, plus the companion documents developed alongside it. Spot an error, or have a comment on the specification? Open an issue on GitHub.

TSON Specification

  • TSON Part 1: Text Data Format
    Draft 2026·Working Draft·view raw ↗

    The notation and reference encoding of the TSON schema system: the lexer, structural grammar, absent sentinel, augmentation syntax (annotations, type annotations, directives), and base type resolution — everything needed to losslessly read and write schemaless TSON data.

  • TSON Part 2: Type System and Schema
    Draft 2026·Working Draft·view raw ↗

    The centre of the TSON series: the schema grammar, the type system and its operations, the schema chain and its resolution model, schema compilation and resolver output, the text encoding rules, and the operations of the schema, meta, and import directives.

  • TSON Developer Guide
    Draft 2026·Working Draft·view raw ↗

    Rationale, extended examples, and implementation guidance for the TSON specification series. Nothing in this guide is normative; where it appears to disagree with [TSON-DATA] or [TSON-SCHEMA], the specifications govern.

Skills

Agent skills that teach an AI assistant to read and write TSON against this revision. Each bundles this revision's own schema sources, so a skill and the spec it describes never drift apart. Unzip a bundle into ~/.claude/skills/for Claude Code, or upload it in claude.ai under Settings › Features.

  • tson-data.skill

    Write, read, convert, and fix TSON data documents (.tn files) — the Typed Schema Object Notation text format, a JSON superset with optional quotes and commas, records vs maps, the absent sentinel `_`, annotations (`@`), type annotations (`!uuid`, `!date`, `!int32`…) and directives (`!!id`, `!!schema`).

  • tson-schema.skill

    Author, review, and explain TSON schema documents — `.tn` files with a `!!meta` header and name-to-type declarations that define records, enums, refined atoms with facets like min and max, choices, generic templates with type parameters, field groups, and constraints for the TSON (Typed Schema Object Notation) type system at tson.io.

Schema Source Files

The normative TSON schema source files in .tnformat, each followed in parentheses by its non-normative resolved-output fixture. To check an implementation: parse the source, run the resolver, canonicalise, and compare against the fixture.

Reports

The working documents belonging to this revision: the change log of what was accepted into it, and the non-normative reports written against it, which record findings and design directions under consideration rather than committed specification.

  • TSON 2026 Revision 34 — Change Log
    Against TSON 2026 Revision 33 (Working Draft)·view raw ↗

    Adjudicated and executed 2026-08-29 — Part 1, Part 2, and all six companion artifacts updated; hash pins recomputed over the shipped bytes

    • SPEC-FEEDBACK.md (17 entries, against Revision 33)
    • Revised companion artifacts: meta-kernel.tn, meta.tn, core.tn and resolved fixtures (implementing #3 step 1, #5, #7, #12)
  • Implementation Feedback
    Non-normative·view raw ↗

    Issues, ambiguities, and inconsistencies found in the specification while building the first implementation, each recorded with the reading that implementation chose and a suggested resolution. The most direct feedback loop the draft currently has.

Implementations of TSON (parsers, encoders, libraries) may be licensed however you choose; the specification's license applies to the written text, not to code that implements it.