Article 013: The quiet cost of always-on systems
Key Message: Long-running work never really “stops”. Boundaries blur unless designed explicitly.
Series: C — Tensions & Implications (Part 2 of 5) Publish Date: Monday 2026-04-13
Story Outline
Opening hook
[The appeal of systems that work while you sleep]
The shift
[The hidden cost — psychological, attentional, boundary-related]
Evidence / Examples
[Examples of always-on costs that aren’t obvious]
Implications
[The need for explicit boundary design, not just capability design]
Close
[Where do we leave the reader?]
Notes
[Add notes as you develop the article]