polishing and fixing continue

chapters/book2/ch01-final.md

@@ -22,7 +22,7 @@ Below that, a timeline. Months to house target at current savings rate.
 
 It was thorough. It was logical. It was most likely how people do these things. It was completely alien to the way my brain processed numbers.
 
-(*Her categories are wrong. Not wrong — differently right. She's averaging ore income across all months but Leon's buyer network isn't consistent — December was eighteen silvers, January was seven, the Sarren brothers haven't committed past March. An average obscures the variance. And the food line — she's using last month's actual spend, but last month Devod brought a ham and three jars of preserves, so last month's food cost is artificially low. Adjust for Devod's contributions regressing to the mean —*)
+(*Her categories are wrong. Off-axis, not broken. She's averaging ore income across all months but Leon's buyer network isn't consistent — December was eighteen silvers, January was seven, the Sarren brothers haven't committed past March. An average obscures the variance. And the food line — she's using last month's actual spend, but last month Devod brought a ham and three jars of preserves, so last month's food cost is artificially low. Adjust for Devod's contributions regressing to the mean —*)
 
 "This is thorough," I said.
 
@@ -68,7 +68,7 @@ I took the ledger. She let me, the same way that Mere let people do things she k
 
 I redid it.
 
-Not her way. My way. The noise way — branching scenarios, edge cases, contingency layers. What if the ore income dropped to zero. What if it doubled. What if Ledger's case assignments shifted to longer jobs with delayed payment. What if the chandler's landlord raised rent by ten percent, fifteen percent, twenty percent. What if Sniff needed medical care — actual medical care, not herbs, the kind that cost fifty silvers and couldn't wait for the surplus to accumulate. I built decision trees where Mere had built columns. I modelled thirteen scenarios where she'd modelled one.
+My way. The noise way — branching scenarios, edge cases, contingency layers. What if the ore income dropped to zero. What if it doubled. What if Ledger's case assignments shifted to longer jobs with delayed payment. What if the chandler's landlord raised rent by ten percent, fifteen percent, twenty percent. What if Sniff needed medical care — actual medical care, not herbs, the kind that cost fifty silvers and couldn't wait for the surplus to accumulate. I built decision trees where Mere had built columns. I modelled thirteen scenarios where she'd modelled one.
 
 (*The food line needs seasonal adjustment — winter produce costs more because supply shrinks and preservation adds margin. Summer surplus offsets but you can't eat a surplus in February. And the workshop supplies — she's listed Mere's moss materials at current prices but dried silverthorn has increased eleven percent in the last six months and if Gavren's supplier adjusts — Gavren would know, I should ask Gavren — no, focus, the line item is two silvers but the trailing average suggests two and a quarter, which across twelve months is three additional silvers which isn't nothing when you're—*)
 
@@ -152,7 +152,7 @@ The light was fading by the time we finished. Winter afternoons in Drenwick surr
 
 "Weekday hours. Try not to be late."
 
-I watched him go. Filed the training data the way I always did — reserve cost, technique assessment, slow progress measured in half-seconds and corrections that shouldn't have been necessary if I hadn't let the skills atrophy. The noise processed it. The noise processed everything.
+I watched him go. Filed the training data the way I always did — reserve cost, technique assessment, slow progress measured in half-seconds and corrections that shouldn't have been necessary if I hadn't let the skills atrophy. The noise processed it the way the noise processed everything. Without asking.
 
 * * *
 
@@ -250,7 +250,7 @@ The note was brief. Ledger's handwriting — precise, angular, the penmanship of
 
 *Pattern identified. Compact is aware and not acting. We need to discuss.*
 
-I read it twice. The noise engaged — not the lazy background hum of a Godsday evening, not the comfortable whirr of budget math and training analysis. The sharper kind. The kind that meant incoming data that didn't fit the quiet.
+I read it twice. The noise engaged — not the lazy background hum of a Godsday evening, not the comfortable whirr of budget math and training analysis. The sharper register. The one that meant incoming data that didn't fit the quiet.
 
 (*"Pattern identified." Ledger doesn't use that word casually. A pattern means multiple data points — not a single incident, not a client complaint, not a routine case assignment. Multiple events connected by something Ledger's network detected. And "Compact is aware and not acting" — that's the second signal. The Compact knows about something and has chosen not to investigate. Which means either it's not worth investigating, which Ledger wouldn't bring to me, or it's the kind of thing the Compact has reasons to leave alone. And when the Compact has reasons to leave something alone—*)