Back Office · office.temerarii.xyz
Produces the show in exchange for the studio's engines - and hunts global clients with us under Models A and B.
Partner · not a seat

Produces the show in exchange for the studio's engines - and hunts global clients with us under Models A and B.

Reports to the Executive Chairman. Titled Producer - partner; joined against the rest of the system on the track name Producer Partner.

Status. Two producers ready to sign collaborative agreements (2026-08-24). Phase One is a value barter; the commercial models follow.

The exchange

The ask. Step in as Producer for the show, providing full-stack value and oversight of all aspects of the streaming and broadcasting architecture.

The give. The studio deploys its resources, marketing automations and skills to build or execute whatever the partner's operations need.

Partnership models

ModelRule
A — ReferralWhen the studio explicitly acts as the partner's U.S. representative: the studio makes the introduction, the partner contracts and delivers directly, and the studio takes an agreed percentage of collected revenue.
B — White labelWhen the studio sources the client or holds first contact: the studio sells and manages the relationship under its brand; the partner operates as the engineering arm at a fixed price.
C — Joint offerBuilt toward once delivery is proven under A and B. Not active.

A and B run concurrently; which applies is dictated by how the client was acquired. Percentages and fixed prices live in the signed schedule, not here.

What this seat owns

Pipelines it owns

None. No pipeline in governance/pipelines.json names Producer Partner 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.

Pipelines it supports

None. Producer Partner does not appear in any pipeline's supporting_roles.

Episodes it leads

Zero. No episode in the season spine names Producer Partner as its led_by. The count is genuinely nil and is printed as nil.

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

BrandOwnsSupportsThis seat / all pipelines
Finessionalsnonenone0 of 3
Temerarii Medianonenone0 of 1
Dom Davis Networknonenone0 of 1
Lil Shop of Culturenonenone0 of 4
Every brandnonenone0 of 4
The content goals per brand are not repeated here. Follower and revenue targets, the never-delegate list and the per-brand self/tech/creative split live on brand operations, which owns them. A second copy of a target is a second target — and the first time one is edited, two pages start telling a participant different things about what they are driving at.

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.

What you are measured on

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.

ONE POINT = ONE US DOLLAR against the weekly adjustment schedule. The adjustment schedule these settle against is on the operations policy, and the weekly cap below limits what any single week can cost.

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. 9 of 14 have a live emitter today.

WhatEffectRead from
The full gate suite green at the end of a week
every seat
not setengine/goal.py
prints GOAL ALIGNED
A blocker open more than three working days without its owner acting
every seat
not setengine/gates/verify_projects.py
prints PROJECTS PASS
A deliverable passed its target week without acceptance (owner seat)
every seat
not setengine/gates/verify_projects.py
prints PROJECTS PASS
A filed report not reviewed by the next standup (reviewer seat)
every seat
not setengine/gates/verify_eod_reports.py
prints EOD-REVIEW PASS
A missed calendar deadline
every seat
-30engine/gates/verify_calendar_alignment.py
prints CALENDAR-ALIGN PASS
A missed or postponed KPI deadline agreed in sprint planning
every seat
-20no emitter yet
An active deliverable with no acceptance criteria
every seat
not setengine/gates/verify_projects.py
prints PROJECTS PASS
Exposing an API key, token or secret in the repository
every seat
-100engine/gates/verify_no_secrets.py
prints NO-SECRETS PASS
Late to an obligatory meeting, live broadcast or event
every seat
-50no emitter yet
Missing end-of-day report — completed, blocking, next
every seat
-10engine/gates/verify_eod_reports.py
prints EOD-REPORTS PASS
No acknowledgement of a direct communication within 4 hours of an operational window
every seat
-15no emitter yet
Pushing unapproved or un-QA'd work to a live production surface
every seat
-50no emitter yet
Submitting work that ignores the documented baseline
every seat
-25engine/gates/verify_render_ready.py
prints RENDER-READY PASS
Work unreachable because it was never pushed, while the owner is offline
every seat
-30no emitter yet
5 of these cannot be scored today. They are real rules with no emitter yet — nothing in the stack currently writes the record they would be read from. They are listed because an admitted gap is safer than an invented signal: a rule pointed at a file nobody writes scores nobody, silently. Expect them to go live during the season, and expect to be told when they do.

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.

WhatEffectWhy a human and not a gate
A segment executed flawlessly on air
every seat
not setGenuinely human-judged
Chat vibe check — the room responds to the segment
every seat
not setGenuinely human-judged
A pitch that fails its live review
every seat
not setGenuinely human-judged
Escalating without showing what you already tried
every seat
-15Human-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
-25Human-judged: 'could have been automated' is an engineering opinion about a specific task, and the Executive Manager's ruling is entered on the panel
Not set8 of the rules above have no point value yet.
The RULE is real; the NUMBER has not been set by the Chairman, so it renders as not set rather than as a figure. 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.
No rule is written specifically for this track. Every rule that applies here applies to all four seats. That is worth knowing rather than glossing: this seat is measured entirely on the shared standard, so its differentiation shows up in the pipelines and episodes above, not in a private scoreboard.

Everything this seat needs to read

Conditions

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.
No pay track matches this seat. 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.

All five roles · the show