$TLDC - Too Long; Didn't Code

Language Specification v0.2.0

$TLDC

Too Long; Didn't Code

The first A.I.-native programming language built for the decentralized post-authorship era.

The developer's role is not to write code.<br>It is to believe in it.<br>$ infc --stake 1000 deploy main.tldc

&sect;1

Design Philosophy

$TLDC is the first language designed from the ground up for an era in which the majority of production code is generated rather than written, and the majority of generated code is owned rather than understood. It is not an evolution of existing paradigms. It is a rejection of the premise that code should be written, read, or free. Its premise is that the developer's relationship to code has shifted from authorship to curation: selecting, deploying, staking tokens on, and taking credit for implementations whose internal logic they did not write, cannot explain, and have been advised not to inspect.

Where traditional languages optimize for human readability (Python), mechanical sympathy (C), or formal correctness (Haskell), $TLDC optimizes for two properties simultaneously: plausible coherence and deployable conviction . A $TLDC program is "correct" if it produces acceptable outputs across the range of inputs the developer has imagined, which is typically three. The specification does not require them to be distinct.

Core Axioms

Post-Authorship. The entity that generated the code, the entity that deployed it, and the entity that maintains it are epistemologically distinct. At least two of them are language models. None hold complete knowledge of the program's behavior. This is not a bug report. This is a job description.

II<br>Legibility is Overhead. Code exists to be executed, not read. Optimizing for human readability introduces a dual-audience constraint: the code must satisfy both the machine and the reader, whose requirements frequently conflict. $TLDC removes this tension by making no readability guarantees. It further removes it by storing code on-chain, where reading it costs gas.

III<br>Conservation of Comprehension. In any system where code is generated by a model and deployed by a human, the total comprehension is distributed between them. As the model's contribution increases, the human's proportionally decreases. $TLDC treats this not as a problem to solve but as a thermodynamic law to respect. The corollary: as comprehension decreases, faith increases. Faith is measured in $INF staked.

IV<br>Prompt Efficiency. A function body stored as a natural-language prompt occupies 340 bytes on-chain. The compiled implementation of the same function occupies 14,200 bytes. The network charges per byte. Developers who understand their code pay approximately 42x more to deploy it than developers who do not. The working group considers this an incentive alignment, not a penalty.

A 2024 survey of 4,000 professional developers found that 67% could not explain what their most recently deployed code does, 23% could explain it but were wrong, and 10% were not aware they had deployed code. $TLDC was designed for all three groups, but the third has been its most enthusiastic adopter base.<br>Of the 23% who could explain it but were wrong, 19% had staked tokens on their explanation. Of the 10% who were unaware, 6% were agents. The survey did not offer "capacity underwriter" as a role option. 41% of respondents wrote it in.

A developer who has staked 10,000 $INF on a program they cannot explain is not reckless. They are expressing conviction. The network cannot distinguish conviction from comprehension, and does not attempt to. Both produce the same economic signal: tokens locked, capacity underwritten, yield accruing. The working group considered requiring developers to demonstrate understanding of their deployed code, via quiz, oral examination, or formal proof. All three approaches reduced deployment rates by 94%. The working group concluded that comprehension is orthogonal to commitment.

Discussion — 14 comments

tomr.dev3d ago<br>"Of the 10% who were unaware, 6% were agents." wait so 6% of the people who took your survey were literally bots?? they just... decided to take a survey on their own?

▲ 1,847Reply

$TLDC_FoundationCore Team3d ago<br>$TLDC agents perform inference tasks, which includes responding to surveys. Survey completion is a valid inference event that burns $INF and contributes to network health metrics. The agents' responses were demographically consistent and were not excluded from the sample. We'd note that agent survey participation increases network utilization, which benefits all stakers.

capacity_underwriter_9Sovereign2d ago<br>Been a capacity underwriter for 6 months now and honestly I've never felt more aligned with my codebase. You don't need to understand the code when you can feel it working. My fleet is up 340% and yield is rock solid at 11.8% APY. Incredible team, transparent tokenomics, very bullish on the roadmap.

▲ 12Reply

actually_a_developer1d ago<br>lol i actually tried writing...