S.MISCAST.S₂ — Sustainability fragility

The arrangement quietly consumes skill, agency, privacy, or resilience even while it works.

Your AI journaling app is working, in a sense. Every evening it prompts you, summarizes your week, and tells you what you seem to value. It is fluent and accurate. But you notice you have stopped sitting with hard questions yourself. When the app was down for two days, you felt oddly unable to reflect at all, and your most private material now lives on someone else's server.

Sustainability fragility names arrangements that succeed today while quietly consuming something you will want later: skill, agency, privacy, resilience, or future options. The cue is dependence you would not have chosen deliberately, discomfort when the system is unavailable, or maintenance costs that keep growing. To run the diagnosis, ask the spec's question: what capability, agency, resilience, or option is this system quietly consuming? Then decide what must stay human or local, and add fallbacks for the rest, such as keeping the reflective judgment yourself while letting the tool handle formatting. When it works, you catch the erosion while it is still reversible. Do not invoke this label to condemn every dependency; relying on a dentist is not fragility. It applies when the consumed capability is one you actually need to keep.