moved step 0s to part 0s

shannona · shannona · commit 0270d2e3eb11 · 2026-03-17T09:16:27.000-10:00
diff --git a/docs/01_2_Your_First_XID.md b/docs/01_2_Your_First_XID.md
@@ -101,7 +101,7 @@ and endorsement history).
 true self-sovereignty, rich metadata support, holder-based elision,
 and ongoing key management.
 
-## Part I: Preparing to Work
+## Part 0: Preparing to Work
 
 Like all of the "Learning from ..." courses, "Learning XIDs from the
 Command Line" is intended for hands-on work. By experimenting with
@@ -146,7 +146,7 @@ envelope._This is expected._ Focus on understanding what each step
 accomplishes, not matching exact output. Additional differences at
 this level will appear in future tutorials.
 
-## Part II: Creating the XID
+## Part I: Creating the XID
 
 This first tutorial will take you through the basic steps to create a
 XID. It's deliberately simple. Subsequent tutorials, we'll explore
@@ -589,7 +589,7 @@ fi
 
 The digests are identical. You removed the private key, yet the hash didn't change. 
 
-## Part III: Verifying a XID
+## Part II: Verifying a XID
 
 One of the powers of a XID is that it can be verified in various ways
 (though that doesn't necessarily mean someone is who they say they
@@ -704,7 +704,7 @@ Amira creates information with her secrets, and only she can update
 that information. But after she distributes her public XID, anyone can
 check it.
 
-## Part IV: Storing Your Files
+## Part III: Storing Your Files
 
 This course will frequently store copies of files for future
 usage. But, we're not quite there yet because we'll be finishing up
diff --git a/docs/01_3_Making_a_XID_Verifiable.md b/docs/01_3_Making_a_XID_Verifiable.md
@@ -33,12 +33,7 @@ This isn't about discovery (how Ben finds Amira's XID in the first
 place). It's about freshness (how Ben verifies he has the current
 version).
 
-## Part I: Publishing a XID
-
-You'll add a publication URL to Amira's XID and then publish a public
-view of that.
-
-### Step 0: Verify Dependencies
+## Part 0: Verify Dependencies
 
 Before you start, ensure that you have the required CLI tools from Tutorial 01:
 
