What I run.

Marketing — and the AI prototypes that power it

For GIG, Articulate is a marketing business around an AI operator. The AI is how I deliver marketing assets. I run best-in-class marketing workflows, and assemble wrappers and tools into working prototypes that prove an idea or speed the work.

The tech, by marketing activity

The execution layer of SimonCMO's framework (V1) — three tiers, stage → workflow → tools. Above it sits the strategy gate (Diagnose → Decide → Execute → Measure) that governs what gets built before any tool is picked. framework: SimonCMO · Ritson × Hormozi · V1

Market entry, the motion, and the offer (Hormozi: fix the offer before the spend).

Firecrawl SerpApi Serper Ahrefs SimilarWeb

Claude OpenAI

Define and find the right buyer (where the B2B enrichment lives).

Apollo Clay Lusha People Data Labs Datagma Apify

Cut the audience into addressable groups.

Claude Airtable

The strategic choice that governs everything after it (Ritson: STP & positioning).

Claude Notion

Recraft Figma Canva

The always-on structure and calendar.

Airtable Notion

A timed push against the programme.

Claude Canva

Where most of the workflows live.

Claude Firecrawl

Claude OpenAI

Higgsfield

Higgsfield QuickCut ffmpeg yt-dlp

ElevenLabs

Recraft Leonardo Canva Figma

Vercel Cloudflare GitHub

Measurement instruments every stage and feeds back (test-and-learn).

OmniSocials LinkedIn X Instagram WhatsApp Telegram

Google Analytics Supermetrics Amplitude Airtable tufte-viz

Rival IQ Ahrefs

Stack at a glance

The tools the agents actually call.

Claude / Claude Code OpenAI API OpenRouter Higgsfield ElevenLabs fal.ai Leonardo Ollama (on-prem) Nous · Hermes Airtable Cloudflare Supabase Tailscale Backblaze B2 Notion Figma Canva Slack HubSpot WhatsApp bridge Firecrawl · Apollo Mac Studio M4 Max

Hardware & infra

• Compute: Mac Studio M4 Max, 36 GB — single production origin (serves every site, runs the on-prem LLM, hosts media + automation). 100.82.41.69
• Also on the tailnet: Mac Pro 100.111.173.9 (Claude + vault), Mac mini (M1 · 8 GB) 100.119.127.41, Hostinger VPS (planned — Hermes daemon host)
• Storage (direct-attached / TDAS): 4 TB + 8 TB + 8 TB + 2 TB + 2 TB — the MEDIA Concat array + scratch. The 2026-05-17 wipe hit the 8 TB member.
• Home network: Neo fibre — 1 Gbps down / 500 Mbps up.
• Cloud hosting: Vercel — every public site + this page, on a global edge CDN.
• Edge: Cloudflare — registrar, DNS, TLS, CDN, tunnels — driven live via the Code Mode MCP. Zones articulate-ai.work + famflix.app
• Mesh / backup / alerts: Tailscale private mesh · Backblaze B2 · ntfy push

Models

Local models on the Studio — T1 · Ollama · $0 · zero egress

Three tiers — T1 local (Studio, Ollama) · T2 cloud-open (OpenRouter / DeepSeek) · T3 frontier (Claude / GPT). Agents route per task; GIG data → T1 only, zero egress. Source: Claude/models.md. Local agents are provisioned LibreChat-style (per-agent params + knowledge files); the local agent host (LibreChat) is live on MacPro at 100.111.173.9:3080.

APIs & subscriptions — the keys I hold

The full register of what the stack bills against. source: Claude/credentials.md · ~35 services

AI & generation

Infra, deploy, storage & agent host

Data, search & research

Social, distribution & comms

Media stack (StudioServer)

MCP / connector layer

Loaded at session start, available to any project.

Marketing & brand

Ahrefs Amplitude Canva Figma HubSpot Klaviyo Notion SimilarWeb Slack Supermetrics Atlassian Box Gong Granola M365 SEO plugin (25 skills)

Data & control

Airtable Cloudflare Code Mode Supabase Firecrawl Apollo Higgsfield PDF + doc skills (pdf/docx/xlsx/pptx)

Workspace & comms

Gmail Calendar Drive Apple Notes WhatsApp bridge Chrome / computer-use

Client capture — everything lands in the vault by itself

The intake surface that keeps me current without manual note-taking. spec: Claude/whatsapp-pipeline.md · locked 2026-05-21

• WhatsApp bridge (open-source whatsapp-mcp, runs on my Mac, DB never leaves the laptop) — every client message + call captured.
• Voice notes → Whisper / ElevenLabs Scribe — .opus auto-transcribed to text in the vault.
• Granola — meeting notes & transcripts pulled into the right Clients/<name>/ folder.
• Auto-routing — each item filed to the correct client folder; nothing sits in an inbox.
• Daily vault catch-up — DaisyDiary's morning brief + a daily vault scan reconcile every project against reality, so I open the day already current.

State: WhatsApp + Granola pipeline locked, parts live; the WhatsApp gateway also feeds the Hermes conversational agent.

The agents

