DTL, not JSON — the sovereign data format
JSON is fine for machines. DTL is fine for humans, machines, and git.
What JSON gets wrong
JSON is not human-first. Punctuation-heavy. Comment-free. Diff-hostile in git. Bracket-mismatch errors that require a linter. Fine as a wire format, wrong as a config format.
What DTL does
DTL — Domain Transport Language — uses @key value pairs, indent-based blocks, human comments, and native size/duration units. It reads like configuration is supposed to read. It diffs like source code is supposed to diff.
Why the whole substrate is DTL
Every NEXUS entity is a DTL file. Every configuration is a DTL file. Every scraped source lands as DTL before it enters the substrate. One format, one parser, one grep. Simplicity compounds.
Why we use different words
Where the industry says LLM, we say CLLM. Where it says vector database, we say NEXUS. Where it says Chain-of-Thought, we say PRISM proof-tree. Where it says RAG, we say LATTICE. Where it says trillion-token dataset, we say Smart Router Dataset. Different words because different architecture. Read the whitepaper.