ch3-4 done

CLAUDE.md

@@ -98,6 +98,14 @@ When Phelan identifies a flaw, he can:
 
 *Document all new exploits Phelan uses in `/world/magic/exploits-log.md` for continuity.*
 
+### Phelan's Combat Magic — Fire & Earth
+In addition to Flaw Sight, Phelan has conventional combat magic he learned as a child due to bullying. He kept it quiet after leaving school and hasn't needed it until guild work takes him into dangerous environments.
+
+- **Fire element:** Strong. His primary combat tool — close-quarters fire weaving combined with melee strikes. Practiced obsessively as a kid.
+- **Earth element:** Serviceable but weaker. Used practically (stabilizing terrain, creating cover) rather than offensively.
+- **Melee + magic combination:** Rare in Corvel. Mages are common (~20% of the population can use magic), so being a mage alone isn't special. What's rare is combining physical combat skills with spell casting — most mages only know spells. Phelan can fight in close quarters while maintaining spell work.
+- **Current state:** A dormant skill resurfacing out of necessity — not his identity, but a real capability he's been sitting on. The skill and muscle memory are there, but his stamina isn't what it was.
+
 ---
 
 ## 5. CHARACTER BIBLE — PHELAN VARRANT
@@ -129,7 +137,7 @@ First-person, present-tense narration is NOT used. **First-person, past tense**
 - Genuine enthusiasm about magical systems that disappears the moment a person tries to connect with him about it
 - Understatement in dangerous situations, overstatement in mundane ones
 - Occasional fourth-wall-adjacent asides that don't quite break it
-- **"The noise" parentheticals** — involuntary brain tangents in `(parentheses)`, clipped fragment style (see "The Noise Convention" in Section 9)
+- **"The noise" parentheticals** — involuntary brain tangents in `(*italicized parentheses*)`, clipped fragment style (see "The Noise Convention" in Section 9)
 
 **DO NOT write Phelan like this:**
 - Warm, spontaneous emotional expression
@@ -230,7 +238,7 @@ All chapter drafts must comply with these rules from the first draft. Do not use
 - **Chapter headings:** Use `# Chapter [Number]: [Title]` — no decorative characters around them
 - **Scene breaks:** Use `* * *` (three asterisks with spaces) — never a blank line alone, never `---`
 - **No headers below H2** within chapter body text
-- **"The Noise" parenthetical tangents:** Phelan's involuntary ADD brain processing is formatted as parenthetical asides `(like this)` — short, clipped fragments, raw brain output. No nested parentheses. Can be block-level or inline with em-dash framing when the tangent interrupts mid-action. Target frequency: 4-6 per chapter (establishing chapters), 3-5 per chapter (ongoing). Higher frequency and shorter fragments during high-stress scenes. See `docs/plans/2026-03-03-the-noise-tangent-convention-design.md` for full rules.
+- **"The Noise" parenthetical tangents:** Phelan's involuntary ADD brain processing is formatted as `(*italicized content*)` — italics inside parentheses. Short, clipped fragments, raw brain output. No nested parentheses. Can be block-level or inline with em-dash framing when the tangent interrupts mid-action. Target frequency: 4-6 per chapter (establishing chapters), 3-5 per chapter (ongoing). Higher frequency and shorter fragments during high-stress scenes. See `docs/plans/2026-03-03-the-noise-tangent-convention-design.md` for full rules.
 - **No tables** in narrative text
 - **No fixed-width or monospace formatting** in prose
 

README.md

@@ -0,0 +1,34 @@
+# The Shade Series — Phelan Varrant
+
+A fantasy novel series following Phelan Varrant, a broke, socially reluctant magical problem-solver with an ability no one else has: he can see exactly where magic breaks.
+
+## Series Overview
+
+- **Genre:** Fantasy / Adventure / Humor
+- **Voice:** First-person past tense, dry wit, ADD-driven tangents
+- **Comparable Titles:** The Dresden Files, Discworld, The Magicians
+- **Publishing Target:** Amazon KDP (Kindle Unlimited)
+
+## Book 1: The Unbreakable Curse
+
+Phelan works in an herbal supply shop, counts coppers, and dreams about the house he can't afford to build. When a client arrives through the Guild of Necessary Services with a dying family member cursed by a working that every authority says is impossible to break, Phelan takes the case because the fee is significant and the problem is interesting. In that order.
+
+## Project Structure
+
+```
+CLAUDE.md                    # Master writing instructions
+chapters/book1/              # Chapter drafts
+world/                       # World bible (magic system, locations)
+characters/                  # Character files
+outline/                     # Series and book outlines
+notes/                       # Cut content, research, ideas
+docs/plans/                  # Design documents
+```
+
+## Writing with Claude Code
+
+This project uses Claude Code as the primary writing assistant. All instructions for voice, world-building, continuity, and formatting are in `CLAUDE.md`. Book-specific instructions are in each book's chapter directory.
+
+## License
+
+All rights reserved. This is an unpublished creative work.

chapters/book1/braindump.md

