Chart the voyage from idea to legacy. Every option we hold, in one structure — drill from category to sub-sub-niche. Filters dim branches, they never delete them.
Long-form is the core asset, but it is not the start. Demand comes first, from four sources that answer different questions and must not be collapsed into one. Video branches off the research, not off the published post — deriving video from a thin article inherits the thinness.
Four sibling sources. Same keyword, different indexes, different truths. Keep them separate — the whole point is that they disagree.
The four streams converge into one row per article: target keyword, working title, search intent, entities to cover, internal links, tone preset. Autoblogging.ai is a generator, not a publisher — hand it finished prose and you pay to write it twice.
The Sheet is the human-reviewable queue. Autoblogging supports n8n natively so the Sheet is not strictly required — keep it precisely because it gives you somewhere to approve rows before spend.
Godlike mode for single high-value pieces with SERP and entity analysis. Bulk for volume, up to 500 rows a batch. Lands in WordPress as pending, never live.
POV injection, fact check, brand voice. Your own SOPs say Google's helpful-content systems penalise unedited AI content — use agents for structure and research, write the unique angle yourself. This step is not optional and volume per site stays modest because of it.
WordPress push, scheduling, optional Web 2.0 syndication to Medium, Dev.to, Hashnode, Telegraph, Tumblr for backlinks.
Video is a medium hub, not a branch of the blog. It draws on the same research that fed the brief, which is why it sits sideways in the map rather than underneath Long-form. Producing it is Cluster B, repurposing it into forty pieces is Cluster C, knowing which landed is Cluster D.
Each agent sits in the zone matching the job it is running. Hover any agent to see its current mission, the model behind it and how long it has been going. Agents move between zones as their work changes.
Six registries that used to be six tabs. They are still six separate things — an agent decides, a tool performs, a platform hosts, a model reasons — and each section says which is which, because that distinction was recorded in the Log and never on the page. Open one at a time.
Every tool, model, platform, doc and install guide named across the SOP manual, the Riser AI Directory and this session's research — merged, deduplicated and carrying its verification status. The Map tells you what to do and the Spine tells you the order; this tells you where each piece actually lives.
An agent takes an instruction and decides how to carry it out. That is the line separating this tab from Tools, which do one job when told, and Platforms, which are the rooms agents work inside.
The Room maps one agent to one zone, because for a CLI agent that is the truth — it runs, it finishes. A swarm breaks that assumption three ways: many workers under one intent, workers that are born and die inside a single job, and a hierarchy where an orchestrator holds the goal while each worker holds a fragment. This tab exists because stretching the Room to cover that would wreck what makes the Room readable.
Where the workers physically run, and therefore whether you can stop one. Local means processes on your machine you can see and kill. Session means contexts inside one editor or CLI process — killing the parent kills them all. Remote means someone else's infrastructure: you can watch, you cannot reach in. Opaque is the fourth state and the newest — a swarm sold as a model, where you cannot see the workers at all, cannot attribute cost to them, and cannot reproduce a run. There the spend cap is the only control you hold.
How work divides. Parallel runs independent branches at once. Pipeline chains them, each feeding the next. Fan-and-judge has several workers attempt the same thing and one synthesise a winner — the most expensive pattern, and the only one that buys you quality rather than speed.
Who talks to whom. Hierarchical is one lead directing workers. Mesh lets every worker talk to every other. Adaptive reshapes itself per task. Hierarchy is auditable; mesh is fast and much harder to reconstruct after something goes wrong.
Six distinct things get called "a swarm" across this stack and they are not interchangeable. A model that runs agents internally, a CLI that spawns subagents inside one session, and a supervisor running separate terminals are three different risk profiles wearing one word.
Mission Control should not rebuild the inside of a running swarm. Ruflo already ships an agents dashboard showing every spawned worker — role, current step, memory namespace, token budget and status — with the ability to inspect a trajectory, kill a runaway worker or reassign it. Rebuilding that means maintaining a worse copy of someone else's live view.
So the split is: this tab is the registry and the budget — which swarms exist, what each is allowed to spend, where it can be stopped. The runtime's own dashboard is the interior, opened on demand. The one thing worth pulling back in is aggregate token burn per swarm, because that is the number that has to sit next to everything else you are spending.
Priced per million tokens, input and output, the way OpenRouter lists them. Output is the number that hurts — it is typically four to five times input, and long-form generation is nearly all output.
Video, image and voice tools bill in credits against a plan rather than per token, so they cannot sit in the table above. They are also the most expensive thing in the system by an order of magnitude — a single generated clip can cost more than a whole article. That is why credit burn is tracked per asset in the Video branch.
A platform holds state, hosts other things, or routes between them. Losing one costs you a system; losing a tool costs you a task. That difference is why they are separated here.
Every named tool in the stack, grouped by what it is for — now including the paid media, ad intelligence, attribution and agency CRM layers. Wired means Mission Control can call it directly. Manual means you open it yourself and the mission waits — which is the honest state of most of this stack today.
The guided passage a new operator sails, from a rough idea to something that outlasts them. Fourteen screens, five phases. Each one says what the operator does, what the system does for them, what comes out the other end, and which books it stands on.
Screens are taught in order because each depends on the one before it — the secrets cannot be written before the domino is named, and the funnel cannot be chosen before the offer exists.
Written so a new chat, with no memory of the previous ones, can pick up exactly here. Every count below was read out of the live files on the day this was written, not recalled — which is itself one of the standing rules in §6.
Two artefacts. Everything else was a source document that has already been merged into one of them.
| Taxonomy Map | Agent OS Workbook | |
|---|---|---|
| File | risertaxonomymap.html | riser_agent_os_v7.xlsx |
| Form | One self-contained HTML file, no build step | Excel, 18 sheets |
| Lives | Hosted at risernavigator.com; previously a private Claude artifact URL | Delivered as a file |
| Purpose | The working reference — what to do, who owns it, what to paste | The audit record — what was checked, what it cost, where it came from |
| Reach for it | Daily and weekly | When settling an argument about a number |
The split was agreed explicitly: things consulted weekly live in the map; a record of one audit on one date lives in the workbook. Putting a static record beside a working reference makes both harder to trust.
Eleven tabs in two rows — the top row is the journey and the working surfaces, the bottom row is reference. Consolidated from seventeen on 30 Aug 2026: Agents, Swarms, Models, Platforms and Tools are now accordion sections inside Resources rather than tabs of their own. They are the same six registries, one level down.
| Tab | What it holds |
|---|---|
| Voyage | The guided passage a new operator sails — 14 screens, 5 phases, 58 books. The landing tab |
| Chart | The full tree, category to sub-sub-niche, with filters that dim rather than delete |
| SOP | The operating procedure rewritten so a beginner can execute it — 7 set-ups, 3 phases, 14 numbered steps, 169 tick boxes, 5 decision boxes, 6 named gaps |
| Roles | 50 roles across 12 functions — the org chart |
| Prompts | 28 copy-paste system prompts |
| Spine | The 90-day order of operations |
| Resources | The directory — 1,524 entries across 107 shelves, each carrying a verification status |
| Resources → sections | Agents, Swarms, Models, Platforms, Tools — 13 agents, 8 swarms, 6 model rows, 30 platforms, 151 tools. Each section states what it holds, so the agent/tool/platform/model distinction is on the page rather than only in the Log |
| Room / Brains | Animated explainers for how the pieces relate |
| Log | 48 dated blocks recording every decision, correction and addition |
| Handoff | This tab |
Directory verification status. Status is the point of that tab — a name with no source is kept and marked, never quietly dropped.
| Status | Count | Means |
|---|---|---|
| verified | 1,344 | An official source confirms it |
| caution | 127 | Name or version mismatch, or traced only to secondhand write-ups |
| unverified | 26 | No official source exists — named in the manual, nothing to link to |
| playbook | 16 | A method, not a product; nothing to install |
| sunset | 11 | Shutting down or already gone |
Roles tab. 50 roles. 7 are unstaffed and one filter press isolates them. 8 more were adopted from later audits and have never been run — marked never run rather than counted as staffed. Autonomy: 5 at L1, 19 at L2, 24 at L3, 2 at L4. Every card names the bots, tools, output, KPIs, the human gate, and the trigger that makes the role stop and escalate.
The seven empty chairs: Prompt and workflow versioner (repo not started) · Media buyer (done by hand) · Ad ops executor (wiring exists, nobody owns it) · CRM and lifecycle operator (set by hand) · Support responder · Checker / QA — the most important empty chair · Security and access owner (lists not written).
Prompts tab. 22 agent system prompts and 6 thinker directives, filterable apart. Each carries required inputs, required output shape, and the named human signer. This is the reading copy, not the master — Set-up 6 puts the editable prompts in a repo.
SOP structure. Set-ups (7): decide what we sell and who we are · put everything we know in one place · give the robots their tools · hire the robot team · turn work into things we sell · keep every old version · the yes button. Phases (3): get ready · watch them work · let it run. Steps (14), beginning at “Has anyone paid?” — deliberately, see §4.
Eighteen sheets. The Read me sheet carries live COUNTA and COUNTIF formulas over every one of them, so the counts recompute rather than being retyped — 63 formulas, recalculated clean.
| Sheet | Rows | What it is |
|---|---|---|
| Read me | — | Orientation and live count formulas |
| Handoff | — | This brief, as a sheet |
| Findings | 86 | The audit record — every claim checked across seven stacks, sorted by index |
| Roles | 50 | Same data as the map’s Roles tab |
| Roster | 74 | Every bot, agent, platform and tool with capability and cost |
| Swarms | 18 | Multi-agent playbooks with a named human governor each |
| Prompts | 28 | Same data as the map’s Prompts tab |
| Tasks | 65 | The task board |
| Playbook | 48 | Framework entries by thinker |
| Cadence | 19 | Recurring jobs — daily, weekly, monthly |
| Thinker Index | 8 | Each thinker with the anti-pattern they forbid |
| Decision Rights | 25 | RACI. AI can be R or C; never A |
| Data Architecture | 14 | Canonical system per domain, export path, restore test, vendor boundary |
| Roadmap | 14 | 13 weeks plus Gate 0 — “STOP: has anyone paid?” |
| Cost | 35 | The tool spend stack |
| Gaps | 8 | Open structural problems |
| Scoreboard | 25 | Metrics with direction-aware status formulas |
| Sources | 96 | Citations |
Editorial standard, applied to every pass.
Security constraints — still in force.
Publishing mechanics. The map is one self-contained HTML file, now served from risernavigator.com. When publishing to an artifact URL instead, use the existing one — do not create a new one, because a new URL orphans every saved link. This environment blocks the artifact preview host, so reading the published version back fails and every publish needs force: true; that was approved once and stands. Verify before publishing, every time: extract the script blocks and run new Function(src) for a syntax check, then render with Playwright, click every tab, and confirm zero page errors. Workbook changes are verified with the xlsx skill’s recalc.py, which must report total_errors: 0.
Seven independently-built AI marketing stacks were audited against each other and against the original SOP, producing the 86 findings. All seven are absorbed.
The most consequential findings, for context on why the audit mattered: a backwards LTV:CAC < 3:1 target; a scoreboard status formula that flipped four rows including the workbook’s own ad-spend gate; an ROI headline inflated roughly 60% by a rate contradicting the same workbook’s payroll tab; a “cut below 3x” rule that could never fire; automated “dynamic scarcity injection” with no human gate; and no gate anywhere requiring a paying customer.
Six named bodies of thinking. Each is in the workbook’s Thinker Index with the anti-pattern it forbids — the forbidding matters more than the framework.
| Thinker | Contributes | Forbids |
|---|---|---|
| Alex Hormozi | Value Equation, Grand Slam Offer | Claims without proof; margin below floor |
| Russell Brunson | Value Ladder, Hook-Story-Offer, Attractive Character | A better version instead of a new opportunity |
| Robert Cialdini | Seven principles of influence, Pre-Suasion | Manufactured scarcity; manipulation over salience |
| Gary Vaynerchuk | Jab-Jab-Jab-Right-Hook, day-trading attention | Creating instead of documenting |
| Tony Robbins | RPM, state-story-strategy, CANI | Strategy applied to an unexamined belief |
| Chris Anderson | The Long Tail, Free, Makers | Chasing head terms in a long-tail market |
Two corrections worth carrying forward: there are seven Cialdini principles including Unity — several source documents listed six. And Acquisition.com is singular. Both are recorded in Findings.
If the map needs republishing to the same URL, ask for that URL rather than publishing to a new one — a new URL orphans every link anyone has already saved.
Every chair the company needs filled, merged from seven independently-built stacks and this SOP. A role is a job someone is accountable for, not a tool and not a bot — which is why each one names a human or a bot, a backup, what it produces, and the thing that makes it stop and ask. Bots are listed as the labour, never as the owner.
22 agent system prompts and 6 thinker directives, each with the inputs it needs, the output shape it must return, and the human who signs it off. Copy one, paste it into the bot's system box, and give it the inputs listed. Every one is written to work from supplied evidence only — if the input is missing, the prompt tells the bot to say so rather than invent it.
The Map is capability — every mission the system can run. This is the other half: the accumulated context those missions read from and write back to. A mission without the vault starts cold every time; the vault without missions is a folder nobody opens.
Obsidian itself cannot be embedded. The desktop app will not sit in an iframe, and Obsidian Publish gives you a URL but a stripped-down graph you do not control the styling of. Neither is the right answer.
The vault is markdown on disk, which is the whole opportunity. Mission Control can read the folder directly, parse the wiki-links out of each file, and render this exact graph from real data — live, styled to match, no dependency on Obsidian being open and no plugin to maintain. Three steps: point a path at the vault, walk the tree for .md files, regex the double-bracket links into edges. Frontmatter gives you the note type for colour, and file modification time gives you recency, which is the more useful signal — a graph that shows you what has gone stale is worth more than one that shows you what exists.
The link worth building first runs the other way: a completed mission writing its output back into the vault as a note, tagged and linked. That is what stops this being a folder that only ever grows.
This is the whole company written as small steps. Do them in order. Do not skip. Each step says what to do, and the blue words are links — click one and it opens the actual page you need. Under each step there are tool names: click the name to jump to it inside this map, or the little arrow to open the site itself. Where there is a real choice to make, an amber box tells you which one to use and why. Ticks are only for this sitting. Close the page and they clear, so you can run the list again for the next client.
Do this once, properly. Everything after it depends on these seven being true.
Three months, in order. Do not start month two until month one is really finished.
Fourteen steps. Step 1 is the gate on all the others, so it is the one to be honest about.
This is the to-do list, not a complaint. Each one is something the steps above ask for that nothing in our stack does.