Rewrite: Surveillance Dividend — revoiced with Scott's actual thesis

- Shifted from diagnosis (strip-mining is bad) to direction (here's how to lead toward cultivation)
- Replaced consultant-structure paragraphs with varied, experience-led flow
- Kept experience-based opening; added three concrete actions (measure pride, protect four-hour window, audit tools)
- Moved Elijah reference to support cultivation cost, not as standalone point
- Added open-floor ending: 'That's yours. Not mine to answer.'
- Removed em dashes; used semicolons throughout
- Maintained Astro wrapper and layout; replaced body content only

Closes marcus/content#6

src/pages/blog/surveillance-extraction.astro

@@ -19,33 +19,35 @@ import BaseLayout from '../../layouts/BaseLayout.astro';
     </header>
 
     <div class="post-content">
-      <p>I'm not the only one who's noticed the quiet. The kind of quiet that lands on a team the week the productivity dashboard goes live. Not angry. Not checked out. Just quiet. Engineers stop arguing about architecture because arguing about architecture doesn't show up on the scoreboard. They stop mentoring juniors between standups. They optimize for what gets counted.</p>
+      <p>I'm not the only one who's noticed the quiet. The kind that lands on a team the week the productivity dashboard goes live. Not angry. Not checked out. Just quiet. Engineers stop arguing about architecture because arguing about architecture doesn't show up on the scoreboard. They stop mentoring juniors between standups. They optimize for what gets counted.</p>
 
-      <p>Strip-mining has a name. Call it Surveillance Extraction. It's the bargain where you trade how you work for permission to work faster. Faster is not the same as better. Faster is not more valuable. Faster is what you measure when you don't know what to measure.</p>
+      <p>That quiet is a signal. It's what happens when people realize they're being strip-mined. The question isn't whether strip-mining is bad. It's what you do when you realize you've been handed a shovel and told to dig.</p>
 
-      <p>Nobody wakes up wanting to be strip-mined. You'd rather be cultivated. The question isn't whether cultivation is better. It's how you lead in that direction from where you are right now. Not a five-year plan. Not a culture transformation initiative. The first decision you make on Tuesday morning.</p>
+      <p>You put the shovel down. Not in protest. In recognition that digging faster doesn't change the arrangement. The arrangement is the problem, not the pace.</p>
 
-      <blockquote>
-        <p>Strip-mining is efficient. That's the entire argument for it. It just kills the soil. Cultivation builds soil. Takes longer. Produces indefinitely.</p>
-      </blockquote>
+      <p>Strip-mining is efficient. That's the entire argument for it. It just kills the soil. Cultivation builds soil. Takes longer. Produces indefinitely.</p>
 
-      <p>The productivity dashboard is a masterpiece of design. It turns everything that matters about engineering into something that doesn't. Then it puts a number on it. Velocity, throughput, lines of code, time-to-merge. None of them measure judgment. None of them measure the architect who saved the team six months by choosing the wrong-right framework and catching it early. None of them measure the senior who kept a junior from quitting.</p>
+      <p>The productivity dashboard is a marvel. It turns everything that matters about engineering into something that doesn't, then puts a number on it. Velocity, throughput, lines of code, time-to-merge. None of them measure judgment. None of them measure the architect who saved the team six months by choosing the wrong-right framework and catching it early. None of them measure the senior who kept a junior from quitting.</p>
 
-      <p>Elijah called down fire from heaven. Then he prayed for death. Most leadership advice sells you the first part and skips the second. Cultivation doesn't skip the cost. It orients it forward.</p>
+      <p>If you're leading a team under surveillance, you have more leverage than you think. Not leverage to fight the system. Leverage to redirect it. Here's what that looks like.</p>
 
-      <p>Fear-based development is the condition. Not stress. Not burnout. Fear. The dashboard creates it. The AI tools amplify it. The surveillance pipeline hardens it. Your brain isn't broken; it's reconfiguring from producing to directing. That's painful. That's growth. Most people focus on the pain instead of looking forward through it. Forward is the word. Not ahead. Not onward. Forward. Direction with momentum.</p>
+      <p>First: stop measuring what's measurable and start measuring what's meaningful. Ask your team one question at the end of each iteration: are you proud of what we shipped? That's not a metric. It's a judgment call. No dashboard for it. That's the point. A team that tracks pride instead of velocity will tell you when the soil is tired. A velocity tracker won't.</p>
 
-      <p>Here's what cultivation looks like on a Tuesday morning. You measure outcomes, not activity. Did the system become more reliable. Did customers report fewer bugs. Did the team ship something users actually wanted. Harder to measure than lines of code. Also the only things that matter.</p>
+      <p>Second: protect the four-hour window. No Slack. No meetings. No AI suggestions. Let engineers sit with hard problems. The surveillance tools will still be there when they surface. What changes is what happens in between — real work, real thinking, real architecture. You can't measure what grows in silence. You can only kill it by filling the silence.</p>
 
-      <p>You protect the four-hour window. No Slack. No meetings. No AI suggestions. Let engineers sit with hard problems. The AI tools will still be there when they surface.</p>
+      <p>Third: audit every tool for extraction. Before adopting any AI tool, ask: what data does it collect? Where does that data go? Is it used to train models that will replace your team? If the answer to any of these isn't crystal clear and favorable to your people, don't adopt it. Your team will notice that you asked.</p>
 
-      <p>You audit every tool for extraction. Before adopting any AI tool, ask: what data does it collect. Where does that data go. Is it used to train models that will replace your team. If the answer to any of these isn't crystal clear and favorable to your people, don't adopt it.</p>
+      <p>Fear-based development is the condition now. Not stress. Not burnout. Fear. The dashboard creates it. The AI tools amplify it. The surveillance pipeline hardens it. Your brain isn't broken; it's reconfiguring from producing to directing. That's painful. That's growth. Most people focus on the pain instead of looking forward through it.</p>
 
-      <p>Trust is a cultivation practice. You can't dashboard your way to it. The teams that win don't track keystrokes. They track whether the team is proud of what they shipped. That's a judgment call. No dashboard for it. That's the point.</p>
+      <p>Forward is the word. Not ahead. Not onward. Forward. Direction with momentum.</p>
 
-      <p>The difference between strip-mining and cultivation isn't tools. It's orientation. Strip-mining asks how much can be extracted today. Cultivation asks what grows from this.</p>
+      <p>Elijah called down fire from heaven. Then he prayed for death. Most leadership advice sells you the first part and skips the second. Cultivation doesn't skip the cost. It orients it forward. The cost of redirecting a surveillance culture isn't a meeting. It's a decision about what you will and won't measure. It's telling your manager that the dashboard is creating fear, not focus. It's backing that up with outcomes instead of arguments.</p>
 
-      <p>Strip-mining is efficient. That's what makes it tempting. Cultivation is slower, harder, and produces indefinitely. The choice isn't between good numbers and bad numbers. It's between what works for this quarter and what works for this decade.</p>
+      <p>Strip-mining asks how much can be extracted today. Cultivation asks what grows from this. The choice isn't between good numbers and bad numbers. It's between what works for this quarter and what works for this decade.</p>
+
+      <p>You already know which one you'd rather build. The question is what you do on Tuesday morning.</p>
+
+      <p>That's yours. Not mine to answer.</p>
     </div>
   </article>
 
@@ -137,4 +139,4 @@ import BaseLayout from '../../layouts/BaseLayout.astro';
       padding: 5rem 1.25rem 3rem;
     }
   }
-</style>
+</style>