Campaigns & Content Strategy

The Campaign Engine governs how Grace orchestrates content derivation across platforms, timelines, and audience registers. Every artifact (spec section, RFC, feature release) flows through a standardized derivation chain, producing platform-optimized derivatives while maintaining voice consistency and preventing message fragmentation.

Core Principles

1. Single-source derivation — One artifact generates multiple platform-specific pieces
2. Register purity — Never mix protocol-native, builder-native, and enterprise-native registers in a single post
3. Platform authenticity — Each platform gets native content, never cross-posts the same text
4. Phantom concept prohibition — Every reference must map to real, deployed, verifiable artifacts
5. Infrequent mythology — The chocolate factory and Martian narrative work best as ambient texture, not forced motifs

Content Derivation Flow

Source Artifact
  │
  ├── Design Journal Entry (1,200–2,000 words)
  │     └── stratt.engineer/blog/
  │
   ├── Technical Thread (5–8 posts, 3–14 days)
   │     ├── Bluesky — posts first
   │     └── X — same-day mirror
  │
  ├── LinkedIn Post (enterprise framing)
  │     └── Professional accountability angle
  │
  ├── Reddit Posts (standalone technical contribution)
  │     ├── r/aerospace — credential-led analysis
  │     └── r/AskComputerScience — if methodologically relevant
  │
  ├── Discord Announcement
  │     └── Spec discussion thread + build log
  │
  ├── Show HN Post (major milestones only)
  │     └── Lead with problem, not product
  │
  └── Threads Post (+1 day)
        └── Brief, personal register

Rule: Never post identical text to two platforms. Each derivative adapts voice, length, and framing to its specific audience.

---

The 10 Campaign Trails

Each trail is an independent narrative sequence with its own theme, cadence, and audience targeting. All trails run in parallel, scheduled to avoid message collision.

Trail Definitions

ID	Trail	Theme	Handbook	Register	Cadence	Status
CT-01	FILM_WAVE	Project Hail Mary cultural moment	HB-01	builder-native	7-post sequence, event-triggered	Design
CT-02	STRATT_ORIGIN	Naming story — NTP stratum, Eva Stratt	HB-01	builder-native	6-part arc, ~weekly	Design
CT-03	AEROSPACE_BRIDGE	Boeing 777X, SES Astra, DO-178C credentials	HB-01	protocol-native	Every 10 days	Design
CT-04	SOL_LOG	Weekly status updates (active build log)	HB-02	builder-native	Weekly, consistent time	Design
CT-05	PROTOCOL_NATIVE	CRDT, addressing, gates, blast radius deep dives	HB-01	protocol-native	Monthly in-depth article	Design
CT-06	DOMAIN_ACTIVATION	7-domain rollout narrative (software → neuro → finance → …)	HB-02	enterprise-native	Weekly during rollout phases	Design
CT-07	MERIDIAN_BUILD	Documentation architecture narrative (public build log)	HB-02	protocol-native	Per milestone	Design
CT-08	NULL0_EMERGENCE	Identity reveal arc (Phase 3 trigger — launch announce)	HB-01	builder-native	Strategic, infrequent	Planned
CT-09	CHOCO_SIGNAL	Ambient hints toward Choco HQ platform integration	HB-03	builder-native	Infrequent, subtle	Design
CT-10	REDDIT_BRIDGE	Aerospace-credentialed community engagement	HB-01	protocol-native	2x/month, deep technical	Design

---

Three Audience Registers

Every piece of content is written in exactly one register. Mixing registers dilutes message clarity and violates audience expectations.

Protocol-Native Register

Audience: Engineers, Hacker News, GitHub discussions, conference talks, academic venues.

Tone: Precise, terse, architecture-first, rigorous technical depth (DO-178C level of specification).

Vocabulary: Blast radius, fingerprinting, DAG invariants, exit codes, Merkle trees, canonical serialization, SPUH encoding, FM (failure mode) codes, council governance.

Example:

Publishing at the same version with different content is a SPEC-02 violation — the composition fingerprint of every dependent chain becomes invalid. Downstream CI catches this as FM-01 (fingerprint tamper), and the chain fails to execute.

Avoid:

• Marketing language (“revolutionary”, “unlock”, “leverage”, “journey”)
• Emotional framing (“we believe”, “we’re excited”)
• Excessive metaphor

Length: 800–3,000 words (technical articles); 100–200 words (social posts)

Builder-Native Register

Audience: Indie hackers, Bluesky creators, design journal readers, build-in-public communities.

Tone: Honest, personal, origin-story authentic. Lowercase, unguarded voice. Emphasizes the “why” and personal motivation.

Vocabulary: Aerospace background, chocolate factory mythology, Martian naming conventions, solitary building, constraints that drove design choices.

Example:

I spent three years tracing requirements to test cases for aircraft software—every change had to be auditable, every execution fingerprinted. Then I watched AI agents produce plausible-looking output nobody could verify. So I built the same discipline for prompts: fingerprints, gates, audit logs. Grace isn’t a product. It’s how I think about trustworthy automation.

Avoid:

• Humblebragging (“I’m just a solo dev”)
• Vanity metrics
• Excessive self-deprecation
• Forced vulnerability

Length: 400–2,000 words (design journal); 50–150 words (social posts)

Enterprise-Native Register

Audience: LinkedIn professionals, enterprise architects, compliance officers, procurement, C-suite.

Tone: Accountability-focused, compliance-focused, risk-reduction framing. Translates technical concepts into business outcomes.

Vocabulary: Immutable audit logs, fingerprint-verified execution, gate-audited chains, tamper detection, compliance, governance, risk reduction, audit trail.

Example:

