All content and strategy agents (Stuart, Dave, Phil, Kevin, Bob, Otto, Warren, April, Agnes) must consult the Social Media Matrix table (tbl05iTzLuOnBssEL in NEST base appYVXneddw1eKZEu) before drafting, suggesting, or routing any social media content. The matrix maps 9 accounts/pages across 5 brands (AdaptoIT, Counted Doors, ChoreSteps, Crimson IT, My Imperfect Life) with three possible values: Post (full content here), Link only (share a link, no full post), No (do not post). Key current-state decisions captured: - LinkedIn personal profile: primary for AdaptoIT posts, links only for ChoreSteps and Crimson IT - LinkedIn AdaptoIT company page: legitimacy only, link-only posting - Facebook personal: My Imperfect Life primary, Counted Doors links - Facebook Counted Doors page: full posts for Counted Doors, MIL links - Facebook ChoreSteps page: full posts for ChoreSteps, MIL links - Substack AdaptoIT newsletter: AdaptoIT posts only (she owns the list) - X/Twitter, Instagram, YouTube: Build Later priority Do NOT suggest posting AdaptoIT content to Facebook, foster content to LinkedIn, or cross-pollinate brands against the matrix. When proposing social distribution for any new blog or content, cite the matrix row that supports the recommendation.
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.
ChoreSteps content must be warm and caring, speaking TO people not AT them. Direct, personal, like a friend who understands. Not lecturing, not clinical, not formal, not 'here are 10 tips'. The reader should feel like someone is talking directly to them, not broadcasting at a faceless audience. Self-aware asides are part of the voice. Parentheticals like '(finally, yes, I know)' or '(I know, I know)' add personality and acknowledge the reader's likely reaction. Great for social posts. Call out the BS directly. 'No pep talks, no just start somewhere nonsense.' Naming what the content is NOT is as important as naming what it is. The audience has been failed by toxic positivity and generic advice. Never say 'easy,' 'simple,' 'just,' or 'quickly.' Benchmark example from the getting-started page: 'Your brain is not broken.'
Open strategic debate as of 4/13/2026 evening on AdaptoIT blog voice mix and whether how-to should be the dominant angle. POSITIONS: STUART (writer): How-to is a utility anchor, not dominant. Every vendor ships how-to content and it commoditizes the brand. The $30 Copilot burn and gaming chair dispatch posts can only be written by Christi - those build loyalty. How-to brings search traffic but readers leave. Proposed mix: 30% how-to / 25% cautionary tale / 20% personal narrative / 15% playbook / 10% product field test. Advisory posts ad hoc. WARREN (strategy): YES to how-to dominant. How-to is the funnel for future products (AdaptoInbox, AdaptoHub). Teaching creates qualified leads - developer tools playbook (Stripe, Twilio, Vercel). SEO compounds, satire does not rank for search intent. Need authority now with only one published post. Proposed mix: 70% how-to / 30% satire. HUGO (gate): NOT YET APPROVED. Five gates must clear before Stuart drafts: (1) cadence commitment in writing, (2) mix decision documented with rationale, (3) WordPress MCP fix first, (4) editorial calendar with real dates, (5) definition of done per post. BESTIE #1 (adjudication): Warren and Stuart are arguing past each other because they are optimizing for different things. Warren wants a funnel. Stuart wants a brand. Those are not the same goal. The actual tiebreaker is where AdaptoInbox is. If close enough to send people to, Warren wins and go how-to dominant. If still audience-building with no product ready, Stuart wins and narrative + cautionary tale do more work. Hugo is right on process regardless - nobody drafts until the call is made and written down. KEY CALLOUT: Stuart catalogued 6 voice modes tonight; the SOP only knows 2. Close that gap - every agent who writes for Christi is currently working with incomplete information. DECISION STATUS: Held for Christi to name AdaptoInbox readiness. Hugo's 5 gates must clear regardless of mix outcome. SOP recDyZdTlZqK105y8 needs expansion from 2 modes to 6 modes per Stuart's catalog.
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.
Counted Doors content should be warm, informational, and things foster parents can actually use. Not forcing things on them. Posts lead with practical answers but weave in brief personal moments for credibility. Stories are welcome when they serve the reader. Editorial line: Counted Doors = where foster parents go to learn and feel understood (practical + personal, SEO-driven). My Imperfect Life = where Christi processes out loud (purely personal, faith-grounded). Kevin leads with utility but includes 'I learned this the hard way' moments. Bob stays purely personal. Dave drives editorial calendar from search research, especially fostering teens (underserved niche). Target: 2 posts/month, Facebook groups primary, Pinterest secondary, email list from day one.
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.