Home / Vaults / The Vault Catalogue
The Vault Catalogue
The index of published vaults — itself a vault, published with a read key, and listed in itself.
Open it yourself — the key is the whole credential.
Read key:
In the official UI: open it read-only in a new tab · From the CLI:
Published deliberately. It grants read, and only read — a write attempt is refused by the server’s write gate (the R1 W0 badge you will see in the chrome).
Read key:
sgit_rk1_fd71e4bde7232498e43a5da869b1501260d9d403031b20af87b5bc801bdf6280:kc67yhgwIn the official UI: open it read-only in a new tab · From the CLI:
sgit clone sgit_rk1_fd71e4bde7232498e43a5da869b1501260d9d403031b20af87b5bc801bdf6280:kc67yhgwPublished deliberately. It grants read, and only read — a write attempt is refused by the server’s write gate (the R1 W0 badge you will see in the chrome).
See it live, here
What this vault demonstrates
| Feature | How this vault uses it |
|---|---|
| Recursion, usefully | an index of published vaults that is itself a published vault, listed in itself — rendered live at /catalogue/ |
| Submission queue | an entry costs a read key and one line; everything else is derived by an agent opening the vault |
| Published to-do lists | todo/awaiting-read-key.md and todo/awaiting-processing.md are public, because a named gap gets filled |
| First-class write-key status | every entry records whether the write key is escrowed or lost, because a frozen vault can never be corrected |
What this shape is for
Machine-and-human-readable registries that update by pushing to a vault rather than deploying a site. The schema here is deliberately the first instance of what a vault hub would need.
Derived facts
9 files · 11 KB · 2 commits · markdown, no app · derived from the read key alone by admin/build/catalogue_derive.py — the same derivation that populates the catalogue, where this vault also has an entry.