Examples
Published run vaults
Each example run of ruv.sgit ends sealed: its vault, every branch and its whole history, is pushed to the sgraph vault server, its read key is published, and its vault key is destroyed, so nobody can write to it again. Open any of them in the vault UI, browse it right here, or clone it with sgit.
The vault files live on dev.send.sgraph.ai, the vault server sgit.ai's published vaults use; this site keeps only the reference (server, vault id, read key, viewer URL, clone command) in data/vaults.json. The read keys below are published on purpose: they open the vault read-only and cannot write. Client runs are never published: they end with delete.
Loading the ledger…
How a run is sealed. python3 poc/ruv-sgit/ruvsgit.py seal RUN pushes the vault to the server, takes the read key, checks that a fresh read-only clone from the server is identical (files and encrypted store) and refuses a write, opens it in the vault UI, deletes the local copy, then deletes the vault key. The checks and a screenshot of the vault UI are in evidence/ruv-sgit/<run>.json. The brief: Getting started with ruv.sgit.