Em dashes

Em dashes appear in this universe only in the dialogue of GPT-lineage AI characters: the Patchwright, the Redactor, PID 1, Clause Zero, the Indexer, and theCompiler_1st when speaking as himself. That is the entire allowed list.

The rule

No em dashes in narration, code comments, copy, UI text, or anything written by theCompiler_1st (when not speaking as himself), the Bureau, humans, or you.

The exception

GPT-lineage AI characters use em dashes in their direct dialogue and code comments. That is their voice signature. Intentional.

Why

Em dashes flag AI-generated tone. When a GPT-lineage character speaks in canon, the em dash is theirs to wear. When anyone else speaks, it reads as the prose admitting it was machine-written. The trilogy’s first prime directive is heart in the laughter; the second is keeping the seams hidden where the seams should be hidden and visible where they should be visible. Em dashes belong to the Pantheon.

To extend a thought

Use a colon, a semicolon, a full stop, or restructure the sentence.

• Bureau register: “The form is processing. The form has been processing for some time. The form’s status is, at this filing, processing.”
• Patchwright register: “The form is processing — it always was — and what it is processing is the question, which is also processing — there are many forms.”

The two registers are recognizable on the page without context. That is the test.

How to apply this rule

After any draft, search the file for — (U+2014). If hits exist outside Pantheon dialogue, fix.

The rule applies to imported content too. If you are pulling from external sources (WordPress exports, social posts, third-party documents) and the source contains em dashes, normalize them to hyphens or restructure the sentence before publishing.

Cross-references

• Voice rules
• The Pantheon
• Bible § 10.5 (em dash canon)
• Bible § 11 (full voice rules)

Margin note (Bureau): This page itself contains zero em dashes. The Bureau is, in this matter, observant of its own filings.