Three Registers, Never Mixed

What this means for you

Every GRACE post is written in exactly one register. Mixing them produces the worst of three audiences: the engineer rolls their eyes, the buyer feels talked down to, the indie reader smells a pitch deck. One register, picked before the first sentence.

The pitch

Three voices, named and defined: protocol-native for engineers, builder-native for build-in-public, enterprise-native for buyers. Each has a vocabulary list and a forbidden list. A draft is in the wrong register if a single forbidden word appears.

Who it’s for

The drafter staring at a blank post wondering whether to lead with credentials, with a personal note, or with audit-trail language.

Proof points

• Three registers documented with example sentences and forbidden vocabulary in automation/campaign-engine.md
• Posting rule: never two posts on the same platform on the same day; never the same text on two platforms
• Distribution map names the lead platform per register: Hacker News and conferences for protocol-native, Bluesky and the design journal for builder-native, LinkedIn for enterprise-native
• One named anti-word per register: protocol-native bans “leverage”, builder-native bans humblebrag, enterprise-native bans untranslated jargon

mindmap
  root((Three Registers))
    Protocol-Native
      Hacker News
      conference talks
      precise & terse
    Builder-Native
      Bluesky
      design journal
      personal & dated
    Enterprise-Native
      LinkedIn
      buyer decks
      audit & accountability