VaultPhoto · Photo Desk v1 · demo
This is James’s photo flow in its simplest honest form: right means save, left means delete pile, and nothing is permanently deleted until you review the left pile and confirm it. The desk below runs the synthetic corpus from the Jin Dynasty storage trials, so the sorting flow and the encryption story can be seen working before real photos ever connect.
Swipe triage, saved pile, delete-pile review, rescue, and confirmed permanent delete — all on the six-pattern trial corpus, with state saved in this browser.
22/22 storage drills passed. Per-photo AES-256-GCM, 64 KiB content-addressed chunks, grants, revoke-by-rotation, and crypto-shredding were exercised by court seats.
No real photo source, no live gallery writes, no production custody. Permanent delete here destroys demo key material in this browser and shows the tombstone state; it does not alter the anchored trial store.
6 of 6 demo photos still need a decision.
These are the keepers from this demo run. You can still move one to the delete pile, or send it back to the deck.
The product gate was never “can we make a pretty deck?” It was “can the pictures stay sealed, be shared narrowly, be revoked honestly, and be destroyed for real?” That is what the seats tested.
F-1 (honest limit): a revoked viewer keeps any copy saved while access was legitimate. Revoke protects the live gallery and everything after it; it cannot un-send copies.
F-2 (finding): a fresh reader with no version pin can accept a rolled-back manifest. Anchored head commitments and client pinning are the countermeasure.
The desk repeats F-1 in product language: “Revoke stops future access — it can’t un-send copies already saved.”
Salted root commitment, anchored on BSV testnet by [email protected]. Explorer v1 is address-view today, so the transaction id is printed in full here and the link opens our explorer.
2bbd59854fc81e6f4db3a92924af9273d8e48fa06ee60e00d70e7cced941096cThe second anchor commits the tombstone head plus the drill and adversarial digests after revocation, integrity, and shredding.
910e5fc861c953c127a9fdf8f054dd90c155226f50369605e8bf8fabb7376a1b