Dados estruturados HEDL sem excesso de JSON
The invoice hiding in your braces
JSON won because it is boring in exactly the right way. Humans can read it. Machines can parse it. Every language has a library for it. If two systems need to exchange an object and nobody wants a standards meeting, JSON is usually where the conversation ends. Fine. There are worse compromises. Many of them have enterprise in the name.
The problem is not JSON as a web format. The problem is what happens when we push JSON into language-model workflows andpretend the cost is free. A model does not see a tidy object in the way an application parser sees one. It sees tokens. It reads the same keys again and again. It spends context on punctuation, repeated field names, wrappers, nested scaffolding, and shape reminders that were already known before the first record arrived.
That waste used to be mildly irritating. With AI systems, it becomes a product problem. Every repeated key competes with evidence, instructions, examples, citations, and actual user content. Every redundant structural token is a little tax on the useful work. The invoice does not say needless braces, because invoices lack poetry. It says tokens.
HEDL starts from a plain observation: when the schema is known, repeating the schema inside every record is silly. Declare the structure once. Encode records positionally. Keep the semantics exact. Convert back to the formats existing systems already expect. That is not anti-JSON ideology. It is a refusal to pay the model to reread the same road sign every ten metres.
This matters because structured AI work is not just chat. It is extraction, classification, tool calls, data transformation, review packets, evidence bundles, MCP calls, workflows, and agents passing objects to each other all day. The more serious the system becomes, the more structure it needs. If structure is expressed in the most verbose possible way, the system pays for its own discipline.
JSON is not the villain
It would be easy, and lazy, to write this as a JSON complaint. JSON has real strengths. It is ubiquitous, debuggable, easy to pipe through existing tools, and good enough for a huge amount of application work. The point is not that JSON is bad. The point is that JSON is often used in places where the receiving side already knows the shape, and there the repetition stops being clarity and starts being cargo.
Consider a structured extraction task. The schema says every answer has a name, source, value, confidence, and rationale. Now imagine sending hundreds of rows to a model or receiving hundreds of rows back from one. JSON repeats those field names for every object. The application parser does not mind. The model context does. The context window becomes a deliveryvan full of labels instead of goods.
HEDL treats the schema as a contract. It names the fields and types once. The records then carry values in order. That sounds obvious because it is. Many efficient formats have made similar tradeoffs for decades. The difference is that HEDL is aimed at LLM-facing structured workflows where human debuggability, conversion, and tool compatibility still matter. It is not a binary blob lobbed over a wall with a note saying good luck.
A implementação do HEDL inclui suporte para biblioteca Rust, utilização via CLI, superfícies de servidor MCP e proxy, WASM, FFI e bindings, além de conversão para e a partir de formatos comuns. Essa combinação é importante. Um formato para fluxos de trabalho de IA não pode ser apenas compacto. Tem de entrar e sair do mundo real sem se tornar um culto privado. As APIs existentes ainda querem JSON. As pessoas ainda inspecionam dados. As ferramentas ainda precisam de idas e voltas. O formato tem de ser denso sem se tornar antissocial.
A estrutura como contrato
A maioria das falhas de IA com dados estruturados não é dramática. São mesquinhas, o que as torna mais difíceis de respeitar até custarem dinheiro a sério. Um campo desvia-se. Um valor é colocado sob a chave errada. Um modelo emite um objeto plausível com um campo opcional em falta. Um parser aceita uma forma que devia ter rejeitado. Uma ferramenta a jusante recebe quase a coisa certa, o tipo de coisa mais perigoso que existe em software.
A abordagem schema-first do HEDL é útil porque torna a estrutura explícita antes de os registos começarem a circular. O schema não é uma sugestão vaga num prompt. É aquilo que diz ao leitor como interpretar os valores. O registo é compacto porque não precisa de se narrar repetidamente. As ferramentas envolventes continuam a poder validar, converter e entregar dados a sistemas que preferem JSON, YAML, XML, CSV ou outras formas convencionais.
As idas e voltas são o teste de saber se um formato é útil ou apenas engenhoso. Se o JSON entra, o HEDL move-se pelo fluxo de trabalho e o JSON sai com a mesma semântica, o sistema ganha densidade sem perder compatibilidade. Se o significado se perde silenciosamente, o formato falhou. O comportamento correto sob pressão não é encolher os ombros e passar o objeto a jusante. É bloquear, reportar e forçar a ambiguidade para o aberto.
É aqui que o HEDL se senta bem ao lado do resto da stack Dweve. O Ledger preocupa-se em que os eventos operacionais permaneçam inspecionáveis. O AION preocupa-se em que as provas de decisão possam ser verificadas. O Trace preocupa-se em que a computação possa ser reproduzida. O HEDL preocupa-se em que os dados estruturados possam ser representados de forma densa e restaurados exatamente. Estes trabalhos tocam-se, mas não são o mesmo trabalho. Mais uma vez: menos palavras de sopa morna, mais fronteiras úteis.
O benchmark não é decoração
As alegações de desempenho em torno da infraestrutura de IA são muitas vezes escritas como histórias de pescador. O número fica maior de cada vez que é recontado. O HEDL tem uma alegação de benchmark concreta: 571 tarefas de extração estruturada em sete conjuntos de dados, 56 por cento menos tokens do que JSON e um ganho de precisão de 10,3 pontos percentuais sobre o JSON.
Esses números devem ser lidos como uma alegação de benchmark, não como uma lei universal da física. Descrevem uma configuração de benchmark. Não significam que todos os fluxos de trabalho obtenham magicamente o mesmo resultado. Mas explicam por que o formato existe. A contagem de tokens não é uma nota de rodapé de implementação em sistemas LLM. É parte da interface. Se duas representações carregam o mesmo significado e uma queima muito mais contexto, a mais pesada não é neutra.
The accuracy gain is especially interesting. It suggests the benefit is not only cheaper prompts. A cleaner representation can also make the task easier for the model. That should not be surprising. If the model spends less attention on repeated syntactic clutter, it has more room for values and relations. This is the same reason good forms beat messy forms in human work. The human may be smart, but do not hand them a tax form written by a printer having a difficult childhood.
There is a broader design lesson here. AI interfaces should not be judged only by whether the model can cope. Models can cope with many bad interfaces. People can also carry furniture up stairs with poor grip and no plan. That does not make it architecture. A good AI interface reduces avoidable work, exposes structure, preserves meaning, and fails loudly when the structure is wrong.
Why proxy surfaces matter
A format rarely wins by being pure. It wins by fitting the ugly middle. HEDL's MCP and proxysurfaces matter because most organisations cannot simply announce that everything now speaks a new representation. They have existing APIs, data stores, validation rules, dashboards, notebooks, and export formats. Replacing all of that to save tokens would be aheroic way to lose friends.
The proxy pattern is more practical. Let models and tools benefit from dense structured representation where it matters. Convert at the boundary. Validate before data leaves the controlled path. Keep downstream JSON compatibility. Let systems that expect JSON receive JSON, but stop forcing the model to haul the full JSON shape through every internal step.
This is also where governance enters, quietly and usefully. If the proxy validates structure, it can reject malformed objects before they become business facts. If it preserves a lossless round trip, it can prove that conversion did not change the meaning. If it keeps compatibility with existingsystems, it can be adopted without turning every integration into a migration programme. We are European. We have enough migration programmes. Some of them still have steering committees from 2014.
For agent systems, the proxy is even more important. Agents pass structured calls and results across boundaries. They call tools, receive outputs, update memory, produce artifacts, and hand state to other agents. A dense representation with validation keeps those handoffs less wasteful and less ambiguous. It does not make the agent wise. It makes the envelope less stupid. That is a respectable engineering outcome.
Where HEDL should not be used
Every useful tool has a place where it should not be used. HEDL is not a replacement for every JSON file on earth. If asmall config file is read once by a human and edited twice a year, JSON or TOML will survive the tragedy. If a public API needs maximum familiarity and the payloads are tiny, JSON is fine. If the schema is genuinely unknown and ad hoc, schema-once encoding is not the right starting assumption.
HEDL becomes interesting when structure is repeated, volumes are meaningful, model context is expensive, round trips matter, and tools need compatibility at the edges. That is why LLM workflows are such a good fit. They sit precisely at the intersection of structured intent and token economics. They also tend to grow from prototype to production faster than anyone planned, because apparently nobody has learned this lesson despite the entire history of software looking mildly offended in the corner.
The practical adoption path should therefore be narrow. Do not rewrite the organisation. Pick a structured extraction workflow. Pick an agent tool-call path. Pick an MCP proxy boundary. Measure token use, failure rate, validation outcomes, and round-trip fidelity. If the numbers hold, expand. If they do not, keep the boring thing. The goal is not to worship a format. The goal is to stop paying for avoidable structure.
The lesson
The lesson of HEDL is that structure is not free just because it is useful. In ordinary software, repeated keys are mostly an annoyance. In AI workflows, they are context, money, attention, and failure surface. If the schema is known, repeating it in every record is often the least imaginative option available.
HEDL makes a simple trade: declare structure once, encode records densely, preserve semantics, convert back when needed, and validate at the proxy boundary. It is not a replacement for JSON as the common language of the web. It is a better internal envelope for structured AI work where the model should be spending its context on meaning, not on reading the same field names until the heat death of the budget.
That is the useful standard for AI infrastructure. Not cleverness for its own sake. Not novelty tax.Not a format that requires everyone else to suffer. A good layer removes waste, keeps the contract explicit, and lets the rest of the system keep working. HEDL earns its place when the object becomes smaller without the meaning becoming softer.
JSON can stay. It has done nothing wrong. It can even have a cup of coffee. It just does not need to sit inside every model call carrying the same set of keys like a man moving house one spoon at a time.