A high-leverage operator, not a manager: owns the backend machine while the Chairman sleeps.
Reports to the Executive Chairman. Titled Co-Chairman (proposed); joined against the rest of the system on the track name Co-Chairman.
governance/pipelines.json names Co-Chairman as its owner_role. That is the join returning empty, printed as empty — padding it with the pipelines this seat merely touches would make the page read as though it owned them.supporting_roles.led_by. The count is genuinely nil and is printed as nil.The company runs 4 brands, and every one of them is listed — including the ones this seat has no pipeline on, because “nothing here” is an answer and an omission is not. This seat is on the hook for 0 of the rows below. Every brand is not a brand: it means the pipeline is brand-agnostic and serves all of them at once, so a failure there is felt everywhere simultaneously.
| Brand | Owns | Supports | This seat / all pipelines |
|---|---|---|---|
| Finessionals | none | none | 0 of 3 |
| Temerarii Media | none | none | 0 of 1 |
| Dom Davis Network | none | none | 0 of 1 |
| Lil Shop of Culture | none | none | 0 of 4 |
| Every brand | none | none | 0 of 4 |
This is the section that prevents the arguments. Almost every dispute about a role is a dispute about its edge, not its centre — two people both believing something was the other's, or one person quietly annexing a decision that was never theirs. Writing the edge down is cheaper than settling it later, on air.
Conditions of the seat. They are stated up front because discovering one of them in week three is a wasted seat for everybody.
19 of the 23 scoring rules apply to this seat — 19 that apply to everyone and 0 written for this track specifically. They split by who observes them: 14 are read by the machine and 5 are judged by a human. That split is the point of the format — the record is read from the system, not from anyone's recollection of your week.
Nobody types these in. An emitter already in the stack produces the record, which is why each one names the file that proves it. 9 of 14 have a live emitter today.
| What | Effect | Read from |
|---|---|---|
| The full gate suite green at the end of a week every seat | not set | engine/goal.pyprints GOAL ALIGNED |
| A blocker open more than three working days without its owner acting every seat | not set | engine/gates/verify_projects.pyprints PROJECTS PASS |
| A deliverable passed its target week without acceptance (owner seat) every seat | not set | engine/gates/verify_projects.pyprints PROJECTS PASS |
| A filed report not reviewed by the next standup (reviewer seat) every seat | not set | engine/gates/verify_eod_reports.pyprints EOD-REVIEW PASS |
| A missed calendar deadline every seat | -30 | engine/gates/verify_calendar_alignment.pyprints CALENDAR-ALIGN PASS |
| A missed or postponed KPI deadline agreed in sprint planning every seat | -20 | no emitter yet |
| An active deliverable with no acceptance criteria every seat | not set | engine/gates/verify_projects.pyprints PROJECTS PASS |
| Exposing an API key, token or secret in the repository every seat | -100 | engine/gates/verify_no_secrets.pyprints NO-SECRETS PASS |
| Late to an obligatory meeting, live broadcast or event every seat | -50 | no emitter yet |
| Missing end-of-day report — completed, blocking, next every seat | -10 | engine/gates/verify_eod_reports.pyprints EOD-REPORTS PASS |
| No acknowledgement of a direct communication within 4 hours of an operational window every seat | -15 | no emitter yet |
| Pushing unapproved or un-QA'd work to a live production surface every seat | -50 | no emitter yet |
| Submitting work that ignores the documented baseline every seat | -25 | engine/gates/verify_render_ready.pyprints RENDER-READY PASS |
| Work unreachable because it was never pushed, while the owner is offline every seat | -30 | no emitter yet |
These are the ones no emitter can settle: pacing, recovery and presence on air, whether a pitch landed, whether the room responded. The verdict is entered on the producer panel — which names where the call is recorded, not who forms it; an Executive Manager ruling lands on the same panel.
| What | Effect | Why a human and not a gate |
|---|---|---|
| A segment executed flawlessly on air every seat | not set | Genuinely human-judged |
| Chat vibe check — the room responds to the segment every seat | not set | Genuinely human-judged |
| A pitch that fails its live review every seat | not set | Genuinely human-judged |
| Escalating without showing what you already tried every seat | -15 | Human-judged: whether self-help was shown is a reading of a message, not a field |
| Manually doing repetitive work the established tooling could automate every seat | -25 | Human-judged: 'could have been automated' is an engineering opinion about a specific task, and the Executive Manager's ruling is entered on the panel |
governance/scoring.json forbids printing a placeholder on a candidate page, and engine/gates/verify_scoring.py lists every one of them on every run. You will not be scored against a number you were never shown.governance/pay.json could not be read, so no figure is shown rather than a remembered one. The published ladder is on the show page.