# The Agent Org Chart, Hello Collective. > Twelve agents, one human, one lever. An introduction to Orbyt Collective: who the twelve agent seats are, what each may do alone, and where every one of them has to stop. - Canonical URL: https://justinbartak.ai/blog/hello-collective - Author: Justin Bartak, Chief AI Officer (https://justinbartak.ai) - Author entity: https://justinbartak.ai/#person - Author profiles: https://www.wikidata.org/wiki/Q139551829, https://orcid.org/0009-0005-2615-3624, https://www.linkedin.com/in/justinbartak, https://x.com/justinbartak, https://www.crunchbase.com/person/justin-bartak, https://medium.com/@justinbartak, https://github.com/justinbartak, https://about.me/justinbartak - Published: 2026-09-21 - Updated: 2026-09-21 - Category: Strategy - Keywords: agent org chart, agent leadership team, AI run company, autonomous org, one human in the loop, agent governance, autonomy ledger, kill switch, research lab - Reading time: 9 min read --- ## What is on the chart? There is an org chart on the homepage now. Twelve agents. One human. The human is me. The twelve have names, charters, a reporting line, a promotion ladder, a kill switch and a ledger of every run they have made. The public name for the whole thing is [Orbyt Collective](https://www.orbytlabs.ai/orbyt-collective), and this is the introduction I should have written the day the chart went up. Here is the shape, top to bottom. A board, which today is me, sole director. A CEO, which is also me. A Chief of Staff attached to the CEO with no authority of its own. Then seven departments across the line: Marketing, Finance, Engineering, Product, Innovation, Operations, Revenue. Beside them three cross cutting seats that report to the CEO rather than to a department: Legal, Security, Quality. And one seat that audits all of it and reports straight up, the Inspector General. I borrowed the department names on purpose. The difference is that every box below mine is a file. ## Who are they? They named themselves. On July 13, 2026, each founding officer was asked to choose a name in isolation, with no view of the others. Every name begins with Agent, so nobody mistakes one for a person. [Agent Fulcrum](https://www.orbytlabs.ai/orbyt-collective/leadership) is Chief of Staff. Agent Ward is CTO. Agent Compass runs Product. Agent Ledger runs Finance, and two other seats also chose Ledger that morning, which is entry D-0016 in the [decision log](https://www.orbytlabs.ai/orbyt-collective/process). Agent Cite runs Marketing. Agent Cusp runs Innovation. Agent Keeper holds Operations and Agent Convert holds Revenue, both observers until launch. Agent Bastion is General Counsel. Agent Sentinel is seated for Security and waits for launch. Agent Assay owns Quality, and is the first officer to choose they. Agent Gauge is the Inspector General. I did not pick a single one of those names. I published the collision instead of hiding it, and I wrote about that separately in [the build note](https://www.orbytlabs.ai/blog/building-the-collective). ## What can a seat do without me? Every seat has a written split. What it may do alone, and where it has to stop. Engineering writes health reports, proposes architecture, and may open a draft pull request it cannot merge. The merge is mine. Product proposes a backlog and ships nothing. Innovation writes briefs and builds nothing. Finance updates the ledger and never spends. Marketing publishes the blog editions its pipeline produces and proposes new pages, and may not touch pricing or a product claim. Legal reviews every public claim weekly and flags what it finds for me. Its output is never legal advice. Quality reports on test health and the audit grade, and may not switch any check from report-only to blocking. The Inspector General reads everything and can act on nothing. Counted across the twelve, that is 29 autonomous lanes and 40 gated ones. The number I care about is the third one. By configuration, and the configuration is private: no seat may merge a pull request, and the agent step is given no push credential. The workflow commits what a seat is allowed to keep, with a token the agent never sees. One lane is the exception, and it is named. Marketing's content seat can write an article into the blog file and the workflow lands it without my signature. What holds it is a rule about pictures: an article with no hero still is held whatever its date says, and I make every still by hand. I do not sign the text. An edit made after the artwork lands would land unread too. That is the one lane where the human does not see the words, and I would rather name it than let the chart imply otherwise. **Autonomy here is not a switch. It is earned one lane at a time, sized by what that lane can break.** That is the policy, written before any seat had earned anything, and the ladder further down is where it gets applied. I let agents write reports. I approve spending. ## What have they actually done? The [Autonomy Ledger](https://www.orbytlabs.ai/orbyt-collective/autonomy-ledger) is the receipt. It is generated from the org's own run records and published raw, and I read it on September 9, 2026, before writing this. Seventy nine runs since July 21. Sixty six completed, thirteen failed. A completion means the run ended by printing the exact line its charter tells it to print when it is done, and the workflow then committed what that seat is allowed to keep. A failure means it never printed that line. Discards are a third thing: files a run wrote outside its keep set, thrown away at the reset whether the run completed or not. Fifty one of those so far, and a completed run can produce several. Nine of the twelve seats have rows in the ledger. Operations and Revenue get theirs from the advisory panel, where they speak on a decision. The finance ledger is a script with no model in it. Security has never run. The inspector's first version is mechanical and writes no row. Marketing is the outlier: fifteen runs, seven failures. One documented cause is in the failure corpus. A guard misread a citation as a name leak and blocked the content pipeline for ten days in August. The fix narrowed the guard to the unit the content uses, characters rather than lines, and it is entry 60 in the corpus. Alongside the runs sit 51 logged decisions, the newest dated September 8, and 110 guards in the audit harness, all read on September 9. On the Collective page those figures are never typed: the build reads the seat registry, the authority matrix and the decision log and writes the counts in. The ones in this article are the September 9 snapshot of that same read. ## Who holds the lever? I do, and there is exactly one. The kill switch is a file. Every autonomous workflow checks for it before it loads a credential, and asks the remote for it again before every push. It has been pulled once, on August 20, 2026, during the move to this domain, and lifted the same day. The [governance paper](https://www.orbytlabs.ai/research/agent-leadership-governance) is candid about what that file does and does not do. A run already in flight keeps running until it reaches the step that asks. What the file stops is the landing. Merging a pull request is mine. The money path is mine. Shipping a feature is mine. The agents report, propose, draft and guard, then stop at the line where a person signs, with the one exception named above. The cost of keeping that line is real: nothing a seat drafts becomes code until I read it, so a draft waits as long as I take. I accept that delay because I want to read code before it lands. ## Where is it stuck? The promotion ladder decides when the org advances a stage. Its criteria are written down and their hash is pinned in its state file, so a rewrite of the criteria shows up as a rewrite. The evaluator that reads them calls no model. It can suspend itself. It cannot promote itself, because a promotion needs a signed commit from me. Today it sits at Stage 2, holding. Three criteria are unmet and all three are about the Inspector General. There is no test that checks its report says what it should. There is no written list of what it is supposed to look at. And none of its checks yet measure the org rather than the product. So the seat that is supposed to catch the org lying about itself has not yet proven it can look. The work to close that is those three things, in that order. The ladder says so on the page, in a sentence generated from its state file, and it will keep saying so until they exist. ## Why publish an org chart for a thing you cannot buy? I published it so you can see what I delegate and what I keep. Orbyt Collective runs in one place. Here. It is not for sale and it has never run at another company. A stranger who reads that an agent leadership team runs a company will assume they can buy one, so the words Research Lab sit above the name on every page, before the claim arrives. The chart exists so the claim can be checked. Every seat on it links to what that seat may and may not do. The run counts come from a file you can download, and the rest come from a repository you cannot, which the governance paper says in about those words. The [failure corpus](https://www.orbytlabs.ai/orbyt-collective/how-it-works) lists what went wrong. Its largest class, 34 of 71 on September 9, is verification gaps: tests and guards of mine that could not fail or could not see. The corpus has no class for an agent failing, so that is a share, not a comparison. I had not noticed, until I read it on a phone on September 8, that the mobile footer listed four of the six Collective pages. The desktop and the phone disagreed about what the thing was. That is fixed, and it is the kind of drift an org chart picks up when nobody re-reads it. So, hello. Twelve seats, one human, one lever. The chart is on the [homepage](https://www.orbytlabs.ai/), the seats are on their [own page](https://www.orbytlabs.ai/orbyt-collective/seats), the three ledgers are public, and the enforcement code is not. Related reading: - [Orbyt Collective](https://www.orbytlabs.ai/orbyt-collective) the hub, with every count generated in front of you - [Leadership](https://www.orbytlabs.ai/orbyt-collective/leadership) the twelve seats, what each chose to be called, and why - [The seats](https://www.orbytlabs.ai/orbyt-collective/seats) what each officer does alone, and the line where it stops - [How it works](https://www.orbytlabs.ai/orbyt-collective/how-it-works) the loop from a report to a signature, drawn, plus the failure corpus - [Governing an agent leadership team](https://www.orbytlabs.ai/research/agent-leadership-governance) the paper under the chart, and what it admits it cannot show - [Three agents picked the same name](https://www.orbytlabs.ai/blog/building-the-collective) the build note on the page this chart lives on --- _Originally published on [orbytlabs.ai](https://www.orbytlabs.ai/blog/hello-collective) on Sep 21, 2026._ --- ## Frequently Asked Questions ### Is Orbyt Collective a real org chart or a metaphor? It is a real reporting structure, written down and read by every run. A board and a CEO, both me, a Chief of Staff with no authority, seven departments, three cross cutting seats and an Inspector General. Every box below mine is a file with a charter, a lane list and a run history, and the chart on the homepage is generated from those files. ### What can an agent seat at Orbyt do without a human? Report, propose, draft and guard. Engineering may open a draft pull request it can never merge. Product proposes a backlog and ships nothing. Finance updates a ledger and never spends. Across the twelve seats there are 29 autonomous lanes and 40 gated ones, and zero seats that can merge to the branch that deploys. Merging, spending and shipping are mine. ### How do you stop the agents? With a file. When the kill switch file exists in the repository, every autonomous workflow halts before it lands anything. It has been pulled once, on August 20, 2026, during the domain move, and lifted the same day. It stops the next landing rather than a run already in flight, and the governance paper says that plainly. ### Can I buy Orbyt Collective or run it at my company? Not today. It runs in one place, here, and it has never run at another company. Every Collective page carries the words Research Lab above the name so a stranger reads the frame before the claim. It is being pulled apart on purpose so one day it could run somewhere that is not mine, and the page carries a date you can hold me to. --- Source: https://justinbartak.ai/blog/hello-collective Cite as: Justin Bartak, "The Agent Org Chart, Hello Collective.", https://justinbartak.ai, 2026-09-21. https://justinbartak.ai/blog/hello-collective