Back Office · office.temerarii.xyz
Run this yourself — the whole content engine is open source

The whole machine is open — see it run, run it yourself, here’s the method.

Built by Dom Davis — Growth Engineer & AI Solutions Architect. The rare triple: studied it (an accredited AI bootcamp + 30+ courses), shipped it (35% YoY · 13 production flows · 8+ years), and teaches it (the Academy). Minus the hype — receipts over rhetoric.

See it run · The Labtemerarii.xyz — the front door, in public.
Run it yourself · This Officethe open-source control room — you are here.
Here’s the method · The Contentbuild-in-public across 9 channels.
We teach it · The Academyfree AI + digital skills · Fall 2026.

This office is the experiment. The whole content engine — the part that plans the calendar, renders every asset, certifies it, and ships it to nine channels — is open source. What you are looking at is its control room. The pages under Media, Calendar, and Storyboards are not a demo: they are this machine’s actual output.

Get the source →Watch it run →

How it works

One file is the source of truth — content-index.json, the calendar. The agent reads it, and for every cell it composes a custom element, renders the video / GIF / email / blog, runs the simulator over every frame, and only ships what certifies. Front and back stay in lock-step: the storyboard you review is the exact composition the renderer produces. — 9 reference n8n flows mapped to typed Python live in the repo.

1 · Calendarcontent-index.json holds every cell — week, day, channel, the brief for each scene.
2 · Composethe agent reads each brief and builds a bespoke custom element on the brand system — no generic templates.
3 · RenderRemotion + ffmpeg produce the asset in every aspect ratio each channel needs.
4 · Certifythe simulator inspects every asset, every frame class; nothing ships until it passes the gate.
5 · Shipcertified assets go to the CDN and out to the channels — the proof lands under Media.

The MCP stack

The whole engine is the MCP stack — Claude Code orchestrating tools and integrations as direct calls (the n8n→typed-Python destination). The pages below are three facets of that one stack, not three separate products:

Live proof — this machine’s output

Run it yourself

Clone it, point it at your brand, run the build. The engine is brand-agnostic — brands live as instances under brands/, the engine stays generic.

# clone the open studio
git clone https://github.com/temerariimedia/temerarii-studio.git
cd temerarii-studio

# regenerate this whole office from source
python apps/office/build_office.py

# point it at your brand (brands/<your-brand>/) and run the engine
python -m engine.run --brand your-brand
Open the repo →

The offer ladder

The open platform is the free top of the funnel; the offers are the rungs you climb from it. There is a fit for every budget and involvement level — routed by tier.

T0 · Open / freeThe whole system, shown + available — this office, the Lab, the Academy, the blog. The free 1-hr consult is the front door off the proof.
T1 · Self-serveSlotSlot (the app) + the Academy cohort + templates — do it yourself with the machine.
T2 · WedgeA run-ahead seasonal campaign build or the Autonomous Outbound Machine (fixed fee).
T3 · RetainerOngoing run-ahead campaigns + reporting — the run-rate.
T4 · EnterpriseSIE compliance-as-a-service · custom dev/apps · full GTM ecosystem.

Lab ↔ Office ↔ Academy

One story, three places: the Lab is the front door (see it run), this Office is the control room (run it yourself), and the Academy is where we teach it.