Andrew Fribush

fig. 2.25.2: every failure the project logged is one cache-coherence bug: a stale read, a dirty write-back, the log read as the database, the wrong home

fig. 2.25.2 · every failure the project logged is one cache-coherence bug: a stale read, a dirty write-back, the log read as the database, the wrong home.
EVERY FAILURE THE PROJECT LOGGED IS ONE CACHE-COHERENCE BUGONE ROW, ONE FAILURE THE PROJECT LOGGED; GREY: WHAT HAPPENED IN THE THREE LAYERS;ACCENT: ITS CACHE NAMESUPERSEDED PROSE LEAKINGLAYER 2 CHANGED; LAYERS 1 AND 3 STILL HOLD THE OLD BODY= STALE READ AFTER A MISSED INVALIDATIONCONFABULATION LAUNDERINGA DIRTY LAYER-1 LINE WRITTEN INTO LAYER 3, READ BACK AS TRUTH, NEVER CHECKEDAGAINST LAYER 2= DIRTY WRITE-BACK READ AS CLEANEVENT LOG AS TRUTHTHE SESSION READS LAYER 3 FOR WHAT IS TRUE, NOT LAYER 2= READING THE CACHE LOG INSTEAD OF THE DATABASESCOPE BY CWDTHE WORKING DIRECTORY DECIDES WHICH LAYER 2 THE MODEL COHERES TO= COHERENCE AGAINST THE WRONG HOME

source: cairn DESIGN.md "Root cause", lines 125-132 (12dd72d) · cacheFailures.data.ts

View in context: Confabulation Is a Cache-Coherence Bug → · All figures

Andrew Fribush, software and computer engineer in Austin. I build consequential systems where software meets institutions: finance, healthcare, commerce, government data, and the mechanisms that govern AI agents. Taking new engagements: hello@andrewfribush.com.