06 — Interface mockups
Summary
A familiar thing on unfamiliar foundations: forge conventions are followed everywhere, and the novelty budget is spent on exactly two things — the ciphertext panel and the tier indicators. The panel is the screen the specification says must be designed in, not bolted on: while a visitor reads a file, it lists the actual requests the page made — names, sizes, opaque bytes — which makes it an argument rather than a marketing claim. The hub index renders four row states (readable, listed-only, structure-visible, and hub — the fractal edge), with mirror offered on every row including the ones you cannot read. The private-vault open flow carries the vault-key refusal word for word, and the fork screen states the measured properties: a rekey turns over 100% of object ids, and forks share zero identifiers.
Key concepts
- The live ciphertext panel — lists the requests this page actually made, all opaque — far more persuasive than any page explaining zero knowledge
- Four row states — readable, listed-only, structure-visible, hub — the affordances differ by what you hold, and the tier you are in is always visible
- Custody without access is a capability — mirror appears on rows you cannot read — holding and verifying ciphertext needs no trust and no key
Key ideas
- The structure-key screen is buildable today, and no conventional forge can express it.
- Never imply a capability that does not exist: no revoke button, no search box that silently searches only what you hold.
- Show the head's age — freshness is the reader's problem, so the interface must surface it.