dtcg-tokens

Turn any inspectable multimodal input into source-specific DTCG 2025.10 JSON, evidence JSON, a standalone HTML proof artifact, and a run record. Start with the full possibility surface, then narrow it with located source evidence and reasons. Strong native vision owns source interpretation, design decisions, artifact authorship, and final visual judgment. Never invent a source, audience, product fact, brand premise, comparison corpus, or proof claim.

Commands

Command	Result
`help`	Show inputs, intents, outputs, vision requirements, and claim limits.
`generate <inputs>`	Create `<name>.tokens.json`, `<name>.evidence.json`, `<name>.proof.html`, and `<name>.run.json`.
`validate <tokens>`	Check DTCG 2025.10 structure, values, names, references, type agreement, and cycles.
`prove <tokens> <evidence> [sources]`	Author, assemble, inspect, and read back a source- and token-specific standalone proof artifact.

Load examples/help.md, examples/generate.md, examples/validate.md, or examples/prove.md only for the matching command. Load examples/failure-global-claim.md only for an absolute uniqueness request. Load evals/contract.md, evals/rubric.md, and scripts/tests/test_ci_contract.py only in Step 24.

Package map

A directory name does not load a file. Load, inspect, copy, or run a file only when the current command, Execution row, step procedure, or Completion gate names its exact relative path.