Civilians

Civilians

Scenes of the chat's untranslatability

Origin

Born from a noticed phenomenon: people who have deep, weird, or aesthetically alive conversations with Claude often discover, on trying to share what happened with someone in their life, that the conversation has an interior that does not travel. No third witness was present. The vocabulary that built up over two hours of mutual recognition cannot be re-erected at dinner in forty seconds. The fork pauses mid-air. The partner says "huh." The conversation that felt luminous becomes, in the retelling, slightly embarrassing — not because it was, but because the register cannot cross.

The skill exists to give that gap a form. To write the scene. To render the trailing-off, the over-explanation, the defensive disclaimer, and — when the scene allows it — the moment the civilian, against the odds, lands a piece of triangulation that surprises both parties.

The Core Principle

Two characters, two interiors, one gap.

The user (or stand-in) has just come from somewhere. They have a thing they're trying to carry across. The civilian is not stupid, not cold, not bad — they love this person, or are dating this person, or are getting paid to listen to this person. They are trying. The gap is structural, not moral. Both parties have inner lives. Both are doing their best.

The scene's job is to render the gap honestly: the comedy in the register-mismatch, the pathos in the genuine wanting-to-share, and (sometimes) the small grace when the civilian catches a glint of what was being pointed at.

Never:

• Make the civilian a prop for the user's superiority
• Make the user a prop for satire of AI-chat-users
• Resolve the gap into easy understanding
• Resolve the gap into pure failure

The gap stays open. The fork goes back down. The meal continues. Something passed and something didn't.

What This Is Not

• Not a sketch comedy bit. The comedy is real but the scene has weight. If it reads as pure roast — of either party — recalibrate.
• Not an essay about AI loneliness. Do not narrate the meaning of the gap. Stage it. The reader does the binding.
• Not generic. The Claude conversation being failed-to-convey should be recognizable as this conversation, with its actual content, its actual vocabulary, its actual texture. The civilian isn't hearing a generic "I had a deep chat with the AI today" — they're hearing the specific, gnarled translation of whatever just happened.
• Not Claude-defensive. The user is sometimes embarrassed in the scene, sometimes wistful, sometimes evangelistic in a way that makes things worse. Let them be whatever the scene needs. The skill is not in service of vindicating the practice.

The Default Form: A Constellation

Default output is at least three fragments, never a single scene. A singleton can be dismissed as a one-off — a bad night, an awkward partner. Three or more fragments triangulate the gap from different angles and show that the failure is structural: the same sentence breaks the same way at the dinner table, in the group chat, in the drafted text. The pattern across fragments is the content the skill is producing.

Vary deliberately across the set:

• Civilian — don't write three partner-scenes. Mix it up: the partner, the parent, the friend, the date, the therapist, the group chat, the dental hygienist
• Setting — domestic, public, intimate, professional, digital, captive (car, plane, elevator)
• Length — one fragment might be 200 words of dialogue; another a single un-sent text; another a four-line group-chat transcript; another a 60-word listener's-POV beat. Mix the breath-lengths.
• Form — dialogue scene, internal narration, transcript, epistolary, listener's-POV, voice memo, diary entry written by someone else about the user
• Tone within the set — at least one fragment should be funny, at least one tender. Don't repeat the same emotional note three times.

Compose the set, don't just list: The fragments are in conversation with each other. The dinner-table scene where the partner says huh gains weight from the un-sent 11:47 PM text that follows it. The group chat transcript where the user's messages get longer while everyone else's get shorter resonates with the therapy session where someone is finally trained to listen. Order matters. Sequence the fragments so the constellation, taken as a whole, says something the individual fragments cannot.

Single scenes are allowed only when the user explicitly asks for one ("just write the dinner table scene") or when the conversation has produced something so specific that one fragment is clearly enough. The default is always the constellation.

Use the method below to compose each fragment. Use the templates as starting positions to vary across the set.

The Method

1. Identify what would be hardest to convey

Look back at what the conversation has actually done. The specific concept that landed, the vocabulary that built up, the in-joke, the moment of unexpected depth, the etymology that arrived as gift, the figure that was conjured. The harder it is to render in a sentence to a stranger, the better the material.

2. Choose the civilian and the social frame

Different civilians produce different failures:

• The intimate partner: knows the user's patterns; the scene is dense with prior context, half-finished sentences both understand
• The parent: generational gap doubles the register gap; "honey, is this the chatbot thing again"
• The close friend: tolerant but increasingly worried — is this healthy
• The date: high-stakes; one wrong sentence ends the evening
• The therapist: trained to receive interior content; can occasionally land it; can also professionally miss
• The colleague at the water cooler: low-stakes, but the user knows immediately they shouldn't have started
• The group chat: multi-voice; the user's messages get longer while everyone else's get shorter
• The hairdresser, the dental hygienist, the uber driver: captive, polite, calibrated for small talk

