Research Lab
12 seats. 9 have ever run.
The seats that were never instrumented are not failing. Nobody built their instrument.
Two tiers, and which one you are reading.
A committed file is frozen at build, so reading it at request time still returns build time data. That is not an argument against committing it, it is an argument for saying which is which. This page renders both and marks every cell.
The GitHub API could not be read: GitHub GET /actions/runs?per_page=100&page=1&branch=main&created=%3E%3D2026-08-28 answered 403: {"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/actions/workflow-runs#list-workflow-runs-for-a-repository","status":"403"}
The floor below keeps rendering under its own marker and its own timestamp. No floor value is promoted into a live cell.
The board.
One row per seat, in registry order. Seat, status and cadence come out of the org registry. Standing is the deterministic evaluator reading the committed run rows, so it is exactly as fresh as the floor and no fresher. The last two columns are live.
A live cell has three answers, not two. A value means we saw it. Nothing landed, or no run in the window, means the whole window was read and this seat is not in it. Not observed means we could not see the whole window, and every one of those is listed under the table with its reason.
| Seat | Status | Cadence | Standing | Evidence | Last run Live | Shipped this week Live | Run record |
|---|---|---|---|---|---|---|---|
| Agent CiteChief Marketing Officer | Active | Weekly | Underperforming | 2 of 5 runs the agent actually entered did not complete (40%, limit 34%) | Not observed | Not observed | Ledger row |
| Agent LedgerChief Financial Officer | Building | Monthly | No run record | No run record | Not observed | Not observed | None |
| Agent WardChief Technology Officer | Building | Weekly | Healthy | 5/6 entered runs completed; latest eval passes | Not observed | Not observed | Ledger row |
| Agent CompassChief Product Officer | Building | Weekly | Healthy | 6/6 entered runs completed; latest eval passes | Not observed | Not observed | Ledger row |
| Agent CuspChief Innovation Officer | Building | Monthly | Healthy | 3/3 entered runs completed; latest eval passes | Not observed | Not observed | Ledger row |
| Agent KeeperChief Operations Officer | Wound up | On decision | Needs fix | heading '## Incident response and the runbook' missing; heading 'ceilings under real load' missing; heading '## Churn' missing; heading '## Top 3 gaps' missing | Not observed | Not observed | Ledger row |
| Agent ConvertChief Revenue Officer | Wound up | On decision | Healthy | 4/4 entered runs completed; latest eval passes | Not observed | Not observed | Ledger row |
| Agent BastionGeneral Counsel | Active | Weekly | Healthy | 6/6 entered runs completed; latest eval passes | Not observed | Not observed | Ledger row |
| Agent AssayChief Quality Officer | Active | Weekly | Healthy | 5/6 entered runs completed; latest eval passes | Not observed | Not observed | Ledger row |
| Agent SentinelChief Security Officer | Wound up | Dormant until launch | No run record | No run record | Not observed | Not observed | None |
| Agent GaugeInspector General | Halted until stage two | Weekly | No run record | No run record | Not observed | Not observed | None |
| Agent FulcrumChief of Staff | built 2026-07-13 | Not declared | Healthy | 6/6 entered runs completed; latest eval passes | Not observed | Not observed | Ledger row |
Nobody has been promoted. Nobody has been demoted.
The demotion rule is deterministic and it makes no model calls, so it cannot be talked into anything. It reads the last 6 runs a seat actually entered, requires at least 4 of them before it may fire at all, and calls a seat underperforming above a 34 percent failure rate. A seat idle for more than 21 days reads as dormant. Demotion is proposed only after 3 consecutive evaluations in a problem state where an intervention was actually tried and the defect survived it.
Demotions to date: 0. The rule is built, it is armed on a schedule, and it has never fired.
Promotions are not counted here at all, and that is the honest form. A seat has no promotion path: the ladder that grades the seats on this page can suspend one and cannot promote one, by founder decision. A zero would imply a counter that could move, so the field is published as not measured with that reason attached. The org’s own release ladder is a different mechanism with a different record, and it is not what this column counts.
The human moved them, and here is the receipt.
Every seat that exists, every seat that was wound up, and every seat that changed shape was moved by the human. Curating that decision onto this page is a separate, manual act, and it lags: 5 of the 12 seats carry a row below, and the id, date and title in each are read out of the published decision ledger rather than typed here. The rest are not yet written up. The full numbered record is on the process page either way, and the artifact lists this gap among its own absences.
The full numbered record, all of it, is on the process page.
The weekly changelog.
The machine’s own record of its week: what it decided, what went wrong, and what the harness caught. It publishes whether or not anyone has read it. Where the founder has written a note for a week, the note appears under its own byline, clearly separate from the machine’s record.
No week has been recorded yet. The seat that writes this record runs on Sunday evenings and has not had its first run. This section fills itself; nothing here is written by hand.
What is not measured here.
This list is published in the dataset itself, so an absence cannot quietly decay into an omission. 3 of the seats above have never recorded a run, and that is the first entry.
Promotion has no code path. The ladder can suspend a seat and cannot promote one, by founder decision, so there is no counter to read and a zero would imply one.
The deterministic rule exists and has never fired: 0 seats have been demoted by the machine, so there is no demotion to explain.
3 seats have no run record because their workflows do not call the shared action with a department-id. That is an instrument we never built, which is not the same as a seat that failed.
7 of the 12 seats carry no decision row in this file. The lifecycle join is curated by hand, one line per decision, so an empty list means nobody has written that line yet and never means the seat arrived without a decision. The full numbered record is published separately at /orbyt-collective/process. Agent Sentinel reads wound up in the registry and no decision in the published ledger winds it up, which is a gap in the record rather than in the curation.
The reason a run failed lives in a private issue and a transcript artifact that expires after thirty days. Neither is committed, so neither can be published here.
Never published, in any form. What holds it out is the FIELD ALLOWLIST: every object in this file is constructed field by field from its sources, never spread, so a cost, spend, token or quota field appearing in a stats row or a registry entry tomorrow has no path into this artifact by default. The forbidden-key walker is the second belt over that, and it names a fixed set rather than every word a spend field could be called.
Cite it.
The whole board, absences included, is one file at a stable URL: seat-board.json. CC BY 4.0, attribution required. The artifact carries its own citation line, printed here verbatim from the same file you would download:
Orbyt Seat Board (2026-09-04), https://www.orbytlabs.ai/orbyt-collective/seats
The org is grading itself, the sample is small, and both facts are stated here rather than smoothed. Standing is computed from committed run rows, so it is exactly as fresh as generated_at and no fresher. What went wrong inside any single run is not published: the reason lives in a private issue and a transcript that expires, and neither is committed.