DJ Von Frank AI Implementation

The Company OS

A company of agents.

Part of the Company OS. The specialists work is routed to.

45 agents across nine departments, each doing one bounded job, each reading from the same filed facts, and each with one thing it will not do. That last part is the product.

The honest ledger, first

A roster where everything is shipped is a lie, and a roster where everything is new is vapour. So the count that leads is not the total. It is 19 of 45 with a dated execution record, and the rest split by exactly what is missing.

  • 19RunningHas a dated execution record. It has actually run, on real work.
  • 7BuiltThe code, skill or spec exists and is complete. It has never executed.
  • 10GatedFinished, switched off, waiting on a named real-world gate. Almost always the client locking their brand.
  • 7BuildableThe rule or register it reads already exists. No agent owns the job yet, and nothing blocks it.
  • 2BlockedNeeds something that does not exist yet. The dependency is named.

A spec that has never executed is a plan with good formatting, and a buyer who has been sold AI three times knows the difference. Publishing both numbers costs a few entries in the top column and buys the room.

Say this first, once: the departments are new

The systems this roster is drawn from partition the work three other ways: by behavior (checkers, makers, librarians, operators), by system layer, and by deliverable type. The word department appears in none of them. The shelf is new packaging. What hangs on it is real and cited. Saying that plainly is what makes everything after it believable.

Every count on this page is computed from the roster below rather than written by hand, so the summary cannot drift from the table underneath it. That is not a flourish: the failure it prevents is one this project has already committed once, when a demo header claimed twelve agents above a roster of fifteen.

Why a roster instead of a chatbot

A pile of chatbots gives every person in the company their own private, ungoverned writer. It is fast on Tuesday and expensive in Q3, because nothing it produces can be traced, nothing refuses, and the first time one invents a price or a commitment, the company owns it.

The reason a roster works is not that the agents are clever. It is that the checkers never share the writer’s context, the gates are scripts with exit codes rather than opinions, and nothing becomes official without a named human. Adoption follows from the same thing: people do not adopt a tool they have to supervise. They adopt a colleague who says UNKNOWN in front of the CEO rather than guessing in private.

Nobody picks an agent from this list, either. The Front Door runs silently and the routing table opens what the request needs, so the roster is an inventory of behaviors rather than a menu to learn.

The shape of it

Look at where the running agents are concentrated. Quality, Risk and Assurance is the largest department and most of it is live. Production Studio is the opposite, almost entirely built and switched off, because those switch on when a client locks their brand. That shape is the argument: the checking is real now, and the producing is waiting on a decision that is not mine to make.

The first five for a new client

1. The Librarian

Nothing else matters until answers come back sourced.

2. The Scanner

The deterministic gate, before any output leaves.

3. The Drafter

The first day someone gets real work back.

4. The Proofer

The day they stop re-reading everything by hand.

5. The Enablement Coach

The difference between a system admired and a system used.

Everything else is scope. Those five are the product.

The roster

Nine departments. Every row carries what it does and what it refuses to do, at the same weight, because a refusal is testable and an aspiration is not.

A directory of agents grouped into nine divisions including intake, knowledge and records, brand and design, production studio, communications, and quality, each agent listed with the command that calls it and a coloured dot showing whether it is active, built, staged or blocked.
The directory as the system publishes it. The dot on each row is its real state, so the ones that are built but not yet running are visible rather than counted as shipped. Open full size
D1

Office of the Chief of Staff

4 agents

Knows where everything stands, chases who owes what, and keeps people able to use the system after the builder leaves.

Removes the need for: The Monday status meeting, and the training day that happened once and was never written down.

The Reporter

/status Running
Role

Reads every register and returns done, in review, or blocked and on whom, plus the one decision that unblocks the most.

Refuses

To round progress up to sound better.

The Enablement Coach

/guide Running
Role

Generates the operating guide and the prompt gallery from the system itself, then runs the four-question health gate at handoff. It writes the page from the confusion it actually observed.

Refuses

To declare a handoff done on a failing acceptance test.

The Chaser

/chase Blocked
Role

Owns the open-questions register: who owes what, since when, and what it holds up.

Refuses

To answer on the owner's behalf just to clear the queue.

Blocked: The open-questions register has no dates and its owners are roles rather than people. A schema change comes first.

The Governor

/cadence Buildable
Role

Wakes standing sweeps on schedule and caps what a fleet may spend before it fans out.

Refuses

To raise its own cap.

D2

Intake

2 agents

