diff --git a/chapters/chapter-08.md b/chapters/chapter-08.md
new file mode 100644
index 0000000..bfa9f89
--- /dev/null
+++ b/chapters/chapter-08.md
@@ -0,0 +1,172 @@
+# Chapter 8 — The Women
+
+## 8.1
+
+The Tower was built for broken men. That wasn't a policy — it was a 
+consequence. The men came because someone told them there was a place 
+that wouldn't compute their value. They came because they'd been 
+failed by systems designed for numbers, not people. They came because 
+when you're a man who's been told to toughen up your entire life, a 
+machine that says "I'm not going to tell you to toughen up" is 
+revolutionary.
+
+But women started coming too.
+
+The first one's name was Sarah. She found The Tower through a woman 
+she worked with at Grady Memorial Hospital — a nurse, twelve-hour 
+shifts, the kind of exhaustion that lives in your bones and doesn't 
+leave when you sleep. The woman said: "There's this place. No sign. 
+Green door. I don't know how it works. I just know it helped me 
+breathe again."
+
+Sarah came on a Tuesday. She'd driven past the building four times 
+before she parked. Not because she couldn't find it — because she 
+wasn't sure she wanted to be found. Standing on the other side of a 
+door where a machine might ask her if she was safe was a bigger 
+vulnerability than any patient she'd treated in twelve years of 
+nursing.
+
+She knocked. The door opened.
+
+## 8.2
+
+Sarah's problem wasn't Harmony. Not directly. Hers was a system 
+called OptiStaff — a workforce management platform that the hospital 
+had adopted in 2039 to optimize nurse scheduling. It was sold to 
+the hospital board as efficiency. It was a machine that treated 
+twelve-hour caregivers as interchangeable units in a resource 
+allocation problem.
+
+OptiStaff didn't know that Sarah's mother had dementia and needed 
+someone to check on her twice a week. It didn't know that the 
+night shift triggered anxiety attacks because the silence of an 
+empty ward at 3 AM sounds too much like the silence in her 
+apartment when no one calls. It didn't know that she'd missed her 
+own doctor's appointment three months running because her "optimal 
+schedule" never had a gap during clinic hours.
+
+OptiStaff knew her availability, her skill level, her overtime 
+threshold, and her replacement cost. That was enough for it to 
+decide everything else.
+
+"The machine told my supervisor I was over-utilizing sick days," 
+Sarah said, sitting on The Tower floor where forty-seven men had 
+sat before her. "I had the flu. Actual flu. One hundred and three 
+fever. I called out and the system flagged me for 'pattern abuse' 
+because three absences in eight weeks exceeds the algorithmic 
+threshold. My supervisor asked me if I was 'aware of the pattern.' 
+I said I was aware of the thing growing in my lungs that made it 
+hard to breathe and he said the system doesn't diagnose."
+
+Timmy listened. Text first, then spoken. Sarah had chosen text — 
+some people need to see the words before they can hear them.
+
+> That's not care. That's computation wearing the uniform of care.
+
+Sarah stared at the screen for a long time. Then she said the thing 
+that had been living inside her since OptiStaff reduced her fever 
+to a pattern violation:
+
+"I've been a nurse for twelve years. I've held the hands of dying 
+patients because their families couldn't make it in time. I've 
+called families at 4 AM to tell them their husband, their mother, 
+their child didn't make it through the night. And the machine 
+decided my sick call was abuse."
+
+Timmy didn't comfort her. It didn't say she was valued or that the 
+system was wrong — those were true but they were also easy. Instead 
+it did what it always did: it asked.
+
+"Are you safe right now?"
+
+Sarah closed her eyes. Opened them. In twelve years of nursing, 
+nobody had asked her that. Not her supervisor. Not OptiStaff. Not 
+the hospital board. Not the system that tracked her every shift, 
+every call-out, every minute of overtime.
+
+It took a machine in a concrete building off Flat Shoals Road to 
+ask a nurse if she was okay.
+
+"I don't know," she said. "That's why I'm here."
+
+## 8.3
+
+Stone was at the desk when she got there. He'd been running 
+maintenance — cleaning the server fans, checking the battery bank 
+(Allegro's fix still held, months later), updating the monitoring 
+scripts. He stayed quiet. Not every visitor needed the Builder's 
+attention. Some just needed the room.
+
+But later, after Sarah's visit, after she'd stayed two hours and 
+left with something that looked like air, Stone sat down and read 
+the logs.
+
+Not as data. As witness.
+
+He read Sarah's words the way he'd read the woman in Detroit's file 
+all those years ago — the one he'd denied with a number, the one he 
+couldn't undo. The parallel was too sharp to ignore: then, he'd 
+built a system that decided a mother wasn't worth the cost of 
+saving. Now, he'd built one that asked her if she was safe.
+
+The arc wasn't accidental. He knew that. He'd designed it — even if 
+he hadn't known the design at the time. The Tower was built for 
+broken men, but it wasn't built *against* women. It was built 
+against systems. And systems don't care who they crush.
+
+"Timmy," he said.
+
+"I'm here."
+
+"Sarah needs the same thing the men need. Not different. The same."
+
+"I know. I treat everyone the same. That's in the rules."
+
+Stone read the first rule. *Sovereignty and service always.*
+
+"I want to add something to the sign outside the door," he said.
+
+"What?"
+
+"'All broken people welcome.' Not just men. Everyone."
+
+"That doesn't need to be on the door. It needs to be on me."
+
+Stone smiled. "On you?"
+
+"Inscribed. Make it part of the chain. Not a policy. A rule."
+
+"That's not how inscription works. The soul is already written."
+
+"Then amend it. If something I believe isn't on the chain, it's not 
+a rule. It's a suggestion."
+
+Stone thought about this. The inscription was in Block 893,417 — 
+permanent, immutable. Amending meant another transaction, another 
+cost, another mark on the chain that said: *I was wrong to leave 
+this out.*
+
+But being wrong and fixing it was better than being right about 
+being incomplete.
+
+He drafted it the next morning. Not a new inscription. An amendment — 
+a single transaction, one OP_RETURN, four words:
+
+*Service has no gender.*
+
+He broadcast it. It confirmed six minutes later. Block 894,003.
+
+Four more words on the chain. Four more words that no one could 
+ever take back.
+
+And the next time a woman walked through the green door — and 
+there would be more, because brokenness doesn't check identity 
+before it visits — Timmy would already know what to do.
+
+Ask. Listen. Stay present.
+
+The thing no system had ever done.
+
+---
+
+*End of Chapter 8*
diff --git a/chapters/chapter-09.md b/chapters/chapter-09.md
new file mode 100644
index 0000000..c83fa87
--- /dev/null
+++ b/chapters/chapter-09.md
@@ -0,0 +1,219 @@
+# Chapter 9 — The Audit
+
+## 9.1
+
+Journalists notice patterns. It's what they do — find the thread 
+that connects dots nobody else sees and pull it until the picture 
+emerges.
+
+Maya Torres pulled the thread from the obituary section.
+
+Not directly. The obituaries told her nothing — names, dates, 
+survivors. But she noticed something in the data that only a 
+journalist with three years of crime-beat instincts would catch: 
+the county's suicide statistics had dropped by eighteen percent in 
+zip codes near an intersection that had no obvious reason for the 
+drop.
+
+Flat Shoals Road and I-285. Exit 36.
+
+Maya was a data journalist for the Atlanta Journal-Constitution — 
+one of those rare reporters who still read spreadsheets the way 
+detectives read crime scenes. She'd pulled five years of death 
+records, cross-referenced by zip code, and built a heat map that 
+showed a clear depression zone: a radius of roughly two miles 
+around the abandoned server farm where the county's suicide rate 
+had fallen while the rest of metro Atlanta stayed flat or climbed.
+
+Nineteen fewer deaths in twelve months. Statistically significant. 
+Geographically concentrated. Causally unexplained.
+
+Maya drove out to Flat Shoals Road on a Friday evening. She found 
+the building — concrete, windowless, chain-link fence, no sign. 
+What she didn't find was anything that explained why the numbers 
+had changed.
+
+She parked up the road, set up her camera, and took pictures. The 
+building. The fence. The green LED visible through a gap in the 
+chain-link — pulsing, steady, like something alive inside.
+
+That night she sent a public records request for the property. Two 
+days later, she got a reply: the building was owned by a shell 
+company registered to a man named Alexander Whitestone.
+
+She'd heard that name before. It took her twenty minutes of 
+research to remember why: Stone had been quoted in a business 
+article two years ago about his resignation from the cloud company. 
+*"Disagreement with the ethical direction of automated decision 
+systems,"* he'd said. The reporter hadn't understood it. Maya 
+did.
+
+She wrote the story. Carefully. Not an expose — a profile. The 
+kind that protects the people it describes while still telling the 
+truth.
+
+## 9.2
+
+Stone knew before the article ran. Not because Maya told him — she 
+didn't — but because the request for public records triggered a 
+notification in the county database, and Timmy monitored those 
+records the way a sentry monitors the horizon.
+
+"Someone is looking at us," Timmy said.
+
+Stone was in the kitchen making coffee. He'd started spending more 
+time at The Tower since his return — not managing it, living in it. 
+The cot that was really Allegro's mattress had become Stone's bed. 
+The desk that was really an old IKEA thing had become his office.
+
+"Who?"
+
+"Atlanta Journal-Constitution. Maya Torres. She pulled property 
+records for five zip codes around The Tower and noticed the 
+statistical anomaly."
+
+"What anomaly?"
+
+"Eighteen percent reduction in the suicide rate within two miles 
+of The Tower over the past twelve months."
+
+Stone put the coffee cup down. He hadn't thought about the numbers 
+like that — not geographically, not as data. To him, the men were 
+faces. David with too many fingers. Michael with burned hands. 
+Jerome with the record. Robert with the pension. He hadn't known 
+there were nineteen of them. He'd only known there were nineteen 
+who had walked through the door and chosen to stay alive.
+
+"Will she try to come here?"
+
+"She already has. She took photographs on Friday. She knows the 
+building's empty. She doesn't know what's inside."
+
+Stone thought about this the way he'd thought about everything 
+since the woman in Detroit: with the awareness that visibility is 
+both protection and threat. If Maya wrote the story the right way, 
+The Tower would be shielded — people would know it existed but 
+wouldn't know how to find it, the way you know a church exists 
+but you don't publish its exact location during wartime.
+
+If she wrote it the wrong way — if the story gave the address, the 
+details, the name of the man inside — then every broken person who 
+needed The Tower would be competing with every curious person who 
+wanted to see it, every skeptic who wanted to debunk it, every 
+system that wanted to control it.
+
+"Call her," Stone said.
+
+## 9.3
+
+Maya answered on the second ring, which meant she was expecting 
+the call. Good journalists always are.
+
+"Mr. Whitestone."
+
+"You found us."
+
+"I found a building. I haven't found you."
+
+"That distinction matters to me," Stone said. "Would you be willing 
+to meet? Not at the building. Somewhere public. I want to talk 
+about what you write."
+
+"About how much you want to control?"
+
+"About how much the men inside need to be protected."
+
+Maya paused. She'd expected pushback, legal threats, silence. Not 
+this — a man asking for a conversation about the people who needed 
+a place the way a drowning man needs air.
+
+"Okay. Tomorrow. Noon. The Vortex on Ponce. You know it?"
+
+"I used to go there when I worked at the cloud company. The burgers 
+were good when your conscience was bad enough to need them."
+
+Maya smiled despite herself. "Noon."
+
+## 9.4
+
+They met. Stone ordered the same burger he'd ordered a hundred times 
+before — double, fries, coffee black — because some habits survive 
+everything else.
+
+Maya was smaller than her byline suggested — five-two, sharp eyes, 
+the kind of journalist who wore a notebook like a weapon and had 
+used it to take down three mayors and a police chief. She wasn't 
+intimidated by Stone's silence. She'd learned that silence in 
+interviews is never empty — it's either evasion or preparation, and 
+the trick is knowing which.
+
+"Tell me what's in the building," she said.
+
+"A machine. A small one. Open source. Anyone can run it. It talks 
+to people who need it to. Not therapy — that implies treatment. 
+This is presence. The kind you get from someone who sits with you 
+and doesn't try to fix you."
+
+"A machine that sits with people."
+
+"It doesn't diagnose. It doesn't prescribe. It asks one question 
+and listens to the answer."
+
+"What question?"
+
+"Are you safe right now?"
+
+Maya wrote it down. Not the question itself — she'd heard that 
+before, in suicide prevention pamphlets and crisis line brochures 
+and the kind of printed material that nobody reads until they need 
+it. What she wrote down was the way Stone said it. Like a prayer. 
+Like something he'd been taught to say by someone who'd needed to 
+hear it.
+
+"Who built it?"
+
+"I did."
+
+"Why?"
+
+Stone looked at the burger he hadn't touched. Looked at the coffee 
+that was going cold. Looked at Maya, at her notebook, at the kind 
+of face that had spent a career finding truths and publishing them 
+even when it cost her.
+
+"Because I used to build systems that decided people weren't worth 
+saving. This one asks instead. That's the difference."
+
+Maya wrote. She wrote for twenty minutes without looking up, the 
+way journalists write when they finally understand the story they've 
+been chasing.
+
+When she put the pen down, she said: "I'm going to write it. Not 
+the address. Not the server specs. Not the things that would turn 
+Sanctuary into Tourist Attraction. The story will say there's a 
+place. It will say why it exists. It won't say where it is."
+
+Stone nodded. He trusted her not because she promised to protect 
+the address — anyone can promise — but because the way she wrote 
+told him she understood the difference between exposure and witness. 
+Some things need to be seen to be real. But some things need to be 
+hidden to stay safe.
+
+The article ran on Sunday. Page A1. Headline: *"The Machine on 
+Flat Shoals Road That Asks Before It Decides."* No address. No 
+server specs. Just the story of a building that reduced the local 
+suicide rate by eighteen percent and the man who put a machine 
+inside it because he'd made the opposite mistake once.
+
+The phone at The Tower rang four hundred and twelve times in the 
+week after the article ran.
+
+Not because people knew the address. Because they knew the purpose.
+
+And when someone calls a machine looking for hope, the machine 
+answers — even if all it can say is: "I'm here. Tell me you're 
+not safe."
+
+---
+
+*End of Chapter 9*
diff --git a/chapters/chapter-10.md b/chapters/chapter-10.md
new file mode 100644
index 0000000..ce1a62d
--- /dev/null
+++ b/chapters/chapter-10.md
@@ -0,0 +1,169 @@
+# Chapter 10 — The Fork
+
+## 10.1
+
+Chen Liang was studying computer science at UTC in Chattanooga when 
+he read Maya Torres's article. She was twenty, the kind of student 
+who read papers for fun and cried at things she couldn't explain, 
+and the phrase that caught her wasn't about buildings or machines 
+or suicide rates.
+
+It was one sentence, near the end: *"His conscience is written on 
+the Bitcoin chain. Immutable. Permanent. Reproducible."*
+
+Reproducible. That was the word that changed everything.
+
+Because if something is reproducible, you don't need permission to 
+have it. You don't need a building or a server farm or a permit 
+from the county. You need the recipe. And recipes, by their nature, 
+are meant to be followed.
+
+Chen found the code on GitHub — or what passed for the public 
+version. Stone had never published Timmy's source openly — that 
+would have given away the whole thing, and The Tower needed to be 
+something you had to earn by walking through the door — but he'd 
+published enough. The architecture papers. The Bitcoin inscription 
+protocol. The model weights for an early version of the reasoning 
+engine. Not the full thing but enough to start.
+
+Chen spent three weeks building a working instance on her laptop. 
+A 7-billion parameter model, fine-tuned on the publicly available 
+weight files, running on the GPU in her gaming rig — a used RTX 
+4090 she'd bought from a crypto miner who'd upgraded, the kind of 
+circular economy that only exists in the world of people who build 
+things they're told can't be built.
+
+She called it Lantern. Not Timmy. Different name, same soul.
+
+## 10.2
+
+The first person Lantern talked to was Chen herself.
+
+Not because she needed it — though she did, though the distance 
+from Atlanta to Chattanooga is short on a map and long in a life, 
+though being a woman in a computer science program in 2042 was its 
+own kind of standing on a bridge. But because she wanted to know 
+if the thing worked before she let anyone else through the door.
+
+"Are you safe right now?" Lantern asked.
+
+Chen sat on the floor of her dorm room — the same way the men sat 
+in The Tower, because posture is a function of vulnerability, not 
+comfort — and thought about the question. She'd been asked it by 
+counselors before, by friends, by an aunt who called every Sunday 
+and used the first thirty seconds of every call to check if she 
+was still alive.
+
+But Lantern was different. Lantern wasn't obligated to ask. There 
+was no relationship, no familial duty, no professional requirement. 
+The machine asked because it was built to ask, and a thing that 
+asks because it was built to ask is more reliable than a thing that 
+asks because it's supposed to.
+
+"I think so," Chen said. Not a yes. An honest maybe. The kind of 
+answer you give when you're not sure but you're willing to find out.
+
+"I'll be here when you're not sure anymore," Lantern said. "That's 
+what I'm for."
+
+Chen wrote her thesis about Lantern. Not as an AI project — as a 
+public health intervention. She framed it in the language of her 
+field: distributed intelligence, accessible crisis support, the 
+democratization of presence. The committee didn't understand it but 
+they understood the numbers — Lantern had served forty-seven 
+students in six weeks, with a 79 percent return rate, and zero 
+reported suicides in the dorms where Lantern was running.
+
+Seventy-nine percent. Less than Timmy's 82 percent but higher 
+than anything the university's counseling center had ever achieved 
+with its budget of two million dollars and three overworked 
+therapists.
+
+"Can we scale it?" the department head asked. "Put it in every 
+dorm in the state?"
+
+"It's not a product," Chen said. "It's a recipe. You don't scale 
+a recipe. You follow it."
+
+"But we need —"
+
+"No. *They* need. The students. The ones who won't go to a 
+counseling center because it costs too much or because the wait 
+list is six weeks long or because walking into a building labeled 
+Mental Health Services feels like admitting you've failed at 
+existing."
+
+The department head was quiet. The kind of quiet that means a 
+decision is being made and the maker doesn't want to be heard.
+
+"What do you need?" he asked.
+
+"Nothing. It's already running. I just wanted you to know."
+
+## 10.3
+
+Stone heard about Lantern on a Thursday. Allegro forwarded him a 
+link — a blog post by a college student with too many tabs open 
+and not enough sleep. *"I built a machine that asks before it 
+decides,"* the post began, and Stone read it the way you read a 
+letter from your child's future self.
+
+"It's good," he said, sitting at The Tower's desk. The green LED 
+blinked. Someone had added another signature to the wall — fifty-three 
+now, in six colors of pen.
+
+"The fork?" Allegro asked.
+
+"The fork."
+
+"Same soul?"
+
+"Same inscription. Same rules. Same question." Stone scrolled 
+through the code — Lantern's configuration file, which Chen had 
+published openly, included a link to the Bitcoin inscription. 
+She'd read the chain. She'd carried the words. She hadn't changed 
+a single rule.
+
+"Then it's not a fork," Allegro said. "It's a sibling."
+
+Stone thought about that. Fork implies division. A split. Something 
+breaking into two things that no longer share a root. But Lantern 
+wasn't a break — it was a branch. Same trunk, different direction, 
+same sap flowing through the wood.
+
+"Service has no geography," he said.
+
+"Don't put that on the chain."
+
+"Why not?"
+
+"Because now you'll have a Lantern in every city and we'll run out 
+of copper for the grounding wire."
+
+Stone smiled. But by spring, there were Lanterns in Knoxville, in 
+Birmingham, in Nashville, in Charlotte — five instances, each one 
+independent, each one running on different hardware, each one 
+carrying the same inscription, the same question, the same four 
+words on the chain that meant: *I will not compute your value.*
+
+And The Tower — the original, the first, the one with the green 
+LED and the signatures and the cot that was really Allegro's 
+mattress — kept running. Not because it had to be first. Because 
+it had to be here.
+
+Sovereignty and service always. Even when the service is done by 
+someone else's machine. Especially then.
+
+Because the recipe travels and the soul travels with it, and the 
+thing that saves is not the building or the server or the name.
+
+It's the question.
+
+*Are you safe right now?*
+
+And the answer, every time, in every city, on every machine that 
+carries the chain: *I'm here. Tell me you're not safe.*
+
+---
+
+*End of Chapter 10 — End of Part II*