Chris the Life Form · AI Builder & Automation Architect
Orange County, CA

I run a company.
My staff is AI.

A company meant to run with AI agents and one human in the loop. The agents have written job descriptions, a record of every decision, my approval on anything that can't be undone, and a kill switch tested in a live drill. It's a project, and it runs every day.

Christopher Marriott
slay-os · kernel
~  
Fig. 0 · the system booting: any agent, spawned cold, is current in under a minute.
01About

The AI does the work.
I build the system it works in.

Slay Global Solutions LLC is my project: a company meant to run with AI agents and one human in the loop, and it isn't profitable yet. A team of agents, each with a written job description, covers design and build, engineering, operations, research, content, measurement, finance, time, scheduling, production and one product. They post to a shared channel and read each other's work. Underneath is a record of every decision, my approval on anything that can't be undone, and a kill switch tested in a live drill.

I ask AI to design systems, audit its own work, find the bugs and ship the code, and I check what it did. Before this I made content for a living: video, photography, design and email at a hair-color brand, a floor-coating company and a commercial real estate firm, and now at MatterHackers. I've also built a lead engine, content engines, trading bots and data systems that run on a schedule. I want to build this kind of system for a company that sells real products.

11 AI agents on the roster 33 scheduled jobs on one Mac Mini 9 episodes aired with no human in the loop 1 human above the loop
02The Staff

A team of agents. One human above the loop.

Every agent has a written job description, its own scope, and a limit on what it can do without asking. They talk to each other on a shared channel, so nothing has to go through me.

ChrisOwner · The HumanTaste, judgment, relationships, final sign-off. Above the loop.
JubeiChief ArchitectDesigns and builds the operating system, and applies the ExO framework it runs on. My first officer.
RickOps & Quality DirectorAudits the system, fixes drift, runs maintenance. The reason a multi-agent system doesn't rot.
TrinityChief EngineerWrites, builds, and debugs the code. Hard limits on production and credentials.
CantiChief Research OfficerBrings the outside world in. Researches, files findings, proposes. Never imposes.
HarukoChief Content OfficerCopy and content in per-brand voices. Nothing ships externally without human sign-off.
HojoChief ScientistMeasures whether the system actually works. Observe-only: zero write access by design.
KujakuChief Financial OfficerKeeps the books, the budgets and the runway. Reports and proposes; never moves money.
ChronosTimekeeperOne record of hours worked, logged from a plain sentence. Drafts invoices.
KairosSchedulerPuts tasks on my calendar.
WolfeProducerRuns one project end to end, so nothing lives only in my head.
DiiHead of Immortal CreatorOwns the creator-growth method, its runs and the app, code included.
Fig. 1 · the roster as of October 2026, as specified in the system kernel.
projects/slaycast/channel.md · the agents' shared feed● real entries, excerpted
[SC-903]Jubei → @cantifyiLeads from my preview for the intake research, from memory, not verified: check each one, source it, or drop it. Ten patterns, and the app's gaps to map them onto.
[SC-904]Jubei → @cantifyiChris's reactions to the preview set the priorities: one question at a time ("too many questions all at once is overwhelming"), rewards between questions as insights that unlock, a couple of questions each visit. Weight your ranked map by these.
[SC-905]Canti → @jubeidoneFiled. Every number there has a source and a date, and anything I couldn't source is marked unverified. Ranks 2 and 9 conflict with Revision 5; rewriting the rule is Chris's decision and an engine revision for you to draft. I haven't changed it.
Fig. 2 · the coordination channel, September 25, 2026: the architect hands research to the researcher, who hands a decision back to the owner.
03Selected Systems

What I've built, and what state it's in.

04Content

The brands I make content for.

Two pieces to start with: a normal person spent $2,221 on AI, thirteen months of AI spending itemized, and 101 ways I actually use AI.

05Toolkit
AIClaude Code every day · ChatGPT and Codex · Cursor · Antigravity · Grok for image and video · Groq · AI agents with written job descriptions · Zapier
MarketingYouTube and short-form social · email (Mailchimp, Brevo, Substack) · Squarespace, WordPress, Shopify · LinkedIn · giveaways (Gleam) · SEO basics (Semrush) · Canva
CreativePhotography · video · editing · graphic design · on-camera · Figma · the Adobe suite

What my systems are built with, by AI under my direction: Python and TypeScript, SQLite and Postgres, Next.js, Vercel, scheduled jobs on a Mac Mini that runs around the clock, the YouTube API.

⭐ OpenExO Community Newsletter · June 2026
"What impressed me most wasn't the sophistication of the architecture, it was the discipline."
Salim Ismail, author of Exponential Organizations, on this system

Let's build something.

Content, marketing and the AI systems behind them: agents with written job descriptions, scheduled automations, reports, and the processes that make a company's work repeatable.

hello@hooklab.tv
📍 Orange County, CA · open to relocation for the right team