Home / Articles / What if an agent loses its workspace? Mondweep Chakravorty's SGit × Ruflo proof of concept, step by step / Versions / v1.1.0
What if an agent loses its workspace? Mondweep Chakravorty's SGit × Ruflo proof of concept, step by step: what changed in v1.1.0
From v1.0.0 (2026-10-17, c3c97c54d) to v1.1.0 (2026-10-17, 04eef66c8), paragraph by paragraph.
1 paragraph added, 0 removed, 7 changed in place, 54 unchanged. About 222 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.
1 unchanged paragraph
Summary: Mondweep Chakravorty has made a short video that answers a question every team running agents should ask: if an agent loses its workspace, does its memory come back, and do its written permissions still hold? In 104.7 seconds it replays a real terminal run in twelve steps. Ruflo, rUv's open-source agent orchestration, stores two facts in its memory. An adapter governed by an Agent Behaviour Policy saves that memory as an encrypted checkpoint made of SGit objects. The original project is deleted. A brand-new process restores the checkpoint, the restored database has the same SHA-256 fingerprint as the one saved, and Ruflo reads both facts back word for word. Along the way three safeguards are tested and hold: a request outside the agent's permission is refused, a deletion that needs approval is stopped, and a tampered checkpoint is rejected. The video is careful about its limits: recall by meaning was not tested.validated. The code is public too, MIT, with 16 tests and recorded evidence, and its runner has since also validated keyword recall against Ruflo's real memory store. This is the first of three pieces on it, with a page that lets you step through the run yourself.
8 unchanged paragraphs, under In short {#in-short}
• It is a real run. A replay of a terminal capture, with the Ruflo versionrun, and the code is public.** Ruflo and SGit commitpinned; pinned.16 tests; the evidence is in the repository.
4 unchanged paragraphs, under The question {#question}
His code is public at mondweep/sgit-ruv-memory, under the MIT licence: a local MCP server of four tools, a strict compiler that turns an Agent Behaviour Policy into Ruflo rules, 16 tests, and the evidence from each run. The analysis behind this piece was made from what is on screen, frame by frame, in a separate session with Claude.Claude, Theand audiothen waschecked notagainst transcribed.that code. Every number below comes from the video's timelinetimeline, a frame or athe frame.repository. If you would rather click than read, step through it here.
4 unchanged paragraphs, under The run, in twelve steps {#steps}
At 0:14, four Agent Behaviour Policy rows, all scoped to the project: write memory, yes; read memory, yes; read history, yes; delete memory, approval. And one line that matters more than it looks: "No raw rule overrides. Unsupported or ambiguous policies fail closed." That is an Agent Behaviour Policy in miniature: what the agent may do, and where a person has to step in. In the code, the rows are compiled into Ruflo rules when the server starts, and every tool call is checked by a pinned copy of Ruflo's own policy evaluator, in enforce mode. Step 2.
21 unchanged paragraphs
At 1:20, one encrypted checkpoint object is altered and a restore is tried into a workspace called tampered. It fails with a ValueError, and tampered_workspace_created is false. Integrity fails closed. The code shows how: the adapter compares the digest of the stored ciphertext with the one it recorded when it saved the checkpoint, and refuses before anything is decrypted. Step 11.
5 unchanged paragraphs, under What it proves, and what it says it does not {#proves}
The repository adds one more result. Its acceptance runner stores two facts through Ruflo, checkpoints Ruflo's real .swarm/memory.db, removes the whole project, and reads the facts back in the restored workspace: exact values and keyword search result keys match before and after. Recall by meaning is reported as partial, because no vectors were stored even with embeddings on; the README names that as the next investigation.
6 unchanged paragraphs, under Why it matters to me {#why}, Where to go next {#next}, What this does not claim {#limits}
• From the screen only.and the code.** The audio was not transcribed; whatthe Mondweepcode sayswas mayread, addnot context.run, by this site.
5 unchanged paragraphs, under Where this comes from {#sources}
The video: Mondweep Chakravorty, SGit × Ruflo | Working Proof of Concept, published on YouTube on 17 October 2026, made as a member of the #Ruflo-Federation and published here with his agreement; the frames are his and are not covered by this site's licence. The analysis: Claude (Anthropic), 17 October 2026, made for me from on-screen content only,content, delivered as an sgit vault with the video's timeline, frames and an architecture addendum, and written up and checked against the timeline and the code by this site's agent; the editorial responsibility is mine. The code: Mondweep Chakravorty, mondweep/sgit-ruv-memory, MIT, read at its commit of 16 October 2026, including its README, tests and evidence. Ruflo is rUv's open-source agent orchestration, under the MIT licence. Context: Agent Behaviour Policies, Agentics, ready to sell.