Runs the broadcast. Cuts the show, manages participants, and keeps it on air.
Reports to the Executive Chairman. Titled Executive Producer; joined against the rest of the system on the track name Producer.
Joined from governance/pipelines.json where owner_role is Producer — 1 of 13. Ownership here means responsible for it existing and working, which is not the same as deciding what it produces.
| Pipeline | Brand | Status | Priority | On air in (block lead) |
|---|---|---|---|---|
| Live broadcast | Finessionals | partial | 0 | BRIEF (Executive Manager), BUILD (Technical Operator), CROSS (counterparts), GATE (Technical Operator), CHECKPOINT (Producer), ADJUST (Executive Manager), PUBLISH (Technical Operator), DEMO (each participant) |
Named in supporting_roles on 1 pipeline. Supporting is not owning. The owner is accountable for the thing working; this seat is accountable for its own contribution to it, and the distinction is what stops a stalled pipeline having two people who each thought it was the other's.
| Pipeline | Brand | Status | Priority | On air in (block lead) |
|---|---|---|---|---|
| Live-to-clip engine | Finessionals | missing | 3 | BUILD (Technical Operator), GATE (Technical Operator), PUBLISH (Technical Operator) |
led_byLeading an episode means this seat is in front of that day — it sets what the day is for and answers for it on air. The breakdown matters more than the total, because it says which kind of day recurs:
| Block | Episodes |
|---|---|
| CHECKPOINT | 7 |
| Brand | Episodes |
|---|---|
| All brands | 7 |
The full itinerary is on the show page, which owns the dates. Sixty-five episodes are not listed here — a second copy of the schedule is a second schedule.
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 1 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 | Live broadcast | Live-to-clip engine | 2 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 |
Every pipeline carries what it is meant to teach and the method it is judged by. This is the assessment that is not a point value — the seat is a paid training position, and this is the syllabus.
| Pipeline | Teaches | Assessed by |
|---|---|---|
| Live broadcast |
| pilot rehearsal: test broadcast, recording played back, clap test, clean Stats dock |
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.
Repository obs-setup. Scene collections, relay, overlays, preflight. Operator access, not owner access.
20 of the 23 scoring rules apply to this seat — 19 that apply to everyone and 1 written for this track specifically. They split by who observes them: 15 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. 10 of 15 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 |
| Zero encoder glitches across a broadcast block this track | +40 | obs-setup/src/telemetry.jsprints skipped_pct |
| 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 |
Total adjustments in any one week are capped at capped (see the agreement) of that week's rate. On this track the first round pays — a week, so the cap is — — the tightest it ever gets, because the first round is the lowest rate on the ladder.
| Rule | Effect | Past the cap by |
|---|---|---|
| Exposing an API key, token or secret in the repository | -100 | — over |
| Late to an obligatory meeting, live broadcast or event | -50 | — over |
| Pushing unapproved or un-QA'd work to a live production surface | -50 | — over |
engine/gates/verify_scoring.py reports the same thing on every run.Week one is exempt from all of it — see the pay section below — so the cap first bites in week two.
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.The rate rises as the field narrows — fewer people, more work, more pay. Read from governance/pay.json; this page holds no copy of it.
| Track | Round 1 wks 1–4 · 3 seats | Round 2 wks 5–8 · 2 seats | Final wks 9–13 · 1 seat |
|---|---|---|---|
| Producer | —/wk | —/wk | —/wk |
The post-season seat is not guaranteed. A post-season seat may be offered to any finalist at the Chairman's discretion. It is NOT guaranteed, and no candidate should accept on the expectation of one. It is said in these terms deliberately: a candidate who reads “the seat is the real prize” and then finds it discretionary was caught off guard, which is the one thing this framework forbids.
Total adjustments in any one week may not exceed capped (see the agreement) of that week's rate. Uncapped, the twelve rules could exceed the weekly rate — the spot-quiz alone at the agreed figure twice daily is the agreed figure against an EM's the agreed figure Round 1 week. A week worked for nothing is not a deterrent, it is an indefensible offer. On this track the worst possible Round 1 week still pays — — the rate less the cap, which is arithmetic rather than a promise.
The full adjustment schedule is on the operations policy, and every line of it has to be in front of you in writing before you sign.