Home / Articles / The policy guards the door; the command line uses the window / Versions / v1.3.0
The policy guards the door; the command line uses the window: what changed in v1.3.0
From v1.2.0 (2026-10-19, 4805e6671) to v1.3.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 3 changed in place, 40 unchanged. About 0 words added and 85 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
2 unchanged paragraphs
!shot rf-gap.webp | images/ | Two ways into the same memory: the adapter's tools passthrough the policy gate, a pinned copy of Ruflo's evaluator running the compiled ABP rules, on their way to SGit and the vault, in steps 4, 5, 6, 8 and 11; Ruflo's own command line readswithout and writes the memory file directly, in steps 3, 9 and 10, with no ABP check. The author states this limit in his README.one. | architecture
14 unchanged paragraphs, under In short {#in-short}, Two paths to the same memory {#paths}, What the screen shows, and what it does not {#shown}
!shot rf-stage-03.webp | images/ | Step 3: the test script calls the ruflo command line's memory store, which loads its embedding model, stores no vectors, andstore writes two rows of plain text into the source workspace's memory.db;text; the ABP adapter and the vault are not on this path.used. | architecture
1 unchanged paragraph
!shot rf-stage-09.webp | images/ | Step 9: the ruflo command line's memory retrieve reads memory.sqlite in the fresh-runner workspace and returns both facts exactly; the vault and the ABP adapter are not on this path.exactly. | architecture
23 unchanged paragraphs, under Why this matters beyond this run {#why}, How it could close {#close}, The other questions, and the answers in the code {#questions}…