Builds and runs the machine that makes everything else cheap.

Reports to the Executive Chairman. Titled Technical Operator / Tech Lead; joined against the rest of the system on the track name Technical Operator.

What this seat owns

• The clip engine, the render path, the pipelines
• Rendering content and updating comp IDs
• Running loops, setting goals, reading gate reports
• Auditing generated content at scale with a VLM
• Telegram ingest, generation pipelines, syndication mechanism

Pipelines it owns

Joined from governance/pipelines.json where owner_role is Technical Operator — 10 of 13. Ownership here means responsible for it existing and working, which is not the same as deciding what it produces.

Pipelines it supports

Named in supporting_roles on 3 pipelines. 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.

Episodes it leads

Leading 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:

Brands those episodes run on

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 brands, and what each needs from this seat

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 5 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.

What each one teaches, and how it is assessed

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.

What this seat is NOT responsible for

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.

Requirements

Conditions of the seat. They are stated up front because discovering one of them in week three is a wasted seat for everybody.

• Must SHIP RENDERED CONTENT, not just code — exercises come with output
• Comfort with the calendar as the source of truth, storyboarding, and template work

What you are measured on

21 of the 23 scoring rules apply to this seat — 19 that apply to everyone and 2 written for this track specifically. They split by who observes them: 16 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.

Automatic — the machine scores these

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 16 have a live emitter today.

Judged — a human decides these

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.

The cap on a single week, and the rules that outrun it

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.

Week one is exempt from all of it — see the pay section below — so the cap first bites in week two.

The ones written for this track

• A production deployment completed with zero errors — automatic, gain
• A content week certifies — every asset, render matches spec — automatic, gain

Everything this seat needs to read

• Content pipelines — what you own
• System harness — stages and gates
• Templates and coverage
• Calendar — the source of truth
• Brand book
• The show and the programme
• Operations and accountability policy

Conditions

What this seat is paid

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.

What winning actually gets you

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.

Week one, and the floor under every other week

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.

All five roles · the show