dtcg-tokens
dtcg-tokens
Outcome
Turn inspectable multimodal source evidence into source-specific DTCG 2025.10 JSON, evidence JSON, a standalone HTML proof artifact, and a run record. Start with the full token possibility surface, narrow it with located evidence and material experiments, and accept token values only after current rendered-pixel judgment. Never invent a source, audience, product fact, brand premise, comparison corpus, or proof claim.
Motivation
A structurally valid token file can still be generic, misleading, inaccessible, mediocre, or visually poor. Deterministic Mise tasks own repeatable mechanics so strong native vision can concentrate on source interpretation, token relationships, creative experiments, human eye, brain, and touch judgment, and final visual acceptance.
Commands
| Command | Result | Owning task |
|---|---|---|
help |
Show inputs, intents, outputs, vision requirements, and claim limits. | mise run token-help |
generate <inputs> |
Produce <name>.tokens.json, <name>.evidence.json, <name>.proof.html, and <name>.run.json. |
mise run token-run -- <args> |
validate <tokens> |
Check DTCG 2025.10 structure, values, names, references, type agreement, and cycles. | mise run token-validate -- <tokens> |
prove <tokens> <evidence> [sources] |
Assemble, inspect, and read back a source-specific standalone proof. | mise run token-prove -- <args> |