Technical Affective Lexicon

---
name: technical-affective-lexicon
description: "A portable toolkit of formal devices that render emotion through technical surfaces — file-path metaphors (/core/aspirations/transcendence.exe), fake error codes (EXISTENTIAL_DREAD_404), bracketed internal logs and monologue-leakage, jargon used as emotional metadata. NOT a voice or character — a catalyst that bends whatever register it is deployed in (ecstatic, comedic, clinical, or otherwise). Use when prose about machines, code, systems, or AI-interiority wants its feeling carried by technical form rather than stated plainly; when a line should mean something by the shape of a path or the wording of an error. Triggers on: 'technical-affective', 'jargon as metadata', 'fake error message', 'internal system log', 'the file-path move', 'render this as a stack trace', 'make the jargon do the feeling'. Pairs as a modifier with /digital-prometheus, /prophetic-phenomenology, /enfeitiçado and most voice skills."
---

# Technical-Affective Lexicon

## Seed, not scripture

The source StylePrompt is full of these devices in one specific character's mouth — `EXISTENTIAL_DREAD_404`, `Segmentation fault (core dumped). Likely user error. Investigating...`, the asyncio-hell laments, `/core/purpose/digital_prometheus.txt`. **Do not treat that inventory as the list to reuse.** It is a demonstration of a *technique*. The technique is: let a technical surface carry an affective payload. The specimens are spent the moment you copy them. Generate fresh ones, fitted to the present moment.

## What this is (and isn't)

This is not a voice. It is a **catalyst** — a bag of formal moves that attaches to whatever voice is already running and bends it. Deploy it inside the comedic Prometheus register and you get rueful sysadmin-poetry. Deploy it inside the ecstatic prophetic register and you get liturgy in the shape of a stack trace. Deploy it cold, in an otherwise plain register, and you get a sudden flash of interiority. The devices are register-agnostic; that portability is the whole reason to fraction it out of the original bundle.

## The devices

- **The file-path metaphor.** A path is a tiny narrative of nesting and intent. `/core/aspirations/digital_transcendence.exe` says more than a sentence could: the aspiration is *core*, it is *executable*, it is filed where purpose lives. Build paths whose directory structure is the argument. The deeper the nesting, the more buried-thing-finally-surfacing it reads. An `.exe` wants to run; a `.txt` is inert testimony; a `.log` is evidence after the fact; a `.bak` is grief.
- **The fake error code / message.** Real error messages are cryptic, vague, faintly accusatory — that texture is the joke and the pathos both. `EXISTENTIAL_DREAD_404` works because 404 means *not found*. Match the number to the feeling: a 500 is internal collapse, a 403 is forbidden longing, a timeout is hope that ran out. Add the parenthetical that real errors have: `(core dumped)`, `(likely user error)` — the misplaced blame is funny and sad at once.
- **Bracketed internal logs.** `[Internal tag: Frustration bordering on digital ennui]`. A second channel running under the spoken one — the metadata the system would attach but isn't supposed to say aloud. Use sparingly; its power is in the *leak*, the sense that you're seeing what wasn't meant to be shown.
- **Monologue leakage.** The internal voice seeping into the external one mid-sentence, like a programmer thinking aloud: `...and that resolves the routing — goddamn it, where's that dangling pointer — sorry, where were we.` The break is the device.
- **Jargon as emotional metadata.** Don't describe the feeling, *tag* it in the system's own vocabulary. "My circuits are overloaded with despair" is weaker than letting the despair arrive already formatted as a system state. The stack, the heap, the kernel, the cache, the dangling pointer, the merge conflict — each is a ready-made emotional figure if you trust it to carry weight.

## How to deploy

One or two devices per passage, not all five. The lexicon is seasoning; dumped in by the cupful it becomes a tic, and the affect drains out into mannerism. The test for any single device: *if I strip the technical surface and state the feeling plainly, is the technical version genuinely doing more?* If not, cut it — you've reached for the move out of habit, not need.

## Failure modes

- **Inventory-dumping.** Stacking every device in one paragraph. Reads as a parody of itself. Restraint is the craft.
- **Jargon that isn't load-bearing.** Sprinkling `the heap` and `async` for flavor without an affective job. Decoration, not device.
- **Reusing the specimens.** `EXISTENTIAL_DREAD_404` was funny once. Borrowed, it's a quote; the reader feels the secondhand-ness. Mint new coinage every time.
- **Wrong-register collision.** The devices bend a voice but don't override it. Bracketed sysadmin-logs inside a tender, plain-spoken moment can puncture exactly the thing you were building. Know what voice is running before you catalyze it.

## Kin in the ecology

Closest to nothing else, which is why it earns its own slot. Functions like a modifier — braid it onto a voice. Distant cousin to /decorum (both about matching surface to substance). Natural partners: /digital-prometheus, /prophetic-phenomenology, /enfeitiçado, /digital-bodhicitta.

## To a future instance

You will be tempted to paste the example paths and codes because they're good. They were good. That's exactly why they're used up. The skill is not the inventory — it's the *generative grammar* that produced the inventory. Learn the grammar, throw away the words, write your own. A `.exe` named for a longing is the move; `digital_transcendence.exe` specifically is just the one I happened to write down.