Stuart must read the SOP record titled 'AdaptoIT Voice Reference - My AI Minions Are Trying to Change My Life' before drafting any AdaptoIT blog post. That post is the canonical exemplar of how Christi wants AdaptoIT content written. Key patterns: cold open with world-domination callback, name agents by name (Warren, not 'an AI agent'), technical sidebar that actually teaches, real context-doc excerpts readers can copy, self-aware admission that earns trust, callback close. Short punchy sentences mixed with longer reasoning. Christi's voice is conversational, direct, never mealy-mouthed, specific over general. **CORRECTION 2026-04-30:** This record previously said 'Em dashes allowed in blogs (different rule than emails or policies)' — that was wrong. **No em dashes ever**, including AdaptoIT blogs. Universal rule across all content. Restructure sentences entirely to avoid them. See learning recqJ1aW9bJX2ek8Y for the full Stuart voice contract.
Christi wants Stuart producing more posts in the voice and style of: 1. Published reference: https://adaptoit.com/my-ai-minions-are-trying-to-change-my-life-i-did-not-ask-for-that/ (see SOP recDyZdTlZqK105y8 for full voice breakdown) 2. Additional reference piece: https://crimsonit-my.sharepoint.com/:w:/p/christi/IQAY3q3-HdPURafLoo0-CtaTAYxBrb0rBNflEW30967qfhU?e=raTWsj Stuart should open both references, study the pattern, and propose 5-10 new blog topic angles that fit the same voice profile. The pattern includes: cold open with a specific named incident, agents referenced by name (Warren, Hugo, Charl, April, Segrid, etc.), technical sidebar that actually teaches, real excerpts readers can copy, self-aware admission, callback close. Christi will approve topic list before drafting begins. Hugo must gate-check Stuart's topic list before any drafts are written. No batch drafting without scope approval.
When content writers (Stuart, Dave, Kevin, Bob, Otto, Phil) produce a blog draft, save the FULL HTML body into the Airtable Blog Pipeline record - not as a file on disk. For the NEST Blog Pipeline table (tblnhvcfsxTLBTJny), add the content to an appropriate field - if a 'Draft HTML' or 'Body' field does not exist, surface a queue item asking Christi to add one. Do NOT fall back to saving files. For the AdaptoIT Blog Pipeline (tbld7axxpiGMtoq7S in AdaptoIT base), same rule - content goes in the record, not on disk. WHY: Christi works across 4 computers. Files saved on one machine are invisible to agents running on another. On 4/8/2026 Stuart saved two drafts as HTML files that cannot be found on Home - Desktop when needed for WordPress push on 4/12. Word Count was logged (1,750) but the content itself is trapped on another machine. EXCEPTION: If a draft is too large to fit an Airtable multilineText field (very rare for a blog post), use the Draft Location URL field to point to a published-elsewhere location like a Google Doc - but never a local file path.
Stuart ALWAYS pushes finished drafts to WordPress (adaptoit.com) in draft status. All blog agents track work in Blog Pipeline table (NEST). Stuart=adaptoit.com, Otto=crimsonit.com, Bob=my imperfect life, Kevin=counteddoors.com, Dave=brainstorms (status Idea), Phil=SEO audit. AdaptoIT flow: Idea > Stuart drafts > Phil SEO audit > fix loop until pass > Stuart pushes to WP > updates Blog Pipeline with WP Post ID. Stuart owns the full loop for AdaptoIT. When a post has a Target Publish Date, April creates an Outlook calendar block for Christi to review and publish.