MasonBRISBANE, AU

One person, one stack, public notes — I document becoming an AI-native builder: what ships, what fails, what compounds.

hilearnteamenjoyconnect
© 2026
Built with Next.js + AI · 2026
M.
hihi
learnlearn
teamteam
experienceexperience
work with mework with me
Subscribe

Personal AI workflow · OCP

Mason's AI Agent Team

Train top-tier AI as partners — a lean, necessary team configuration to pursue a larger vision.

31 May 2026

Notion sets direction → Gemini filters signal → Obsidian + NotebookLM compound cognition → Git ships owned domains → Cursor builds product → Hermes distributes → Notion closes the loop.

"AI Agent Team" is how one person runs an OCP — role labels (CIO, CKO, …) map to tools and agents, not a headcount.

Six layers below ↓
  1. L1CIO🔬
  2. L2CKO🧩
  3. L3CMO🌐
  4. L4COO⚡
  5. L5CTO💻
  6. L6CEO🗂️

Six layers

OCP configuration

Expand any layer card for inputs, outputs, tool practices, and iron rules.

01
CIOIntake🔬

Information filtering

Chief Information Officer — the sensing system.

GeminiPerception & research

Noise dies here — only high-quality insight flows downstream.

  • Inputs: timed high-signal collection tasks.
  • Outputs: weekly insight briefs, on-demand research memos, key insights.

Gemini · Perception & research

  • Full-network scan, deep research, multimodal digest (audio briefs / Q&A).
  • Scheduled high-signal collection tasks as inputs.
02
CKOCognition🧩

Knowledge compounding

Cross-domain cognitive graph — structure what you actually understand.

ObsidianMason WikiNotebookLMAdvisor panel

Store only internalized cognition — vision and understanding, not hoarding.

  • Structured insights become a cross-disciplinary Mason-format network.
  • Outputs: wiki/ (publishable) + raw/ (source archive).

Obsidian · Mason Wiki

  • LLM Wiki (`CLAUDE.md`) drives ingest, bidirectional links, six-dimension deconstruction.
  • `wiki/` publishable lane · `raw/` archival lane.

NotebookLM · Advisor panel

  • One notebook per strategic theme — multimodal review on your sources.
  • Audio briefs for commute blocks; verify before acting on claims.
03
CMOPublish🌐

Owned distribution

Content publishing hub — social amplifies, domains compound.

GitSource of truthVercelDeploy railmasonma.orgOPC personal brand

Social distributes; owned domains hold the asset.

  • Free-media vault → Git → automated deploy on owned domains.
  • Social and newsletter channels drive traffic back to owned assets.

Git · Source of truth

  • Obsidian vault → GitHub → Vercel CI/CD for masonma.org.
  • Single repo truth — PR-based deploys.

Vercel · Deploy rail

  • `pnpm build` gate before every production ship.

masonma.org · OPC personal brand

  • For non-technical prosumers: story, AI harness competence, growth & positioning, cross-domain minds.
04
COOExecute⚡

Execution & distribution

AI employees — the hands that run the pipeline.

Hermes AgentMiniMax orchestration
Qclaw AgentWorkflow automation

Mason directs. Agents execute. Every release needs Mason’s final approval.

  • Curator selects angles · Atomizer splits publishable units · Distributor stages channel handoff.
  • Mason is the director; agents execute — nothing publishes without final sign-off.

Hermes Agent · MiniMax orchestration

  • Curator · Atomizer · Distributor — topic pick, break down, multi-platform handoff.
  • Custom agents, scheduled automation, connectors.

Qclaw Agent · Workflow automation

  • One workflow = one responsibility — idempotent scheduled jobs.
05
CTOBuild💻

Product development

AI developer team — the product-building engine.

Claude CodeCPO · terminal agent
CursorDev team · IDE

If it ships as code, it routes through Layer 5 — not content workflows.

  • All code lives here — never mixed with the prose / publishing lane.
  • Ship gate: `pnpm build` before merge.

Claude Code · CPO · terminal agent

  • Long-context refactors, multi-file sweeps, CI-parity terminal work.

Cursor · Dev team · IDE

  • Vibe coding — natural-language intent → implementation.
  • Micro-SaaS agents and automation scripts.
06
CEOCommand🗂️

Strategy & orchestration

One-person ERP — the prefrontal cortex.

NotionCommand Center

Notion sets direction and manages work — it does not touch code.

  • Notion sets direction and holds state — people, projects, data.
  • Daily close-the-loop review feeds the next cycle.

Notion · Command Center

  • Daily plan & review · goals · project tracking · agent dispatch · content idea pool.
  • Core DBs: Command Center / Idea Pool / Content Engine / Journal.

Layer 4 · Hermes × Qclaw

COO execution rail

Hermes Agent (MiniMax) · orchestrated by Qclaw connectors & schedules

→→
×

Mason is the director. Agents execute. Nothing ships without final approval.

Operating loop

Daily cycle · same direction, closed loop

  1. 01
    CEONotionStrategy & daily rhythm
  2. 02
    CIOGeminiSignal intake
  3. 03
    CKOObsidian + NotebookLMCognition
  4. 04
    CMOGit → owned sitesPublish
  5. 05
    CTOCursor + ClaudeProduct
  6. 06
    COOHermes + QclawExecute & distribute

Gate

Before a tool enters

01

Does it solve a clear, specific pain point?

If the pain is vague, wait.

02

Does it integrate cleanly into an existing layer?

Must slot into one of the six layers.

03

Can I master it in under 2 hours?

Two hours to first useful output.

04

Does it add complexity without clear ROI?

Complexity tax needs a receipt.

Avoid the "tool collector" trap — master this compact OCP stack.

  • Agent Team = the who / what.
  • Layers = the how.
  • Prompts = the exact language.

Notion sets direction; each layer owns one job; Mason only intervenes at decision gates.

Notes from the stack, weekly.

When a layer materially changes how I build, I document it — not gadget noise, only what survives real work. Sent in Makerloop.

M
A
S
O
N