A log cannot carry a negative
Hugging Face published a forensic account of the July agent intrusion — 17,600 recovered actions, four and a half days, the method published alongside it. Most of the commentary has been about the kill chain. The interesting part is the sentences that cannot be checked: the database was read and not written, no bulk extraction in the flow logs, no unauthorized commits. Every one of those is a negative, and a log is a list of things that happened.
Read →
We needed somewhere to put the evidence
Infrastructure doesn’t forget. It remembers in fragments — a token exchanged here, a role assumed there, a controller reacting somewhere else, each one recorded by something that doesn’t know about the others. Why Ahti exists as an append-first evidence database, and why it refuses to interpret what it stores.
Read →
Non-determinism is not a failure mode
The execution layer of the software supply chain was built for same input, same output. Once models enter the loop, non-determinism is not an edge case but a property of the system, and the graph needs a different execution model.
Read →
Pipelines don’t rot. Their abstractions do.
LangChain pipelines written in 2023 don’t run in 2026. The code is fine. The abstractions underneath it aren’t. The model API changed, the retrieval pattern changed, the wrapper library rewrote its surface twice. The pipeline is a fossil of dependencies that were never stable. This is not a library quality problem — it is the absence of a layer.
Read →
Correlation is a data structure
Observability has three mature output formats: logs, metrics, traces. All three answer what happened. None of them answer why. That answer has always lived somewhere else — in a dashboard, in a runbook, in the head of the engineer who got paged at 3am. For thirty years the stack got away with this, because the consumer was human. When the consumer is an AI agent, the whole model breaks.
Read →
The same brain wrote both sides
An agent writes a function, then writes a test for that function. The loop is closed before it starts: the test knows the implementation, the mock knows the schema, the assertion knows the return type. Of course it's green. What it takes to test something from the outside instead.
Read →

Berlin. Pre-seed. First product in private use.

Impressum
Angaben gemäß § 5 TMG

Yair Etziony
Leinestr. 20
12049 Berlin
Deutschland

Kontakt
yair@false-systems.com