Series Context Quick Reference
Use this when checking for overlap and building series connections in outlines.
For the full roadmap and phase descriptions, always read docs/content-strategy.md.
For publish dates, read docs/distribution-schedule.md.
Phase Arc
| Phase | Articles | Mode |
|---|---|---|
| A — Noticing the shift | 001–005 | Name what’s changing without proposing solutions |
| B — Reframing the work | 006–011 | Explore how roles, tools, and attention evolve |
| C — Tensions & implications | 012–017 | Examine what this breaks, complicates, or challenges |
Published / Drafted Articles
| # | Slug | Key insight | Phase |
|---|---|---|---|
| 001 | desktop-as-centre | IDE is still central, but not always the most important thing | A |
| 002 | work-continues-without-you | Progress is no longer tied to presence | A |
| 003 | development-used-to-be-synchronous | Async breaks tight-feedback-loop assumptions | A |
| 004 | ide-as-intervention-surface | IDE shifts from “where work happens” to “where decisions are corrected” | A |
| 005 | faster-feedback-not-whole-story | Continuity matters more than speed | A |
| 006 | from-keystrokes-to-supervision | Supervisory role is not a loss of agency | B |
| 007 | how-to-allocate-attention-at-scale | Tools scale faster than human attention | B |
| 008 | beyond-vibe-coding | Chat is coordination, not creation | B |
| 009 | git-as-memory | Git becomes the long-term record of intent | B |
| 010 | what-long-running-agents-change | Persistence matters more than intelligence | B |
| 011 | working-from-a-phone | Mobile work reveals what must stay central | B |
| 012 | the-goalkeepers-dilemma | Skills you stop practising are the ones you need when AI fails (Bainbridge 1983) | C |
Upcoming Articles
| # | Title | Key message | Planned date |
|---|---|---|---|
| 013 | The quiet cost of always-on systems | Long-running work never stops; boundaries blur unless designed explicitly | 2026-04-13 |
| 014 | Why experience matters more in async development | Judgement compounds in async systems | 2026-04-20 |
| 015 | What breaks when you remove the editor from the centre | Debugging, learning, onboarding all change | 2026-04-27 |
| 016 | What breaks without editor | Some things get harder, not easier | 2026-05-04 |
| 017 | The centre doesn’t disappear; it moves | The “centre” is contextual and temporary | 2026-05-11 |
Key Concepts Established (Do Not Re-introduce)
- Presence ≠ progress (002): Established that work continues without you
- IDE as intervention surface (004): Framing of review-not-creation is done
- Supervision as valid role (006): Settled — no need to defend it again
- Attention allocation (007): Covered the “where to look” problem
- Git as memory (009): Commits-as-intent already done
- Persistence > intelligence (010): Long-running agent characterisation done
- Reservoir / skill maintenance risk (011): Named but not explained (012 explains the mechanism)
- Bainbridge 1983 / ironies of automation (012): The deskilling mechanism is done
Phase C Tone Rules
Phase C (012+) is distinct from phases A and B:
- Drop directly into discomfort. No warm-up, no “as we’ve seen”. Earn the reader fresh.
- Tension first. Open with the problem, not the context.
- Hold trade-offs; do not resolve. Phase C does not propose solutions.
- Assume a Phase C-entry reader. Each article must stand alone for someone who hasn’t read 001–011.
Linking to Prior Articles
When a natural thematic connection exists, link inline using relative paths:
/articles/002-work-continues-without-you
/articles/004-ide-as-intervention-surface
etc.
Link the first relevant mention only. Do not create “see also” blocks.