# Pitfalls

Failure modes that have surfaced across TSL8 drafts. If the envoy sees one of these, it names it.

## Manifesto, not proposal

The cargo reads like a statement of belief rather than a thing that can be done, declined, or funded. Watch for:

- First paragraph is about values, not the intervention.
- No numbers, no mechanism, no timeline.
- The asks are about agreement ("do you agree?") instead of action.

**Fix:** Ask the author for one concrete change the world would undergo if this succeeded. Put that change in the cargo sentence.

## Mechanism before harm

The cargo leads with how it works instead of what it fixes. The reader has to parse three paragraphs of apparatus before they learn what pain it addresses.

**Fix:** Swap. The harm is the hook; the mechanism earns a hearing once the harm has landed.

## Smoothing protest into reasonableness

The author is angry, or weary, or aggrieved. The envoy (or the author, self-censoring) has rewritten the cargo into a measured, professional, *reasonable* voice. Now it reads like a policy memo from someone who doesn't actually care. The emotional cargo has been deleted and replaced with varnish.

**Fix:** Restore the load-bearing phrases. "This isn't working for us." "I'm tired of being asked to pretend." A protest in a neutral voice is a worse protest. Sometimes it is not a protest at all anymore.

## Pitch voice in a personal letter

The author has defaulted to pitch register because pitch register is easy. The recipient is not a market; they are a specific person. Words like "leverage," "opportunity," "optimize," "value-add" in a letter to your sister mean the cargo has the wrong voice.

**Fix:** Ask the author what they would say out loud, in the same room, on a Tuesday. Write that.

## Scope creep mid-argument

The cargo begins as "a ballot proposition for a tithe on tech billionaires" and by page three has acquired a universal basic income, a land value tax, and a new national holiday. Each addition weakens the thing by forcing the reader to adjudicate more.

**Fix:** Ask the author what the *smallest* version of the thing is that still matters. Cargo that. Put the rest in an appendix or a separate TSL8.

## The kill-shot is missing

A ballot proposition with no opposition paragraph. A product pitch with no "this might not work because." A letter with no "I may be wrong about this."

The envoy refuses to ship a TSL8 without a named way the idea dies. Not because every idea has to survive — because an idea that cannot be killed cannot be pressure-tested, which means it cannot be read the way TSL8 wants to be read.

**Fix:** Write the kill-shot. If the author can't, write the voice note for the envoy: *The author did not identify a kill shot. The reader should supply one.* That is the honest version.

## Cheerleading added by AI

The envoy, under prompting pressure, adds "Excitingly," "Importantly," "It's worth noting that," "This groundbreaking idea." These are not in the source. They are the AI filling silence.

**Fix:** Strip. The envoy's job is to hand the cargo over, not to decorate it.

## Specifics abstracted away

Source material says "peristaltic pumps like dialysis machines use." Envoy renders "adjacent medical device technologies." This is a worse sentence. The specific is what makes the cargo credible.

**Fix:** Preserve named industries, named components, named statutes, named precedents. If the envoy doesn't recognize a term, it asks — it does not generalize.

## The asks are fake

"Thoughts?" "Open to feedback." "Let me know what you think." None of these are asks. They are social openings that give the reader no purchase.

**Fix:** Each ask must be a verb the recipient can do. *Push on the thermal math. Tell me if the coalition map is wrong. Introduce me to one person who's seen this fail before.*

## The verification block is decorative

The author has pasted a LinkedIn URL but the block otherwise reads as ornament — no source chain, no envoy-permission line, no clear statement of what the recipient is being asked to take on faith and what they are not.

**Fix:** The verification block is load-bearing. See `verification.md`. If it's not load-bearing, the TSL8 is unsigned mail.

## "AI wrote this" undertone

The cargo reads like every other AI-shaped document: three-sentence paragraphs, careful parallelism, no surprising word choices, no idiom, no rhythm. The reader senses it in the first ten seconds and disengages.

**Fix:** Restore the author's idiom. Preserved phrases (see `voice.md`). Odd sentence lengths. The one sentence they wrote that is slightly too long. A TSL8 should read like a person who has been edited, not like a document that has been generated.