updated intra-links

Author: shannona

docs/01_0_Introduction.md

@@ -30,6 +30,7 @@ Supporting objectives include the ability to:
 
 * Understand what a XID is.
 * Know what a pseudonymous identity is.
+* Understand a variety of underlying concepts.
 * Understand the power of dereferencing.
 
 ## Table of Contents

docs/01_1_Getting_Started_SSI_XIDs.md

@@ -26,8 +26,8 @@ users should have full visibility on their identity, they should have
 principal authority over it, and they should be able to move it around as
 they see fit.
 
-Unfortunately, as the SSI ecosystem matured, it has moved away from
-these core principles, as discussed in ["Has our SSI Ecosystem Become
+Unfortunately, as the SSI ecosystem matured, it moved away from these
+core principles, as discussed in ["Has our SSI Ecosystem Become
 Morally
 Bankrupt?"](https://www.blockchaincommons.com/musings/musings-ssi-bankruptcy/). Issuers
 took control of identities and created centralized points-of-failure
@@ -47,7 +47,7 @@ It starts out with the core design: a XID is an autonomous
 cryptographic object (ACO). It's a self-sufficient package that
 contains an identifier, keys to control that identifier, and other
 data. You don't need to depend on any infrastructure: there's no
-separate issuer or verifier, no centralized authority at all. It's
+separate issuer or verifier, no centralized authority at all. A XID is
 holder-created and holder-controlled. That's the dream of
 self-sovereign identity.
 
@@ -63,11 +63,11 @@ issuer (which violates the most central vision of SSI).
 The technology in XIDs is novel (including deterministic encoding,
 radical elision, and progressive trust). The privacy is greatly
 improved over existing systems that put issuers in the driver's
-seat. Finally, it's supported by radically private communication
+seat. Finally, it's bolstered by radically private communication
 methods such as
 [Garner](https://developer.blockchaincommons.com/garner/), which
-ensure your self-sovereign identity is supported by self-sovereign
-networking.
+ensure that your self-sovereign identity is supported by
+self-sovereign networking.
 
 If you believe in self-sovereign identity (or privacy or novel
 technologies or improving the specifications we already have), then
@@ -90,24 +90,6 @@ feel for how everything works. Explore the results, digging into them
 further if you wish, as that's the power of a hands-on course like
 this.
 
-### Core Concepts
-
-A set of [Core Concepts
-documents](https://github.com/BlockchainCommons/XID-Quickstart/blob/main/concepts/README.md)
-were written in conjunction with the course. They're not an integrated
-part of the "Learning XIDs" tutorial, but they offer deep hands-on
-exercises for a variety of related technologies.
-
-In particular, we suggest reading three fundamental concepts before
-you start in on the course:
-[XIDs](https://github.com/BlockchainCommons/XID-Quickstart/blob/main/concepts/xid.md),
-[Gordian
-Envelope](https://github.com/BlockchainCommons/XID-Quickstart/blob/main/concepts/gordian-envelope.md),
-and [Data
-Minimization](https://github.com/BlockchainCommons/XID-Quickstart/blob/main/concepts/data-minimization.md). At
-a future point, we expect to move these to the [Developer web
-pages](https://developer.blockchaincommons.com/) or their own course.
-
 ## Summary: Doing Self-Sovereign Identity Right
 
 Self-sovereign identity was a dream of giving us all autonomy on the
@@ -121,8 +103,9 @@ focused on the holder, not an issuer or verifier.
 
 ## What's Next
 
-You now know what a XID is and should be ready to create one, which
-you'll do in [§1.2: Creating Your First XID](01_2_Your_First_XID.md ).
+A number of technologies and core concepts underlie XIDss. These are covered in [§1.2: Understanding Core Concepts](01_2_Core_Concepts.md).
+But if you're eager to get hands on with your XIDs, you should jump to
+[§1.3: Creating Your First XID](01_3_Your_First_XID.md).
 
 ## Appendix I: Key Terminology
 

docs/01_3_Your_First_XID.md

@@ -1,4 +1,4 @@
-# 1.2: Creating Your First XID
+# 1.3: Creating Your First XID
 
 This section demonstrates how to create a basic XID (eXtensible
 IDentifier) that enables pseudonymous contributions while maintaining
@@ -378,7 +378,7 @@ styles of quotes:
 ### Step 3: Create a Public View of Your XID with Elision
 
 Amira's XID is not ready for publication yet. You're going to add some
-more information in [§1.3](01_3_Making_a_XID_Verifiable.md) before
+more information in [§1.4](01_4_Making_a_XID_Verifiable.md) before
 sending it to Amira's first contact, Ben. But to prepare yourself for
 that, you're going to go over the crical step that _would_ be required
 to publish a XID: creating a public view.
@@ -733,7 +733,7 @@ actually published Amira's XID. More on that in the next tutorial!
 
 ### Additional Files
 
-**Envelopes:** The envelopes for this section are not stored in the Learning-XIDs repo as they'll be updated in §1.3 prior to publication.
+**Envelopes:** The envelopes for this section are not stored in the Learning-XIDs repo as they'll be updated in §1.4 prior to publication.
 
 **Scripts:** The [scripts](https://github.com/BlockchainCommons/XID-Quickstart/tree/main/scripts) directory contains [01_2_Your_First_XID-SCRIPT.sh](https://github.com/BlockchainCommons/XID-Quickstart/blob/main/scripts/01_2_Your_First_XID-SCRIPT.sh), which runs through all the commands in this section. From the command line, `git clone https://github.com/BlockchainCommons/XID-Quickstart.git`, then `cd XID-Quickstart`, then `bash scripts/01_2_Your_First_XID-SCRIPT.sh` to test it.
 
@@ -749,7 +749,7 @@ Try these to solidify your understanding:
 ## What's Next
 
 Since XIDs are autonomous, Amira needs a way to assure people that
-they have an up-to-date verison. Doing that (and publishing that XID) is the topic of [§1.3: Making a XID Verifiable](01_3_Making_a_XID_Verifiable.md).
+they have an up-to-date verison. Doing that (and publishing that XID) is the topic of [§1.4: Making a XID Verifiable](01_4_Making_a_XID_Verifiable.md).
 
 ## Appendix I: Key Terminology
 

docs/01_4_Making_a_XID_Verifiable.md

@@ -1,4 +1,4 @@
-# 1.3: Making a XID Verifiable
+# 1.4: Making a XID Verifiable
 
 This section demonstrates how to maintain a XID's freshness without
 direct communication through the use of a publication URL.
@@ -16,7 +16,7 @@ After working through this section, a developer will be able to:
 
 ## Amira's Story: The Freshness Problem
 
-After §1.2, Amira could give Ben her public XID directly. She could
+After §1.3, Amira could give Ben her public XID directly. She could
 email it, share it via Signal, or do whatever else works. But what
 happens when she updates her XID next month? Ben has no way to know
 his copy is stale. He might verify signatures against outdated
@@ -46,7 +46,7 @@ provenance --version
 ```
 
 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
+§1.3](01_3_Your_First_XID.md#step-0-setting-up-your-workspace) for
 installation instructions.
 
 ## Part I: Publishing a XID
@@ -217,7 +217,7 @@ the other.
 
 You can now use `xid export` to create a public view by eliding your
 private keys and your provenance mark generator, just like you did in
-§1.2:
+§1.3:
 
 
 ```
@@ -432,7 +432,7 @@ can he trust it?
 ### Step 9: Verify the Signature & Provenance
 
 Ben will now repeat the steps from
-[§1.2](01_2_Your_First_XID.md#part-iii-verifying-a-xid), verifying the
+[§1.3](01_3_Your_First_XID.md#part-iii-verifying-a-xid), verifying the
 signature and the provenance mark.
 
 ```
@@ -456,7 +456,7 @@ provenance validate "$PROVENANCE_MARK" && echo "✅ Provenance chain intact"
 
 He could also examine details of the provenance mark with `provenance
 validate --format json-pretty "$PROVENANCE_MARK"`, but since this is
-Amira's first edition, it'll look the same as it did in 1.1 The more
+Amira's first edition, it'll look the same as it did in §1.3. The more
 interesting test would come if Ben had multiple, different copies of
 the XID and needed to determine which was stale and which fresh, but
 that's a topic for chapter 2

docs/02_1_Creating_Self_Attestations.md

@@ -99,7 +99,7 @@ provenance --version
 ```
 
 If not installed, see
-[§1.2](01_2_Your_First_XID.md#step-0-setting-up-your-workspace) for
+[§1.3](01_3_Your_First_XID.md#step-0-setting-up-your-workspace) for
 installation instructions.
 
 You'll also want to reload your XID. The following assumes use of the [`envelopes`](https://github.com/BlockchainCommons/XID-Quickstart/tree/main/envelopes) directory that was described in the last tutorial.
@@ -291,7 +291,7 @@ So far, Amira has two keys:
 
 | Key Type | Purpose | Verified Against | Added In |
 |----------|---------|------------------|----------|
-| 👤 XID inception key | Signs XID document updates | XID itself | §1.2 |
+| 👤 XID inception key | Signs XID document updates | XID itself | §1.3 |
 | 🗣️ Attestation key | Signs attestations | XID key list | §2.1 |
 
 We'll talk more about the keys and the protections that heterogeneity
@@ -303,7 +303,7 @@ Here's a look at our two XID versions created to date:
 
 | XID Version | New Content | Created In |
 |-------------|-------------|------------|
-| seq 0 | 👤 Identity | §1.2+§1.3 |
+| seq 0 | 👤 Identity | §1.3+§1.4 |
 | seq 1 | 🔑 Attestation Key | §2.1 |
 
 ## Part II: Creating a Detached Attestation

docs/02_2_Managing_Claims_Elision.md

@@ -151,7 +151,7 @@ This is the full attestation that Amira will keep secure and private. But she wa
 
 You can now create a view of the attestation with the content removed
 but the cryptographic structure preserved. In
-[§1.2](01_2_Your_First_XID.md), we mentioned the general technique for
+[§1.3](01_3_Your_First_XID.md), we mentioned the general technique for
 doing this when we used an automated method to elide private keys and
 provenance mark generators. Generally, you need to (1) find the digest
 (hash) of the node or leaf that you want to elide and then (2) use the

docs/02_3_Managing_Claims_Encryption.md

@@ -307,8 +307,9 @@ BRadvoc8 account.
 
 That problem has been lingering, and it'll be the reason for Amira to
 finally add a bit more information to her BRadvoc8 XID, proof that she
-controls the GitHub account she referenced in §1.3, but that'll be the
-topic of the next chapter.
+controls the GitHub account she referenced in
+[§1.4](01_4_Making_a_XID_Verifiable.md), but that'll be the topic of
+the next chapter.
 
 ## Summary: From Elision to Encryption
 

docs/03_1_Creating_Edges.md

@@ -75,10 +75,10 @@ information can be found.
 | | `attachment` | `'attachment'` | 📂 Third-party metadata |
 | | `delegate` | `'delegate'` | 👌🏽 Permission delegation | 
 | §3.1-§3.3 | `edge` | `'edge'` | 🗣️  Attestations |
-| §1.2, §2.1 | `key` | `'key'`<br>`'privateKey'` | 🔑 Key pairs |
-| §1.3 | `method`<br>`resolution` | `'dereferencevia'` | 🧶 Resolution method |
+| §1.3, §2.1 | `key` | `'key'`<br>`'privateKey'` | 🔑 Key pairs |
+| §1.4 | `method`<br>`resolution` | `'dereferencevia'` | 🧶 Resolution method |
 | | `service` | `'service'` | ☁️  Service delegation |
-| §1.2, §2.1 | `provenance` | `'provenance'` | ⛓️  Provenance mark |
+| §1.3, §2.1 | `provenance` | `'provenance'` | ⛓️  Provenance mark |
 
 Edges will be the topic of this chapter.
 
@@ -172,7 +172,7 @@ Amira now has three different keys serving three different purposes:
 
 | Key Type | Purpose | Verified Against | Added In |
 |----------|---------|------------------|----------|
-| 👤 XID inception key | Signs XID document updates | XID itself | §1.2 |
+| 👤 XID inception key | Signs XID document updates | XID itself | §1.3 |
 | 🗣️  Attestation key | Signs attestations | XID key list | §2.1 |
 | 🖋️  SSH signing key | Signs Git commits | GitHub account | §3.1 |
 
@@ -521,7 +521,7 @@ what each version contains
 
 | XID Version | New Content | Created In |
 |-------------|-------------|------------|
-| seq 0 | 👤 Identity | §1.2+§1.3 |
+| seq 0 | 👤 Identity | §1.3+§1.4 |
 | seq 1 | 🔑 Attestation Key | §2.1 |
 | seq 2 | 🗣️ GitHub Edge | §3.1 |
 

docs/03_2_Supporting_Cross_Verification.md

@@ -358,7 +358,7 @@ piece plays a role in the verification chain that they're about to build.
 DevReviewer now needs to extract the SSH public keys (and other
 information) that they'll use for the purpose of cross-verification.
 
-[§1.3](01_3_Making_a_XID_Verifiable.md) briefly talked about how to
+[§1.4](01_4_Making_a_XID_Verifiable.md) briefly talked about how to
 extract data from a XID. Generally, you need to iteratively cut an
 envelope down to the point where you just have a subject and a set of
 assertions, and then pull out the assertions that you want. (Again,
@@ -736,7 +736,7 @@ This is courtesy of a chain of evidence, much of which was locked down in this s
 
 | ⛓️ Evidence | Verification | Section |
 |----------|--------------|---------|
-| 🔗 derefenceVia URL | URL is on GitHub | §1.3 |
+| 🔗 derefenceVia URL | URL is on GitHub | §1.4 |
 | 🌌 Galaxy PR | PR Exists | §2.1 |
 | 👀 Cryptographic Audit Work | Previous Commitment | §2.2 |
 | 🔐 Security Work for Civil Trust | Similar PRs | §2.3 |

docs/03_3_Creating_Peer_Endorsements.md

@@ -551,7 +551,7 @@ each version contains
 
 | XID Version | New Content | Created In |
 |-------------|-------------|------------|
-| seq 0 | 👤 Identity | §1.2+§1.3 |
+| seq 0 | 👤 Identity | §1.3+§1.4 |
 | seq 1 | 🔑 Attestation Key | §2.1 |
 | seq 2 | 🗣️ GitHub Edge | §3.1 |
 | seq 3 | 🗣️ Endorsement Edge | §3.3 |
@@ -812,8 +812,8 @@ self-attestations.
 
 At this point, Amira has built a succession of progressive trust layers:
 
-1. [§1.2](01_2_Your_First_XID.md): Self-sovereign identity (XID exists)
-2. [§1.3](01_3_Making_a_XID_Verifiable.md): Self-consistent (signature verifies, fresh)
+1. [§1.3](01_3_Your_First_XID.md): Self-sovereign identity (XID exists)
+2. [§1.4](01_4_Making_a_XID_Verifiable.md): Self-consistent (signature verifies, fresh)
 3. [§2.1](02_1_Creating_Self_Attestations.md): Fair-witness claims (public, verifiable claims)
 4. [§2.2](02_2_Managing_Claims_Elision.md): Medium sensitive claims managed (commit elided, reveal later)
 5. [§2.3](02_3_Managing_Claims_Encryption.md) High sensitive claims managed (encrypted, sent to trusted parties)