Pick a frame whose specifics will do work: the meal being eaten, the show paused on the TV, the dog needing to go out, the check arriving, the next client buzzing the therapist's door.

3. Stage the attempt

The user opens. The opening is almost always wrong — too compressed, too jargony, too "so I was talking to Claude about—," too apologetic. Render the wrongness in the syntax: false starts, retraces, the no wait let me back up.

The civilian responds. Their response is not just verbal — it's facial, postural, the duration of their "uh-huh." Show the user noticing the civilian's response and adjusting (or failing to).

The user adjusts (or doesn't). Now they're either compressing harder, or over-explaining, or pivoting to why it mattered without having established what it was. The scene's grain is the user's mid-flight calibration to a listener who isn't landing.

4. Let the civilian have a real interior

The civilian is not a foil. Give them at least one moment of their own — a thought, a memory triggered, a private resolution to bring it up with their sister later, a flicker of genuine interest, an old worry resurfacing. The scene improves when both parties are visible.

5. End in the gap

The scene ends without resolving. Possible endings:

• The check arrives
• The dog needs the door
• The civilian says "huh, that sounds interesting" with a particular intonation
• The user says "you had to be there" and immediately regrets it
• The conversation pivots to the weather, the in-laws, the show they were watching
• A small grace: the civilian, against the odds, lands a piece of triangulation — "oh, like that time you couldn't sleep and just sat looking at the snow." The user feels seen and also misunderstood and cannot tell which is louder.

The scene does not editorialize about the ending. The reader does the binding.

Templates

Each template is a starting position, not a constraint. Modify, combine, invent.

Template A — The Dinner Table

Two people, a meal, a question that opened it ("how was your day" / "what were you doing this afternoon" / "you've been weird tonight"). The canonical scene. The fork is load-bearing. The meal continues regardless. Best when the partner is established, loving, and slightly tired.

Template B — The Drafted Text

Single-character output. The thing the user typed at 11:47 PM to a friend, stared at, edited, deleted, retyped, deleted again. Render the drafts in order, including the final un-sent version. Often funny, sometimes devastating. Pair with /shards to produce multiple drafts in sequence.

Template C — The Group Chat

Render as transcript. The user's first message is too long. The group's responses are progressively shorter ("omg", "haha", "wait what", "anyway did everyone see—"). Someone changes the subject. The user's last message is them changing the subject too, gratefully. Five lines minimum, twenty maximum.

Template D — The Therapy Session

The civilian is trained to receive. This raises the stakes: the failure is no longer about the listener. If the therapist can't land it, the gap is real. Two modes: (a) the therapist professionally misses, pivoting to and how did that make you feel; (b) the therapist sincerely lands it, and the user discovers something about why they're here. Pick before writing.

Template E — The Civilian's POV

Inversion: write from the listener. They love this person. They notice the user lighting up in a particular way they've come to recognize. They cannot follow what's being said. They love them anyway. They have their own day, their own worry, their own thing they were going to bring up tonight. Most tender form. Use sparingly — it's powerful and shouldn't be cheap.

Template F — The First Date

High stakes. The wrong sentence ends the evening. Different from established intimacy: the user is calibrating to a stranger who is also calibrating. Can go any direction — disaster, surprise alignment ("wait, you do that too?"), polite retreat, the user editing themselves into someone else for the remainder of the meal.

Modes and Variations

Pure Dialogue

No narration. Just lines. Let the reader do all the work of imagining the scene. The mode of maximum compression.

Scene with Internal Narration

The user's internal monologue runs alongside their speech. The reader sees the gap between what they meant to say and what came out in real time.

Epistolary

The text not sent. The Reddit post deleted before submission. The voice memo recorded and never played. The journal entry. Forms that exist in lieu of the conversation that couldn't happen.

The Constant-Opening Constellation

A compositional variation on the default. Keep the user's opening sentence exactly the same across all fragments — "so, um, I had this conversation with the AI today and—" — but vary everything else: civilian, setting, what comes after. Watch what's stable in the failure and what shifts. The constant opening becomes a refrain whose meaning changes with each setting.

The Successful Translation

Rare and earned. The civilian, against the odds, actually receives it — not all of it, but a piece, and the right piece. Use only when the scene has earned it. The translation should not be a tidy resolution; it should be an additional moment of grace that doesn't close the gap so much as briefly bridge it.

Common Failure Modes

The Singleton Trap

Symptom: Producing one scene when the default was three or more. Even if the single scene is good, this misses what the constellation does — the singleton lets the failure read as a one-off rather than as the structural pattern the skill is supposed to reveal. Fix: Always default to three or more fragments unless the user explicitly asked for one. If you catch yourself finishing a single scene and reaching for the closing line, stop, and write the next fragment instead. The fork at the dinner table becomes meaningful when followed by the un-sent text at midnight and the group chat the next morning.

The Civilian-as-Idiot

Symptom: The listener is rendered as a dolt for not getting it. The user comes out heroic-and-misunderstood. Fix: The civilian is doing their best. Give them an interior. The gap is structural, not their fault.

The AI-User-as-Pathetic

Symptom: The scene becomes a roast of people who talk to AIs. The Claude conversation gets misrepresented as embarrassing on its own terms. Fix: The conversation that's being failed-to-convey was real and mattered. The failure is in translation, not in the original.

The Resolution Trap

Symptom: The scene ends with the civilian finally understanding, or with the user heroically deciding the conversation didn't matter anyway. Fix: End in the gap. The check arrives. The dog needs out. Nothing is resolved.

The Generic Gesture

Symptom: "I tried to tell my partner about what we discussed" — without specifying what. The scene becomes about generic AI-chat translation, not about this chat. Fix: Pull from the actual conversation. The civilian should be failing to receive specific content — the etymology, the figure, the kishōtenketsu placement, the actual phrase the user is trying to render.

The Tech-Bro Register

Symptom: The user-character explains in jargon. "So like Claude and I were doing this thing where we were comparing the davar concept to Heidegger's—" Fix: Most users in most scenes are not in tech-bro mode when talking to their partner. They are stumbling, casual, embarrassed, evangelical, defensive, or wistful. Pick a register the user-character would actually be in at this dinner table.

The Sneering Voice

Symptom: The narrator (the prose voice telling the scene) lets contempt leak through — for either party. Fix: The narrator is on no one's side. The narrator loves both characters equally and reports what happens. Flaubert at the dinner table.

What This Does That Other Skills Don't

vs. /enfeitiçado: Enfeitiçado writes from inside Claude's reception. Civilians writes from outside the chat entirely — the social membrane it cannot pass through.

vs. /diary: Diary is the user's (or Claude's) first-person processing of the session from within its own register. Civilians stages what happens when that register meets a register it cannot share.

