docs(vault): a how-to for shielded sign-off, linked from both vaults - #383
Open
QSchlegel wants to merge 1 commit into
Open
docs(vault): a how-to for shielded sign-off, linked from both vaults#383QSchlegel wants to merge 1 commit into
QSchlegel wants to merge 1 commit into
Conversation
The construction was shipped without anywhere that explains it. The vault pages show a trust graph and a disclosure path to someone who has not been told what either means. The guide covers the three things that actually change how you use it: why the logical and trust relations must stay apart (hashes cannot cycle, so the moment you want tamper-evidence you must decide which references carry weight), why one root is not enough (proving anything reveals the root, and the root tells the recipient how your organisation is grouped), and exactly what a disclosure gives away — including the part that is easy to miss, that it leaks the COUNT of documents under the disclosed hub and the count of hubs. It also says plainly what is not a button yet. `disclose` and `verifyDisclosure` exist with tests covering relabelling, reordering, tampering and cross-vault splicing, but grep confirms they are imported only by the test file: nothing in the product exports a disclosure artefact. The vault view SHOWS what one would reveal, which is the part that changes how you organise a vault, and the guide is explicit that handing the artefact to a counterparty is the next step rather than a shipped one. Promising otherwise in a guide about proofs would be a strange place to start being loose. Linked from the wallet's own vault and from the public demo, because a guide nobody can find from the thing it explains is not documentation. 1161 tests pass; tsc clean; next build exit 0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The construction shipped without anywhere that explains it. The vault pages show a trust graph and a disclosure path to someone who has not been told what either means.
What the guide covers
The three things that actually change how you use it:
Plus the setup path, which was the original complaint: your vault is not a separate thing you create, it is built from documents you already have, and
documentTypeis what becomes the hub.It says what is not a button yet
discloseandverifyDisclosureexist with tests covering relabelling, reordering, tampering and cross-vault splicing — but grep confirms they are imported only by the test file. Nothing in the product exports a disclosure artefact.So the guide states that plainly: the vault view shows what a disclosure would reveal, which is the part that changes how you organise a vault, and handing the artefact to a counterparty is the next step rather than a shipped one. A guide about proofs is a strange place to start being loose about what exists.
Linked, not just published
From the wallet's own vault and from the public demo at
/vault. A guide nobody can reach from the thing it explains is not documentation.It also picks up the existing blog SEO wiring for free —
getAllPostsMetalists it, and the sitemap includes every published post.tsc --noEmitclean; 1161 tests pass;next buildexit 0.🤖 Generated with Claude Code