Home / Articles / Scion and sgit / Versions / v1.4.0
Scion and sgit: what changed in v1.4.0
From v1.3.0 (2026-10-27, db67c5ce1) to v1.4.0 (2026-10-28, 1b709edea), paragraph by paragraph.
0 paragraphs added, 0 removed, 2 changed in place, 42 unchanged. About 21 words added and 0 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
9 unchanged paragraphs, under In short {#in-short}
• The gaps are real. No bisect yet, though blame orshipped bisect;in sgit-ai 0.27.0; long histories need a depth; never tested at Scion's scale.
19 unchanged paragraphs, under What Anthropic built {#scion}, Why I recognised it {#recognised}, Measured on a real, busy vault {#measured}…
Scion does blame, bisect and merges on the server and builds history indexes as derived data; sgit's server cannot read a commit, so those run on the client. Today sgit has path history, signed authorship, signed tags and verification, butand nosince blamesgit-ai 0.27.0 on 28 October, blame, grep and noline-level bisect.merges on the client; bisect is designed but not yet built. Where it is behind on its own terms: a partial clone of a long history still walks the commits one request at a time, so a folder with all 1,295 commits takes nearly four minutes, and a depth avoids it; history log for one file over that history takes minutes of CPU; one server process queues concurrent full clones; and the largest vault it has been proven on is 35,000 objects and ten agents, not 100 GB and 30,000 merges a day. Being designed for something is not the same as being proven at it.
14 unchanged paragraphs, under What it means {#means}, What this does not claim {#limits}, Where this comes from {#sources}