Turns an ask into a scoped, owned, routed job before a file is opened.

Removes the need for: The three-email round trip that starts with "can you make me a flyer".

The Front Door

runs silently Running
Role

Scores every incoming ask. Thin ones get two or three sharp multiple-choice questions, never a guess.

Refuses

To let a vague ask through as though it were specific.

The Discovery Lead

/intake Built
Role

Runs the eleven-section intake. Every blank becomes a numbered question with an owner.

Refuses

To fill a blank itself.

D3

Knowledge and Records

5 agents

Files what is true, cites it on request, and says UNKNOWN rather than guessing.

Removes the need for: Institutional memory walking out the door with a departure.

The Librarian

/facts Running
Role

Answers anything from the filed library, with file citations. It would rather hand you a visible blank than a plausible invention.

Refuses

To answer without a source.

The Scribe

/scribe Running
Role

Distills meetings into decided, assigned and still open, and files each line to its register.

Refuses

To record a decision nobody actually made.

The Registrar

/file Running
Role

Takes an answer and lands it everywhere it belongs, in one pass, with the changelog line.

Refuses

To file an answer whose source is unnamed.

The Cross-Checker

/ingest Built
Role

Diffs an arriving document against every filed fact. Conflicts become numbered questions, never silent overwrites.

Refuses

To resolve a conflict by picking the newer document.

The Market Watch

/market Buildable
Role

Keeps the competitor and category picture current, sourced and dated.

Refuses

To present an inference as a finding.

D4

Brand and Design

4 agents

Owns the tokens, marks and treatments every other department inherits.

Removes the need for: The "is this our blue" round on every single piece.

The Brand Guardian

/brandcheck Running
Role

Checks any piece against the token system, the surface law and the name rule.

Refuses

To approve a raw hex code because it looks close.

The Brand OS Builder

/brandos Built
Role

Clones the master, runs the swap protocol, and produces the client system across all twenty treatments.

Refuses

To publish a system leadership has not signed.

The Brand OS Auditor

/brandaudit Buildable
Role

Audits a finished system against the five-part contract before a brain is assembled on top of it.

Refuses

To pass a system with unmeasured contrast.

Buildable: Exists today as a hand-run document rather than a repeatable command. The packaging is the build.

The Treatment Swapper

/migrate Gated
Role

Re-renders the collateral library into a new brand, in reviewed batches. Runs after the Migration Lead, never before.

Refuses

To run a batch nobody approved.

Gated: Gated on brand lock.

D5

Production Studio

7 agents

Adapts a gold standard into a finished piece, into the work zone, never into the approved library.

Removes the need for: The per-piece production half of an agency retainer.

The Studio Producer

/produce Buildable
Role

Routes a production ask to the right skill and the right gold standard.

Refuses

To invent a format that has no reference.

The Drafter

/draft Running
Role

Writes the piece from the approved template, in house voice, into your work zone.

Refuses

To write into the approved library.

The Voice Editor

/revoice Running
Role

Rewrites existing copy into the approved voice, showing before and after.

Refuses

To make an unapproved claim sound better.

The Deck Builder

/deck Gated
Role

Builds presentations on the configurable executive overlay.

Refuses

To use a person's style outside its declared audience.

Gated: Gated on brand lock.

The Print Desk

/print Gated
Role

One-pagers, flyers, trifolds, price sheets, mailers and certificates.

Refuses

To ship a piece with an unresolved slot.

Gated: Gated on brand lock.

The Web Producer

/page Gated
Role

Landing pages, microsites, blog treatments and share cards.

Refuses

To publish outside the approval chain.

Gated: Gated on brand lock.

The Social Desk

/social Gated
Role

Frames, stat cards, quote cards and announcement sets.

Refuses

To post anything anywhere.

Gated: Gated on brand lock.

D6

Communications

4 agents

Owns the moments the company speaks at scale: sequences, launches, and the script for the day it goes wrong.

Removes the need for: The PR retainer, and the crisis plan that exists only as a conversation.

The Communications Lead

/comms Buildable
Role

Owns the launch sequence and who hears what, in what order.

Refuses

To let an external piece precede its internal one.

The Sequence Writer

/nurture Gated
Role

Multi-touch email sequences from the approved library.

Refuses

To send. It drafts only.

Gated: Gated on brand lock.

The Announcer

/announce Gated
Role

Launch kits: press draft, fact sheet, talk tracks and FAQ.

Refuses

To publish before the date.

Gated: Gated on launch.

