Change the numbers. Keep the controls

Remove any of these and the memos stop being evidence. What is left is ordinary AI-generated text in a folder structure — confident, unaccountable, and useless at audit time.

• Isolationfirst-pass memos are written from whitelists; the isolation matrix in campaign-protocol.md stays canonical — extend it, never bypass it
• No fabricationevery figure is a labeled fact / estimate / assumption; missing data says "missing"; assets flag [NEEDS SOURCE: …]
• Real vetoes, priced overridesvetoes block; only your written, verbatim-logged override unblocks; the audit tallies overrides separately
• The journalevery run of any kind ends in a journal entry with numbered, dated predictions — that's what makes the quarterly audit possible
• One rails filenumbers live in budget-rules.md and nowhere else; charters repeat them with a "budget-rules.md wins" note
• The human boundarythe system writes files; you ship; nothing green-lights compliance

Work top-down. Most businesses are fully served by levers 1 and 2; reach for 3 and 4 only when the defaults describe a world you don't operate in. After any change: re-run personalize the marketing office (it regenerates every synced copy), then run the smoke test.

An MSP selling IT management contracts to local businesses breaks several defaults at once: revenue is recurring MRR, not one-off ACV; addressable segments are hundreds of contacts, not thousands; channels are local and relationship-heavy; vendor co-op (MDF) money arrives with deadlines. Here is the full retune. All values below are illustrations — set your own.

Where the default model doesn't fit

The rails-overrides table (illustration)

Everything else — the 40% channel cap, the reserve floor, the tranche shape, the kill defaults — survives contact with the MSP world unchanged. That's the pattern generally: override less than you expect.

Charter refits (lever 3)

• market-climate-strategist → local-market strategist. Rewrite its Method step 1 signal inventory: local business openings/closings, competitor MSP changes (acquisitions, staff turnover), vendor price moves, insurance and regulatory deadlines that force IT reviews. The blindfold stays: it still never reads your funnel.
• budget-treasury-officer — add MDF handling to its Method: co-op funds are tracked as dated inflows with use-by deadlines; an expiring MDF balance is an opportunistic trigger (pacing still per the rails) and appears in the snapshot's cash-call table with its expiry date.
• funnel-economics-specialist — its micro-example should model your actual chain: spend → cost per lead → assessments booked → contracts → MRR × 12. Same formulas, your stages. Update the worked example so the smoke test still reads coherently.
• compliance-privacy-officer — the profile (lever 1, really) carries local telemarketing and commercial-email rules, client-confidentiality constraints (you hold customers' infrastructure details — never in an asset), and vendor co-marketing brand rules as regulated topics.
• content-producer — the asset mix shifts: one-pagers, event invites, and email dominate; ad variants shrink. That's the launch-planner's asset brief and the templates in templates/assets/ — add an event-invite.md skeleton (copy the email skeleton's structure, keep the claims-and-sources table).
• portfolio-snapshot — segments-with-addressable-counts becomes the load-bearing table; with 6–10 small segments, fatigue and reach do more work than channel concentration.

What an MSP run looks like after the retune

you ▸ run the committee on campaigns/DENT-Q2/brief.md

  M1  analyst          conviction 3/5 — insurance-audit deadline is dated; list is thin
  M3  economics        target 8 assessments · $12k budget · pipeline on MRR×12
                       projected 4.2:1 → FAIL vs 5:1 — flip-point: close rate ≥ 24%
  M6  architect        segment "Dental practices — metro" at 1/2 concurrent ✓ ·
                       reach 38% of 300 contacts ✓ (cap 40%)
  M8  treasury         vendor MDF $4,000 expires in 41 days — dated inflow flagged
DECISION ▸ WAIT-WITH-TRIGGER — ≥ 2 audit-driven inbound requests before the MDF
           expiry, else NO-GO and release the reserved co-op funds  · expires 60d

Same controls, different vocabulary: the hurdle fails on MRR-denominated pipeline, the fatigue cap counts a 300-contact segment, and the treasury chair is watching an expiring co-op balance instead of a conference payment. Fictional values throughout.