Roles — Temerarii Media Back Office

Five entries: one owner and four seats. Each page says what the role owns, what it is explicitly not responsible for, which pipelines it is accountable for, and how many episodes it leads. None of that is typed here. Ownership is joined from governance/pipelines.json and the episode counts from engine/lib/season.py, so a role page cannot disagree with the system it describes.

The seats, the leadership, the partners and the collaborators

Five kinds of entry. Seats are competed for in the contest; the leadership seat is appointed; a proposed seat is under discussion and nothing on it is in force; partners and collaborators are exchanges, not seats. The two phases every entry runs under — the sandbox barter to 2026-09-30, then the October contest — are stated once on the policy page.

Role	Reports to	Pipelines owned	Supports	Episodes led
Dom Davis Owns the company, the machine and the decision to stop.	—	Not a seat. Owns the programme rather than a pipeline.
Producer Runs the broadcast. Cuts the show, manages participants, and keeps it on air.	Executive Chairman	1	1	7
Executive Manager Runs a brand as its CEO — GTM, funnel, reporting, and what gets produced.	Executive Director	1	3	13
Creative Lead Owns what the work looks like and what it says.	Executive Chairman	1	6	0
Technical Operator Builds and runs the machine that makes everything else cheap.	Executive Chairman	10	3	26
Executive Director Runs the pods. Delegates, tracks and reviews every creative and developer, and leads the other Executive Managers.	Executive Chairman	0	0	0
Co-Chairman A high-leverage operator, not a manager: owns the backend machine while the Chairman sleeps.	Executive Chairman	0	0	0
Producer (partner) Produces the show in exchange for the studio's engines - and hunts global clients with us under Models A and B.	Executive Chairman	0	0	0
Collaborator Builds the automation with us; gets first use of the engines for their own business.	Executive Director	0	0	0

Those episode counts sum to 46, not 65. The remaining 19 are attributed to nobody in particular by design — 13 to counterparts, 6 to each participant. Two days a week belong to the whole room rather than to a seat, and rounding them into a track would overstate one person's ownership of a day the format deliberately shares.

The registry holds 13 pipelines. Every one of them is owned by a track on this page. Priority order and the build status behind each are on the pipelines page, which owns them.

One of these is not like the others

Four of the five entries are seats being competed for — three people per track, narrowing to two, then to one, across thirteen weeks. The Chairman entry is not hired, not eliminated and not assessed. It has no track, which is why both joins return nothing for it and why it uses a different page shape. Printing four empty tables under his name would have been the tidier-looking mistake.

The person who can end the broadcast must not be one of the people competing in it. That single rule decides the access model — including why platform credentials are never held by a Producer during a selection round, even though the Producer runs the show.

What applies to every seat

Every seat, without exception. Every participant must have their own Kick, Twitch, YouTube, Instagram, TikTok and Facebook channels, all six available for joint co-streams. This is a condition of the seat, not a preference. Nobody appears on camera before counsel-reviewed release forms are signed. The Chairman may stop the programme at any time, with payment pro-rated by the day. How the record is read: The record is read from the system — registry entries executed, gates passed, work published. Where a rule genuinely cannot be read by a machine, governance/scoring.json marks it source:producer and says so on the page; nothing is scored as machine-observed that a human actually decided.

Every seat is scored from the same registry: governance/scoring.json, 23 rules.
17 are read by the machine — 11 of those have a live emitter today and 6 are declared with no emitter yet. 6 are judged by a human and entered on the producer panel. 10 carry a point value the Chairman has not set, so they render as not set and not as a number. Each seat page lists the ones that apply to it, the emitter that proves each, and the rules that cost more than that seat's own weekly cap.

Where these pages come from

Section	Source	Join
Purpose, owns, boundaries, requirements	`governance/roles.json`	read directly
Pipelines owned and supported	`governance/pipelines.json`	`owner_role` / `supporting_roles` → `track`
Episodes led	`engine/lib/season.py`	`led_by` → `track`
Brands, and what each teaches	`governance/pipelines.json`	`brand` / `teaches` / `assessed_by` of the pipelines the seat owns
What you are measured on	`governance/scoring.json`	`track` → role `id`, split on `source`
Pay, the weekly cap, the floor	`governance/pay.json`	track `id` → role `id`
Per-brand content goals	brand operations	linked, never restated — a second copy of a target is a second target

A join that returns nothing is printed as nothing. Where one does, the seat page says so with the reason rather than padding the section. An empty section on a roles page is information — it is usually the most useful thing on it, because it is where the org chart and the build disagree.

The show · content pipelines · broadcast architecture