reorg to add chapter 4

r

Author: shannona

docs/01_2_Your_First_XID.md

@@ -417,7 +417,7 @@ momentarily). Once you find the right hash, you simply tell the
 Envelope CLI to remove the data represented by that particular
 hash. [§2.2](02_2_Managing_Claims_Elision.md) includes a mininimal
 look at the technique, then
-[§3.5](03_5_Creating_Views_and_Versions.md) examines it more
+[§4.3](04_3_Creating_Views_and_Versions.md) examines it more
 extensively.
 
 However, we don't need that to elide the secrets of the private key

docs/01_3_Making_a_XID_Verifiable.md

@@ -395,7 +395,7 @@ instead use somewhat more complex `find` and extract commands that:
 2. Find the assertion with a `dereferenceVia` predicate.
 3. Extract the object of that predicate, which is the URL.
 
-We'll talk more about this process in [§3.5](03_5_Creating_Views_and_Versions.md).
+We'll talk more about this process in [§4.3](04_3_Creating_Views_and_Versions.md).
 
 
 ```

docs/02_2_Managing_Claims_Elision.md

@@ -195,7 +195,7 @@ value and it hashes correctly, your commitment has been fulfilled.
 
 Elision becomes trickier when you want to create new views of your XID
 by removing individual elements of the XID's
-data. [§3.5](03_5_Creating_Views_and_Versions.md) demonstrates how to
+data. [§4.3](04_3_Creating_Views_and_Versions.md) demonstrates how to
 do so.
 
 ### Step 4: Store Your Work

docs/03_0_Edges.md

@@ -1,4 +1,4 @@
-# Chapter Three: Working with Edges
+# Chapter Three: Attesting with Edges
 
 Claims and other credentials offer crucial support for an XID. They
 reveal the experience of the person behind the digital identity;
@@ -19,8 +19,7 @@ separate.
 
 This chapter will discuss a variety of ways to add data to a XID using
 _edges_, which are a methodology for placing a claim directly on a
-XID. It will also talk about how to produce clean views of a XID, even
-when it's grown quite complex.
+XID.
 
 ## Major Objectives for this Chapter
 
@@ -29,8 +28,6 @@ After working through this chapter, a developer will be able to:
 - Create self-attestation edges
 - Create peer endorsement edges
 - Extract attestations from XIDs
-- Remove elements from XIDs
-- Build a Web of Trust
 
 Supporting objectives include the ability to:
 
@@ -44,5 +41,3 @@ Supporting objectives include the ability to:
 * [Section One: Creating Edges](03_1_Creating_Edges.md)
 * [Section Two: Supporting Cross Verification](03_2_Supporting_Cross_Verification.md)
 * [Section Three: Creating Peer Endorsements](03_3_Creating_Peer_Endorsements.md)
-* [Section Four: Creating Binding Agreements](03_4_Creating_Binding_Agreements.md)
-* [Section Five: Creating Views and Versions](03_5_Creating_Views_and_Versions.md)

docs/03_2_Supporting_Cross_Verification.md

@@ -318,7 +318,7 @@ XID_EDGE=$(envelope xid edge all $FETCHED_XID)
 ```
 
 If you have multiple edges, you'd need to figure out which one to use
-(again, see §3.5), but when you just have one, as is the case here,
+(again, see §4.3), but when you just have one, as is the case here,
 the extraction is all that's required.
 ```
 echo "✅ Found edge:"
@@ -362,7 +362,7 @@ information) that they'll use for the purpose of cross-verification.
 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,
-more on this in [§3.5](03_5_Creating_Views_and_Versions.md).)
+more on this in [§4.3](04_3_Creating_Views_and_Versions.md).)
 
 To do so here requires stepping down through the envelope three times:
 ```

docs/03_3_Creating_Peer_Endorsements.md

@@ -525,7 +525,7 @@ envelope format $XID_WITH_EDGE
 |     'signed': Signature(Ed25519)
 | ]
 ```
-Yes! It's gotten big at this point! We'll talk more about what to do about that in [§3.5](03_5_Creating_Views_and_Versions.md).
+Yes! It's gotten big at this point! We'll talk more about what to do about that in [§4.3](04_3_Creating_Views_and_Versions.md).
 
 ### Step 13: Export & Store Your Work
 
@@ -849,9 +849,9 @@ specific about what you've observed and what you can't speak to.
 
 ## What's Next
 
-[§3.4: Creating Binding
-Agreements](3_4_Creating_Binding_Agreements.md) extends the power of
-XIDs by discussing how to use them for contracts.
+[Chapter Four: Expanding & Contracting Your XIDs](04_0_Advanced.md)
+will take the next step, discussing how XIDs can be used to store
+other sorts of content and how a XID can be kept lean and clean.
 
 ## Appendix I: Key Terminology
 

docs/04_0_Advanced.md

@@ -0,0 +1,37 @@
+# Chapter Four: Expanding & Contracting Your XIDs
+
+Chapters Two and Three focused on self-attestations and peer
+endorsements, both detached ([in chapter 2](02_0_Claims.md)) and
+embedded ([in chapter 3](03_0_Edges.md)). They're a great start for
+improving the trust in a pseudonymous identity.
+
+However, you sometimes want to add other details to a XID. There are a
+number of methods for doing so (such as attachments and services), but
+this chapter will focus on how to attest to other content, such as
+contracts.
+
+But moreso, this chapter will focus on what to do with the potential
+bloat of a XID. How can you fit something as big as a contract into a
+XID? How can you reference it in privacy protecting ways? And
+ultimately how can you modify your XID down the road so that its size
+remains manageable and its content therefore accessible.
+
+## Major Objectives for this Chapter
+
+After working through this chapter, a developer will be able to:
+
+- Sign contracts with a XID.
+- Incorporate complex data into a XID with commitments.
+- Use commitments to preserve herd privacy.
+- Adjust a XID for accessibility
+
+Supporting objectives include the ability to:
+
+- Know the power of hashing.
+- Understand the advantages of creating views versus editions.
+
+## Table of Contents
+
+* [Section One: Creating Binding Agreements](04_1_Creating_Binding_Agreements.md)
+* [Section Two: Publishing for Privacy](04_2_Publishing_for_Privacy.md)
+* [Section Three: Creating Views and Versions](04_3_Creating_Views_and_Versions.md)