Skip to content

docs(three-machine-rehearsal): map rehearsal shortcuts to a fully distributed ceremony - #4

Merged
mellowcroc merged 1 commit into
add-ceremony-tools-installerfrom
fix/rehearsal-independence-mapping
Aug 20, 2026
Merged

docs(three-machine-rehearsal): map rehearsal shortcuts to a fully distributed ceremony#4
mellowcroc merged 1 commit into
add-ceremony-tools-installerfrom
fix/rehearsal-independence-mapping

Conversation

@mellowcroc

@mellowcroc mellowcroc commented Aug 20, 2026

Copy link
Copy Markdown
Collaborator

The three-machine rehearsal co-locates roles and centralizes two things so it runs fast on three hosts. The README flagged this as "not production independence evidence" but did not spell out what actually changes when every role is its own independently operated machine — which is the natural next question after running it.

Adds a "From this rehearsal to a fully distributed ceremony" section mapping each of the three co-location shortcuts to its distributed replacement:

Rehearsal shortcut Distributed replacement
Central key generation (00-coordinator-initialize.sh mints all keypairs on Machine 1) Each role generates + enrolls its own key; only the public key + signed enrollment reach the coordinator
Central operational evidence (steps 33–41; coordinator generates receipts, roles re-upload) Each witness/mirror/auditor produces and signs its own record locally (ops prepare-public-witness-receipt, relay mirror receiptops prepare-mirror-receipt, audit)
Role co-location (Machines 2/3 each hold five keys) One key per machine — the scripts are already identity-parameterized, so the 3-machine split is illustrative

Points to COORDINATOR_RUNBOOK.md / ROLE_RUNBOOK.md as the authority for the distributed procedure. Docs only, single file.

Motivation: came up while running the tiny rehearsal end to end on both AWS S3 and Cloudflare R2 — the flow works, but a reader planning a real separate-machine ceremony needs to know exactly which rehearsal shortcuts to drop.

@mellowcroc
mellowcroc force-pushed the add-ceremony-tools-installer branch from e5df0f1 to 9f949a0 Compare August 20, 2026 13:27
…tributed ceremony

The rehearsal co-locates roles and centralizes two things (key generation and
operational-evidence generation) so it runs fast on three hosts. The README
flagged this as 'not production independence evidence' but did not say what
actually changes when every role is its own independently operated machine.

Add a table mapping each of the three co-location shortcuts to its distributed
replacement:
- central keygen -> each role generates and enrolls its own key;
- central operational evidence (steps 33-41) -> each witness/mirror/auditor
  produces and signs its own record locally (ops prepare-public-witness-receipt,
  mirror receipt -> ops prepare-mirror-receipt, audit);
- role co-location -> one key per machine (the scripts are already
  identity-parameterized, so the 3-machine split is illustrative).

Points to COORDINATOR_RUNBOOK.md / ROLE_RUNBOOK.md as the authority for the
distributed procedure. Docs only.
@mellowcroc
mellowcroc force-pushed the fix/rehearsal-independence-mapping branch from 48b1796 to e539379 Compare August 20, 2026 13:28
@mellowcroc
mellowcroc merged commit 334656b into add-ceremony-tools-installer Aug 20, 2026
1 check passed
@mellowcroc
mellowcroc deleted the fix/rehearsal-independence-mapping branch August 20, 2026 13:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant