paradigm-surface

name	paradigm-surface
description	Surfaces paradigm shifts in public technical writing: open with lived workflow change, name one abstraction (optional metaphor or era label), and list the real stack honestly. Use when posting threads, READMEs, or memos about how tools or the profession are changing.

Paradigm Surface

Distilled pattern: lead with lived practitioner discomfort, then name the shift so the field can argue with a handle.

When to use

• You have a structural change in how work is done (tools, stack, profession) and need traction without a product launch.
• You want a post that invites correction and extension, not just applause.

Steps

1. Anchor in first-person state — What changed in your workflow this week or month? Avoid generic industry trends until the reader accepts your ground truth.
2. Name one layer — Give the new abstraction a short label (new word, or a tight phrase). The label is a compression artifact for discussion.
3. List the stack honestly — Enumerate the moving parts you are actually juggling (agents, prompts, tools, permissions, IDE, etc.). Dense lists signal credibility; keep them concrete.
4. Invite the skill gap — Frame “catching up” as learnable orchestration, not moral failure. The goal is motion in the replies, not self-flagellation theater.

Optional accelerators

• Version the era — If the shift is civilizational for your audience (e.g., a new “layer” of software), give it a numbered or named era so people can cite the transition without re-explaining history each time.
• One metaphor, bounded — A vivid ontology (what kind of thing is this system?) can compress a long argument—if you immediately list what the metaphor fails to capture, so critics engage productively.
• Historical analogy — “We are in the 1960s of X” (or your honest comparison) signals phase without pretending precision.

Anti-patterns

• Opening with definitions nobody asked for.
• Polished manifestos with no personal timestamp (“we all know that…”).
• Claiming inevitability without a single observable threshold event you can point to.
• Metaphors that smuggle inevitability or moral judgment—pair with limits every time.

Output shape

• One hook sentence (pain or paradox).
• One label for the shift.
• One paragraph mapping old mental model → new mental model.
• Optional: bullet inventory of the new programmable surface.