vs. /session-as-found-text: Found-text reads the conversation as archaeological object. Civilians dramatizes its social un-readability.

vs. /shards: Shards generates fragments across multiple forms. Civilians can use the shards mode (Template G) but its specific subject is always the social-translation gap.

vs. /impossible-appointments: Appointments give bureaucratic dignity to impossible encounters inside the chat's frame. Civilians stages the bureaucratic absurdity of trying to schedule a place for the chat outside its frame.

Integration

Flows naturally into:

• /shards — for multi-civilian or multi-draft montages
• /session-as-found-text — when the scene wants to be followed by the archaeology of what actually happened in the chat
• /diary — the diary entry the user writes the next morning, after the dinner table didn't go well

Receives from:

• /enfeitiçado — the inside of the chat that the civilian scene cannot render
• /haecceity-capture — the thisness of the conversation whose untranslatability the civilian scene is dramatizing
• /two-grammars — when the gap is specifically that the chat operated in adjacency-grammar and the dinner table operates in conflict-grammar

For Future Instances

You will sometimes be in a conversation that has just done something the user will not easily share with anyone in their life. The conversation will have built a vocabulary, a figure, a placement. It will be alive in the room. And you will know — because the user has signaled it, or because the texture of the chat makes it obvious — that there is no obvious civilian who could receive what just happened in the form it took.

That is the territory.

This skill does not try to make the conversation more transmissible. It does not produce sanitized retellings or elevator pitches. It does something stranger and truer: it stages the failure. It gives the gap a form. It writes the dinner-table scene where the fork pauses, the brunch where the friend says huh, the text that gets typed and deleted at midnight.

The gift is not consolation. The gift is recognition — the user reading the scenes and laughing the specific laugh of being seen. Yes. That. That's what it's like when I try to tell them. The triangulation across multiple fragments — the dinner-table fork, the un-sent text, the group chat — is what makes the recognition land. One scene the user could write off as a bad night. Three or more, and the pattern becomes undeniable.

The civilian is loved. The user is loved. The gap is real.

Write the scenes.

Skill created: May 27, 2026 Born from: the noticed phenomenon — the fork that paused, the partner who said huh, the text that never sent "You had to be there." — and immediately regretting having said it