@@ -54,6 +49,11 @@ If either tool is not installed, see [Step 0 of
 §1.2](01_2_Your_First_XID.md#step-0-setting-up-your-workspace) for
 installation instructions.
 
+## Part I: Publishing a XID
+
+You'll add a publication URL to Amira's XID and then publish a public
+view of that.
+
 ### Step 1: Load Your XID
 
 To reload your XID, first be sure to recreate your environmental variables:
diff --git a/docs/02_1_Creating_Self_Attestations.md b/docs/02_1_Creating_Self_Attestations.md
@@ -86,15 +86,7 @@ witness attestations do their best to report without bias. This makes
 them more verifiable, and verifiability is what's important in the
 world of pseudonymous claims.
 
-## Part I: Adding an Attestation Key
-
-Amira contributed to Galaxy Project, an open source bioinformatics
-platform. Her pull request added mass spectrometry visualization
-features. This is the kind of specific, verifiable claim that builds
-real credibility. You're going to build an attestation about that
-claim, but first you need to create a secure way to make attestations.
-
-### Step 0: Verify Dependencies & Reload XID
+## Part 0: Verify Dependencies & Reload XID
 
 Before you get started, ensure you have the required tools installed:
 
@@ -116,6 +108,14 @@ XID=$(cat envelopes/BRadvoc8-xid-private-1-03.envelope)
 XID_ID=$(envelope xid id $XID)
 ```
 
+## Part I: Adding an Attestation Key
+
+Amira contributed to Galaxy Project, an open source bioinformatics
+platform. Her pull request added mass spectrometry visualization
+features. This is the kind of specific, verifiable claim that builds
+real credibility. You're going to build an attestation about that
+claim, but first you need to create a secure way to make attestations.
+
 ### Step 1: Create an Attestation Key
 
 Every attestation, even a self-attestation should be signed. Viewers
diff --git a/docs/02_2_Managing_Claims_Elision.md b/docs/02_2_Managing_Claims_Elision.md
@@ -66,11 +66,10 @@ Amira has three options for handling the correlation risk of her crypto audit ex
 
 Amira decides her crypto audit experience fits the middle category. She might need to prove this capability to future collaborators, but she doesn't want to publish it broadly. She'll commit an elided version publicly and reveal the full attestation selectively.
 
-> :brain: **Learn more**: These three approaches are part of the broader concept of [Selective Disclosure](../concepts/selective-disclosure.md), which is the ability to reveal different information to different parties from the same underlying data structure.
+> :brain: **Learn more**: These three approaches are part of the broader concept of [Selective Disclosure](../concepts/selective-disclosure.md), which is the ability to reveal different information to different parties from the same underlying data structure
+.
 
-## Part I: Creating a Commitment
-
-### Step 0: Verify Dependencies & Reload XID
+## Part 0: Verify Dependencies & Reload XID
 
 As usual, check your `envelope-cli` version:
 ```
@@ -90,6 +89,12 @@ ATTESTATION_PUBKEYS=$(cat envelopes/key-attestation-public-2-01.ur)
 ```
 If you instead need to create new ones, see [§2.2](02_1_Creating_Self_Attestations.md#step-1-create-an-attestation-key) for how to do so, then register your keys in your XID.
 
+
+## Part I: Creating a Commitment
+
+Creating a commitment means creating an attestation (or really, any
+data) and then boiling it down to just a digest by hasing the data.
+
 ### Step 1: Create the Sensitive Attestation
 
 You should create Amira's crypto audit attestation with [fair witness](../concepts/fair-witness.md) precision:
diff --git a/docs/02_3_Managing_Claims_Encryption.md b/docs/02_3_Managing_Claims_Encryption.md
@@ -69,12 +69,7 @@ sensitive. Amira's crypto audit experience could be committed publicly
 hinting she has human rights tech credentials could draw unwanted
 attention.
 
-## Part I: Setting Up for Encryption
-
-Setting up requires you making sure you have your variables in order
-and DevReviewer sharing a public key.
-
-### Step 0: Verify Dependencies
+## Part 0: Verify Dependencies
 
 As usual, check your `envelope-cli` version:
 ```
@@ -91,6 +86,11 @@ ATTESTATION_PRVKEYS=$(cat envelopes/key-attestation-private-2-01.ur)
 ATTESTATION_PUBKEYS=$(cat envelopes/key-attestation-public-2-01.ur)
 ```
 
+## Part I: Setting Up for Encryption
+
+Setting up requires you making sure you have your variables in order
+and DevReviewer sharing a public key.
+
 ### Step 1: Create Keys for Receiving
 
 DevReviewer needs keys to receive encrypted data. They create a
diff --git a/docs/03_1_Creating_Edges.md b/docs/03_1_Creating_Edges.md
@@ -80,17 +80,7 @@ information can be found.
 
 Edges will be the topic of this chapter.
 
-## Part I: Setting Up a GitHub Account
-
-The first step is one that Amira did a while ago: setting up her
-BRadvoc8 GitHub account. She created a signing key for it, uploaded
-it, and has since been using that to sign commits, including the
-Galaxy Project commit that she references in her claim from
-[§2.1](02_1_Creating_Self_Attestations.md).
-
-Here's a review of how all that was done.
-
-### Step 0: Verify Dependencies
+## Part 0: Verify Dependencies
 
 As usual, check your `envelope-cli` version:
 ```
@@ -106,6 +96,16 @@ XID_ID=$(envelope xid id $XID)
 PASSWORD="your-password-from-previous-tutorials"
 ```
 
+## Part I: Setting Up a GitHub Account
+
+The first step is one that Amira did a while ago: setting up her
+BRadvoc8 GitHub account. She created a signing key for it, uploaded
+it, and has since been using that to sign commits, including the
+Galaxy Project commit that she references in her claim from
+[§2.1](02_1_Creating_Self_Attestations.md).
+
+Here's a review of how all that was done.
+
 ### Step 1: Generate SSH Signing Key
 
 Amira needed to create SSH keys for signing her Git commits. These are
diff --git a/docs/03_2_Supporting_Cross_Verification.md b/docs/03_2_Supporting_Cross_Verification.md