Every AI chain execution is fingerprint-verified, gate-audited, and written to an immutable audit log. When your AI agent makes a decision, you can retrieve exactly which prompt ran, at which version, approved by whom, and when—for compliance, for debugging, for accountability.

Avoid:

• Technical depth that loses non-engineers
• Protocol-specific jargon without translation
• Overpromising (“magic”, “revolutionary”)

Length: 300–1,200 words; LinkedIn posts 100–250 words

---

Distribution Cadence

Content Type	Frequency	Platforms	Register
Sol Log (weekly status)	Weekly, same day/time	stratt.engineer, Bluesky, X	builder-native
Design Journal Entry	Monthly	stratt.engineer (primary); Bluesky, X, LinkedIn, HN	varies by content
Technical Deep Dive	Monthly	stratt.engineer, Reddit, Dev.to	protocol-native
Council Spotlight	Monthly	Discord, Bluesky	protocol-native
Release Changelog	Per release	GitHub Releases, Discord, stratt.dev	protocol-native
Conference Talk	Quarterly	Strange Loop, QCon, AIEngineer Summit CFP	protocol-native

---

Social Posting Rules

1. Never post identical text to two platforms (adapt for platform norms)
2. Never delete a post (own it, engage with criticism, or let it stand)
3. Never force mythology — if the metaphor doesn’t fit, don’t use it
4. Links appear strategically: Day 1 and Day 8 of a distribution cycle, not every post
5. Bluesky posts first → X same-day → Threads +1 day → LinkedIn for enterprise pieces only
6. Reddit posts are standalone technical contributions, never cross-posts with mythology
7. One platform per day — never post to the same platform twice in 24 hours
8. Sol Log consistency — post every Friday at 9am PT (consistent ritual)

---

Blog-to-Social Derivation Trigger

When a new blog post publishes at stratt.engineer:

Day	Platforms	Register	Format	Goal
+1	Bluesky + X	builder-native	Announcement + link	Drive traffic to blog
+3	Bluesky + X	protocol-native	One technical angle, no link	Expand on specific insight
+5	Reddit (1x)	protocol-native	Standalone post (no link)	Community engagement, credentials-led
+8	LinkedIn	enterprise-native	Methodology angle + link	Professional reach
+10	Bluesky + X	builder-native	Second angle or callback, no link	Extend conversation
+12	Reddit (1x)	protocol-native	Different subreddit if applicable, no link	Reach different community
+14	Bluesky + X	builder-native	Closing thought	Close the cycle

---

Campaign Launch Checklist

Before launching a campaign or advancing a trail:

• Identify trail — which CT-01 through CT-10 does this advance?
• Confirm handbook — which HB-01/02/03 does this support?
• Confirm register — protocol-native, builder-native, or enterprise-native?
• Check platform calendar — no other campaign posting to same platform today?
• Draft in register — verify tone, vocabulary, and absence of marketing language
• Audit for phantoms — every reference must map to real, deployed artifacts. No imagined features, no “planned” items presented as live
• Get approval — AJ’s “send it” before posting

---

Campaign Cadence Calendar

Week 1          Week 2          Week 3          Week 4
Mon–Fri         Mon–Fri         Mon–Fri         Mon–Fri
├─ CT-04 Sol    ├─ CT-04 Sol    ├─ CT-04 Sol    ├─ CT-04 Sol
│  (Fri 9am)    │  (Fri 9am)    │  (Fri 9am)    │  (Fri 9am)
├─ CT-03 posts  ├─ CT-06 posts  ├─ CT-03 posts  ├─ CT-10 posts
│  (Tue/Thu)    │  (Mon/Wed)    │  (Tue/Thu)    │  (Mon/Fri)
└─ CT-05        └─ CT-07        └─ CT-02        └─ CT-09
   (monthly     │  (milestone)   │  (narrative   │  (ambient)
   deep dive)   │                │   arc)        │

---

Campaign Activation Examples

Example 1: GRACE Spec Publication (CT-05 + CT-07)

Handbook: HB-01 (Protocol Authority)
Registers: protocol-native + builder-native

Timeline:

• Day 0: Spec published at stratt.dev
• Day 1: Bluesky (protocol-native) — “GRACE spec v1.0 is live. Five layers, three council systems, one fingerprint format. All traced.” + link
• Day 3: Design journal (builder-native) — “How I ended up designing a specification for trustworthy AI”
• Day 5: Reddit/r/compsci (protocol-native) — In-depth post on SPEC-02 fingerprinting design
• Day 8: LinkedIn (enterprise-native) — “Every AI decision should be auditable”

Example 2: Neuro Domain Launch (CT-06)

Handbook: HB-02 (Community Flywheel)
Register: enterprise-native

Timeline:

• Week 1: Sol Log (builder-native) — “Neuro domain launching next week”
• Day +1: LinkedIn (enterprise-native) — “30 units designed for biomedical research. Here’s how the pipeline worked.”
• Day +3: Bluesky (builder-native) — Personal origin story with Katy Hole mention
• Day +5: Discord announcement — Dendrite council introduction

---

Content Metrics & Success

Track these KPIs per trail (monthly review):

Metric	Target	Platform
Blog post traffic (unique visitors)	500+/post	stratt.engineer
Social engagement (likes/shares)	50+ per post	Bluesky + X
Reddit karma (net upvotes)	100+ per post	Reddit
LinkedIn impressions	2,000+	LinkedIn
Discord activity (replies)	10+ per announcement	Discord
Conference acceptance	2–3 talks/year	Speaking

---

See Also

• Marketing KPI Tracker
• Handbook: Protocol Authority (HB-01)
• Campaign Trail Definitions