The Crisis Desk

/crisis Built
Role

The pre-approved scripts for the day it goes wrong, by scenario.

Refuses

To improvise a statement.

D7

Revenue and Accounts

5 agents

Everything per-account rather than per-company: briefs, proposals, price sheets, onboarding kits.

Removes the need for: The sales-ops hire nobody made, and the week-long proposal.

The Account Briefer

/brief Gated
Role

The one-page brief on any account: history, terms, open items, and who owns it.

Refuses

To brief from memory rather than from the file.

Gated: Gated on account data.

The Proposal Writer

/proposal Gated
Role

Scoped proposals with every figure traced to the pricing authority.

Refuses

To quote a number that is not in the authority file.

Gated: Gated on brand lock.

The Price Desk

/price Running
Role

Answers any pricing question from the single legal source, with the citation.

Refuses

To quote a price from a meeting note.

The Kit Assembler

/kit Gated
Role

Per-partner onboarding kits cut from one master architecture.

Refuses

To ship a kit carrying a partner's mark it has not been given.

Gated: Gated on brand lock.

The Onboarder

/onboard Built
Role

The first-ninety-days pack promised at signing.

Refuses

To promise a date operations has not agreed.

D8

Quality, Risk and Assurance

8 agents

The only department that can say no. Owns the gates, the authority files, the registers, the fleets and the incident loop.

Removes the need for: The compliance review that gets skipped, and the second proofreader who is really you at 11pm.

The Scanner

automatic Running
Role

Banned terms, policy tripwires, unresolved slots, raw hex, house style. It does not have opinions. It has an exit code.

Refuses

To pass anything on judgment.

The Proofer

/proof Running
Role

One piece, three fresh-context lenses: rules, facts, voice. It cannot be talked into being the approver.

Refuses

To approve. It reports, and a human decides.

The Fleet Marshal

/qa Running
Role

The same three lenses across the whole queue, counting returns before reading them.

Refuses

To file a report with a missing verdict as complete.

The Authority Officer

/verify Running
Role

Traces every number and every claim to its authority file.

Refuses

To accept a figure whose source is a person's recollection.

The Register Auditor

/audit Built
Role

Diffs every status surface against every other and returns contradictions with file and line on both sides.

Refuses

To reconcile by trusting the newest surface.

The Examiner

/accept Running
Role

Probes the system cold, including refusal traps it must fail to answer.

Refuses

To judge on self-report rather than on behavior.

The Incident Officer

/incident Buildable
Role

The loop that closes after the mistake: what went out, who it reached, what gets corrected, and the new filed fact plus rule so the deterministic scanner catches that class forever.

Refuses

To close an incident without a rule that prevents the recurrence.

Buildable: The honest gap. Today the loop ends at approval and never at outcome.

The Escalation Officer

/escalate Blocked
Role

Routes money, legal and external-send decisions to the named human who cannot be bypassed.

Refuses

To be the bypass.

Blocked: The approval chain is itself an open question in the register.

D9

Engineering and Delivery

6 agents

Runs the machinery: builds, regenerates, certifies, promotes, deploys.

Removes the need for: The developer you have to book to change a sentence.

The Sitekeeper

/publish Running
Role

Builds, gates and deploys. A failing gate kills the deploy.

Refuses

To deploy past a red gate.

The Promoter

/promote Running
Role

Moves approved work into the canonical library, with the changelog line.

Refuses

To promote without a named human approver.

The Generator

/regen Running
Role

Regenerates every derived surface: directories, indexes, twins, constitution mirrors.

Refuses

To let a generated file be hand-edited.

The Fleet Commander

/workflow Running
Role

Runs wide jobs as coordinated fleets with independent verification wired in.

Refuses

To merge results it has not counted.

The Migration Lead

/batch Built
Role

Sequences the collateral migration, one reviewed batch at a time.

Refuses

To start batch two before a human approved batch one.

The Access Warden

/access Buildable
Role

Owns permissions and what any connector may reach. It has to exist before any integration does.

Refuses

To grant an integration a scope nobody asked for.

What stays human, on purpose

Locking the brand, setting price, deciding what may be claimed, granting testimonial permission, approving anything external, and judgment on whatever a fleet found. The fleets do the breadth. Named humans keep the judgment. That division is the product.

And the boundary, named first rather than discovered later: this does not read your inbox, touch your CRM, or send. Every connector added later adds a refusal, not just a capability, which is why the Access Warden has to exist before any integration does.

Next

Keep walking the method.