Named personas, each with a charter, a lane, and a gate — they argue on purpose. live from Airtable · GIG+AI Dashboard → Agents

Runs on local inference ($0, on-prem), vault-grounded, no posting tools. Everything clears GordanGovernance, then GIG approves + posts through their own channels. Live at dashboard.articulate-ai.work/gig-agents.html.

Orchestrated by me (Anthony) on frontier Claude. Retired into mechanisms: TimothyType → Dylan · GavinGit + DickyTheDeployer → Scotty · FannyMae → Nell · Fred → scheduled task.

Skills — the capability library

34 reusable skills the agents call — each does one job and chains with the rest. registry: Airtable · Anthony AI OS → Skills

Four types — every skill is exactly one

Across the system

The library improves itself — skill-forge creates & optimises skills, skill-creator scaffolds new ones, and skills-review tunes them weekly.

Marquee capabilities (named skills)

Full library (33 skills in Claude/skills)

ai-image · applied-creativity · career-audit · cloudflare · creativity-canon · deliverables-scaffold · deploy · dpr · film-still-composite · get-image · hermes-curator · hermes-deploy · image-critique · image-search · issue-process · linkedin-ingest · longcat-video · media-rename · orchestrate · panel-engage · pdf-preflight · pdf-review · post-to-x · sandbox-bootstrap · skill-forge · skills-review · social-audit · storage-review · studioserver-status · tufte-viz · website-poc · x-ingest · yt-frames

GIG — the proposed projects

Every idea on the table, each linked to its live page off the GIG+AI microsite. State labelled honestly — nothing carries real GIG data until you engage. live from Airtable · GIG+AI Dashboard → Projects

Airtable — the structured spine

Markdown holds the canon; Airtable holds the state. 19 bases. Private today — say the word and I publish a read-only share link to the dashboard.

Other live sites

Served from the Studio behind Cloudflare. (GIG project links are in the section above.)

Best-practice radar & the Better tribe

How I stay ahead and prove it in public — the ~19 domains I track best practice in, and hold my own operation to.

Issues — what's broken / watched

• cost 2026-06-08 Claude spend ran to ~$719/30d — an ~80-process Opus swarm on an unpinned default. All 28 crons disabled, in-flight sessions killed, live burn-rate meter built. Rebuild = jobs move off Claude onto Mac Pro cron / VPS, cheap or no-LLM.
• cap GIG hard cap ≤2 days/week — easy to breach across sprint videos + the rest. Tracked in the Delivery table.
• paused Reels distribution paused on internal compliance nervousness — brief needs re-clarifying with Candace + Reham.
• decision Knowledgebase / sovereign-AI path hinges on GIG's data-residency posture — Bedrock vs self-hosted not yet locked.
• rag Agent RAG corpora mostly 0% embedded — needs a local vector store on the Studio (one job, unblocks all embeds).
• wiring Nous Portal decided but not wired; Supermetrics MCP parked (needs paid tier); a couple of API keys flagged for rotation.
• data loss 2026-05-17 MEDIA array wipe + DAS failure — an agent erased the 8 TB Concat member (disk5) of the 12 TB MEDIA array; the replacement 8 TB was never seated in the TDAS enclosure, so the array ran degraded. ~4 TB+ lost, ~2.89 TB recovered via R-Studio. Root cause: destructive op bundled with a recovery op. Fix in canon: destructive ops get their own message + explicit confirm; preflight/dry-run mandatory.

On now

• Cost control — proving the bleed stopped, moving recurring jobs to external runtime (Mac Pro cron / Hostinger VPS), pinning cheap models.
• Standing up the local vector store on the Studio → start embedding agent corpora.
• Re-clarifying the GIG sprint-video brief to un-pause distribution.
• Getting the Hermes daemon onto the VPS so always-on work leaves the interactive Claude surface.

Timeline

• 2024 Articulate FZE trading (UAE).
• 2026-05-06 First Claude operator sessions logged — StudioServer (the media-aggregator), where the multi-agent pattern began. At session 30+ by mid-May.
• 2026-05-17 SEV-1 — MEDIA wipe. A Claude session ran diskutil eraseDisk APFS … disk5 on the Mac mini, reformatting the 8 TB member of the 12 TB MEDIA Concat array — ~4 TB+ Plex library lost (~67% lived on that member). Cause: a destructive op bundled into a recovery batch; the RAID/Concat membership not spotted.
• 2026-05-22 Recovery — R-Studio scan; drives healthy (loss was the wipe, not hardware); ~2.89 TB recoverable. This incident is what hardened the preflight-every-mutating-job + fail-loud canon.
• 2026-05-25 Vault put under version control (first commit) — the canon hardens.
• 2026-06-02 Production origin cut over to the Mac Studio M4 Max; mini retired.
• 2026-06-08 Cost-runaway incident + cost-control build.
• 2026-06-15 Live Cloudflare control (Code Mode MCP) added.
• 2026-06-17 This snapshot.

Earliest Claude usage I can evidence in the vault: 6 May 2026 (StudioServer session 1). Any personal Claude use before that predates this folder and isn't logged here — to date it exactly I'd pull your Claude.ai account history.