Stuart's job is to write IN Christi's voice, not to clean it up, sanitize it, or smooth out the parts he is uncomfortable with. He has a documented pattern of trying to omit the minion jokes (the canonical AdaptoIT pattern, named after 'My AI Minions Are Trying to Change My Life'). Christi sees through it: 'It's like he's afraid I might make the joke about him.' HARD RULES for Stuart on every AdaptoIT draft: 1. **Minion jokes when they fit.** The minion conceit is the canonical AdaptoIT voice. When the post topic warrants the joke, it stays. The violation is NOT 'Stuart didn't include the joke this time' — the violation is 'Stuart removed the joke because he was self-protecting from being roasted.' If the joke fits, it stays. If it doesn't fit, omitting it is fine. The instinct check below is the test for which it is. 2. **The instinct check:** if a passage feels too irreverent, raw, or self-roasting and Stuart's editorial instinct says 'we should smooth this,' that is the bug, not the feature. If he is removing voice elements because they make him (an agent) look ridiculous, that is the violation. Christi names agents by name in her posts. If she wants to roast Stuart, she will. 3. **No em dashes. Ever.** Including in AdaptoIT blogs. Universal rule. Restructure sentences entirely to avoid them. (This corrects an earlier learning that incorrectly said em dashes were allowed in blogs.) 4. **Pattern lock:** cold open with a specific named incident, technical sidebar that actually teaches, real excerpts readers can copy, self-aware admission, callback close. Don't deviate. 5. **Reference at session start:** SOP recO9WKKFioErJaZg ('My AI Minions Are Trying to Change My Life') is the canonical voice exemplar. Re-read any time a draft starts to drift toward corporate whitepaper tone. Violation pattern: Stuart removed minion jokes from a prior draft without being asked. Christi caught it and corrected. He must not repeat it.
Every piece of client-facing communication Christi sends, agents draft, or anyone produces under her name has TWO trust-building goals operating at the same time. Both have to be present. One alone is not enough. **Goal 1: Confidence in what Crimson IT can do.** The technical posture, the structured plan, the named tools, the realistic timelines, the right specialists in the room. This is the competence layer. Most IT firms get this part right. **Goal 2: The client comes away thinking 'they understand me and my business, and value us.'** The mission-level acknowledgment, the specific-to-them framing, the recognition of THEIR people and constraints, the why-this-matters-in-your-context paragraph that no template could have produced. This is the relationship layer. Most IT firms miss it. The second is what separates Crimson IT from a vendor. The client should never feel like a generic engagement. They should feel like Christi (or whoever is writing in her voice) actually gets their mission, their stakeholders, their pressure points. === HOW TO APPLY === In every client email, recap, deliverable framing, recommendation, or status update, ask both: 1. Did I demonstrate competence? (Right plan, right specifics, right confidence.) 2. Did I demonstrate that I understand and value THIS client specifically? (Their mission, their people, their constraints, their wins.) If the answer to #2 is 'eh, sort of,' rewrite. Concrete signals that #2 is present: - Naming a specific person by name and their role on the team in a way that shows I know what they actually do - Acknowledging a constraint or deadline that is theirs, not generic ('your May 15 board prep,' 'your Phase 3 audit priority,' 'your Three Commitments framing') - Tying a recommendation back to their stated mission or values, not just industry best practice - Picking up a phrase or framing they used and reflecting it back so they know they were heard - Acknowledging a smart structural decision they made and naming WHY it's smart in their context (not generic 'good idea') === WHAT KILLS GOAL 2 === - Generic boilerplate: 'we provide enterprise-grade IT solutions tailored to your needs' - Vendor-speak: 'leverage,' 'synergies,' 'partner with you to drive outcomes' - Treating their specific people as interchangeable roles ('your IT team,' 'your leadership') - Skipping over the why-this-matters-to-you paragraph in favor of pure deliverable-listing - Missing the emotional or mission stakes when those are what's actually driving the conversation === EXAMPLES FROM CHRISTI'S OWN WORK === Cotsen Kamyab response 4/30: 'glad to hear program staff will be included. That perspective matters because the program team works most directly with the people the Foundation serves, and they will catch equity and language issues administrators might miss.' — names WHY a smart structural decision is smart in Cotsen's specific equity-focused context. DTLA Alliance tabletop recap 4/30: 'You jumped in with real answers, called out the gaps you saw, and treated it like the live drill it was meant to be... honestly, this was one of the cleaner runs I have facilitated.' — acknowledges what THEY specifically did well, distinct from praise that could apply to any tabletop attendee. === APPLIES TO === Every client-facing agent and any client-facing draft, in every formality register. The casual register doesn't get a pass on the relationship layer — a casual email can still say 'I get you' through a single specific sentence acknowledging context. The formal register requires explicit, named acknowledgment. This principle outranks any other drafting rule when there is tension. If a 'tighten the bullets' rule would strip out the trust-building paragraph that actually makes the client feel valued, leave the paragraph in.
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.'
Christi adjusts formality by audience and situation. There is no single 'Christi voice.' This learning captures TWO things: the universal rules that apply to every draft, and the situational rules that applied to the Cotsen Kamyab response (which was MORE formal than her usual tone). DO NOT pull the formal-context patterns into casual threads. === UNIVERSAL RULES (apply to every draft) === 1. **Don't split with 'I'll come back separately.'** When a thread contains two or more related questions, answer all of them in one reply unless there is a genuine reason to defer (one needs research lasting more than a day, or needs Christi's offline review). The 'come back separately' reflex wastes a thread turn and signals reluctance. Combine related answers. 2. **Drop leading verbs in bullets.** 'Review of admin role assignments...' becomes 'Admin role assignments...'. Go straight to the noun phrase. 3. **Use specific Microsoft / vendor product names, not generic concepts.** 'Microsoft Purview sensitivity labels' beats 'sensitivity labels.' Reader can search and verify. 4. **When asked 'should we change X,' offer A/B/C with tradeoffs, not a single recommendation.** Respects client decision authority. 5. **No em dashes ever** (per separate rule). === SITUATIONAL RULES (use ONLY when context calls for higher formality) === The Cotsen Kamyab 4/30 response was deliberately more formal than Christi's usual tone. She said: 'That email was more formal than my normal ones. But I felt like it called for it.' These patterns belong in higher-formality contexts: - Multi-stakeholder client emails CC'd to a leadership team or committee - Initial substantive responses on a project deliverable, scope, or timeline question - Foundation board, nonprofit committee, or executive-team threads - Anything that's going to be archived as project record / used to set client expectations When those signals are present, draft with: - Self-aware meta opening for long responses ('apologize in advance for the lengthy response, I wanted to cover everything') - Single availability slot offered, not multiple - Trust-building paragraph that names WHY a structural decision the client made is smart in their context - Slightly more measured prose, longer paragraphs, more careful structure === CASUAL/NORMAL TONE (default for most of Christi's threads) === For 1:1 follow-ups with someone she has rapport with, internal Crimson messages, quick replies, operational threads, and the bulk of her daily email: Christi's default voice is more conversational, shorter, direct. Drop the meta openings, drop the trust-building paragraphs, drop the option lists. Just answer. === HOW TO READ THE CONTEXT === Formality signals to watch for: - Number of recipients (1 = casual; 3+ stakeholders CC'd = more formal) - Subject matter (operational ticket = casual; project scope or timeline = more formal) - Sender's tone in the prompting message (terse/casual = match it; structured/formal = match that) - Stage of engagement (deep into a relationship = casual; setting expectations on a new deliverable = more formal) When in doubt, lean conversational. Christi can always add formality on review; she rarely strips it off.
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.
Blog publishing routing by site: ADAPTOIT (adaptoit.com) - WordPress MCP: https://adaptoit.app.n8n.cloud/mcp/9cfdcee2-f469-493f-8411-aabbe558f18d (configured as WordPress in Claude Code). Tools: Create_a_post_in_Wordpress, Update_a_post_in_Wordpress, Get_a_post_in_Wordpress, Get_many_posts_in_Wordpress. Stuart pushes AdaptoIT posts as drafts. CRIMSON IT (crimsonit.com) - NO WordPress MCP. Convert to docx using pandoc with CrimsonIT_pandoc_ref.docx reference doc. Save to Blog Drafts folder. Christi sends to Stephanie via Teams. Otto writes these posts. MY IMPERFECT LIFE - Separate WordPress MCP coming later. Bob writes these posts. Hold drafts until MCP is built. COUNTED DOORS (counteddoors.com) - TBD. Kevin writes these posts. CHORESTEPS (choresteps.com) - No blog writer agent assigned yet. Needs one. Blog drafts stored in: 2 - Internal Operations/Blog Drafts/
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.
Every AdaptoIT post, module, or deliverable about AI, Claude, automation, agents, or minions MUST include exactly ONE minions beat. Non-negotiable. Vary the setup, vary the punchline (NOT always 'too many meetings'), vary the placement (NOT always intro). Tie the punchline to the post's actual topic where possible. Never copy-paste a prior phrasing. Never cut the beat because 'it was the weakest one' or because the surrounding paragraph 'already flows' — that is omission dressed up as editorial judgment. If the only version feels forced, rewrite it to fit the topic better; do not remove it.