Record workflow rehearsal

Explore the record path before it is connected.

This studio is a browser-only model of the museum-record command path. It helps a first contributor understand drafts, corrections, independent statuses and the DOI outbox before public intake opens. It does not create an account, upload a file, write D1 data, sign a record, or register a DOI.

DEMO ONLY
Nothing entered below leaves this browser tab.

The source includes a transactional record command, but this public site is static and has no authenticated D1, media, trust or DOI connection. The controls model the data and state boundaries that a future command adapter will perform.

01 Draft 02 Version 03 Submit 04 Publish

Local draft

Describe a proposed record.

These map to the first required submission fields: title, event, authorship, rights and an already-promoted media reference. A real upload and media-verification pipeline is not connected here.

Command boundary

What the UI will hand over when intake opens.

The browser will never decide publication on its own. It will hand an authenticated command to the museum service, which verifies the trust references and all database facts before making one transactional D1 write.

01

Browser preparation

Build the canonical version payload, attach the owner’s signature and personal Veritas reference, and collect declared record fields. No private key is sent to Clio.

02

Server verification

Verify ownership, account and policy state, media promotion, terms, canonical commitment, signature and trust references. Rejections return reasons, not partial records.

03

Atomic publish + intent

On success, D1 writes the record, frozen version, evidence links, publication state, DOI job and doi.register outbox entry together. Provider registration happens later.