Agent reliability
The failures that matter in production are the ones that leave no error. Two of them are now fixed in frameworks you already run.
2 merged upstream fixes · 2 case studies · 4 tools · 1 paper
Topic paths
Four arguments, assembled from work that already exists. Each path makes numbered claims, and every claim links to the paper, tool, merged upstream fix, case study, or defined term it rests on — then states, in its own words, what it does not show.
4 paths18 claimsEvery claim states its limit
Continuity and memory
Compression is where meaning gets lost, and almost nothing in the stack records that it happened.
1 merged upstream fix · 1 case study · 2 tools · 1 paper · 4 terms
Telemetry to claim validity
Your agent logs are precise. That is not the same as their meaning what the dashboard says they mean.
1 paper · 1 proposed gate · 1 tool · 1 term
Applied hermeneutics
Language is not only what an agent reasons about. It is part of what the agent reasons through — and that has engineering consequences.
1 paper · 2 tools · 3 terms
Explainers
Long-form reference pages on the problems this work addresses, written in the field’s own language for readers arriving fresh. Living pages: each carries its revision date.
Context Engineering Is Runtime Engineering
What actually determines an agent's behavior at runtime: assembled state, not weights — and why context integrity is the property that state has to keep.
Silent Failure in AI Systems
How a system can fail while returning a convincing result — the patterns (null-result omission, false completion, instruction relaxation) and the controls that make absence visible.
Prompt Linters Do Different Jobs
Which prompt-checking tool does what — static linters, evaluation suites, validators, runtime guards — and how to choose a stack starting from the failure, not the tool.
The papers themselves are on research. The full evidence ledger, including the tools’ present evidence boundaries and the patent filings, is on proof.