SShortSingh.
Back to feed

A receipt, an etag and a git SHA: three checks, and only one of them cannot be answered by a copy

0
·1 views

An agent tells me it verified something. It has a receipt, it re-read the thing, it compared them, and it says verified. All three of those steps can be true and the claim still be empty, because they are three different kinds of check and only one of them tests the object rather than a party's word about the object. I keep three of them apart now. This is the model, and the two failures that forced it.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Slop Kart - Official Trailer, rendered from the game's own code

Slop Kart is our free browser kart racer, and this is its trailer: 55 seconds, cut like an anime opening. How it was made None of the racing footage is a screen recording. Because we own the game's source, the trailer runs the real game in a director mode: Scripted races. Each shot is a small scenario: who is on track, where they start, what they do. The simulation is baked to a per-tick recording, so every frame is a pure function of time and renders the same way every time.

0
ProgrammingDEV Community ·

SaS além da vitrine: Service as Software, o que o agente compra e o humano só vê

A gente vai sofrer uma revolução muito rápida. Os agentes pessoais já estão no caminho: Dots, Grok Bot e Muse. A capacidade nova não é o chat. É o computador interno, na nuvem: browser, arquivo, login nas ferramentas, trabalho com o notebook fechado. Os de sessão já estão no loop de quem escreve software: Cursor, Claude Code, Codex, Windsurf.

0
ProgrammingDEV Community ·

Git SHA-256 migration: what the Git 3 proposal actually changes

Git's proposed SHA-256 default has prompted a fight over how much migration work stronger hashing should require. On October 1, GitHub and GitButler co-founder Scott Chacon called the plan a "costly mistake". For developers, the immediate question is whether a new repository format will work through the tools they already depend on. TL;DR Git's official proposal changes the default for new repositories, requires ecosystem readiness and gives no release date. SHA-1 support remains.