fig. 2.25.1: three layers, and the next session reads the wrong one: nothing runs from the project back to the conversation to mark its copy dead fig. 2.25.1 · three layers, and the next session reads the wrong one: nothing runs from the project back to the conversation to mark its copy dead.⛶ NOTHING RUNS FROM THE PROJECT BACK TO THE CONVERSATION TO MARK ITS COPY DEAD ONE BOX, ONE LAYER; INK ARROW: DONE EVERY SESSION; THIN GREY: ONCE AT START; DASHED ACCENT: NEVER DONE INITIAL LOAD, SESSION START ONLY INVALIDATE WHEN A PROJECT FILE CHANGES: MISSING COMPACTION WRITES CONVERSATION INTO HISTORY NEXT SESSION READS HISTORY INTO CONVERSATION LAYER 2 · PROJECT DURABLE, MUTABLE THE TRUTH LAYER 1 · CONVERSATION EPHEMERAL, VOLATILE WHERE THE MODEL REASONS LAYER 3 · HISTORY DURABLE, APPEND-ONLY WHAT HAPPENED AND WHY MODEL READS source: cairn DESIGN.md "Root cause", lines 109-125 (12dd72d) · threeLayers.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 .