@@ -0,0 +1,76 @@
+Help me break up these over arching ideas into separate chapters.
+
+- Phelan meets Mere to help the dog.
+- Phelan notices the curse on the dog is flawed and has a vulnerability. He sees this before inspecting the dog, he can "see" the flaw from several feet away. 
+- This is the first time he's worked on a curse with real stakes on the line. Mere's approval means something to him, something he hasn't had before, he seldom cares about what people's feelings are. This is filed and noted.
+- Phelan breaks the curse on the dog using below:
+
+The Curse Architecture
+
+  Someone placed a fear curse on a stray dog. The working overwrites the dog's visual perception so that every human registers as a predator (wolf-shaped, threat-posture,
+  wrong eyes). The curse is well-anchored — standard curse-breaking won't work because dogs can't participate in the verbal/gestural components those techniques require.
+
+  But the caster made a mistake. They only hijacked vision. The curse doesn't touch smell, hearing, or spatial awareness. A dog's nose still processes humans as humans. Its
+   ears still register human voices as non-threatening. Only its eyes lie.
+
+  This is sloppy work disguised as clean work — the curse looks solid because the visual overwrite is strong and well-anchored. But the caster either didn't understand how
+  dogs process the world (humans are visual-dominant; dogs are scent-dominant) or didn't care enough to cover all channels. They built a curse for a human brain and put it
+  on a dog.
+
+  What Phelan Sees
+
+  When Phelan examines the curse with Flaw Sight, he sees the working as a lattice — but the lattice only connects to one sensory pathway. The other pathways are clean.
+  There's a gap where the visual overwrite ends and the dog's natural scent processing begins, and that gap is live — the dog's own senses are already fighting the curse
+  every moment, pushing conflicting data through the channels the curse doesn't control.
+
+  The flaw isn't subtle. It's structural. The curse is a wall built across one road while three other roads run wide open.
+
+  The Fix — Feeding the Contradiction
+
+  Phelan doesn't attack the curse. He doesn't try to break the anchoring or overpower the working. He does something lateral:
+
+  1. He uses Mere's binding salts (which she's already been dissolving in the dog's water to dampen the curse) as a base for a small amplification working — not to dampen
+  the curse this time, but to boost the dog's scent processing. Make the nose louder.
+  2. He anchors a simple sensory-enhancement working to the binding salt solution, keyed to the dog's olfactory pathways. This is basic magic — scent amplification is a
+  known technique used by trackers and hunters. Nothing exotic.
+  3. The enhanced scent data floods the dog's perception. The nose is now screaming "HUMAN — SAFE — KNOWN — HUMAN" while the eyes still say "PREDATOR." But dogs trust their
+   noses more than their eyes. The enhanced scent data tips the balance.
+  4. The curse's internal logic collapses. The working was designed to maintain "humans = predators" as a consistent perceptual reality. But it can only enforce that claim
+  visually. With the scent channel amplified, three out of four sensory channels now reject the curse's premise. The working can't sustain a definition that the dog's own
+  enhanced senses overwhelmingly contradict. It's a contract that says "X is true" while the evidence says "X is false" — and Phelan just made the evidence louder.
+  5. The curse unravels from the inside. Not broken by force. Dissolved by its own inconsistency. The lattice destabilizes, the anchoring loses coherence, and the working
+  collapses.
+
+  The Cost
+
+  - Phelan has to briefly sync with the dog's sensory framework to anchor the amplification correctly. This means experiencing the world as the dog does for a few seconds —
+   overwhelming scent data, flattened visual field, sound processing he's not built for. Disorienting and exhausting.
+  - After the curse breaks, he gets the standard post-exploit crash: physical tiredness, brief sensory distortion, a headache that suggests his brain is filing a formal
+  complaint.
+  - It's not a major crash (this isn't the triple chain from the main case), but it's enough for Mere to see that what he just did cost him something. This is important —
+  she sees both the competence and the price.
+
+  The Narrative Payoff
+
+  - For Mere: She watches him do in minutes what she's been working around for weeks. She sees the cost. She files both observations.
+  - For the reader: This is a demonstration of how Phelan works — not with power, but with perception. He didn't overpower the curse. He saw where it was wrong and made it
+  destroy itself. This sets up the main case (the triple chain) by establishing his method.
+  - For the dog: The curse breaks. The dog can see humans as humans again. Its first act is probably to approach Mere, because her scent is already the one it trusts most
+  from weeks of care. Good emotional beat.
+  - For Phelan: He used Mere's own materials (the binding salts she'd already been using) as the foundation for his fix. Her symptom management became part of his cure.
+  This is a competence-recognizes-competence moment.
+
+
+- The day after the dog curse fix, Phelan get's a letter from a carrier - it's from the guild, they want to have an interview. 
+- Phelan goes to the interview, there are 3 people sitting and a single chair for him to sit in as though he's on trial. Nothing else is the room. The 3 men ask questions like how long he's had the ability to use magic. How long he went to school. Several confirming questions about his current life (which suggest they have been watching him closely since his application). Finally a man comes into the room from the left. He whispers something into the middle chair mans ear (he must be of a higher standing). They ask about the dog curse, which confirms they have been following him. Phelan asks what about that case they wish to know. The lead man says, "How did you break it"?. Phelan is at a quandry, he's never told anyone about his gift, not sure if he should. Finally comes to the decision that it's now or never, and loosely explains the ability as "I just see problems in the workings, and use them to my advantage". This is enough for them to recognize the talent he has. They say they accept his application, it pays per job, but also a retainer salary based on rank in the guild. They have a job in mind for him that will be his first case. They will give him the specifics in about 2 weeks, so he has time to adjust and tidy up his current job. 
+
+- The guild's filtering system (the polite receptionist, the "eight-week waiting list" that doesn't exist, it's just an excuse for them to watch you) — Phelan appreciates this kind of structured misdirection
+- We should have section where Phelan get's a copy of the guild rules here, so the reader knows the rules of the guild.
+- Phelan's reaction to being accepted: not celebration, not relief — more like a chess piece finally reaching the right square. Satisfaction at a plan working.
+
+- Phelan then goes to his current job and resigns with 2 weeks notice.
+- This is where we introduce Leon, Phelan goes to talk to him about the curse and the guild. He is eager to talk about how he broke the curse to Leon. It's the kind of thing both of them would find interesting. Leon chains off the curse break idea and overload and explains a simliar case he found where he was exploring a tomb and found an expensive item locked by a ward. He found that by sending a huge amount of inputs into a ward he was able to cause the system to overload and crash, allowing him to remove the item from the ward and sell it. 
+
+- the guild gives him his first job, to obtain a rare herb from inside an old dungeon. Phelan has heard of these before, but not actually explored one. Dugeons often hold great magical artifacts and sometimes one can find rare monster materials used for thousands of magical uses. 
+
+- Phalen is a secretly a mage, adept in attack magic using the fire element and some earth (although it's not as good as his fire magic). This is required for him to be able to survive the old dungeon. 

chapters/book1/ch01-draft.md

@@ -14,7 +14,7 @@ I knew what they were for, or rather, what you could do with them if you were in
 
 I was re-shelving a crate of dried silkweed when I noticed the ward-jar on the third shelf was doing it again.
 
-(Third ring off-axis. Resonance gap between second and third anchors. Moisture seepage through the preservation field at roughly the speed of patience. Moonpetal chalk by month's end. Artificer blames storage. Gavren eats the cost. Customer gets expensive dust.)
+(*Third ring off-axis. Resonance gap between second and third anchors. Moisture seepage through the preservation field at roughly the speed of patience. Moonpetal chalk by month's end. Artificer blames storage. Gavren eats the cost. Customer gets expensive dust.*)
 
 I moved the jar to a higher shelf where the air was drier. It wouldn't fix the flaw — not my job — but it would slow the decay enough that the product would sell before it mattered.
 
@@ -50,7 +50,7 @@ Seventh bell. Open for business.
 
 I leaned against the counter —
 
-(Eleven coppers. Shaved half-silver, probably not worth a full half. Two meals if honest, three if creative. Same as this morning. Same as yesterday. The arithmetic hadn't changed. The habit was load-bearing.)
+(*Eleven coppers. Shaved half-silver, probably not worth a full half. Two meals if honest, three if creative. Same as this morning. Same as yesterday. The arithmetic hadn't changed. The habit was load-bearing.*)
 
 — and waited for the day to start being something other than this.
 
@@ -60,7 +60,7 @@ The morning rush, such as it was, arrived in the predictable sequence of human n
 
 First through the door: a dockworker with a bruised shoulder and the particular squint of a man who'd been told by his wife to see a healer and had decided, independently, that a jar of something from a shelf would be cheaper and involve fewer questions about how he'd been injured.
 
-(Bruised shoulder, left side. Carried something heavy and twisted. Not the first time — the calluses said dock work, the squint said wife sent him. Wedding band, copper, worn thin. Arnica salve, second shelf. In and out.)
+(*Bruised shoulder, left side. Carried something heavy and twisted. Not the first time — the calluses said dock work, the squint said wife sent him. Wedding band, copper, worn thin. Arnica salve, second shelf. In and out.*)
 
 He was correct on both counts. I pointed him toward the arnica salve, he grunted in a way that passed for gratitude among people who carried things for a living, and he was gone in under two minutes. Efficient. I appreciated efficiency in customers the way I appreciated it in plumbing — when it worked, you didn't have to think about it.
 
@@ -112,7 +112,7 @@ I noticed all of this in approximately two seconds, which was unusual. I noticed
 
 My process — the automatic, near-involuntary cold read I ran on every person who walked through a door — engaged the way it always did.
 
-(Posture: confident, not performed. Clothing: practical, well-maintained, not expensive. Hands: no rings, short nails, callus on right index finger — writing or detailed manual work. Eyes: scanning, not browsing. Already knows what she's here for. Cataloguing the rest while she locates it.)
+(*Posture: confident, not performed. Clothing: practical, well-maintained, not expensive. Hands: no rings, short nails, callus on right index finger — writing or detailed manual work. Eyes: scanning, not browsing. Already knows what she's here for. Cataloguing the rest while she locates it.*)
 
 All of this was normal. Data. The kind of behavioral surface I could read on anyone in a room and use to predict their next three decisions with reasonable accuracy.
 
@@ -180,7 +180,7 @@ I rang up the binding salts and the silverthorn, wrote the transaction in the le
 
 I noticed it anyway.
 
-(Warmth. Brief. She didn't pull away faster than necessary. Didn't linger either — no data there. But the absence of avoidance. The neutral duration. Was that a signal or the lack of one? Baseline: most people retract. She didn't. Deviation from norm or absence of norm? Insufficient sample size. One interaction. One touch. Meaningless. Noted anyway. Filed under —)
+(*Warmth. Brief. She didn't pull away faster than necessary. Didn't linger either — no data there. But the absence of avoidance. The neutral duration. Was that a signal or the lack of one? Baseline: most people retract. She didn't. Deviation from norm or absence of norm? Insufficient sample size. One interaction. One touch. Meaningless. Noted anyway. Filed under —*)
 
 *Stop it,* I told myself. I was reading subtext into a woman who didn't have subtext. If she hadn't pulled away, it was because there was no reason to pull away, and assigning meaning to the absence of avoidance was exactly the kind of pattern-matching error I spent my life not making.
 
@@ -234,7 +234,7 @@ I locked up and stepped into the evening.
 
 Drenwick at dusk was tolerable. The light did something to the river that made it look like it belonged in a better city, and the noise from the docks softened into a background hum that my brain could file away without processing. I walked the route I always walked — south along the quay, past the chandler's and the net-mender's, through the gap in the old customs wall —
 
-(Two bricks missing. Load-bearing? No — decorative course. Gap hadn't widened in the three years I'd been using it. Mortar on the adjacent bricks still sound. Someone had removed them deliberately, not knocked them out. Interesting. Irrelevant. Filed.)
+(*Two bricks missing. Load-bearing? No — decorative course. Gap hadn't widened in the three years I'd been using it. Mortar on the adjacent bricks still sound. Someone had removed them deliberately, not knocked them out. Interesting. Irrelevant. Filed.*)
 
 — where no one had bothered to repair the gap because the only thing on the other side was scrub grass and a path that led to the part of the waterfront where rent was cheap enough that someone like me could afford to exist.
 
@@ -244,13 +244,13 @@ The shack itself was one room, which was generous if you considered it a sleepin
 
 The workshop was the thing. Not the house — houses were shelter, and shelter was solvable. The workshop was where the actual work would happen. The work I was meant to be doing, if I could ever get far enough past the arithmetic of survival to start.
 
-I spread the drawings on the table, which I did most evenings, not because I needed to review them but because looking at them was the closest thing I had to faith. Four rooms. A workshop with ventilation and proper warding anchors built into the foundation. A main room large enough to not feel like a shack. A bedroom. And a second bedroom that existed in the plans for reasons I had not articulated to anyone, including myself, but which had appeared in revision six and survived every subsequent draft without being questioned.
+I spread the drawings on the table, which I did most evenings, not because I needed to review them but because looking at them was the closest thing I had to faith. Five rooms. A workshop with ventilation and proper warding anchors built into the foundation. A main room large enough to not feel like a shack. A bedroom. A kitchen — which, embarrassingly, hadn't appeared until revision four, because apparently I'd been planning to sustain myself on determination and ambient river moisture. And a bathroom, added in revision six. Why it took me six revisions to understand that a person needs a place to bathe and relieve themselves, I'll never know, but it's there now.
 
 Twelve coppers and a shaved half-silver.
 
 The house needed approximately eight hundred silvers in materials alone.
 
-(Eight hundred for materials. Sixty for permits. Two hundred minimum for warding work if done by a licensed artificer, one-forty if I sourced the anchors myself and contracted just the inscription. Labor: three hundred if hired, less if I did the framing. Total: thirteen hundred, give or take. Current savings: twelve coppers and a shaved half-silver. Time to break ground at current rate of accumulation: forty years. Margin of error: irrelevant when the number starts with forty.)
+(*Eight hundred for materials. Sixty for permits. Two hundred minimum for warding work if done by a licensed artificer, one-forty if I sourced the anchors myself and contracted just the inscription. Labor: three hundred if hired, less if I did the framing. Total: thirteen hundred, give or take. Current savings: twelve coppers and a shaved half-silver. Time to break ground at current rate of accumulation: forty years. Margin of error: irrelevant when the number starts with forty.*)
 
 At my current rate of savings — which was not a rate so much as a theoretical concept, like perpetual motion or honest politics — I would be able to break ground in roughly forty years, give or take the occasional windfall or catastrophe.
 
@@ -274,6 +274,6 @@ I wouldn't ask her out. The math was clear, even if the rest wasn't. I was a she
 
 I put the drawings away, ate my one honest meal — bread, hard cheese, an apple that was optimistic about its own freshness — and lay on the cot listening to the river do the thing it did at night, which was exist loudly and without consideration for people trying to sleep.
 
-The second bedroom stayed in the plans. I didn't think about why.
+The plans stayed on the table. Nine revisions and counting.
 
 I thought about crystal density, and golden hair, and the particular way she'd said *simple deduction* without irony, and I fell asleep annoyed at a woman whose name I didn't know for reasons I couldn't quantify, which was — if I was being honest, and I was usually honest — not a bad way to end a day that had otherwise been entirely about counting coppers.

chapters/book1/ch02-draft.md

@@ -10,17 +10,17 @@ By the evening of day three, I had developed three complete scenarios.
 
 **Scenario One: The Expertise Gambit.** She enters the shop. She browses — specifically the back cases, because that's where her interest lies. She picks up a product. I notice a labeling error, or a quality concern, or something subtle enough that only someone with real knowledge would catch it. I correct the information casually, demonstrating competence without arrogance. She's impressed. A conversation develops naturally. In the warm glow of shared expertise, I suggest continuing the discussion over coffee.
 
-(Four variations depending on which product she picked up first. Eleven possible responses mapped. Optimal follow-up to each calculated. Flaw: assumed she would browse. She didn't browse last time. She was surgical. The entire scenario depended on a window that probably wouldn't exist.)
+(*Four variations depending on which product she picked up first. Eleven possible responses mapped. Optimal follow-up to each calculated. Flaw: assumed she would browse. She didn't browse last time. She was surgical. The entire scenario depended on a window that probably wouldn't exist.*)
 
 I kept the scenario anyway. Hope is a poor strategist but an excellent motivator.
 
 **Scenario Two: The Coincidental Encounter.** I happen to be reorganizing the shelf nearest the front door when she enters. Natural proximity. A greeting that doesn't feel forced. The conversation unfolds organically from the coincidence of my being right there, which isn't a coincidence at all, but she doesn't need to know that.
 
-The flaw in this plan was fundamental and should have been obvious: it required me to look natural while loitering near a door. (Practiced in stockroom mirror. Results: instructive. Phelan Varrant standing near a door with intent looked approximately like a man waiting to serve legal papers. Something about the posture. Or possibly the face. Casual proximity transformed into vaguely threatening surveillance. Filed under "emergency use only.")
+The flaw in this plan was fundamental and should have been obvious: it required me to look natural while loitering near a door. (*Practiced in stockroom mirror. Results: instructive. Phelan Varrant standing near a door with intent looked approximately like a man waiting to serve legal papers. Something about the posture. Or possibly the face. Casual proximity transformed into vaguely threatening surveillance. Filed under "emergency use only."*)
 
 **Scenario Three: The Direct Approach.** I ask her. That's it. No setup, no manufactured context, no elaborate staging. I simply say the words.
 
-(Seventeen rehearsals. Stress-tested for ambiguity, unintended implications, potential misinterpretation. Rejected: "Would you like to grab coffee?" — too casual, implies haste. "Can I take you to coffee?" — grammatically awkward, suggests physical transport. "I'd enjoy having coffee with you" — presumptuous, centers my enjoyment. "Do you drink coffee?" — information-gathering, not invitation. Final: "Would you like to get coffee sometime?" Six words. No subtext. No room for error.)
+(*Seventeen rehearsals. Stress-tested for ambiguity, unintended implications, potential misinterpretation. Rejected: "Would you like to grab coffee?" — too casual, implies haste. "Can I take you to coffee?" — grammatically awkward, suggests physical transport. "I'd enjoy having coffee with you" — presumptuous, centers my enjoyment. "Do you drink coffee?" — information-gathering, not invitation. Final: "Would you like to get coffee sometime?" Six words. No subtext. No room for error.*)
 
 I was almost proud of it.
 
@@ -60,7 +60,7 @@ It took me a moment. Then another moment. Then a third moment in which I recogni
 
 Gavren opened his mouth. Closed it. Opened it again. "Go," he said, in the tone of a man granting clemency to someone who hadn't asked for it. "Stock the feverwort before you leave."
 
-I stocked the feverwort in what I believe was record time — (Probability of return visit: unknown. Insufficient data. She bought binding salts — consumable. Silverthorn — consumable. Both items she'd need to replenish. Estimated timeline: one to two weeks. Unless she found a better supplier. Filed under "not thinking about it.") — though I didn't verify because I was operating on approximately thirty percent of my normal cognitive capacity and the other seventy percent was busy not thinking about the fact that I was about to spend an afternoon with a woman whose name I still didn't know.
+I stocked the feverwort in what I believe was record time — (*Probability of return visit: unknown. Insufficient data. She bought binding salts — consumable. Silverthorn — consumable. Both items she'd need to replenish. Estimated timeline: one to two weeks. Unless she found a better supplier. Filed under "not thinking about it."*) — though I didn't verify because I was operating on approximately thirty percent of my normal cognitive capacity and the other seventy percent was busy not thinking about the fact that I was about to spend an afternoon with a woman whose name I still didn't know.
 
 That last part struck me as I was hanging up my apron. Four days of planning. Three complete scenarios. Seventeen rehearsals. And I had never once, in any version, included the step where I learned what to call her.
 
@@ -72,7 +72,11 @@ Mere. I filed it where it would stay.
 
 * * *
 
-The arcane district occupied six blocks between the guild quarter and the river, a stretch of narrow streets where the shops had names like "Aldric's Precision Implements" and "The Calibrated Eye" and the windows displayed things that most people walked past without understanding. I understood them. (Window display: three focusing rods, price tags facing outward. Two silvers each. Overpriced by forty percent. The grain on the middle rod suggested second-growth timber — adequate channeling but half the lifespan. Margin: obscene.) I also understood the markup, which was why I never bought anything here, but understanding was free and I'd always been better at looking than purchasing.
+The arcane district occupied six blocks between the guild quarter and the river, a stretch of narrow streets where the shops had names like "Aldric's Precision Implements" and "The Calibrated Eye" and the windows displayed things that most people walked past without understanding. I understood them. 
+
+(*Window display: three focusing rods, price tags facing outward. Two silvers each. Overpriced by forty percent. The grain on the middle rod suggested second-growth timber — adequate channeling but half the lifespan. Margin: obscene.*) 
+
+I also understood the markup, which was why I never bought anything here, but understanding was free and I'd always been better at looking than purchasing.
 
 Mere walked the way she'd walked through Gavren's shop — efficiently, with the focused attention of someone cataloguing everything and filing it for later. She didn't browse. She *surveyed.* Every window got a three-second assessment before she either moved on or stopped, and when she stopped, it was because something had caught her eye that warranted the full weight of her attention.
 
@@ -84,7 +88,9 @@ She picked up the third kettle from the left, turned it over, and examined the r
 
 I leaned in. She was right. The slip was barely visible — a fractional deviation where the inscribing tool had jumped, probably from a vibration or a moment's lost focus. Most people would never notice. Most artificers wouldn't notice unless they were specifically auditing their own work.
 
-What she couldn't see — what I could, because the thing I did with magic was not the thing she did with her eyes — was the consequence. (Micro-gap in the power word geometry. Channeling efficiency degraded — fifteen percent, maybe twenty. Cascade through the sequence. Slower heat time, higher drain. Functional but wasteful. Wheel that was almost round.)
+What she couldn't see — what I could, because the thing I did with magic was not the thing she did with her eyes — was the consequence. 
+
+(*Micro-gap in the power word geometry. Channeling efficiency degraded — fifteen percent, maybe twenty. Cascade through the sequence. Slower heat time, higher drain. Functional but wasteful. Wheel that was almost round.*)
 
 "The power word's compromised," I said. "Not enough to break the working, but the channeling efficiency would be off. Fifteen percent, maybe twenty. You'd notice it as a slower heat time."
 
@@ -268,16 +274,18 @@ The thought sat in my chest like something warm and dangerous. I let it stay for
 
 I pulled out the house plans. I did this most evenings, but tonight the drawings looked different. Not better, not worse — just charged with a meaning I usually kept at arm's length.
 
-Four rooms. Workshop with ventilation and warding anchors. Main room. Bedroom. And the second bedroom — revision six, survived every subsequent draft, never questioned, never explained.
+Five rooms. Workshop with ventilation and warding anchors. Main room. Kitchen. Bathroom. Bedroom. The bedroom that tonight, for some reason, looked small.
 
-I'd told myself I didn't think about why the second bedroom was there. (Not looking at the sun doesn't mean you've forgotten it exists. The thought approached — not arriving, not landing. Stray animal testing whether it was safe to come closer. Mere needed to be home by sixth bell because her mother rearranged her workspace. Said it like weather. It wasn't weather. The thought got close enough to have a shape —)
+The bedroom had always been adequate. A bed, a wardrobe, a window. Enough space for one person who didn't accumulate things. 
 
-The dog. Thursday. A curse with strong anchoring and an unusual target. I could work with that. I could think about curse architecture and intervention strategies and the specific mechanics of fear-anchoring in non-human subjects, and all of that was interesting and useful and did not require me to think about why a second bedroom had appeared in revision six of a set of house plans drawn by a man who lived alone and expected to continue living alone and was, by every reasonable metric, not the kind of person who planned rooms for people he hadn't asked to fill them.
+(*Not looking at the sun doesn't mean you've forgotten it exists. The thought approached — not arriving, not landing. It was a stray animal testing whether it was safe to come closer. Mere needed to be home by sixth bell because her mother rearranged her workspace. Said it like weather. It wasn't weather. The thought got close enough to have a shape — a bed wide enough for two, a second wardrobe, the particular geometry of a room that expected someone to stay —*)
+
+The dog. Thursday. A curse with strong anchoring and an unusual target. I could work with that. I could think about curse architecture and intervention strategies and the specific mechanics of fear-anchoring in non-human subjects, and all of that was interesting and useful and did not require me to think about why the bedroom measurements had started to look insufficient in the plans of a man who lived alone and expected to continue living alone and was, by every reasonable metric, not the kind of person who redesigned rooms for people he hadn't asked to fill them.
 
 Thursday. The dog. The curse.
 
 I put the plans away, ate my bread and cheese, and lay on the cot listening to the river. I thought about architecture — magical, structural, and the kind you built on paper for a future that kept getting closer and further away at the same time.
 
-I fell asleep thinking about flaws. The kind in kettles, the kind in curses, and the kind in plans that included rooms you couldn't explain.
+I fell asleep thinking about flaws. The kind in kettles, the kind in curses, and the kind in bedrooms that had started feeling too small for reasons I wasn't ready to measure.
 
 It was not a bad way to end a day.

chapters/book1/ch03-draft.md

@@ -0,0 +1,303 @@
+# Chapter 3: Thursday
+
+Mere's bookshop occupied a narrow building on the eastern edge of the arcane district, wedged between a scrivener's office and a tea house that smelled aggressively of cardamom. The sign read "Thresholds — Magical Texts & Theory" in lettering that was either deliberately understated or the product of a signmaker who'd been told to keep costs down. I suspected the latter. The window display held three grimoires on wooden stands, a rack of spell theory pamphlets, and a hand-lettered card that said *Staff recommendations available upon request* in handwriting I recognized.
+
+I recognized it because I'd spent an unreasonable amount of the last two days thinking about the person who'd written it. This was not relevant to the task at hand. I noted it and moved on.
+
+The door had a bell. The bell was enchanted — a minor working, the kind of thing an artificer does in an afternoon. Keyed to detect intent, so it rang differently for browsers versus buyers versus people who'd wandered in looking for the tea house next door. Functional. Clean. Well-maintained.
+
+(*Third anchor slightly over-tensioned. Compensating for age — the original inscription was at least eight years old, re-calibrated twice. Whoever maintained it knew what they were doing but was working with a framework that needed replacing, not patching. Like putting new soles on boots that needed new uppers.*)
+
+"You're staring at my door," Mere said.
+
+She was standing behind the counter with the expression of someone who had been watching me examine her doorbell enchantment for longer than was socially appropriate. Which, given that any amount of time spent examining someone's doorbell enchantment was socially inappropriate, meant she'd been watching for a while.
+
+"The intent-detection array is interesting," I said.
+
+"It tells me who's going to waste my time." She came around the counter. "The dog is in the back."
+
+No preamble. No small talk. No acknowledgment that the last time we'd seen each other we'd spent an afternoon together that neither of us had called a date, which had ended with her walking away along the canal and me going home to stare at bedroom measurements I wasn't ready to think about. Just *the dog is in the back,* delivered with the same flat efficiency she applied to everything.
+
+I found this enormously reassuring.
+
+The back room of Thresholds was half storage, half workspace — crates of unsorted texts along one wall, a desk covered in cataloguing notes, and a cleared area in the corner where someone had arranged blankets, two water bowls, and a food dish with the careful precision of a person who had thought about every detail of an animal's comfort and executed accordingly.
+
+The dog was under the desk.
+
+I saw the curse before I saw the dog.
+
+That requires explanation. Normally, my awareness of magical flaws operates at close range — ten feet, perhaps fifteen in ideal conditions. I sense them the way most people sense a draft: vaguely, directionally, without much detail until I focus. Background noise. The river underneath.
+
+This was different. I was standing in the doorway, a good twelve feet from the desk, and the curse's lattice structure was *there* — fully visible, hanging in my perception like a blueprint drawn in light. Every anchor point. Every connection. Every line of intent, glowing with the particular clarity that meant my brain had already started pulling it apart without asking permission.
+
+(*Fear curse. Visual channel override — hijacking optic processing to reclassify human silhouettes as predator signatures. Clever work. No. Not clever. Competent work done by someone who hadn't thought about what they were doing. Three primary anchors, two redundant supports, a feedback loop that refreshed the fear response every time the visual trigger fired. Built for a human perceptual framework. Grafted onto a canine one. Like writing instructions in a language the reader only half spoke — the dog's brain was filling in the gaps with its own fear, which meant the curse was running on fifty percent magical compulsion and fifty percent the animal's own confused terror, and the person who'd cast it probably didn't even know that.*)
+
+"How long have you had him?" I asked, not moving from the doorway.
+
+"Three weeks. I found him in the warrens — someone had dumped him after the curse took hold. He'd been running for at least a day. Dehydrated. Half-starved." She said this the way she said everything: facts, delivered without performance, the emotional weight carried entirely by what the facts described. "He won't let anyone touch him. He'll eat if no one's in the room. The binding salts in the water help — he'll tolerate a person at about four feet now, as long as you don't make sudden movements."
+
+I was still looking at the curse from the doorway, and my brain was doing the thing it did — the thing I'd never been able to explain to anyone, the thing I'd spent my whole life calling instinct or training or *some background in how magical workings are structured* — and what it was telling me was this:
+
+The curse was a wall built across one road while three other roads ran wide open.
+
+The caster had hijacked the dog's visual processing. That was all. Smell, hearing, spatial awareness, proprioception — everything else was untouched. The dog's nose still worked perfectly. Its ears still worked perfectly. Its entire sensory world, minus one channel, was still intact and still telling it the truth. But the visual override was so aggressive, so constant, that it drowned out everything else. The dog *saw* predators, and seeing predators meant fearing predators, and fearing predators meant running, and running meant it never held still long enough for its other senses to contradict what its eyes were telling it.
+
+Sloppy work disguised as clean work. A curse designed for the architecture of a human brain — where vision dominates, where seeing is believing — applied to an animal whose nose was a more reliable instrument than its eyes had ever been.
+
+"I can fix this," I said.
+
+Mere looked at me. The assessment look — the one I'd learned to recognize from the shop, from the kettle, from the canal wall. She was processing new data and deciding where it fit.
+
+"You've been standing in the doorway for two minutes," she said. "You haven't examined the dog."
+
+"I don't need to examine the dog. The curse is—" I stopped. Recalibrated. *The curse is visible from here and I've already mapped its entire structure* was not a sentence I was prepared to say out loud, because it would raise questions I couldn't answer without explaining things I'd spent my entire adult life not explaining. "The curse architecture is simpler than it looks. It's only affecting one sensory channel — vision. Everything else is untouched."
+
+"I know," she said. "That's why the binding salts work. They're not suppressing the curse directly — they're lowering the overall magical field strength enough that his other senses can compete with the visual override. When the fear signal weakens, his nose tells him I'm safe, and the nose wins."
+
+I stared at her.
+
+She had arrived at the same structural understanding I had — not through seeing the lattice, not through any magical perception, but through observation, logic, and weeks of patient trial and error. She'd watched the dog's behavior, noted what worked and what didn't, and reverse-engineered the curse's architecture from the outside.
+
+"That's exactly right," I said.
+
+"I know." Not boastful. Factual. She'd done the work. She knew what the work had shown her. "The problem is I can't increase the salt concentration without side effects. Too much dampening and his natural magical resistance starts to degrade. I'm managing symptoms, not curing anything."
+
+"You're doing more than managing symptoms. You built the foundation." I came into the room slowly, keeping my movements deliberate. Under the desk, a pair of dark eyes tracked me — not with panic, not at this distance, but with the rigid alertness of an animal that was permanently four seconds from bolting. "Your salt solution weakens the curse's grip. If I can amplify a competing sensory channel enough to flood the visual override with contradictory data, the curse's internal logic should collapse. It can't sustain a fear response when three other senses are screaming *safe.*"
+
+"Which channel?"
+
+"Scent. It's his strongest. And your binding salts are already priming the pathway — lowering the magical interference enough that the scent data is partially getting through. I'd be amplifying what you've already started."
+
+She was quiet for a moment. Not uncertain — processing. Running the logic, testing it against what she knew.
+
+"You'd use my salts as a base," she said.
+
+"Modified. Repurposed. But yes — your materials, your groundwork. I'm adding a layer, not replacing what you built."
+
+Something shifted in her expression. Not a smile — something underneath a smile, something that hadn't decided yet what shape it wanted to take. She'd spent three weeks working on this animal with tools everyone would have said were inadequate, managing a curse no one thought she could manage, and the person she'd brought in to help was telling her that her approach wasn't just adequate — it was the foundation for the cure.
+
+"I need a day," I said. "To work out the amplification sequence. The binding salt modification. I want to get this right."
+
+"Tomorrow," she said.
+
+"Tomorrow."
+
+* * *
+
+The shack. The cot. The river sounds. The curse.
+
+I lay in the dark and my brain would not stop.
+
+This was not unusual. This was, in fact, the fundamental operating condition of a mind that processed the world as a series of interconnected systems waiting to be optimized, improved, or exploited. Most nights the river underneath ran at a manageable current — background processing, the steady hum of a machine that never fully powered down. I'd learned to sleep over it the way people who live near railways learn to sleep through trains.
+
+Tonight was not most nights. Tonight the current had teeth.
+
+(*Binding salt crystalline structure — lattice geometry maps onto the curse's anchor pattern at three points. Three points of contact means three potential amplification vectors. But the salt dampens broadly, which means amplification requires selectivity — boost the scent pathway without boosting the fear pathway. How? The silverthorn. Silverthorn has anxiolytic properties, which means it's already interacting with the fear signal at a neurochemical level. If I layer the silverthorn into the salt modification, it creates a selective filter — amplify scent, suppress fear, let the contradiction build until—*)
+
+I sat up. Drew breath. The thought was moving too fast and I needed it to slow down, but it wouldn't slow down, because it had found a seam and my brain did not let go of seams.
+
+(*Wrong approach. Don't fight the curse. Don't even touch the curse. Make the dog's own perception fight the curse. The binding salts weaken the magical signal. The silverthorn suppresses the fear response. The amplification boosts scent processing. Three layers. Three interventions. None of them attack the curse directly. They create conditions where the curse attacks itself — the visual override screams "predator" while the scent channel screams "safe" and the fear suppression means the dog can actually process the contradiction instead of just bolting, and then the curse's own feedback loop turns against it because every time it refreshes the fear signal it has to fight harder against three channels of contradictory data and the energy cost compounds and the anchors strain and—*)
+
+(*—it unravels. From the inside. The curse destroys itself because it was built on one road and I opened the other three.*)
+
+The migraine arrived at approximately the second bell. Not gradually — it landed like a fist behind my left eye, the kind of pain that makes you realize how much of your awareness is usually dedicated to *not hurting* and how disorienting it is when that allocation gets reassigned. My vision went bright at the edges. My thoughts, which had been racing with the manic precision of a well-oiled machine discovering a new gear, ground to a halt with the ugly abruptness of that same machine hitting something it wasn't designed to process.
+
+I knew an herb for this. The day job had its uses.
+
+Thornwell root. Not a common remedy — most apothecaries didn't stock it because the applications were narrow and the taste was genuinely, memorably terrible. But Gavren kept a small supply for his own headaches, and I'd pocketed a measure of it three months ago because I'd recognized the symptoms of a brain that occasionally ran itself into walls and wanted a tool on hand for when it happened again.
+
+(*Theft. Technically. From a man who paid me fairly and trusted me with his inventory. Filed under: things I would replace when I could afford to, which would be never, which meant I would simply have to be a person who had stolen thornwell root from his employer and live with that specific weight alongside all the others.*)
+
+I chewed the root — bitter, chalky, the kind of flavor that clung to the inside of your mouth like a grudge — and waited. The next two hours were spent on the edge of vomiting from the nausea. The migraine didn't fade so much as withdraw, pulling back from my awareness the way a tide pulls back from shore, leaving behind the particular exhaustion of a mind that had been running at full capacity for too long and was now being forcibly shut down.
+
+I slept. Not well, but thoroughly — the deep, heavy unconsciousness of a system that had exceeded its operational limits and was no longer asking permission to rest.
+
+* * *
+
+Friday morning, I looked like something the river had deposited on the bank overnight.
+
+The face in the water basin was pale in a way that went beyond my usual complexion and into the territory of *that man should probably not be standing up.* My eyes were bloodshot. My hands had a fine tremor that I attributed to dehydration and addressed with three cups of water in rapid succession. My head felt hollowed out — not painful anymore, just empty, the way a room feels after you've moved all the furniture.
+
+I had the solution, though. Every step, every modification, every precisely calibrated intervention. It sat in my mind with the crystalline clarity of something that had been forged under pressure and cooled into permanence. The migraine, the lost sleep, the hours of my brain tearing itself apart and reassembling the pieces — all of that had produced a clean, elegant, workable plan.
+
+I put on a clean shirt. It did not help my appearance appreciably, but I had standards, and arriving to perform precision magical work looking like I'd been sleeping in a ditch was beneath those standards, even if the underlying reality was not far off.
+
+The walk to Thresholds took twenty minutes. I spent most of it not thinking about how I looked and the rest of it not thinking about the fact that Mere had never seen me like this. In the shop, I'd been competent. On the date — the afternoon that wasn't a date — I'd been charming in whatever way I managed charming. Both times I had been, if not impressive, at least functional. A person who appeared to have his life in a condition resembling order.
+
+Today I looked like a man who had spent the night fighting his own brain and lost.
+
+The door bell chimed — browser intent, apparently, which felt inaccurate but I wasn't going to argue with an enchantment.
+
+Mere was behind the counter. She looked up. Her expression did not change, exactly, but something behind it went very still — the same kind of stillness I'd seen when she processed unexpected data, except this time the data was my face, and what my face was communicating was not subtle.
+
+"You look terrible," she said.
+
+"Good morning to you too."
+
+"I'm not being rude. I'm being accurate. You look significantly worse than either of the two previous times I've seen you, and in those cases you looked fine." She came around the counter, studying me the way she'd studied the kettle in Aldric's shop — systematically, noting every detail, running comparisons against her stored observations. "What happened?"
+
+"Migraine," I said. "Bad night. I'm fine."
+
+"You're not fine. Your hands are shaking and your eyes are bloodshot and you're holding your head at an angle that suggests your neck hurts."
+
+My neck did hurt. I had not noticed this until she said it, which was either a testament to my capacity for ignoring physical discomfort or an indication that my self-assessment capabilities were currently impaired. Both seemed likely.
+
+"I worked late on the amplification sequence," I said. "The solution is clean. I know exactly what to do. The headache was a side effect, and it's mostly passed." This was true. It was also not the whole truth, in the same way that describing a hurricane as "some wind" was not the whole truth. But the whole truth — *my brain locked onto the problem at sundown and did not let go until the second bell, and the migraine that followed was the kind that makes you reconsider your relationship with consciousness itself* — was not something I was prepared to share, because sharing it would mean explaining the mechanism, and explaining the mechanism would mean explaining *me,* and I had spent my entire adult life not doing that.
+
+"You did this last night," she said. Not a question. "Preparing. For the dog."
+
+"I wanted to get it right."
+
+She was quiet for a moment. Not the processing quiet — something else. Something I hadn't seen on her face before and couldn't immediately categorize, which was unusual, because I categorized everything and I was rarely wrong.
+
+"You hurt yourself," she said. "Working on this."
+
+"I had a migraine. It's not—"
+
+"You had a migraine because you spent all night working on a solution to my dog's curse. You didn't have to do that. You could have taken longer. You could have come back in a few days. But you said tomorrow, and then you — did this to yourself." She gestured at me. At the general condition of me.
+
+I didn't have a response that was both honest and comfortable, so I defaulted to the option that was neither. "It looks worse than it is."
+
+She didn't believe me. I could see that clearly, even through the fog of exhaustion, because Mere's disbelief was not performed — it simply existed on her face as a fact, the same way her honesty existed as a fact and her bluntness existed as a fact. She didn't believe me, and she wasn't going to pretend otherwise, and she wasn't going to argue about it either.
+
+"Sit down," she said.
+
+She pulled a chair from behind the counter — not offered, not suggested. Placed. She put the chair where I was standing and the physics of the situation left me with no option but to sit. Then she went to the back room and returned with a cup of water, which she put in my hand with the careful precision of someone who had decided what was going to happen next and was implementing it with zero tolerance for input.
+
+"Drink that," she said.
+
+I drank it. It occurred to me that being managed by Mere Fields was not substantially different from being managed by anyone else, except that she was better at it because she didn't waste energy on the social performance that usually accompanied the process. No gentle suggestions. No *would you like to* or *maybe you should.* Just the chair, the water, and the flat certainty that both were necessary.
+
+Then she took my hand.
+
+Not dramatically. Not with eye contact, not with a speech, not with any of the social choreography that usually preceded physical contact between two people who had known each other for less than two weeks. She was standing beside the chair, and she reached down, and she took my hand, and she held it.
+
+Her fingers were cool. Her grip was firm in a way that suggested she'd decided to do this and was not going to do it halfway. She was looking at the shelf behind me — not avoiding my eyes, exactly, but not seeking them either. She'd made a decision and executed it, the way she executed everything: directly, without preamble, without checking whether the other person was ready.
+
+(*Her thumb was resting on the tendon between my second and third knuckle. Her hand was smaller than I'd expected. She was holding on the way you hold something you've decided not to drop. This was — this was data I was going to need to process later, in a room where she wasn't present, because processing it now would require acknowledging what it meant and I was not equipped for that operation on four hours of migraine sleep and three cups of water.*)
+
+"The dog is in the back," she said. Same words as yesterday. Same flat delivery. As if nothing had changed, as if she wasn't holding my hand in a bookshop on a Friday morning, as if the distance between *sitting down, drink that* and *fingers laced through mine* was the most natural progression in the world.
+
+Maybe, for her, it was.
+
+"Right," I said. "The dog."
+
+I stood up. She let go. Neither of us mentioned it.
+
+* * *
+
+The back room was the same as yesterday — crates, desk, blankets, bowls. The dog was under the desk, watching me with the rigid alertness of an animal that lived in permanent crisis. Its dark eyes tracked my movements with a precision that would have been impressive if it wasn't heartbreaking.
+
+I knelt on the floor, slowly, at a distance of about five feet. From here the curse was vivid — the lattice structure humming with the low, constant energy of a working that had been running for weeks and showed no signs of degrading on its own. The anchors were solid. The feedback loop was stable. Left alone, this curse would outlast the dog.
+
+(*Not going to happen.*)
+
+"I need your binding salts," I said. "The same batch you've been using — don't mix a fresh one. The dog's scent memory is keyed to the specific mineral signature of your solution. New salts would read as unfamiliar and we'd lose the trust baseline you've built."
+
+Mere brought the salts without questioning the request or the reasoning. She understood — not the magical mechanics, but the logic. Consistency mattered. The dog trusted what it knew.
+
+I worked in silence for several minutes, modifying the salt solution with the amplification sequence I'd built in the dark of the shack while my brain ate itself alive. The modification was delicate — not complex, exactly, but precise in a way that required steady hands, which mine were not, and clear focus, which mine was barely. I compensated for the tremor by bracing my wrist against my knee. I compensated for the fog by following the plan I'd already built, step by step, the way a navigator follows a chart through water he's too tired to read by eye.
+
+Mere watched. She didn't comment, didn't offer advice, didn't ask what I was doing. She watched the way she'd watched me examine the kettle — noting everything, filing everything, assessment without interference. I appreciated this more than I could have articulated, because articulation was not currently among my available resources.
+
+"I'm going to pour the modified solution into his water bowl," I said. "When he drinks, the amplification will activate — slowly, over about ten minutes. His scent processing will intensify. He'll start receiving stronger olfactory data, and that data will contradict what his eyes are telling him. The curse can't sustain a fear response when three other senses are reporting safety. It will try — the feedback loop will fire harder, burn more energy — but the contradiction is structural. The curse was built on one channel. I'm opening the other three."
+
+"And it will collapse," Mere said.
+
+"From the inside. The curse destroys itself. I don't have to touch it."
+
+She nodded once. Not impressed — understanding. She saw the elegance of it: not force, not a direct assault on a well-anchored working, but a lateral approach that turned the curse's own design against it. A wall built across one road, defeated by traffic on the other three.
+
+I poured the solution into the water bowl. Then I moved back — all the way to the doorway, giving the dog the maximum distance the room allowed. Mere stayed closer, three feet from the bowl, because her scent was part of the equation. She was *safe.* She'd been safe for three weeks, through careful work and patient presence, and the dog's nose knew it even when the dog's eyes didn't.
+
+We waited.
+
+The dog watched us from under the desk. Its nostrils flared — once, twice, catching something new in the water, something that registered as familiar but different. Mere's salts, the base it had been drinking for weeks, but altered now, carrying a resonance that called to the animal's strongest sense.
+
+It took four minutes for the dog to approach the bowl. Four minutes of watching, smelling, the visible war between *afraid* and *thirsty* playing out behind dark eyes. I held still. Mere held still.
+
+The dog drank.
+
+The effect was not dramatic. There was no flash of light, no surge of energy, no visible moment where the curse shattered like glass. What happened was slower and quieter and, in its way, more complete: the dog lifted its head from the bowl, and its nostrils flared wide, and I watched — through the lattice, through the structure only I could see — as the scent data flooded inward like water through a broken dam.
+
+(*Anchor one: strain. The feedback loop firing, trying to reassert the fear response, but the scent data is contradicting the visual data and the dog's brain is choosing the nose over the eyes because it was always going to choose the nose over the eyes because that's what dogs do, that's what the caster didn't understand, you built a human curse for a human brain and put it on an animal that trusts its nose the way humans trust their eyes and now the nose is winning—*)
+
+(*Anchor two: failing. Energy cost spiking. The curse is burning through its reserves trying to maintain a fear response against three channels of contradictory input and it can't, it was never designed for this, it was designed for a species that believes what it sees and the dog doesn't believe what it sees because its nose is telling it the truth and the truth is Mere, the truth is weeks of patient care and binding salts in the water and food left by hands that never grabbed, never hit, never did anything but help—*)
+
+(*Anchor three.*)
+
+(*Gone.*)
+
+The lattice dissolved. Not with a snap or a crash — it just… stopped. The way a river stops when you place the dam: not dramatically, but completely. The magical structure that had been burning in my perception for two days faded to residue, then to nothing, and the dog was standing in the middle of a back room in a bookshop, blinking at the world without a filter for the first time in weeks.
+
+It looked at me. I held still.
+
+It looked at Mere.
+
+Its tail moved. Not a wag — not yet. A tentative, experimental motion, the canine equivalent of a question: *Is it safe? Is it actually safe?*
+
+Mere didn't move. She didn't call to it, didn't crouch down, didn't do any of the things people usually do when they want an animal to approach. She just stood there, being Mere — present, patient, smelling like three weeks of care.
+
+The dog crossed the room. Three steps, then a pause. Two more steps. Then it pushed its head against her hand, and Mere's fingers curled into the fur behind its ears, and the dog leaned into her with the full weight of an animal that had finally found the thing its nose had been promising was real.
+
+I sat on the floor with my back against the door frame and watched, and I did not examine what I was feeling, because what I was feeling was complicated and large and I was very, very tired.
+
+Mere looked at me over the dog's head. She didn't smile. She didn't say thank you. She said, "You used my salts."
+
+"They were the foundation. The whole approach was built on your work."
+
+She looked down at the dog, who was now pressing its entire body against her legs with the desperate, relieved affection of a creature that had spent weeks terrified and had finally, completely stopped.
+
+"Good," she said.
+
+It was the most Mere thing she could have said, and it was enough.
+
+* * *
+
+The letter arrived twenty minutes later, carried by a guild courier who looked mildly annoyed at having to locate a bookshop in the arcane district and who handed over the sealed envelope with the enthusiasm of a man delivering his fortieth message of the day.
+
+The seal was the Guild of Necessary Services — the small press, not the formal stamp, which meant internal communication rather than client-facing correspondence. I opened it standing at the counter while Mere sat on the floor with the dog, which had not left her side and showed no indication of planning to.
+
+The letter was four lines.
+
+*Mr. Varrant,*
+
+*Your application has been reviewed. Present yourself at 14 Greystone Lane on the 15th, ninth bell, for interview. Bring documentation of current employment and arcane licensing.*
+
+*— Administrative Office, Guild of Necessary Services*
+
+No warmth. No encouragement. No indication of whether "reviewed" meant "considered favorably" or "considered at all." Four lines of procedural efficiency, delivered without personality, conveying exactly the information necessary and nothing more.
+
+I appreciated this immensely.
+
+Seven weeks of silence, and then four lines on a Friday morning, arriving in a bookshop that smelled like binding salts and dog, while a woman I'd known for less than two weeks sat on the floor with an animal I'd just freed from a curse I'd broken by not sleeping and she'd cured by not giving up.
+
+Chess piece. Right square. The board looked different from here — not simpler, but clearer. The shack, the land, the house plans with the bedroom that had started feeling too small. The Guild, the interview, the ability I'd been calling a quirk that was actually a career. The woman on the floor who held my hand in the morning and said *good* like it meant *everything.*
+
+I folded the letter and put it in my pocket.
+
+"What is it?" Mere asked, not looking up from the dog.
+
+"Job interview," I said.
+
+"When?"
+
+"The fifteenth."
+
+She nodded, the same way she'd nodded when I'd said *tomorrow* — accepting the fact, filing it, moving on. "You should eat something before then. You still look terrible."
+
+"I know."
+
+"I can make tea. The shop has a kettle. It's not enchanted — just a kettle."
+
+"Tea would be good."
+
+She stood up, and the dog stood up with her, and the two of them walked to the front of the shop together while I stayed in the back room and did not think about hand-holding or bedroom measurements or the way a four-line letter could feel like the first page of something.
+
+I thought about tea instead. Tea was simpler.
+
+Nothing else was going to be simple for a very long time, and some part of me — the part that saw flaws, that found the cracks, that couldn't stop pulling things apart to understand how they worked — knew that the complicated version was better. Harder, more expensive, requiring tools and people and a willingness to need things I'd spent thirty years not needing.
+
+But better.
+
+The dog barked once from the front room — a real bark, the sound of an animal that had remembered what its voice was for — and Mere said something to it that I couldn't hear, and the kettle began to whistle, and I sat on the floor of a bookshop and let the afternoon be what it was.

chapters/book1/ch03-input.md

@@ -1,32 +1,65 @@
-# Chapter 03 Input — The Guild
+# Chapter 03 Input — Thursday
 
 ## Scene Goals
-- Phelan receives his Guild of Necessary Services results — he's accepted
-- Show the guild joining process: what it means, what it costs (dues he can barely afford), what it gives him access to (the network, safe houses, reputation, better-paying work)
-- Establish his goals now that he's in: more income, independence, ability to use his real skills instead of stocking shelves
-- Deepen Mere's family background: parents are divorced, mother hates the father (Devod Fields), Mere knows where her father lives but has no real connection to him at this point
-- The family revelation should come naturally — maybe Mere mentions it in passing, or Phelan pieces it together from something she says
-- Start transitioning from "life setup" chapters toward the case — by the end of ch3, the reader should feel the world is established and something is about to happen
+
+### Thursday — The Examination
+- Phelan meets Mere at her work to examine the cursed dog — this is the "Thursday" promised at the end of Ch02, the dog is in the back room of the shop.
+- Mere works at a Magical books seller, where people can buy small spell theories and existing grimwars.
+- First real demonstration of Flaw Sight in action — Phelan sees the curse's lattice structure from several feet away before even approaching the dog
+- The curse is a fear curse that overwrites the dog's visual perception (humans register as predators). The caster only hijacked vision — smell, hearing, and spatial awareness are untouched. Sloppy work disguised as clean work: they built a curse for a human brain and put it on a dog
+- Phelan needs time to figure out how to break the curse, so he asks for a day to prepare and ponder on the solution.
+
+### Thursday Night — The Brain Storm
+- Phelan has a long night of his brain going into hyperdrive trying to theorize different solutions to the curse. Triggers a migraine and he uses a little known herb to treat it. It works, but takes 2 hours for the migraine to end and it forces him to sleep.
+
+### Friday — The Fix
+- Phelan returns to Mere's shop looking terrible — exhausted, pale, visibly worn from the overnight brain storm. This is the first time Mere has seen him like this (in ch01 and ch02 he was fine)
+- Mere asks why he looks so bad. He gives partial honesty: explains the migraine and rough night, but does NOT mention the hyperfocus brain storm that caused it. Downplays it.
+- Mere's realization: he willingly went through pain to help her. No one has ever done anything like that for her before. This is the key emotional shift of the chapter.
+- Her response is not dramatic — she's taken aback but processes it her way. Practical comfort: water, a chair, making sure he's okay before they start. Then she holds his hand. First time she's initiated physical contact. She doesn't frame it, doesn't make eye contact about it — she just does it. This is Mere processing care through action: *I should do something. This is something.* It's enormous and neither of them will say so. Internal note to herself: she should try to help when he's like this. She doesn't like him feeling bad.
+- The tone of this beat is endearing, not melodramatic. She doesn't enjoy his pain but finds it meaningful that he'd bear it for her.
+- Phelan breaks the curse laterally — not by attacking it, but by amplifying the dog's scent processing using Mere's own binding salts as a base. The enhanced scent data floods conflicting information until the curse's internal logic collapses and it unravels from the inside
+- The curse-breaking goes smoothly. No post-exploit crash. The visible cost is entirely from the overnight brain storm — Mere sees what his *thinking* costs him, not what the fix costs. He shows up wrecked but performs flawlessly anyway, which makes the fix more impressive.
+- The dog's first act after the curse breaks is approaching Mere — her scent is the one it trusts most from weeks of care
+- Chapter closes with a guild letter arriving by carrier — they want an interview. This is the hook into Ch04
 
 ## Key Dialog
-<!-- Specific lines or exchanges you want included. -->
+
+### Thursday
+- Mere explains her binding salt / silverthorn approach in her characteristic flat, factual delivery — she's been managing symptoms, not curing the curse
+- Phelan's internal narration when he sees the flaw: the curse is "a wall built across one road while three other roads run wide open"
+- Phelan describes his plan to Mere in practical terms — boosting the scent channel to create contradictory data the curse can't sustain. He does NOT explain Flaw Sight directly, but the precision of his analysis is notable
+
+### Friday
+- Mere's question about his appearance — direct, characteristically blunt: why does he look like this? She's seen him twice before and he was fine both times.
+- Phelan's deflection — acknowledges the migraine and bad night, frames it as no big deal. He won't tell her about the hyperfocus episode because that would reveal too much about how his brain works.
+- The moment Mere connects the dots — he went through this *for her dog*. For *her*. Quiet beat. She doesn't say something grand; she processes it internally and responds with practical care, then holds his hand. The hand-holding is the response — action instead of words.
+- Phelan's narration should clock the hand-holding with devastating precision — her grip, the temperature of her fingers, the fact that she didn't look at him when she did it — and then immediately pivot to the curse work, because that's what he does with things that matter.
+- After the fix, Mere's reaction is layered: she saw him arrive wrecked, watched him perform flawlessly anyway, and saw the dog trust her. All three observations filed away without drama.
+- Phelan used Mere's own materials as the foundation — competence-recognizes-competence moment. She should register this.
 
 ## Character Moments
-- Phelan's reaction to being accepted: not celebration, not relief — more like a chess piece finally reaching the right square. Satisfaction at a plan working.
-- The guild's filtering system (the polite receptionist, the "eight-week waiting list" that doesn't exist) — Phelan appreciates this kind of structured misdirection
-- Mere's mention of her father should be offhand, almost dismissive — she doesn't have feelings about it because she hasn't had reason to. Yet.
-- If Jonael or Leon appear here, establish their dynamic with Phelan quickly — competence-based respect, not warmth
-- The financial pressure doesn't go away with guild membership — it gets worse short-term (dues, equipment, reputation-building before real cases come in). Phelan doing the math and not liking the answer.
+- This is the first time Phelan has worked on a curse with real stakes tied to someone's approval. Mere's opinion matters to him — something he hasn't experienced before. He files this observation and does not examine it
+- Mere sees two things on Friday: what his thinking costs him (the wrecked state he arrives in) and what his competence looks like (the flawless fix despite that state). Both observations noted without drama.
+- Mere's emotional beat — realizing no one has willingly gone through pain for her before — is the vulnerability moment of the chapter. It's her vulnerability, not his. He doesn't know the weight of what he's done. She does.
+- Her response to his state is practical care: water, a chair, checking he's okay — and then holding his hand. First initiated physical contact. This is how she processes care: action, not words. The hand-holding is the biggest relationship escalation in the chapter, and it happens without announcement or acknowledgment from either of them.
+- The dog approaching Mere after the curse breaks is the second emotional beat of the chapter — earned through her weeks of patient care, not through Phelan's fix
+- The guild letter at the end should hit Phelan as "chess piece reaching the right square" — satisfaction at a plan working, not celebration
 
 ## Mood / Tone
-- Forward momentum — things are finally moving for Phelan
-- But grounded by financial reality — every step forward costs money he doesn't have
-- The guild scenes should feel like entering a world that fits him better than the herbal shop ever did
-- Mere's family stuff is low-key, conversational — no drama, just information that the reader files away
+- **Thursday:** Quiet tension — Phelan approaching an unfamiliar animal, reading the curse, planning the approach. Investigation-mode energy.
+- **Thursday night:** Not shown directly, but its effects define Friday. The reader learns about it through Phelan's state and his partial explanation to Mere.
+- **Friday arrival:** The contrast between how Mere has seen Phelan before (competent, put-together) and how he looks now (wrecked, pale, exhausted). This contrast drives her question.
+- **Friday fix:** Technical precision — this should read like a skilled operator performing a procedure, not a wizard casting a spell. The curse unravels cleanly. No fireworks, no crash.
+- **Warm aftermath:** The dog approaching Mere is genuine warmth in a story that doesn't do warmth often. Earn it.
+- **The guild letter** shifts the energy forward — momentum, possibility, the next move
 
 ## Freeform Notes
-- The guild joining is Phelan stepping into his real life — the herbal shop was survival, this is purpose
-- Mere's divorced parents / absent father is pure setup for Devod Fields appearing later. Don't force it, just plant it
-- Consider: does Phelan quit the herbal shop, or keep it as a safety net? Keeping it adds ongoing financial tension. Quitting raises the stakes.
-- The "eight-week waiting list" receptionist could be a fun recurring character
-- By end of ch3, the reader should know: who Phelan is, what he wants, who Mere is, what the guild is, and be ready for the case to arrive
+- This chapter establishes Phelan's method for the reader: he doesn't overpower problems, he perceives where they're wrong and makes them destroy themselves. This sets up the triple chain in the main case
+- Mere's binding salts becoming part of the cure is thematically important — her symptom management was the foundation for his solution. Neither of them alone could have done it
+- The "noise" parentheticals should be active during the curse analysis — this is investigation-mode, where his ADD brain breathes and the tangents are often the key insight
+- Phelan sees the flaw BEFORE inspecting the dog — from several feet away. This is notable. He's always been aware of nearby magical flaws (can't turn it off), but the ease and distance here suggests the ability is stronger than he gives it credit for
+- The guild letter is a single-line or short note — formal, minimal. "Your application has been reviewed. Present yourself at [address] on [date] for interview." No warmth, no explanation. Phelan appreciates this kind of efficiency
+- Keep the dog scene grounded — no magical fireworks. The curse unravels quietly, from the inside. The most dramatic moment is the dog taking its first steps toward Mere
+- The two emotional beats are distinct: (1) Mere realizing someone willingly bore pain for her — this is about *her* emotional history, and (2) the dog choosing Mere — this is about earned trust through patient care. Both are quiet. Both land.
+- The chapter has two distinct cost moments that should NOT be confused: the overnight brain storm cost (visible on Friday, drives Mere's emotional beat) and the flawless execution (no cost — he's already paid it). This makes the fix more impressive and keeps the vulnerability beat focused on what his *thinking* costs, not what his magic costs.

chapters/book1/ch04-draft.md

@@ -0,0 +1,235 @@
+# Chapter 4: The Interview
+
+Fourteen Greystone Lane was the kind of building that didn't want to be found. Not hidden — hiding implied effort, implied someone had something to conceal and was worried about it. This was quieter than that. The building simply declined to be memorable. Sandstone facade, clean but not polished. Two stories, narrow frontage, wedged between a solicitor's office and a cartographer's workshop. The sign — small, brass, unadorned — read "Guild of Necessary Services" in lettering that communicated exactly nothing about what happened inside and everything about the kind of people who'd chosen it.
+
+(*Ward work on the door frame — subtle. Detection array, not defensive. Keyed to identify, not exclude. Three-layer inscription, professionally maintained, recently re-calibrated. The windows had secondary wards behind the glass — passive monitoring, recording foot traffic patterns. Someone was counting who walked past, how often, and whether they slowed down. The whole building was a net dressed up as a wall.*)
+
+I appreciated this. Security architecture that looked like nothing was, in my experience, the only kind worth having. The loud kind — heavy wards, visible glyphs, guards at the door — announced that something valuable was inside and dared people to try. The quiet kind made you walk past without wondering. I'd walked past this building six times in the three years I'd lived in Drenwick and never once looked twice. That was professional work.
+
+I pushed open the door at quarter to nine. The interior matched the exterior's commitment to aggressive unremarkability — a small reception area with two chairs, a desk, and a woman behind it who looked up with the practiced warmth of someone who had been trained to make visitors feel welcome and then leave.
+
+"Good morning," she said. "Can I help you?"
+
+"Phelan Varrant. I have an appointment at ninth bell."
+
+She consulted a ledger that I suspected contained nothing of substance. "Ah — Mr. Varrant. Yes, I see your name here. Unfortunately, we're currently running an eight-week waiting list for new consultations. I can schedule you for—"
+
+"I received a letter," I said. "Instructing me to present myself today. For interview."
+
+She looked at me. The warmth didn't change — it was too well-crafted for that — but something behind it shifted. A gear engaging. She'd been running a script, and I'd given the response that moved her to the next page.
+
+"Of course," she said, as though the waiting list had never existed. "Down the hall, second door on the left. They're expecting you."
+
+The transition was seamless. No acknowledgment of the fiction, no wink, no shared understanding that she'd just tested whether I'd accept a polite dismissal or push past it. She simply redirected, the way a canal lock redirects water — smoothly, mechanically, without apology for having been in the way.
+
+I walked down the hall and did not look back, because looking back would have signaled uncertainty, and I was not uncertain. I was, if anything, more certain than I'd been walking in. Any organization that filtered its visitors through a receptionist who could lie that convincingly and pivot that cleanly was an organization that understood operational security at a level I respected.
+
+The second door on the left was closed. I knocked once.
+
+"Enter."
+
+* * *
+
+The room had been designed to make people uncomfortable, and it was very good at its job.
+
+A table. Three chairs behind it, occupied. One chair in front of it, empty. Nothing else. No windows — the walls were bare stone, clean but unfinished, the kind of surface that absorbed sound and returned nothing. The lighting came from two bracketed oil lamps that had been positioned to illuminate the empty chair while leaving the three men behind the table in relative shadow. It was a deposition chamber. It was a confessional. It was the architectural equivalent of being told to sit down and explain yourself.
+
+I sat down. I did not explain myself.
+
+The three men were distinct in the way that parts of a machine are distinct — different functions, same mechanism. The man in the center chair was the one who mattered. I knew this before he spoke, before he moved, before he did anything other than exist in his chair with the particular stillness of a person who had learned that authority didn't require performance. He was perhaps fifty, lean, with close-cropped gray hair and eyes that assessed without appearing to. His hands were folded on the table. He hadn't looked at the door when I entered. He'd been looking at me before I walked in — not physically, but in the way that mattered. He'd read my file. He knew things.
+
+The man to his left was the questioner — I could tell by the sheaf of papers in front of him and the particular posture of someone who had a list and intended to get through it. Younger than the center man, broader, with the methodical energy of a person who believed in process. He had a pen. The pen was already inked.
+
+The man to the right was the observer. He had nothing in front of him — no papers, no pen, no visible purpose beyond being present. He sat back slightly in his chair, arms crossed, watching me with the patient attention of someone whose entire job was to notice what the other two missed. I noted him, respected the role, and filed him as the most dangerous person in the room.
+
+"Mr. Varrant," said the center man. His voice matched his posture — quiet, unhurried, expecting to be heard without raising the volume. "Thank you for coming."
+
+"Thank you for the invitation. It was... concise."
+
+The corner of his mouth moved. Not a smile. An acknowledgment.
+
+The questioner opened. "Your application states you've been practicing magic since age twelve. Is that accurate?"
+
+"Yes."
+
+"Licensed at sixteen. Standard certification through the Arcane Compact's educational track. Attended Brannick's Academy for four years, withdrew before completion. Is that correct?"
+
+"Withdrew" was generous. I'd left because I'd learned everything the instructors could teach me by year three and spent year four irritating them by pointing out inefficiencies in their methods. But "withdrew" was what the records said, and I wasn't going to argue with records that made me sound more dignified than the reality warranted.
+
+"That's correct."
+
+"Current employment: Gavren's Botanical and Sundry. Herbal supply and licensed magical components. Three years." He looked up from his notes. "You're overqualified for that position."
+
+"The position pays."
+
+"Not well."
+
+"No," I agreed. "Not well."
+
+The questioner made a note. The observer said nothing. The center man watched me the way Mere watched things — systematically, cataloguing, running an assessment that wouldn't be shared until it was complete.
+
+"Your application lists your magical specialty as 'structural analysis of arcane workings.'" The questioner read this from the page with the careful neutrality of someone quoting someone else's words. "Can you elaborate?"
+
+"I examine how magical workings are built. Their architecture — the anchoring, the channeling, the logic of the intent-binding. When a working has flaws, I can identify them."
+
+"Flaws," the questioner repeated.
+
+"Inefficiencies. Gaps. Points where the structure doesn't hold together as well as the caster intended."
+
+"And what do you do with these flaws, once identified?"
+
+"Depends on the job."
+
+The questioner waited. I did not elaborate. There was a particular kind of silence that functioned as a question, and I'd learned years ago that the correct response was to let it sit there, unanswered, until the other person decided whether to push or move on. The questioner pushed.
+
+"Could you give an example?"
+
+"I noticed a preservation ward at my current employer's shop was degrading due to a resonance gap between the second and third anchors. Moisture was seeping through. I moved the product to a drier shelf to slow the decay."
+
+"That's a rather modest example for someone applying to this guild."
+
+"You asked for an example. You didn't specify the scale."
+
+The observer made a sound. It might have been a cough. It might have been something else.
+
+The questioner continued through his list. How long had I lived in Drenwick? Three years. Prior residence? Caldburn, small town, nothing notable. Family? Mother, living, no contact. Father? None. Current associations? Gavren Holst, employer. Mere Fields, acquaintance. The questions were precise, procedural, and revealed — with each answer I gave — that they already knew the answers. They weren't gathering information. They were confirming it. Checking my responses against a file they'd been building since my application arrived, and probably before.
+
+"Do you have any combat magic training?" the questioner asked, turning a page.
+
+"Basic defensive work. Standard curriculum from Brannick's."
+
+This was a lie. Not a large one — the kind of lie that lived in the gap between what was true and what was safe to share. I'd learned fire magic as a child, practiced it obsessively, combined it with physical fighting in ways that most mages never attempted. But combat magic was a flag — it drew attention, raised questions about temperament and intent, and invited the kind of scrutiny that a man applying to a guild whose sign was deliberately small did not need.
+
+The observer's eyes moved. A fractional shift — not toward me, not away. A recalibration. I couldn't tell if he'd caught the lie or simply noted the pause before my answer. Either way, the moment passed. The questioner moved on.
+
+I was seventeen minutes into the interview — I'd been counting, because my brain counted things whether I wanted it to or not — when the door on the left opened and a man entered.
+
+He was short, unremarkable, dressed in the kind of clothes that said "administrative staff" the way a uniform said "soldier." He crossed to the center man, leaned down, and whispered something. The whisper lasted four seconds. The center man's expression did not change.
+
+(*Staged or genuine? The timing was precise — deep enough into the interview to feel natural, early enough to redirect. The whisperer entered from the left, not from the hall. Internal door. Staff access. Either the interruption was planned to test my reaction, or their intelligence network had produced something they wanted to act on immediately. Both options meant the same thing: they were watching me, and they were watching me now.*)
+
+The center man looked at me directly for the first time. Until now, his attention had been ambient — present but unfocused, the way a lantern illuminates a room without pointing at anything. Now it pointed.
+
+"Mr. Varrant," he said. "We understand you recently resolved a situation involving a cursed animal. A dog, specifically, belonging to a Miss Fields."
+
+I kept my expression neutral, which required more effort than it should have. The dog curse had been broken four days ago. In a private back room. In a bookshop that did not advertise its owner's side projects. The fact that these men knew about it meant their network was faster and more thorough than I'd estimated, and I'd estimated generously.
+
+"I did," I said.
+
+"The curse was a fear working. Anchored to the visual processing channel. Resistant to standard removal techniques." He said this without consulting notes. He'd memorized it, or he'd been briefed minutes ago and had a memory built for retention. "Two individuals with relevant experience had assessed the animal prior to your involvement and concluded the curse was not removable without risking the animal's life."
+
+I hadn't known that. Mere hadn't mentioned other people trying. I filed this and said nothing.
+
+"How did you break it?"
+
+The question landed in the room the way a stone lands in still water — quietly, with effects that spread. The questioner's pen stopped moving. The observer leaned forward, marginally, the first voluntary motion I'd seen from him. The center man waited with the patience of someone who understood that this question was the interview, and everything before it had been furniture.
+
+I had spent my entire adult life not answering this question. Not because anyone had asked — no one had ever been in a position to ask, because I'd never done anything visible enough to prompt it. I'd moved ward-jars to higher shelves. I'd noticed chisel slips in kettle inscriptions. I'd seen flaws and worked around them quietly, calling it instinct or training or "some background," and the world had accepted these explanations because the world was not paying close enough attention to demand better ones.
+
+These men were paying attention.
+
+"The curse was designed for a human perceptual framework," I said. "Applied to a canine subject. The caster anchored the fear response to the visual channel — which dominates in humans but doesn't in dogs. The animal's other senses — scent, primarily — were unaffected. I amplified the competing sensory input until the curse's internal logic couldn't sustain itself. It collapsed under its own contradictions."
+
+"You identified the architectural mismatch," the center man said. "Between the curse's design assumptions and the target's actual sensory hierarchy."
+
+"Yes."
+
+"How?"
+
+There it was. The second question behind the first. Not *what did you do* but *how did you see it.* The question I'd been avoiding since I was fourteen years old and realized that the river running underneath everything wasn't normal, wasn't common, wasn't something other people had and simply didn't mention.
+
+I looked at the three men behind the table. The questioner with his notes. The observer with his silence. The center man with his quiet authority and his question that cut to the bone of what I was.
+
+"I see problems in workings," I said. "Structural weaknesses. Gaps in the logic, flaws in the anchoring, places where the architecture doesn't hold. When I focus on an active working, I can perceive its structure — where it's strong, where it's not. I used that to identify the mismatch and design an intervention that exploited it."
+
+It was the most I'd ever said about it out loud. It was also the least — a headline, not an article. I hadn't mentioned the lattice. I hadn't mentioned that I'd seen the curse's full architecture from twelve feet away, in a doorway, without examining the dog. I hadn't mentioned that the perception was constant, involuntary, and sometimes so loud it gave me migraines that made me reconsider my relationship with consciousness.
+
+I'd given them enough to understand what I could do. Not enough to understand what I was.
+
+The three men exchanged a look. It was brief — the kind of look that communicated volumes between people who'd been working together long enough to have developed a private shorthand. The observer nodded, once, almost imperceptibly. The questioner set down his pen.
+
+The center man smiled.
+
+It was a small smile, contained, professional — but genuine in a way that surprised me. Not impressed. Not amazed. *Satisfied.* The way a person smiles when a piece they've been watching falls into place exactly where they expected it to land.
+
+"Mr. Varrant," he said. "Every member of this guild has something that sets them apart. A skill, a perception, a capability that doesn't fit neatly into the Compact's registry of licensed specialties. We don't ask our members to explain these gifts in full. We ask them to demonstrate discretion about what they share, with whom, and when." He paused. "You've just demonstrated exactly that."
+
+I understood. The question hadn't been about my ability. It had been about my judgment — how much I'd reveal when asked directly, by people in a position of authority, in a room designed to make honesty feel like the only option. I'd given them the truth without giving them the whole truth, and that was the answer they'd wanted.
+
+"Welcome to the Guild of Necessary Services," he said.
+
+* * *
+
+The acceptance was procedural, which suited me perfectly.
+
+The questioner produced a bound document — not a booklet, exactly, but a collection of pages stitched together with the particular care of something that had been reproduced many times by hand and was expected to be kept. The cover page read, in the same understated lettering as the building's sign: *Guild of Necessary Services — Member Code and Operating Standards.*
+
+"Read this thoroughly," the questioner said. "You'll be expected to know it."
+
+I took it with me to the reception area, sat in one of the two chairs, and read it while the receptionist pretended I wasn't there with the same effortless professionalism she'd applied to pretending the waiting list existed.
+
+The rules were straightforward, which I respected, and ruthless in their simplicity, which I respected more.
+
+*Rule One: Never betray a client who has engaged your services in good faith.* No caveats, no exceptions. If someone paid and played straight, you delivered. Full stop.
+
+*Rule Two: Never work both sides of the same engagement.* If two parties in a dispute both approached the guild, one of them got turned away. No playing the middle. No hedging.
+
+*Rule Three: Do not create problems that fall on other members.* Your mess was your mess. If your work made another member's life harder — drew attention to the guild, compromised a cover, burned a contact — you answered for it. The guild's reputation was a shared asset, and damaging it was treated accordingly.
+
+*Rule Four: Everything not covered by Rules One through Three is judgment.*
+
+I read Rule Four twice. It was the most elegant piece of organizational philosophy I'd ever encountered — a single sentence that simultaneously granted enormous operational freedom and placed the entire weight of responsibility on the individual member. No detailed guidelines for edge cases. No decision trees. No approved-methods list. Just: *use your judgment, and be prepared to defend it.*
+
+(*Most organizations buried you in rules because they didn't trust your judgment. This one gave you four rules and trusted you to fill in the rest. Either they were remarkably confident in their selection process, or they were remarkably efficient at removing members who filled in the blanks wrong. Probably both.*)
+
+The remaining pages covered operational details. The guild took twenty percent of all job commissions — this funded the retainer system, safe houses, the information network, and administrative costs. Members received a monthly retainer salary scaled to guild rank. In exchange, members were expected to complete a minimum of two engagements per quarter. Fall below that, lose rank. Lowest-ranked members who consistently underperformed were released. Equipment was your own responsibility, but the guild maintained a lending inventory for specialized jobs. Case reports were mandatory within seventy-two hours of engagement completion — brief, factual, filed with the administrative office.
+
+The final clause was the one with teeth: *The guild protects its members. This protection is contingent on members protecting the guild. Disclosure of guild operations, membership, methods, or client information to any external party — including the Arcane Compact, municipal authorities, or other guilds — constitutes grounds for immediate expulsion and recovery of all guild-provided resources.*
+
+Recovery. I noted the word choice. Not "return." *Recovery.* The distinction implied that the guild would come and get its things, whether you offered them or not.
+
+I closed the document and sat with it for a moment, feeling the weight of it — not physical weight, but the weight of having found something that fit. The rules aligned with my own code in ways that felt less like coincidence and more like recognition. I'd been operating by these principles for years, alone, without a framework. Now there was a framework. Now there were people who operated the same way, and they'd just told me I was one of them.
+
+The receptionist looked up. "All finished?"
+
+"Yes."
+
+She opened a drawer, produced a small leather pouch, and set it on the desk. "Your first month's retainer. Starting salary for Tier One — fifteen silvers."
+
+I picked up the pouch. It had the particular weight of coins — dense, compact, real in a way that coppers never quite managed. Fifteen silvers. More money than I'd held at one time in — I ran the calculation and stopped, because the answer was depressing and I didn't want to revisit it on what was, by any reasonable measure, a good day.
+
+"Your point of contact will reach out within two weeks regarding your first engagement," she said. "In the meantime, we recommend settling any outstanding obligations with your current employer. The guild prefers its members to be available without encumbrances."
+
+"Understood."
+
+She smiled — the warm, practiced smile of the filtering system, the polite dismissal mechanism, the first test I'd passed on my way in. But there was something else in it now. Something that hadn't been there forty-five minutes ago. Not warmth, exactly. Recognition.
+
+"Welcome, Mr. Varrant."
+
+* * *
+
+I walked out of 14 Greystone Lane with fifteen silvers in my pocket and a document that told me, in clear and simple language, that I belonged somewhere.
+
+The morning was bright. Drenwick looked the same as it always did — river traffic, foot traffic, the smell of fish and forge smoke and the particular urban perfume of too many people in too small a space. Nothing had changed. The city hadn't rearranged itself to mark the occasion. The cobblestones under my feet were the same cobblestones I'd walked over this morning on my way to an interview, and they'd be the same cobblestones tomorrow.
+
+But the math was different.
+
+(*Fifteen silvers. Minus rent — two silvers a month, and the landlord's agent would probably faint from shock at receiving payment that wasn't in coppers. Minus food — a silver and a half if I ate properly, which I should probably start doing. Minus incidentals — call it a silver. That left ten and a half. But next month there'd be another fifteen, and the month after that, and job commissions on top. Even at the base rate, even at Tier One, even with the guild's twenty percent cut — the arithmetic was different now. Thirteen hundred silvers for the house. Divide by eight silvers a month in savings. A hundred and sixty months. Thirteen years. Not forty. Thirteen years was still a long time, but thirteen years was a number you could hold without it crushing you. Thirteen years was a plan, not a fantasy.*)
+
+I walked south along the quay, past the chandler's, past the net-mender's, through the gap in the old customs wall. The same route I walked every day, but the familiar geography felt different with fifteen silvers in my pocket and a two-week window before my first real job. Two weeks to give Gavren his notice. Two weeks to wrap up the life that had been a holding pattern and step into the one I'd been applying for.
+
+The shack was the same as always — one room, river sounds, the drawings on the table. I set the leather pouch down next to the house plans and stood there for a moment, looking at both.
+
+Nine revisions. Five rooms. A workshop with ventilation and warding anchors. A main room. A kitchen. A bathroom. A bedroom that had started feeling too small for reasons I still wasn't ready to examine.
+
+Thirteen years. Give or take.
+
+I picked up a pencil — not to revise, not today. Just to hold it. To feel the weight of a tool that was connected to a plan that was connected to a future that had, as of forty-five minutes ago, become marginally less impossible.
+
+The guild had a job for me. Something specific, something they'd had in mind before I'd walked through the door. Two weeks. That was enough time to give Gavren his notice, stock the feverwort one last time, and sit in the shack with the drawings and the fifteen silvers and the quiet knowledge that the next page of something had started, whether I'd intended to turn it or not.
+
+I put the pencil down. I ate a meal that, for the first time in recent memory, did not require creative arithmetic to justify. Bread, cheese, an apple, and — extravagantly — a strip of dried meat from the vendor by the canal bridge, purchased on the walk home with the reckless confidence of a man who had ten and a half silvers in reserve and a monthly income.
+
+The river did what it always did. The shack was still a shack. The plans were still plans.
+
+But the distance between where I was and where I was going had just gotten shorter, and for a man who measured everything, that was enough.

chapters/book1/ch04-input.md

@@ -1,27 +1,50 @@
-# Chapter 04 Input — The Case Arrives
+# Chapter 04 Input — The Interview
 
 ## Scene Goals
-- Transition from life-establishment into the main plot: the Unbreakable Curse case
-- A client arrives through proper Guild channels with a dying family member — Ned Floundry, cursed with a working considered impossible to break by the Arcane Compact
-- Two registered curse-breakers have already failed. The client is desperate enough to hire "Necessary Services"
-- Phelan takes the case because the fee is significant and the problem is interesting. In that order.
-- First real demonstration of Phelan as a professional — how he takes a case, how he interviews a client, how his mind works when given a real problem
-- End with Phelan committed to the case and the reader understanding the stakes (dying person, ticking clock, "impossible" problem)
+- Phelan arrives at the Guild of Necessary Services for his interview
+- The filtering system is on display: the polite receptionist, the "eight-week waiting list" that doesn't exist. Phelan appreciates this structured misdirection — he recognizes the security architecture
+- The interview room: three men seated behind a table, a single chair for Phelan as though he's on trial. Nothing else in the room. Deliberately austere
+- The panel asks confirming questions — how long he's had the ability to use magic, how long he went to school, questions about his current life that reveal they've been watching him closely since his application
+- The panel asks about attack magic usage - which Phelan lies about, some secrets are best held back.
+- Mid-interview interruption: a man enters from the left, whispers something to the middle chair (who is clearly the highest-ranking). They ask about the dog curse — confirming they've been following him
+- Phelan asks what specifically about the dog case they want to know. The lead man: "How did you break it?"
+- Phelan's quandary: he's never told anyone about Flaw Sight. Decides it's now or never. Gives a loose explanation — "I just see problems in the workings, and use them to my advantage." Not the full truth, but enough
+- They recognize the talent. Accept his application. Explain: pay is per job plus a retainer salary based on guild rank. They have a first job in mind — specifics in about two weeks, so he has time to adjust and wrap up his current employment. 
+- Phelan receives a copy of the guild rules — the reader learns the rules of the guild here
+- Phelan gets his first month's salary from the receptionist on the way out — 15 silvers. Starting retainer for the lowest guild rank. For a man who's been counting coppers, this is a different world. His brain immediately runs the math: fifteen minus rent, minus dues, minus food — seven or eight left over. Thirteen hundred divided by eight. A hundred and sixty months. Thirteen years instead of forty. The house timeline just changed from impossible to merely improbable
+- Chapter ends with Phelan walking out a guild member — not celebratory, but satisfied. A plan that worked
 
 ## Key Dialog
-<!-- Specific lines or exchanges you want included. -->
+- Receptionist interaction should be brief and polished — the "eight-week waiting list" delivered with practiced sincerity. Phelan sees through it immediately and respects the craft
+- Panel questions should feel like a deposition — precise, professional, slightly uncomfortable. They know things about him they shouldn't unless they'd been watching
+- The lead man's "How did you break it?" should land as the pivotal moment — quiet, direct, the question Phelan has been avoiding his entire life
+- Phelan's loose explanation of Flaw Sight: not a speech, not a confession. A careful, minimal disclosure. "I see problems in the workings." Let them infer the rest. The panel smiles at this answer. They are well aware guild members have special gifts, all of them do. This was a test to see how much information Phalen gave out when randomly asked. It points to the fact this is a rather secret org with many secrets to hide. They like members who know how to give just enough to get by without spilling the beans.
+- Guild rules delivery should be procedural — someone hands him a document or booklet. The rules themselves should reflect the Guild's character: practical, no-nonsense, secrets with teeth
 
 ## Character Moments
-- Phelan's shift from day-job mode to professional mode — a different gear entirely. More focused, more precise, slightly intimidating
-- The client should be sympathetic but also slightly manipulative (or at least strategic) — they found Phelan for a reason
-- Phelan's reaction to the curse being "unbreakable" — not skepticism exactly, more like a programmer hearing "it can't be done." His brain is already looking for the flaw before he's agreed to anything.
+- Phelan reading the room: cataloguing the three men (posture, authority dynamics, who defers to whom), the room design (deliberate austerity as a power move), the interruption (staged or genuine?)
+- The moment of decision about revealing Flaw Sight is internal and quiet — not agonized, but weighted. He's kept this secret his entire life. The guild is the first structure that might actually deserve to know, if only just a little.
+- Phelan's reaction to acceptance: not celebration, not relief. A chess piece reaching the right square. Satisfaction at a plan working
+- The guild filtering system (receptionist, waiting list, surveillance) — Phelan doesn't resent being watched. He respects competent tradecraft. He'd have done the same thing
+- Financial note: the retainer salary plus per-job pay changes his math. Not enough to build the house, but enough to stop counting coppers. This matters
 
 ## Mood / Tone
-- Shift in energy from the first three chapters — the story is starting now
-- Professional, measured tension — not action, but the quiet intensity of someone assessing a problem
-- The ticking clock (weeks to live) creates urgency without requiring immediate action
+- Controlled tension throughout — Phelan is being evaluated, and he knows it. He's also evaluating them
+- Professional, measured — this is two competent parties sizing each other up
+- The Flaw Sight disclosure moment should feel like a door opening — not dramatic, but significant. The first time he's said that much out loud to anyone
+- Relief that isn't relief — Phelan doesn't do relief. He does "the next step." Walking out as a guild member is the next step
+- Forward momentum — Ch04 should leave the reader feeling that the story has shifted gears
 
 ## Freeform Notes
-- This maps to Milestone Beat #2 from the Book 1 outline: "Case introduction — client arrives, stakes established"
-- The fee should be enough to matter to Phelan's land/house goal — making this personal as well as professional
-- Consider whether Mere has any connection to or opinion about the case — even if just "that sounds dangerous" from someone who doesn't say things she doesn't mean
+- The guild rules need to be established here for the reader. Key rules to include:
+  - Never burn a client who paid in good faith
+  - Never work both sides of the same job
+  - Don't make messes that land on other members
+  - Everything else is judgment
+  - Additional rules: the guild takes 20% of the job commission as their cut. Equipment expectations, case reporting, the understanding that the guild protects its members but only if members protect the guild's reputation.
+  - The guild always takes a cut of the job payment as part of it's Dues. This allows them to give a retainer salary to all members, with the understanding that guild members must do two jobs per quarter year, or they loose rank with the guild. Lowest ranked members will be cut.
+- The three interviewers should have distinct presences even if not fully named — the lead (authority, quiet), the questioner (thorough, procedural), and the observer (silent, watchful). They can be developed more fully later
+- The man who enters with the dog-curse intel is a nice structural detail — it shows the guild's information network is active and fast
+- Phelan's "loose" explanation of Flaw Sight should be enough to intrigue but not enough to fully expose. He's giving them the headline, not the article. This protects him while still being honest enough to pass their scrutiny
+- The "noise" parentheticals should be active during the interview — Phelan is processing fast, reading the room, cataloguing details. The tangents here are cold-read data intake and speculation.
+- The lead interviewer doesn't exactly know what the ability Phelan has is, just that no one else has it. — they recognize rare talent without knowing exactly what they're looking at.

chapters/book1/ch05-input.md

@@ -0,0 +1,36 @@
+# Chapter 05 Input — Two Weeks
+
+## Scene Goals
+- Phelan resigns from Gavren's herbal shop — gives the two weeks' notice he promised in Ch01. Gavren is unsurprised (he called it). This should be a small, earned moment between two people who respect each other without warmth
+- Leon D'Nardis is introduced — Phelan goes to him to talk about the dog curse break and the guild acceptance. This is the first time the reader meets Leon
+- Phelan and Leon riff on the curse break — Phelan is genuinely eager to discuss the technical details. This is the kind of conversation both of them find interesting. Leon chains off the idea and describes a similar case: he found an expensive item in a tomb locked by a ward, and discovered that flooding the ward with a huge volume of inputs caused it to overload and crash, letting him remove the item. Ward-overload as a brute-force cousin to Phelan's precision approach
+- The two weeks compress — montage-style pacing. Phelan wraps up at the shop, adjusts to guild membership, prepares mentally
+- First job details arrive at the end — the specifics of the dungeon herb retrieval. This is the hook into Ch06
+
+## Key Dialog
+- Gavren resignation scene: callback to Ch01 where Gavren said "give me two weeks." Phelan honoring that promise. Keep it short, professional, with an undercurrent of mutual respect
+- Leon conversation is the centerpiece — two ADD brains riffing off each other. One feeds the other. Fast, tangential, occasionally brilliant. Leon's ward-overload story should feel like a parallel approach to Phelan's lateral thinking — similar philosophy (exploit the system's own logic), different method (brute force vs. precision)
+- Leon and Phelan should share hacks and tips naturally — this is how their friendship works. Transactional, intellectually stimulating, built on mutual trust
+- The job details at the end should be delivered through guild channels — a formal brief, probably delivered by messenger or available at the guild office. Minimal detail in this chapter — just enough to set up Ch06
+
+## Character Moments
+- Gavren's farewell: he knew Phelan was "passing through" (established in Ch01). The resignation confirms it. Gavren should handle it with the same mechanical precision he handles everything. Maybe a small, unexpected gesture — nothing sentimental, something practical
+- Leon's introduction should establish his core dynamic with Phelan immediately: transactional trust, shared ADD, intellectual kinship. They don't do warmth. They do interesting
+- Leon's ward-overload story reveals his character — he's a tomb-raider / treasure-hunter type, morally gray, practically skilled. He found an exploit through persistence rather than perception. His method works but it's loud and risky. Phelan's is quiet and precise. They respect each other's approaches
+- The two-week compression should show Phelan's state: anticipation masked as routine. He's waiting for the job the way he waits for everything — by being productive about something else
+- Financial update: the guild retainer has started. Not transformative, but the math is different now. Coppers becoming silvers
+
+## Mood / Tone
+- Transitional energy — the story is shifting from setup to mission. This chapter is the hinge
+- The Gavren scene should feel like a quiet goodbye — not emotional, but resonant
+- The Leon scene should be energetic, fast-paced — two smart people enjoying each other's brains. The most "fun" this book has been so far
+- The compression section should feel like time moving — not rushed, but purposeful. Days sliding past
+- The job details arriving at the end should shift the energy to anticipation — what's next
+
+## Freeform Notes
+- Leon's personality: has ADD but not as severe as Phelan's. Relationship is transactional — they help each other, they trust each other. They riff off each other's thoughts, one feeds the other. Occasionally Leon supplies the "nugget" that triggers Phelan's brain to click
+- Leon's ward-overload story is important setup — it introduces the concept of input flooding as a magical exploit technique. Different from Phelan's flaw-based approach but from the same family of thinking. This gives the reader a sense that Phelan isn't the only clever person in Corvel, which makes his specific ability more interesting, not less
+- The two-week compression is a pacing tool — we don't need to see every day. Hit the beats: resignation effective, last day at the shop, adjusting to guild rhythms, first retainer payment, the job arriving
+- Consider: does Phelan tell Leon about Flaw Sight directly? Probably not the full extent — Leon knows Phelan is unusually good at reading magical workings, but may not know it's a distinct perceptual ability. The conversation works either way
+- The job brief at the end: rare herb, old dungeon. Keep it minimal here — the full briefing happens in Ch06. Just enough to establish the mission type and raise Phelan's interest
+- "The noise" should be active during the Leon conversation — this is where the ADD brain format shines. Two people whose parenthetical tangents actually land in the conversation

chapters/book1/ch06-input.md

@@ -0,0 +1,37 @@
+# Chapter 06 Input — Preparation
+
+## Scene Goals
+- Full job briefing: the guild needs a rare herb that only grows in the deep chambers of an old dungeon outside Drenwick. Dungeons in Corvel often hold magical artifacts and rare monster materials used for thousands of magical applications. Phelan has heard of these places but never explored one
+- Phelan's fire and earth combat magic is established through equipment preparation — he's dusting off skills he hasn't used since school. Fire is his strong element, earth is serviceable but weaker. This is presented as a dormant skill resurfacing out of necessity, not a dramatic reveal
+- Context for combat magic: mages are common in Corvel (~20% of population can use magic), so being a mage isn't special. What's rare is combining melee combat skills with spell casting — most mages only know spells. Phelan learned both as a child due to bullying. Kept quiet since leaving school
+- Jonael Carterson is introduced naturally through equipment/supply preparation. He's a practical contact — someone Phelan goes to for gear, information, or logistics
+- Phelan departs Drenwick and travels to the dungeon exterior
+- Chapter closes with Phelan arriving at the dungeon entrance — Flaw Sight immediately reads the old wardwork protecting the entrance, and it's riddled with flaws. Centuries of decay, magical entropy, overlapping workings from different eras. The door is locked, but the lock is full of cracks
+
+## Key Dialog
+- Job briefing should be professional and specific — what the herb is, why it's valuable, where it grows, what's known about the dungeon's defenses. The guild doesn't send people in blind
+- Phelan's internal narration during fire magic prep should be nostalgic-practical — remembering the skills he learned as a bullied kid, assessing what's still sharp and what needs warming up. No sentimentality, just inventory
+- Jonael introduction: competence-based respect, not warmth. He's the kind of person who knows what you need before you finish asking. Phelan finds this efficient and slightly unsettling (usually he's the one reading people)
+- At the dungeon exterior, Phelan's Flaw Sight description should be vivid — the old wardwork as a decaying lattice, centuries of magical sediment, flaws everywhere. Beautiful in its decay, like reading archaeological strata
+
+## Character Moments
+- The fire magic backstory: Phelan learned to fight because he was bullied. He doesn't frame this as trauma — it's a fact that produced a useful skill. The combination of melee and magic is something he's been sitting on because he hasn't needed it. Now he does
+- Jonael's introduction should establish him as the "straight man" — drawn into Phelan's orbit by professional necessity, competent, possibly exasperated by Phelan's manner but respecting his skills. Their dynamic is efficiency-based
+- Phelan preparing for the dungeon should show a different gear — methodical, physical, practical. He's checking weapons, testing fire runes, stretching muscles he hasn't used in years. The reader should see that Phelan is not just a cerebral operator
+- The arrival at the dungeon should shift Phelan's energy — this is new territory. He's heard about dungeons, read about them, but never stood at the mouth of one. A mix of professional assessment and genuine curiosity
+- Flaw Sight at the dungeon entrance is the chapter's strongest image — ancient wardwork decaying like an old fortress, flaws everywhere, but also a sense of craftsmanship underneath. Whoever built these wards was skilled. Time and entropy are what made them vulnerable
+
+## Mood / Tone
+- Preparation scenes: methodical, grounded, slightly tense — the practical reality of walking into danger
+- Fire magic flashback: matter-of-fact. Phelan doesn't do origin-story drama. He was bullied, he learned to fight, he got good at it, he stopped needing it. End of story
+- Travel: brief, atmospheric — Drenwick fading behind, the landscape changing as he approaches the dungeon's region
+- Dungeon arrival: awe suppressed by professionalism. The dungeon is old, imposing, magical. Phelan catalogs it like a job site. But underneath the catalog, there's wonder — he's never seen magical infrastructure this old
+- Closing beat: anticipation. The wards are full of flaws. He can get in. The question is what's inside
+
+## Freeform Notes
+- The fire/earth magic needs to feel like a real skill with real limits — not a superpower, not a cheat. Fire is strong because he practiced it obsessively as a kid. Earth is weaker because he only learned enough to be functional. Neither replaces Flaw Sight as his primary tool — they're survival skills for an environment where perception alone won't keep him alive
+- Melee + magic combo being rare is important worldbuilding — most mages are specialists who stand back and cast. Phelan can fight in close quarters while maintaining spell work. This makes him unusual in combat situations, which pays off in Ch07
+- Jonael doesn't need a full introduction here — just enough to establish his presence, competence, and dynamic with Phelan. He can be developed further in later chapters
+- The dungeon should feel ancient — not just old, but layered. Multiple eras of magical work stacked on top of each other. This is interesting to Phelan both professionally and intellectually
+- The herb itself should be specific enough to feel real — give it a name, properties, reason for growing in dark magical environments. It's not a generic "rare ingredient" — it's a specific thing the guild needs for a specific purpose
+- "The noise" should be active during equipment prep (cataloguing, planning, tangents about fire magic theory) and especially at the dungeon entrance (Flaw Sight data intake, processing the ward architecture, involuntary fascination with the ancient workings)

chapters/book1/ch07-input.md

@@ -0,0 +1,36 @@
+# Chapter 07 Input — The Dungeon
+
+## Scene Goals
+- Phelan enters the dungeon by exploiting the decayed ward system — threading through the flaws he identified in Ch06's closing. This is a practical demonstration of his "thread through" technique on ancient infrastructure
+- The old dungeon interior should feel atmospheric — centuries of accumulated magical residue, strange lighting, the sense of being inside something that was once important and is now forgotten. The magic here is old, layered, and partially sentient in the way old workings sometimes become
+- First real combat sequence — Phelan uses fire magic against dungeon creatures. This is the first time the reader sees him fight. The combination of melee skills and spell casting should be visceral and distinctive — he's not standing back and throwing fireballs, he's moving, striking, and weaving fire into close-quarters combat
+- Phelan locates the rare herb in a deeper chamber, but hits a complication: the chamber containing the densest growth is sealed behind a secondary ward system that's different from the entrance wards — newer, intentionally placed, and more intact. Someone sealed this chamber on purpose
+- Chapter ends with Phelan assessing the sealed chamber — the complication is real but not impossible. He can see the flaws, but this ward was built by someone who knew what they were doing. It'll take work
+
+## Key Dialog
+- Minimal dialog — Phelan is alone in the dungeon. This chapter lives in his internal narration
+- His commentary during combat should be terse, technical — assessing threats, managing resources, noting what works and what doesn't. No quips or banter (there's no one to banter with)
+- His reaction to the sealed chamber should be investigative — "noise" tangents firing as he reads the ward, building theories, cataloguing the differences between this deliberate seal and the ancient entrance wards
+- Internal observation: whoever sealed this chamber did it to keep something in, not to keep people out. The ward design tells him this. Important distinction
+
+## Character Moments
+- Phelan in combat reveals a different person — faster, more instinctive, less cerebral. The "noise" gets quieter during fights because his body takes over. Afterward, the brain catches up and processes what happened. Post-combat is where the observations land
+- Fire magic should feel like something he's good at but rusty with — the skill is there, the muscle memory is there, but the stamina isn't what it was. He's burning energy faster than he should because he's out of practice
+- The dungeon atmosphere should trigger Flaw Sight involuntarily — so much old magic that he's constantly processing, which is exhausting. He has to actively manage the sensory input to stay functional
+- The sealed chamber is a puzzle, and puzzles engage Phelan differently than combat — the shift from fight mode to analysis mode should be palpable. His brain lights up. This is what he's good at
+- Resource management: fire magic drains his reserves. He needs to conserve enough for the sealed chamber. This tension should be present throughout the combat — every spell costs, and he can't afford to be empty when he reaches the real problem
+
+## Mood / Tone
+- Atmospheric and tense — the dungeon is dark, old, and not entirely dead. The magic here has had centuries to settle into patterns
+- Combat scenes: fast, visceral, fragmented. Short sentences. Phelan's narration gets clipped under pressure. "The noise" goes sparse — just tactical observations
+- Between combats: the dungeon's age and strangeness. Phelan as an observer in a place that doesn't get observed often. Old inscriptions, dead workings, the archaeological layers of magical infrastructure
+- The sealed chamber: shift to investigative tension. The fight is over; the puzzle begins. This is where Phelan's real strength lives
+- Closing mood: determination mixed with caution. He can solve this. He just needs to be smart about it
+
+## Freeform Notes
+- The dungeon creatures should be appropriate to the setting — things that thrive in old magical environments. Not generic fantasy monsters. Think: creatures that feed on residual magical energy, or that have been warped by centuries of ambient arcane exposure. They should feel like they belong here
+- Fire magic in an enclosed space has consequences — heat, smoke, light. These are advantages (visibility, area denial) and disadvantages (oxygen consumption, attention-drawing). Phelan should be aware of the practical effects
+- Earth magic gets a minor showing — Phelan uses it for practical purposes (stabilizing a passage, creating cover) rather than offense. It works but it's clearly his weaker element
+- The sealed chamber ward being different from the entrance wards is important — it suggests someone came here after the dungeon was abandoned and sealed a specific room. Why? What's in there besides the herb? This question doesn't need answering in this chapter — it's tension for Ch08
+- Phelan's stamina management is a real concern — Flaw Sight passive drain + fire magic active drain + earth magic occasional use = he's going to hit a wall. The timing of that wall matters. He needs to reach the sealed chamber with enough left to work
+- "The noise" formatting note: combat scenes should have minimal, tactical parentheticals. Investigation/puzzle scenes should have more frequent, longer tangents as the brain engages fully. The contrast between these two modes is part of Phelan's character

chapters/book1/ch08-input.md

@@ -0,0 +1,37 @@
+# Chapter 08 Input — Clean Work
+
+## Scene Goals
+- Phelan solves the sealed chamber — analyzes the ward with Flaw Sight, identifies its architecture (designed to keep something in, not people out), finds the exploitable flaw, and breaks through
+- The herb retrieval itself should be straightforward once the chamber is open — the challenge was access, not collection. The herb grows in the magical residue of the sealed chamber, which is why it's rare: it needs specific arcane conditions to thrive
+- Whatever was sealed in the chamber should be addressed — it doesn't need to be a major threat, but there should be a reason someone sealed this room. Could be a creature, could be an unstable magical artifact, could be a failed experiment. It should be solvable with what Phelan has left, but it should cost him
+- Post-dungeon crash: Phelan exits the dungeon and experiences the cumulative toll — Flaw Sight overuse, fire magic drain, the sealed chamber exploit. Physical exhaustion, sensory distortion, the works. He needs recovery time
+- Return to Drenwick — compressed travel, arrival, turning in the job to the guild. He gets paid. First real guild paycheck
+- Chapter closing hook: through guild channels, a new case arrives — the Ned Floundry situation. Someone is dying from a curse considered unbreakable by the Arcane Compact. Two registered curse-breakers have already failed. The client is desperate enough to hire Necessary Services. This sets up the main case starting in Ch09
+
+## Key Dialog
+- Phelan's internal narration during the ward analysis should be the chapter's technical centerpiece — detailed Flaw Sight work, reading the ward's intent, understanding what was sealed and why. This is the kind of puzzle that makes his brain sing
+- After the chamber: practical assessment. He has the herb. He's running on empty. Time to leave
+- Guild interaction when turning in the job: professional, efficient. He completed the assignment. They pay him. The relationship is established — competence delivered, compensation received
+- The Ned Floundry case introduction should be delivered through guild channels — a formal case brief, not a dramatic encounter. The details are clinical: dying person, known kill timeline, "unbreakable" curse, two failed attempts. The fee is significant. Phelan's reaction: the fee matters, and the problem is interesting. In that order
+
+## Character Moments
+- The sealed chamber exploit should show Phelan at his best and his limits — brilliant analysis, clean execution, but the cost is visible. He's not superhuman. He's skilled, perceptive, and running out of gas
+- The crash after exiting is important — this is the second time the reader sees the post-exploit cost (after the dog in Ch03). Establishing the pattern: Phelan's ability is powerful but it takes a real toll. The dungeon crash is worse than the dog crash because the cumulative load was higher
+- Guild payment: the financial subplot advances. This isn't life-changing money, but it's real professional income. The house math shifts slightly. Phelan notices
+- The Ned Floundry case brief should trigger something in Phelan — not just professional interest. "Unbreakable" is a word that his brain hears as a challenge. His Flaw Sight has never met something truly without flaws. The question isn't whether the curse has weaknesses — it's whether he can find and chain them before the patient dies
+- The chapter should end with Phelan taking the case — motivated by the fee and the intellectual challenge. The reader should understand: the first seven chapters were setup. The real story starts now
+
+## Mood / Tone
+- The sealed chamber: focused intensity, then release. The puzzle, the solution, the cost
+- Post-dungeon: exhaustion and quiet satisfaction. A job done well, if painfully
+- Return to Drenwick: familiar ground after unfamiliar territory. The city feels different when you come back to it from outside — smaller, more known, more like something you might eventually call home
+- Guild payment: professional satisfaction. Not triumph — completion. This is what the job looks like
+- Ned Floundry case: the energy shifts. Something bigger is coming. The dungeon was a job. This is a case. Phelan's brain is already working before he's finished reading the brief. The "noise" kicks into gear
+
+## Freeform Notes
+- The sealed chamber's contents should be interesting but contained — this isn't a major plot thread, it's a job complication. Something that was dangerous enough to seal away but manageable enough for Phelan to handle (barely, given his depleted state). The resolution should demonstrate resourcefulness under constraints
+- The herb should have a name and properties established by now (from Ch06 briefing). The retrieval should confirm what was described — it grows in specific arcane conditions, it looks/smells/behaves a certain way. Small worldbuilding details that make it real
+- The crash establishes a pattern the reader can track: Flaw Sight use + magical exertion = predictable physical cost. This pattern will matter when the triple chain happens in the climax — the reader will understand how dangerous that level of exertion is because they've seen the scale
+- Ned Floundry case details to establish: dying person (Ned), known timeline (weeks), "unbreakable" classification by the Arcane Compact, two prior failed attempts by registered curse-breakers, client arriving through guild channels (desperate, willing to pay). The fee should be significant enough to matter for Phelan's house goal
+- The transition from dungeon-quest to main-case should feel like a gear shift — the dungeon was Phelan proving himself to the guild. The Floundry case is the guild recognizing what he can do and putting him where it matters
+- "The noise" should be especially active when reading the Floundry case brief — his brain is already pulling threads, building theories, asking questions the brief doesn't answer. This is the hyperfocus onset, the beginning of the rabbit hole that will define the next act of the book

chapters/book1/ch09-15-brainstorm.md

@@ -0,0 +1,409 @@
+# Chapters 09-15 Brainstorming Guide
+
+## Status: Author Decision Document
+
+This file covers the Ned Floundry arc (the main case) through to Book 1's resolution. Each chapter section includes a recommended story path, questions for the author to answer, and specific ideas to build from. Nothing here is locked until it becomes a `chXX-input.md`.
+
+---
+
+## Story So Far (Ch01-08 Recap)
+
+- **Ch01-02:** Phelan's day job, voice, financial state, Mere introduction, first date
+- **Ch03:** Flaw Sight demonstrated (cursed dog), post-exploit crash established, guild interview invite
+- **Ch04:** Guild interview, Phelan reveals Flaw Sight (loosely), accepted as member
+- **Ch05:** Resignation from Gavren's shop, Leon D'Nardis introduced, ward-overload riffing, first job details arrive
+- **Ch06:** Job briefing (dungeon herb), combat magic prep, Jonael introduced, travel to dungeon
+- **Ch07:** Dungeon exploration, first combat (fire + melee), sealed chamber discovered
+- **Ch08:** Sealed chamber solved, herb retrieved, crash, return to Drenwick, guild payment, **Ned Floundry case arrives through guild channels**
+
+**Where we stand at Ch09 open:** Phelan is back in Drenwick, recovering from the dungeon, with his first real guild paycheck. The Floundry case brief is in his hands. His brain is already working.
+
+---
+
+## Antagonist — LOCKED: The Arcane Compact (Systemic Corruption)
+
+### The Corruption
+The Arcane Compact — the governing body that registers, regulates, and taxes magical practitioners — is rotten at the top. The senior leadership has built a network of **shell companies posing as approved vendors.** Compact members (the lower-level practitioners, administrators, and functionaries who make up the bulk of the organization) are required to use these "approved" vendors for licensed materials, components, and services. The money flows upward through the shells and into the pockets of the top leadership instead of being distributed across Drenwick's economy as the Compact's founding charter mandates.
+
+Most Compact members have no idea. They follow procurement rules because that's what the rules say. The corruption is structural — hidden in boring vendor lists and purchasing requirements, not in dramatic villainy. The kind of fraud that works because nobody wants to read the paperwork.
+
+### What Ned Found
+**Ned Floundry** — through his work (occupation TBD, but something that gave him access to trade records, shipping manifests, or financial ledgers) — noticed the pattern. The same vendors appearing across too many Compact transactions. Company names that trace back to the same registrations. Money flowing in circles that always end at the top.
+
+He asked questions. He may have told someone, or simply asked the wrong person the right question. The Compact leadership couldn't afford to let him talk.
+
+### The Curse as Silencing Tool
+The curse was commissioned by Compact leadership — not cast by them directly, but procured through their own network. A skilled, discreet curse-wright built the three-nested-working structure. It was designed to be lethal AND to be classified as "unbreakable" by the very people who ordered it. The Nessisary sevices guid was not used, this was freelance.
+
+### The Rigged Failure
+The Compact controls curse-breaker licensing. When Ned's family sought help through official channels, the Compact assigned two registered curse-breakers to the case — **deliberately choosing practitioners who were competent enough to appear legitimate but not skilled enough to handle a three-layered working.** The curse-breakers weren't told to fail; they were set up to fail. They tried, hit the self-stabilizing structure, and reported honestly that the curse appeared unbreakable. The Compact's classification confirmed their findings. Case closed.
+
+Except the family didn't stop. They found the Guild of Necessary Services.
+
+### The Antagonist Figure
+The corruption is systemic, but the case needs a face. A **mid-level Compact official** — someone high enough to access the vendor scheme, low enough to be expendable if things go wrong — is the operational antagonist for Book 1. They classified Ned's curse as unbreakable. They selected the doomed curse-breakers. They're the one who acts when Phelan gets close. The top leadership stays in shadow — they're the series-level threat (Books 2-3).
+
+### Questions Still Open
+- **Who is this mid-level official?** Name, personality, how they interact with Phelan. Are they a true believer in the system, a reluctant participant, or an ambitious climber?
+- **What exactly is Ned's occupation?** Something that naturally gives him access to financial records — a clerk, an accountant, a trade inspector, a shipping coordinator?
+- **Does Ned know why he was cursed?** Does he connect his questions about vendors to the curse, or does he think it was random? If he knows, has he told anyone?
+- **How much of the corruption does Phelan uncover in Book 1?** Enough to know it exists, not enough to prove it or bring it down. The thread stays live
+
+### Thematic Fit
+Systems that are supposed to protect people being used to exploit them — the Compact's founding principles vs. its current reality. Phelan exploits flaws in magical systems; the Compact leadership exploits flaws in institutional ones. The parallel is exact, and Phelan will notice it. He sees structural weaknesses in everything. Including organizations.
+
+### Series Arc Implications
+- **Book 1:** Phelan discovers the corruption exists. Can't prove it. The mid-level official is exposed or neutralized, but the structure survives
+- **Book 2:** The Compact knows Phelan is dangerous. An antagonist who knows who The Shade is
+- **Book 3:** The Compact becomes a direct pressure. Phelan's ability — and what he knows — can no longer stay quiet
+
+---
+
+## Chapter 09: The Client
+
+**Milestone Beat:** Case introduction — client arrives, stakes established, Phelan takes the case
+
+### Recommended Story Path
+
+Phelan meets the client (a family member of Ned Floundry — spouse, sibling, or child) through guild-arranged channels. The meeting should feel professional: a guild office or neutral location, not Phelan's shack. The client presents the situation: Ned is dying, timeline is weeks, two curse-breakers have failed, the Compact has classified the curse as unbreakable.
+
+Phelan reads the case brief with the reader — clinical details, medical timeline, the two failed attempts and what the curse-breakers reported. His brain is already running. The "noise" is loud. He asks specific, uncomfortable questions that reveal his analytical approach (and unsettle the client).
+
+The fee negotiation is a beat: it's significant enough to matter for the house math. Phelan notices this. The reader notices Phelan noticing. He takes the case for the money and the problem. In that order. (He tells himself.)
+
+End hook: Phelan visits Ned for the first time. Initial Flaw Sight reading of the curse — and his first reaction. Something is wrong with this curse. It's not what it looks like.
+
+### Questions to Answer
+
+- **Who is the client?** Ned's spouse, sibling, adult child, or business partner? This person needs to recur — they're the emotional anchor to the case stakes
+- **Where does the meeting happen?** Guild office? A private room? The client's home (upscale, showing what the fee can afford)?
+- **How much is the fee?** Enough to meaningfully shift the house math? Enough to cover a full season of land taxes? The specific number should make Phelan's internal calculator visibly react
+- **How sick is Ned?** Bedridden? Lucid? The first impression of Ned-as-a-person matters — the reader needs to care about this person surviving
+- **Does Phelan examine the curse in this chapter or save it for Ch10?** Recommended: a brief, shocking first look at the end of Ch09 as the hook. Full analysis in Ch10
+
+### Key Ideas
+
+- The two failed curse-breakers' reports should be available to Phelan — reading their notes and understanding where they hit walls is both investigative content and an opportunity to show Phelan thinking differently than conventional practitioners. **Seed for later:** these reports are honest but incomplete. The curse-breakers weren't incompetent — they were out of their depth, and Phelan should be able to tell the difference. The question of *why* the Compact sent practitioners who couldn't handle this type of working doesn't need to land yet, but the evidence should be visible in hindsight
+- The client's desperation should be visible but controlled — they came through guild channels, which means they're organized enough to navigate the system. This isn't a weeping mess; this is someone who has run out of options and is being methodical about finding new ones
+- Financial beat: Phelan's internal math. The dungeon paycheck (Ch08) was good. This fee would be transformative. He doesn't let it show on his face. The narration lets the reader see it
+- **Ned as a person:** Brief interaction or description that establishes Ned as someone worth saving — not a saint, just a decent person who noticed something wrong and paid for it. If Ned is lucid, he might mention the Compact in passing — not explaining the corruption, but something like "I asked the wrong question to the wrong people." A seed the reader can remember later
+- Mere mention: Phelan either tells Mere about the case or she notices something has shifted. Light touch — she's not involved yet. But she notices things
+
+---
+
+## Chapter 10: Three Locks
+
+**Milestone Beat:** First investigation — Phelan reads the curse, discovers three nested workings
+
+### Recommended Story Path
+
+Phelan conducts a deep Flaw Sight analysis of Ned's curse. This is the chapter's technical centerpiece — the reader needs to understand (through Phelan's perception) what makes this curse different from everything he's seen before.
+
+The curse appears as a single, elegant working from the outside. Conventional curse-breakers saw one lock and tried to pick it. They failed because it's not one lock — it's three, nested inside each other, each reinforcing the others. When you push against one, the other two compensate. This is why it's "unbreakable" — not because it's indestructible, but because it's self-stabilizing.
+
+Phelan's Flaw Sight peels back the layers. Each working has a different architectural signature — they weren't all cast at the same time, or possibly not by the same person. Each individual working has a flaw. None of the flaws are fatal alone. But together...
+
+The hyperfocus takes hold. Phelan goes deep. He starts seeing connections, building theories. He doesn't come up fully — this is the onset of the rabbit hole. He's functional but consumed.
+
+End hook: Phelan understands the structure. He doesn't yet know how to exploit it. But he knows it's possible — and two things bother him. First: someone very skilled built this, and they're still out there. Second: the two curse-breakers who failed — their approach was sound for a single-layer curse. They never looked deeper. Either they weren't good enough to see the layers, or they weren't *supposed* to see them. Phelan files this thought. It bothers him.
+
+### Questions to Answer
+
+- **Where does the analysis happen?** At Ned's bedside? Does the guild provide a workspace? Does Phelan bring Ned (or the curse residue) somewhere controlled?
+- **How does Ned react to Phelan?** If Ned is lucid, this interaction matters. Does Ned trust him? Fear him? Recognize what Phelan is doing differently from the other curse-breakers?
+- **How much does Phelan tell the client about what he's found?** Three nested workings suggests someone with resources and access to a skilled curse-wright. Does he share this? Does the client connect it to Ned's work?
+- **Does Phelan recognize the craftsmanship?** The curse-wright is skilled but anonymous — no signature, no flourishes. Built to be functional and untraceable. This tells Phelan something: this was a commission, not personal. Professional work for a paying client
+
+### Key Ideas
+
+- The three-working structure is the chapter's core revelation. Each working should have a distinct character:
+  - **Working 1 (outermost):** The visible curse — what the other curse-breakers saw and attacked. A degradation working that weakens Ned's body over time. Well-crafted, conventional
+  - **Working 2 (middle):** A stabilizer — it monitors Working 1 and repairs any damage done to it. This is why the curse-breakers failed. They'd crack Working 1, and Working 2 would patch it before they could follow through
+  - **Working 3 (innermost):** The anchor — binds the entire structure to Ned's life force. It's what makes the curse lethal. If you somehow broke Workings 1 and 2, Working 3 would kill Ned on the way out. It's a dead man's switch
+- Phelan's Flaw Sight reads each working's flaws:
+  - Working 1's flaw: [Author decides — related to its intent-binding or material components]
+  - Working 2's flaw: It monitors Working 1 too narrowly — it watches for direct attacks, not cascading internal failures
+  - Working 3's flaw: It's keyed to Ned's current life force signature, which the curse itself is changing. The anchor is slowly losing its grip because its target is moving
+- The "noise" should be intense in this chapter — longer tangents, faster connections, the brain firing on all cylinders. This is Phelan at his most engaged and least socially functional
+- Medical detail: Ned's condition. The curse is killing him in a specific, traceable way. Phelan should observe the physical effects — not for sentiment, but because the symptoms tell him how the working operates. Competence as a form of care
+
+---
+
+## Chapter 11: Interested Parties
+
+**Milestone Beat:** Complication — someone doesn't want the curse broken
+
+### Recommended Story Path
+
+Phelan is deep in analysis, working the problem. Then the Compact makes a move.
+
+**The pressure comes through official channels first.** The Guild of Necessary Services receives a formal communication from the Compact: the Floundry curse has been classified as unbreakable by two licensed practitioners and confirmed by Compact review. Continued unauthorized interference with a classified working may constitute a regulatory violation. Professional language. Bureaucratic threat. The kind of letter that's designed to make people stop and check with their lawyers.
+
+The guild pushes back. Their code: "Never burn a client who paid in good faith." The Compact's classification doesn't override a guild contract. This moment establishes the guild's character — they back their people, even against institutional pressure.
+
+**Then the pressure gets personal.** The mid-level Compact official (the operational antagonist) approaches Phelan directly — or through an intermediary. A conversation, not a threat. Reasonable. Understanding. They offer him a way out: **a bribe large enough to build the house.** Walk away from the Floundry case. Take a different assignment. No hard feelings. The money is clean.
+
+Phelan turns it down. But the narration lets the reader see the cost. He did the math. He always does the math. The bribe was more than the case fee. Enough for the house, the land taxes, materials. He said no, and the number sits in his head like a splinter.
+
+**Parallel track:** Phelan starts pulling the thread on why the Compact cares. The curse-breakers' reports — competent practitioners who somehow didn't look deeper than the first layer. The classification — rubber-stamped faster than normal. The official channels that are a little too invested in this one case. He doesn't have the corruption picture yet, but the shape of it is forming. Something is wrong with how the system handled Ned Floundry.
+
+End hook: The Compact official, having failed with the bribe, makes a harder move — perhaps a veiled threat against Phelan's guild standing, or interference with access to Ned, or an attempt to have the case reassigned. Phelan now knows this isn't just a hard case. Someone with institutional power is actively working against him. And the fact that they're trying to stop him means the curse *can* be broken — otherwise, why bother?
+
+### Questions to Answer
+
+- **Who is the mid-level official?** Name, personality, presentation. Are they smooth and reasonable (making the bribe feel like a favour) or cold and administrative (making it feel like a transaction)? Do they believe in the corruption, or are they just following orders from above?
+- **How does the bribe land?** Does the official name the amount, or let Phelan name his price? Does Phelan hesitate visibly, or does his rejection come fast while his internal narration screams? The reader needs to feel how much the money matters
+- **Does Phelan tell the guild about the bribe?** Reporting it strengthens the guild's case. Keeping it private keeps his options flexible (Phelan thinks in contingencies)
+- **Does Jonael help trace the institutional pressure?** His photographic memory and rune knowledge could be useful for reviewing Compact records or procurement paperwork — early breadcrumbs toward the shell company discovery
+- **Does Ned say something in this chapter that connects to the corruption?** If Ned is lucid enough, a conversation where he hints at what he found — without fully explaining — builds the mystery. "I was just an accountant who noticed a pattern" or similar
+
+### Key Ideas
+
+- **The bribe is the chapter's centerpiece.** Not the Compact's letter — that's institutional, impersonal. The bribe is personal. Someone looked at Phelan's financial situation, calculated what he wants most, and offered it to him. This means they've done their research. They know about the land, maybe the house plans. This is unsettling AND tempting. Phelan's code says no. His bank account says please
+- **Guild politics:** The Compact pressuring the guild reveals the power dynamics of Drenwick. The guild is smaller, less official, but it has teeth — its reputation, its code, its willingness to take cases others won't. The Compact is bigger, richer, more established, but it can't simply shut the guild down without drawing attention. Two systems in tension
+- **Phelan's deduction:** He doesn't yet know about the shell companies or the vendor scheme. But he sees the pattern of institutional overreach — the Compact caring too much about one curse on one person. His cold-reader instincts apply to organizations the same way they apply to people: when someone works too hard to look uninvolved, they're involved
+- **Mere scene:** She observes Phelan's behavior shifting — consumed, distracted, the noise louder than usual. Her bluntness cuts through: "You haven't eaten. Your shirt is the same one from yesterday. Whatever you're working on, it's winning." She doesn't ask about the case. She notices the effects and states them as facts. If Phelan mentions the bribe (unlikely — but if he does), her response would be characteristically direct: "How much?" And then, after hearing the number: "That's a lot." No judgment. Just the fact. She trusts him to have already decided
+- **Flaw Sight as institutional analysis:** A subtle beat — Phelan realizes he reads organizations the same way he reads magical workings. Structures, pressure points, flaws in the logic. The Compact's interference has cracks in it. The bribe was too targeted. The classification was too fast. The curse-breaker assignments were too convenient. He's seeing the lattice
+
+---
+
+## Chapter 12: The Team
+
+**Milestone Beat:** Deepening — investigation continues, allies pulled in (Mere, Leon, Devod intro)
+
+### Recommended Story Path
+
+Phelan can't solve this alone. He hates this fact. The case requires skills and perspectives he doesn't have — or at least, skills he can't deploy while maintaining the level of hyperfocus the curse analysis demands. For the first time, he has to ask for help. He is terrible at this.
+
+**Leon D'Nardis** is pulled in for his perspective on the working's architecture. The two ADD brains riff on the curse structure — Leon's ward-overload approach (from Ch05) applied to the three-working problem. Leon doesn't have Flaw Sight, but his brute-force thinking illuminates angles Phelan's precision approach misses. Leon supplies a critical observation — the "nugget" — a seemingly offhand comment about cascading failures that triggers something in Phelan's brain. Not the solution yet, but the direction.
+
+**Mere Fields** contributes through pattern recognition. She doesn't see magic the way Phelan does, but she sees behavioral patterns. She looks at the curse-breakers' reports and notices something Phelan missed — not about the magic, but about the sequence of events. A timing pattern, a procedural gap, something structural that her autistic pattern-matching catches. She also serves as the emotional anchor: she sees Ned as a person, not a puzzle. She forces Phelan to acknowledge the human cost, not with lectures, but by stating facts. "He has a daughter. She's seven."
+
+**Devod Fields** is introduced — through Mere, reluctantly. The connection: Mere mentions needing a specific component or piece of information, and Phelan asks about her contacts. She admits, with obvious discomfort, that her father would know. The reunion is awkward, brief, and loaded with unspoken history. Devod is exactly as described: enthusiastic, scattered, full of ideas. Nine of them are useless. Phelan endures them because Mere asked. Then Devod says something — offhand, buried in idea number seven — that lands.
+
+End hook: Phelan has the pieces. Leon's cascading-failure concept. Mere's pattern insight. Even Devod's accidental contribution. The solution is forming, but it's going to require something Phelan has never attempted: chaining three exploits simultaneously. And to figure out the exact chain, he's going to have to go deeper into Flaw Sight than he ever has.
+
+### Questions to Answer
+
+- **What is Leon's "nugget"?** It should connect to his ward-overload concept from Ch05 — something about how cascading failures propagate through linked systems. Maybe: "If one working watches another, and you make the watched one fail in a way the watcher doesn't recognize as failure..." This gives Phelan the key to bypassing Working 2
+- **What does Mere notice in the reports?** This is where her pattern recognition cracks the conspiracy open. She reads the two curse-breakers' reports and notices something Phelan was too focused on the magic to see: **both practitioners used the same approach, in the same sequence, targeting the same layer.** Not because they independently arrived at the same method — because they were both trained at the same Compact-approved curriculum, and both referred to the same Compact diagnostic guidelines. The guidelines told them where to look. The guidelines were written by people who knew the curse's structure. The curse-breakers weren't told to fail — they were given a map that led them to the wrong room. Mere states this flatly: "They both followed the same procedure. The procedure doesn't account for nested workings. Who wrote the procedure?"
+- **What is Devod's accidental contribution?** One of his scattered ideas, probably phrased badly, contains a kernel: maybe something about anchor points shifting when the thing they're anchored to changes. This connects to Working 3's flaw (it's keyed to Ned's life force, which the curse is altering). Alternatively — Devod, as a carriage driver who does deliveries, might know something about the vendor landscape in Drenwick. He might offhandedly mention a company that Ned was asking about before he got sick. An accidental connection between the case and the corruption
+- **How does Mere reconnect with Devod?** Does she contact him directly? Does Phelan push her to? Is it purely practical ("he knows about X") or does Phelan sense this matters to her in ways she won't admit?
+- **Where does this all happen?** Phelan's shack? A guild workspace? Leon's place? Multiple locations as Phelan assembles the team?
+
+### Key Ideas
+
+- **Asking for help:** Phelan requesting assistance should be painful to read in the best way. He doesn't say "I need help." He says "I need a different perspective on a structural problem" or "There's a pattern I'm not seeing." Same thing. He knows it. The reader knows it. He hates it
+- **Leon and Phelan riffing:** This should feel like the Ch05 conversation but higher stakes. Faster, sharper, with more urgency. Two ADD brains at full speed, feeding off each other's tangents. The reader should be able to follow the logic chain even when it jumps tracks
+- **Devod's introduction:** Comedy with depth. He arrives with too much energy, too many ideas, and an obvious desire to be useful that's both endearing and exhausting. His bad ideas should be genuinely bad — not stupid, just logically flawed in ways that make you see how he got there. His good idea should be buried so deep in the noise that Phelan almost misses it
+- **Mere between Devod and Phelan:** She handles the reunion with her characteristic flatness. "This is my father. He has ideas. Most of them are wrong. You should listen anyway." She doesn't perform the emotional weight of the reconnection, but it's there if you're paying attention. Phelan, the cold reader, pays attention
+- **The growth beat:** Phelan is forced to accept that the solution requires other people. Not just their information — their perspectives. The noise in his head isn't enough. He needs noise from outside. This is the "let people in" arc advancing
+
+---
+
+## Chapter 13: The Crash
+
+**Milestone Beat:** Hyperfocus crash — Phelan pushes too hard, goes down
+
+### Recommended Story Path
+
+Phelan has the theory. He needs to map the exact chain — which flaw feeds into which working, in which sequence, with what timing. This requires the deepest Flaw Sight analysis he's ever attempted: simultaneously perceiving all three workings and their interconnections, modeling the cascade in real time.
+
+He goes in. The "noise" takes over completely. The parenthetical tangents become the narration. The real world becomes the interruption. Time distorts. He's been at it for hours — possibly the better part of a day — without eating, sleeping, or responding to external stimuli. This is the hyperfocus state described in the character bible pushed to its limit.
+
+The mapping works. He finds the chain. But the cost hits before he can act on it: a full crash. Physical collapse, sensory distortion, inability to use magic, migraine, disorientation. Worse than the dungeon crash (Ch08), worse than the dog crash (Ch03). This is the escalating pattern paying off — the reader understands the scale because they've seen the smaller versions.
+
+**While Phelan is down, others step up.** This is structurally critical. The people he reluctantly brought in (Ch12) prove their worth when he's at his most vulnerable:
+- Mere manages the practical fallout — his physical state, keeping the client informed, maintaining the timeline
+- Leon holds the technical thread — Phelan managed to communicate the chain concept before crashing, and Leon keeps the analysis organized
+- Jonael handles logistics — supplies, contacts, whatever Phelan will need when he recovers
+- Even Devod contributes — maybe by keeping watch, running errands, or providing something unexpectedly useful
+
+Phelan wakes up and discovers that the world didn't end without him. People carried the work forward. This is disorienting in a different way than the crash.
+
+End hook: Phelan has the chain mapped. He knows how to break the curse. But the crash cost time — Ned's timeline just got tighter. And the antagonist may have used the delay to act.
+
+### Questions to Answer
+
+- **How long is Phelan out?** Hours? A full day? The timeline matters because Ned is dying. Every hour Phelan is down is an hour lost
+- **Where does the crash happen?** At Ned's bedside (dramatic)? At his own shack (private)? At a guild workspace (where others can find him)?
+- **Does Phelan successfully map the full chain before crashing, or does he get most of it?** If he gets all of it, the crash is purely physical cost. If he gets most of it, he needs to fill the gap after recovery, which adds tension
+- **What does Mere do during the crash?** This is her biggest character beat in the book — how she handles Phelan's vulnerability tells the reader everything about their relationship. She doesn't panic, she doesn't hover emotionally, she manages the situation. Care expressed through competence
+- **Does the Compact official act during Phelan's downtime?** This is a natural window for escalation. Options: attempting to have Ned moved to a Compact-supervised facility (ostensibly for his "safety"), filing a formal complaint against the guild, or — more subtly — having the curse reinforced or adjusted. If the team discovers the interference, it confirms the conspiracy and raises climax stakes
+
+### Key Ideas
+
+- **Narrative structure shift:** The parentheticals take over. During the deep analysis, the formatting should reflect Phelan's state — the "noise" isn't parenthetical anymore, it's the main text. Brief flashes of physical reality (someone saying his name, a hand on his shoulder, the passage of light through a window) become the interruptions. This is the extreme end of the formatting convention established throughout the book
+- **The vulnerability beat:** Phelan unconscious or incapacitated is the moment the reader sees him as fully human. No detachment, no dry observations, no control. Just a person who pushed too hard and broke. How the supporting cast reacts — with competence and care, not drama — validates his (reluctant) choice to involve them
+- **Waking up:** Phelan's first coherent thoughts after the crash. Assessment: physical state (terrible), magical reserves (empty), timeline (how long was I out), the chain (do I still have it). Then the slower realization: someone fed him, kept him hydrated, covered him, organized his notes. Mere's handwriting on a sheet: "Ned stable. Leon has your diagrams. Eat something."
+- **The growth beat crystallized:** Phelan has spent his life relying on himself because other people are unreliable variables. He just experienced what happens when you've proven to reliable people that you're worth supporting. They held the line. He didn't have to ask twice. This changes something, even if he won't admit it yet
+- **Financial anxiety:** Even while recovering, Phelan's brain calculates. Time lost = risk to the case = risk to the fee = risk to the house. The stakes are personal and financial, not just intellectual
+
+---
+
+## Chapter 14: The Triple Chain
+
+**Milestone Beat:** Climax — cascading failure of all three workings
+
+### Recommended Story Path
+
+Phelan is recovered enough to work but not fully restored. He has the chain mapped. The window is closing — Ned's condition is deteriorating, and the antagonist may be aware that Phelan is close.
+
+The preparation should be meticulous. Phelan walks through the chain with Leon (and possibly Mere, if her pattern insight is relevant to the timing). This isn't a solo hero moment — it's a team-supported precision operation. Phelan is the one with Flaw Sight, the one who executes, but the support structure makes it possible.
+
+**The triple chain itself:** Phelan engages all three workings simultaneously. He can't attack them — that triggers the stabilizer (Working 2) and the dead man's switch (Working 3). Instead, he has to thread through each working's flaw in a precise sequence that causes each to fail in a way that looks like natural degradation rather than an attack.
+
+The chain:
+1. **Working 3 (anchor) first:** Exploit its flaw — the shifting life-force signature. Not breaking it, but loosening it further. Making the anchor's grip slip just enough that it won't fire the dead man's switch when the other workings collapse
+2. **Working 2 (stabilizer) second:** Feed it false data. Because it only watches for direct attacks on Working 1, Phelan triggers a failure mode that looks like internal instability rather than external assault. The stabilizer sees Working 1 degrading "naturally" and doesn't intervene — or intervenes wrong, accelerating the collapse
+3. **Working 1 (visible curse) last:** With the stabilizer confused and the anchor loosened, Phelan cracks the visible curse. It collapses. Working 2 tries to repair but is already processing false data. Working 3 tries to fire but can't lock onto Ned's shifted signature. Cascading failure. All three go down
+
+The execution should be tense, technical, and physically devastating. Phelan is operating on depleted reserves, maintaining focus on three simultaneous workings while managing his own rapidly draining energy. The "noise" is focused to a point — no tangents, no asides, just the chain.
+
+The curse breaks. Ned's body reacts — not instant recovery, but the removal of the active killing force. He'll live.
+
+Phelan collapses. Again. But this time, people catch him.
+
+### Questions to Answer
+
+- **Who is present for the triple chain?** Just Phelan and Ned? The full team? The client watching? Each audience changes the scene's dynamics
+- **Does the Compact make a final move during the execution?** The mid-level official could attempt to intervene — sending Compact agents to stop the procedure, or having the curse-wright reinforce the working in real time. This would add combat-level tension to the technical procedure and would require the team (Leon, Jonael) to physically protect the workspace while Phelan operates
+- **How close to death is Phelan by the end?** The energy cost should be severe — closer to the "then death" end of the exhaustion spectrum than he's ever been. He should know, mid-chain, that he might not come back from this
+- **Does anyone else contribute during the execution?** Leon holding a stabilizing working? Mere monitoring Ned's physical state? Or is this purely Phelan's moment, supported by prep but executed alone?
+- **What does the Compact official's reaction look like?** They'll know the curse broke — if they have monitoring in place, or if the curse-wright reports back. Their response matters: do they panic, go to ground, escalate to their superiors, or try to spin it? This sets up the political fallout in Ch15
+
+### Key Ideas
+
+- **The chain as writing:** This is the book's technical climax, and the reader needs to follow it without a magic PhD. Use Phelan's perception — the lattice, the threads, the cracks — to make the abstract tangible. Each step should feel like lock-picking: precise, tense, one wrong move away from catastrophe
+- **Physical cost in real time:** Phelan's body failing during the chain. Hands shaking. Vision narrowing. The taste of blood. Each working he engages drains him further. He does the math: he has enough energy for two clean engagements and one sloppy one. The order matters. (This is why he starts with the anchor — it needs the most precision, and he does it while he's least depleted)
+- **The moment it works:** The cascade. Each working failing feeds energy into the next failure. For a moment, the lattice is beautiful — a controlled demolition, each piece falling exactly where it should. Then it's gone. Ned breathes differently. The room feels lighter. Phelan feels empty
+- **Leon's contribution:** Even if Leon isn't casting during the chain, his understanding of cascading failures (from Ch05 and Ch12) informed the entire approach. The ward-overload concept — brute force through a system's own logic — is the philosophical foundation of the triple chain, refined through Phelan's precision
+- **The second collapse:** Phelan going down after the chain should echo the Ch13 crash but with a crucial difference — this time, he knows people are there. He lets go. That's the growth beat
+
+---
+
+## Chapter 15: The Settlement
+
+**Milestone Beat:** Resolution — case closes, personal beat, forward momentum for series
+
+### Recommended Story Path
+
+The aftermath. Ned Floundry will survive — the curse is broken, his body is recovering, though the damage done will take time to heal fully. Phelan is recovering from the worst magical exertion of his life.
+
+The case closure happens through professional channels: guild report filed, fee collected, client satisfied. The guild's reaction to the triple chain should be measured — they understand what Phelan did, even if they don't fully grasp how. His reputation within the guild shifts. He's not the new member with an interesting trick anymore. He's something else.
+
+**The Compact thread: partial resolution, open wound.** The mid-level official is identified — Phelan, the guild, and possibly Ned all know who orchestrated the curse. But proving it is another matter. The official's connection to the curse-wright is indirect (intermediaries, shell company procurement). The Compact's institutional weight means a direct accusation would be Phelan's word against the organization.
+
+What Phelan *does* know: the corruption exists, the vendor scheme is real, and someone at the top is funneling money. He can't prove it yet. He doesn't have the evidence trail. But he's seen the lattice — and it has flaws.
+
+The mid-level official may face consequences — perhaps quietly reassigned, or cut loose by the leadership above to protect the scheme. The Compact's public position: the curse was broken, the classification was an honest error, the system works. Internally, the leadership knows Phelan is a problem. He broke something they guaranteed couldn't be broken. He asked questions that got uncomfortably close to the vendor scheme. He is now a name on a list.
+
+**Ned Floundry as a loose end:** Ned knows what he found. The curse was meant to silence him permanently. It failed. Does Ned go public? Does he have evidence, or just suspicions? Does Phelan advise him — and if so, what does he say? Phelan is pragmatic: going public without proof gets you another curse. Building a case takes time and allies. This is a thread for the series, not a resolution for Book 1
+
+**Personal beats:**
+- **The fee:** Phelan gets paid. The house math shifts significantly. Not enough to build, but enough to start planning seriously. He does the calculations. For the first time, the number is moving in the right direction
+- **Mere:** Their relationship has changed through the case. She contributed. She saw him at his worst. She stayed. Something small shifts — not a dramatic declaration, but a quiet adjustment. Maybe she mentions the land. Maybe she already has opinions about the house design. Maybe she just shows up with food and stays longer than usual
+- **Devod:** The reconnection with Mere isn't resolved — it's started. Devod proved useful. Mere noticed. The door is slightly open. This is a thread for future books
+- **Leon and Jonael:** The team that formed around this case doesn't dissolve. They go back to their separate orbits, but the connections are established. Phelan has people now, whether he wanted them or not
+- **The Arcane Compact:** Breaking an "unbreakable" curse draws attention — but for the corrupt leadership, the real threat isn't Phelan's magical skill. It's that Ned Floundry is alive, and the investigation that led to the cure also led toward questions about vendor schemes and rigged assignments. Phelan now sits at the intersection of two dangerous pieces of knowledge: how to break things the Compact says can't be broken, and why the Compact said it in the first place. He isn't going to tell them how. And they can't afford to let him keep asking why
+
+End: Phelan in his shack (or on his land), doing the math, looking at the house plans, and for the first time allowing himself to think it might actually happen. Not because of the money — because of the people. A quiet ending. The noise, for once, is manageable.
+
+### Questions to Answer
+
+- **How much time passes in this chapter?** Days? A week? The resolution needs breathing room — rushing it undermines the emotional payoff
+- **Does Phelan visit Ned after recovery?** A scene between them could be powerful — the person he saved, now living. Phelan would be uncomfortable with gratitude. Ned might sense this. A brief, honest exchange
+- **What is the guild's formal response to the triple chain?** Do they promote Phelan? Give him a bonus? Simply note it in his file? Their reaction signals what comes next for his career
+- **Does the Compact make contact?** Even a hint — a letter, a request for a report, a visit from an official — plants the seed for the series arc
+- **What's the final Mere beat?** This needs to be earned and understated. Not a confession, not a kiss (unless the earlier chapters have built to it naturally). Something that Phelan would remember. Something that tells the reader: this is going somewhere, and it matters
+- **Is there an epilogue or final scene that sets up Book 2?** A new case arriving? A letter from an unknown party? Or just the quiet implication that Phelan's life has changed?
+
+### Key Ideas
+
+- **The fee and the math:** Make the numbers real. The reader has tracked Phelan's financial state from Ch01 (broke, one meal a day) through the dungeon paycheck (Ch08, a real improvement) to this. The Floundry fee should be the biggest single payment he's ever received. Show the math: land taxes, building costs, material estimates. The house goes from fantasy to plan. Not today, but it's no longer "never"
+- **Mere's quiet claim:** She doesn't ask to be part of the house plan. She doesn't need to. She starts talking about it as though she already is. "The kitchen should face east" or "You'll need drainage on the north side." Phelan notices. He doesn't correct her. That's the love story
+- **Phelan's reputation:** "The Pirate Shade broke an unbreakable curse" becomes a sentence that moves through Drenwick. He doesn't seek the reputation. It finds him. This is both an asset (better cases, better fees) and a liability (more attention, more enemies)
+- **Devod as a recurring presence:** He shouldn't disappear after the case. Maybe he stops by. Maybe he has ideas about the house (nine bad ones, one good one). He's part of the ecosystem now
+- **The final "noise" beat:** The last parenthetical of the book. It should feel different — not the frantic processing of a case, not the overwhelming input of Flaw Sight. Something quieter. Something like contentment, filtered through a brain that doesn't know how to sit still. *(The land. The plans. The kitchen facing east. The numbers that almost work. Almost.)*
+
+---
+
+## Thread Tracking Across Ch09-15
+
+### Compact Corruption Thread
+| Ch | Status |
+|----|--------|
+| 09 | Seeds — Ned's cryptic comment about "asking the wrong question." Curse-breaker reports available but unremarkable on first read |
+| 10 | Implied — three-working structure = resources, sophistication, a paying client behind the curse-wright. Phelan notes the curse-breakers' reports both targeted the same layer |
+| 11 | Active — Compact pressures the guild, mid-level official offers Phelan a bribe. Phelan starts seeing institutional interference as a pattern |
+| 12 | Cracked open — Mere's pattern recognition catches the rigged curse-breaker assignments. Devod may connect to the vendor landscape. The conspiracy takes shape |
+| 13 | Opportunistic — Compact official may act while Phelan is down (move Ned, pressure guild, reinforce curse) |
+| 14 | Climax — possible Compact interference during the chain. The team may need to physically protect the workspace |
+| 15 | Partial resolution — mid-level official identified but corruption unproven. Ned alive = the silencing failed. Compact leadership knows Phelan is dangerous. Thread stays live for series |
+
+### Ned Floundry as a Person
+| Ch | Status |
+|----|--------|
+| 09 | Introduced — first impression, medical state, enough humanity to make the reader care |
+| 10 | Present — Phelan examines him, observes symptoms, sees the person inside the puzzle |
+| 11-12 | Background — his condition worsens, ticking clock |
+| 13 | Stake — time lost during crash = time lost for Ned |
+| 14 | Saved — the curse breaks, he'll live |
+| 15 | Aftermath — brief interaction, gratitude that makes Phelan uncomfortable |
+
+### Devod Fields
+| Ch | Status |
+|----|--------|
+| 09-11 | Not present |
+| 12 | Introduced — through Mere, reluctantly. Awkward reunion. Ideas. One good one |
+| 13 | Minor role — contributes during Phelan's crash |
+| 14 | Not present (unless needed) |
+| 15 | Aftermath — the door is open, the relationship is starting |
+
+### Mere's Dual Role
+| Ch | Status |
+|----|--------|
+| 09 | Light touch — notices Phelan has a new case |
+| 10 | Minimal — Phelan is consumed |
+| 11 | Scene — observes Phelan's state, blunt commentary |
+| 12 | Active contributor — pattern recognition on the reports, introduces Devod |
+| 13 | Essential — manages the crash, care through competence |
+| 14 | Support — monitors Ned during the chain (if present) |
+| 15 | Emotional anchor — the quiet claim on the future |
+
+### Financial Subplot
+| Ch | Status |
+|----|--------|
+| 09 | Fee negotiated — Phelan's internal math reacts |
+| 10-13 | Background — the fee is motivation, mentioned in stress |
+| 11 | Possible bribe scene — the money he turns down vs. the money he's working for |
+| 14 | Earned — the case is solved, the fee is secured |
+| 15 | Realized — payment received, house math shifts, plans become possible |
+
+### Phelan's Growth Arc
+| Ch | Status |
+|----|--------|
+| 09 | Solo operator takes a case |
+| 10 | Solo investigation |
+| 11 | Realizes the case has dimensions beyond the puzzle |
+| 12 | Asks for help (badly). Receives it (gratefully, ungracefully) |
+| 13 | Forced vulnerability. Others carry the work. Trust validated |
+| 14 | Team-supported execution. He's still the one who does it, but he couldn't have without them |
+| 15 | Quiet acceptance. He has people. The noise says this is fine |
+
+---
+
+## Series Setup Threads (for Book 2-3)
+
+These should be planted lightly in Ch09-15, not forced:
+
+1. **The Compact corruption** — Phelan knows it exists. Ned knows what he found. Neither has proof. The leadership knows Phelan broke their "unbreakable" guarantee and got close to the vendor scheme. Book 2: they send someone who knows who The Shade is. Book 3: the full confrontation
+2. **Phelan's reputation growth** — "The Pirate Shade" becomes a name that means something. Better cases, more attention, higher stakes. The Compact's corrupt leadership hears the name and starts making plans
+3. **Flaw Sight's true nature** — Is it just a rare talent, or is it something more? Phelan hasn't questioned what he can do, only how to use it. The Compact's interest in him isn't just about the curse — someone in the hierarchy may want to understand (or control) what he can see
+4. **The team** — Leon, Mere, Jonael, Devod. They're not a formal team. But the infrastructure exists. Book 2 can activate it faster. The Compact targeting Phelan means targeting his people — raising the personal stakes
+5. **The house** — Still not built. But closer. The dream that drives Phelan forward, the thing that's really about Mere, the goal that requires him to keep working impossible cases
+6. **Ned Floundry as an ally** — A man who owes Phelan his life and has evidence of Compact corruption. He's a resource for the series arc — if he can stay alive long enough to use what he knows
+
+---
+
+*This document is a brainstorming guide, not a locked outline. All decisions remain with the author. Convert sections to `chXX-input.md` files as decisions are made.*

characters/phelan-varrant.md

@@ -67,6 +67,14 @@
 - **Widen** — destabilize a working to cause controlled failure
 - **Chain vulnerabilities** — link multiple flaws across separate workings for cascading effect (rare, dangerous, exhausting — his signature move)
 
+### Combat Magic (Fire & Earth)
+- Learned fire magic and melee fighting as a child due to bullying. Kept quiet since leaving school. Hasn't needed it until dungeon work
+- **Fire element:** Strong. His primary combat tool — close-quarters fire weaving combined with physical strikes. Practiced obsessively as a kid
+- **Earth element:** Serviceable but weaker. Used for practical purposes (stabilizing terrain, creating cover) rather than offense
+- **Melee + magic combination:** Rare in Corvel. Most mages (~20% of population can use magic) are specialists who stand back and cast. Phelan can fight in close quarters while maintaining spell work. This makes him unusual in combat situations
+- **Current state:** Dormant skill resurfacing out of necessity. The skill and muscle memory are there, but stamina isn't what it was. Burns energy faster than he should because he's out of practice
+- **Not his identity:** Combat magic is a real capability he's been sitting on, not his defining trait. Flaw Sight remains his primary tool
+
 ### Other Skills
 - Cold reading / behavioral prediction
 - Guild-level problem solving and investigation

docs/plans/2026-03-03-the-noise-tangent-convention-design.md

@@ -28,17 +28,19 @@ Phelan's private word for the constant background processing his brain does. Int
 
 ### 2. Parenthetical Aside Format
 
-After the introduction, tangent passages are formatted as parenthetical asides:
+After the introduction, tangent passages are formatted as **italicized parenthetical asides** — italics inside parentheses to visually distinguish involuntary brain tangents from regular narrative asides:
 
 ```
 Regular narration here.
 
-(Short, clipped tangent thoughts. Sentence fragments. Rapid-fire observations.
-Raw brain output without social niceties or full prose. The noise made visible.)
+(*Short, clipped tangent thoughts. Sentence fragments. Rapid-fire observations.
+Raw brain output without social niceties or full prose. The noise made visible.*)
 
 Regular narration resumes, sometimes mid-action.
 ```
 
+The `(*…*)` format works cleanly on Kindle and provides an immediate visual cue that this is "the noise" rather than a standard parenthetical.
+
 ## Rules for Parentheticals
 
 ### What qualifies: