Back Office · office.temerarii.xyz
Every term disclosed in writing before signing — DRAFT, not in force
StatusDRAFT — NOT IN FORCE. Counsel review is already the longest-lead blocker before anyone goes on camera; this belongs in that same review, not after it.
The pay ladder carries the same status: DRAFT alongside governance/policy.json — counsel review pending. Nothing on this page is in force, and no offer goes out against it until counsel has reviewed it.

This is the operations and accountability policy for the Finessionals programme — the terms every participant is held to, written down in one place so a role page, an agreement and this office cannot disagree with each other. UPDATED 2026-08-24: engagement runs in TWO PHASES (see `phases`). The sandbox until 2026-09-30 is an Ask-and-Give barter - no fee, therefore no adjustments; the consequence of not holding velocity is not transitioning. From October, Finessionals is a competitive contest with its own milestone pool, and paid client work is distributed by the engagement's model. The Upwork rail remains the payment MECHANISM for contest milestone releases and fixed-price client work. Previously: ALL ENGAGEMENTS ARE UPWORK FREELANCE CONTRACTS (confirmed 2026-08-08). This is the single most important fact for this document and it changes the conclusion.

The two phases

Stated once, here; roles.json entries point at it. Dates are absolute.

Sandbox - Ask and Give — now until 2026-09-30

A strict barter to pressure-test operational processes. The Give: the studio deploys its resources, automated marketing engines and development skills to build whatever a collaborator's own business needs, with priority access before the wider market. The Ask: the collaborator executes on the studio's projects in their role.

Paid client work. May begin before October. Once processes are proven at the required velocity, paid client contracts are routed to the team and distributed by the engagement's model (referral share or fixed-price white label).

Target. Operational supremacy: a project from idea to a deployed app and an automated GTM engine in days, not months (2-4 day deployments).

Finessionals - the contest — from 2026-10-11

Finessionals operates purely as a competitive contest structure with its own distinct prize/payment pool tied to specific milestones. governance/pay.json holds that ladder and is the only place its figures live. Client revenue is separate and follows the engagement models.

Adjustments. The accountability framework below applies to contest milestones and paid client work - never to the barter phase.

Partnership models

For producer and engineering partners. Which model applies is dictated by how the client was acquired; A and B run concurrently. Percentages and fixed prices live in the signed schedule, never on a page.

ModelRule
A — ReferralThe studio explicitly acts as the partner's U.S. representative: it makes the introduction, the partner contracts and delivers directly, and the studio takes an agreed percentage of collected revenue.
B — White labelThe studio sources the client or holds first contact: it 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.

Who enforces, and how often

The accountability framework is enforced by whoever holds the Executive Manager authority: the Executive Director during the sandbox and beyond; a Co-Chairman only if that seat is settled.

Unapproved 'AI slop' pushed to the monorepo is a quality failure under the quality section; AI use is mandatory under the ai_mandate section.

Adjustment amounts are in governance/pay.json (the contest ladder) and the signed agreement - not here.

A rule that was not disclosed in writing before the contract was signed CANNOT be applied to that contract. This is deliberately self-enforcing — it makes disclosure the company's problem rather than the freelancer's, which is the only version that actually holds.
Chairman's directive, 2026-08-08. Every term is known BEFORE signing. Nothing is discovered mid-season.

Disclosed before signing — every line

The list below is the disclosure obligation itself. If an item on it was not put in front of someone in writing before they signed, the rule behind it does not apply to that contract.

  1. The complete adjustment schedule, every line, with amounts
  2. That elimination may occur AT ANY TIME, not only at round boundaries
  3. That pay prorates to the final day worked
  4. That week one is paid in full and carries no adjustments
  5. The full pay ladder including how rates step at weeks 5 and 9
  6. That rates follow the CALENDAR, not the number of seats remaining — so an early elimination means fewer people at the same rate until the next step
  7. The velocity benchmark, stated as an expectation rather than implied
  8. The required working knowledge, and that it is checked
  9. That own model access is a condition of the seat, at the freelancer's cost
  10. That the programme is filmed, published, and that elimination is public
  11. That the Chairman may stop the programme at any time, with pay prorated by the day
  12. What the seat is worth after the season — SET by the Chairman 2026-08-09: a post-season seat is DISCRETIONARY and NOT guaranteed. Because it is not guaranteed, the disclosure is that THE STIPEND IS THE COMPENSATION, in those words. See governance/pay.json → post_season_seat.
Initialled clause by clause. Initialled per clause, the same pattern as the participant release, so nobody can say a term was buried in a block of text.

And it holds mid-season. A new or altered rule takes effect only after written notice, and never retroactively. If a change materially worsens the terms, the freelancer may end the contract and be paid in full to that day.

The engagement model — Upwork freelance

Classification largely resolves itself. Upwork establishes freelancer-as-independent-contractor by construction, so the behavioural-control concern raised below is much weaker than it would be for a direct engagement.

THE DEDUCTIONS CANNOT BE EXECUTED ON UPWORK. There is no deduct mechanism in either contract type.

Hourly: Tracker hours are billed under Payment Protection. The remedy is to DISPUTE HOURS, not to shave a fee off an agreed rate.
Fixed price: Milestone escrow. Fund, freelancer submits, then APPROVE / REQUEST REVISION / DISPUTE. There is no fourth option that releases an amount minus a penalty.

Applying deductions off-platform means altering agreed terms outside Upwork. That is the category of behaviour that puts an account at risk — and the ENTIRE hiring pipeline for this programme runs on that account. Same family as every other platform-standing risk already recorded: not recoverable by working harder.

Every deduction becomes a MILESTONE STRUCTURE, a contract-end trigger, or a hiring criterion. Upwork already gives you the levers; they are just shaped differently.

Written asExecutes as
the agreed figure per missed KPIKPIs ARE the milestones. Not met, not released. This is the native mechanism and it is stronger than a fine — it withholds the whole milestone, not the agreed figure.
the agreed figure tardinessAttendance is a milestone acceptance criterion. Repeat lateness ends the contract rather than trimming it.
no-call-no-show, immediate terminationUNCHANGED — end the contract. Upwork supports this directly and it is the correct response.
the agreed figure quality first-passREQUEST REVISION. That is exactly what the button is for, and most of this baseline is already machine-checkable by existing gates.
the agreed figure unapproved live deploymentContract-end trigger. It is not a fee-sized event.
the agreed figure comms SLA / the agreed figure EOD / the agreed figure lazy question / the agreed figure silo / the agreed figure manual labourMilestone acceptance criteria and renewal criteria. None of these is worth a payment dispute, and each becomes a reason not to renew.
the agreed figure knowledge check, twice dailyHIRING CRITERION, assessed before the contract — and a renewal criterion after. Quizzing a freelancer for money mid-contract is the least defensible item in the framework and the largest financial exposure in it.

What the platform gives you that a fine does not

Which is why the schedule has to be in the contract terms up front. An adjustment executes as a reduced milestone release, and a freelancer may dispute a partial release. A schedule they agreed to before funding is defensible; one produced afterwards is a dispute. Disclosure is not a courtesy here — it is the mechanism.

The terms

Every section below is the policy as written and selected. Amounts are the adjustment schedule; they are not the pay. Weekly rates, what a winner earns and how the ladder steps at weeks 5 and 9 are on the show page and are deliberately not repeated here — one contractual number in two places becomes two different numbers.

Attendance, punctuality and availability

Time is the constraint. Tardiness bottlenecks a production line where everyone else is already live.

RuleWhat happens
Late to any obligatory meeting, live broadcast or event$50 adjustment
Failure to attend an obligatory event with no prior communicationImmediate termination of the agreement
Why this one keeps money attached — Failure to attend an obligatory event with no prior communication. It kills a broadcast that twelve other people showed up for. Real, attributable, immediate cost.
Exceptions. Overridden only at the Chairman's sole discretion, on insight escalated by the Executive Manager.

Performance, KPI deadlines and payment

RuleWhat happens
All payment is contingent on KPIs met AND written approval from the Executive ManagerCondition of the seat — no amount attached. Enforced by elimination, not by a fee.
Every missed or postponed KPI deadline previously agreed in sprint planning$20 adjustment
What leadership owes you. Leadership supplies context, direction and recommended deadlines. Questions during briefing are expected.

Task ownership and subject-matter mastery

RuleWhat happens
A task assigned in a meeting is the assignee's sole responsibility — whether executed alone or with help, accountability does not transferCondition of the seat — no amount attached. Enforced by elimination, not by a fee.
Become the subject-matter expert within your scope. 'I do not know' is acceptable only when followed by 'and I will find the answer today'Condition of the seat — no amount attached. Enforced by elimination, not by a fee.

The standard of velocity

The benchmark. Chairman's current output: raw idea to deployed app, live website and an autonomous baseline marketing engine carrying 13 weeks of scheduled content — in two weeks.

The goal. Compress that full-stack cycle to 2–4 days. Adding people must not slow it down.

Note. This is a BENCHMARK, not a deduction. It belongs in the job description because it sets expectation honestly — a candidate who cannot work at this pace should self-select out before signing, not be fined afterwards.

Communication and the momentum SLA

RuleWhat happens
Acknowledge direct communications within 4 hours during operational windows$15 adjustment
End-of-day report: what completed, what is blocking, what is next$10 adjustment

Quality assurance and the zero-slop standard

RuleWhat happens
Submitting work that ignores the documented baseline — missing corner mark, broken kinetic typography, output failing the LSOC style guide$25 adjustment
Rework caused by ignoring documented guidelines is completed off-the-clockCondition of the seat — no amount attached. Enforced by elimination, not by a fee.
Pushing unapproved or un-QA'd work to live production — social feeds, live sites, master branch$50 adjustment
Note — Submitting work that ignores the documented baseline — missing corner mark, broken kinetic typography, output failing the LSOC style guide. Most of this is ALREADY machine-checkable by the existing gates. A gate that fails is more defensible than a reviewer who is annoyed.
Why this one keeps money attached — Pushing unapproved or un-QA'd work to live production — social feeds, live sites, master branch. Real, attributable, and sometimes irreversible. A published mistake can be scraped and indexed before it is pulled.

Solve first

RuleWhat happens
Escalating without showing what you already tried$15 adjustment
Conflict, recorded rather than hidden — Escalating without showing what you already tried. DIRECTLY CONTRADICTS the stated position that questions are encouraged. Fining questions produces silence, not self-reliance — and silence surfaces on Thursday instead of Monday.

Infrastructure and asset hygiene

RuleWhat happens
Code to the monorepo, assets to the shared drives. Nothing lives only on a local diskCondition of the seat — no amount attached. Enforced by elimination, not by a fee.
Work unreachable because it was never pushed, while the owner is offline$30 adjustment

Required working knowledge

Everyone must be able to speak to any active project in a meeting they are in. Knowledge of pending projects is optional.

Required working knowledge:

RuleWhat happens
Failing to answer correctly with a real example when randomly asked$10 adjustment
Capped at twice per day
Arithmetic — Failing to answer correctly with a real example when randomly asked. At the cap this is the agreed figure/day, the agreed figure/week — most of a Round 1 stipend, from quizzes alone. This is the single largest exposure in the framework.

The AI and automation mandate

The firm scales through leverage. Manual execution of repetitive work is the thing being replaced.

RuleWhat happens
Actively use agentic tooling — Claude Code, Codex, MCP/CLI integrations, connectors, or equivalent autonomous agentsCondition of the seat — no amount attached. Enforced by elimination, not by a fee.
Maintain your own model access: a funded subscription/API, or an open-source model on your device or a VPSCondition of the seat — no amount attached. Enforced by elimination, not by a fee.
'My AI is down' or 'I ran out of credits' does not excuse a missed KPI. Keep a fallbackCondition of the seat — no amount attached. Enforced by elimination, not by a fee.
Manually doing repetitive work that the established tooling could automate$25 adjustment
Note. KEEP ALL OF THIS AS REQUIREMENT even in the record-weighted variant. Conditions of the seat are legitimate and enforceable by elimination; they do not need a fine attached.

Elimination, proration and week one

TermWhat it means
Elimination is at willElimination may occur AT ANY TIME, not only at round boundaries.
Pay proratesPay is prorated to the final day worked, with any agreed adjustments applied.
Week one carries no adjustmentsADJUSTMENTS DO NOT BEGIN UNTIL AFTER WEEK 1. Week one is learning the machine; penalising it would punish the onboarding the programme exists to provide.
Week one is paid in fullWeek one is paid in full regardless of elimination or adjustment. APPROVED by the Chairman 2026-08-08.
Why week one is guaranteed. Week one is learning the machine. It removes the worst case — eliminated on Tuesday of week two, publicly, having earned very little — and it makes the offer defensible to a candidate reading the terms cold.

How it is paid for. At-will elimination underspends the programme budget which assumes everyone survives to their round boundary. Every early exit frees more than this costs.

How it relates to the grace period. The week-one adjustment grace period in policy.json — same principle, now backed by guaranteed pay rather than only suspended penalties.
How proration actually executes. This is executable. Fund a WEEKLY milestone; on elimination, release the partial amount for days worked. Upwork fixed-price supports partial release when ending a contract — so proration works natively. IMPORTANT CORRECTION to an earlier note: reduced release IS mechanically possible; what is not possible is clawing back money already released, or trimming an hourly tracker payment. Because a freelancer may dispute a partial release, THE ADJUSTMENT SCHEDULE MUST BE IN THE CONTRACT TERMS UP FRONT — which is exactly what the acknowledgement does.

Questions are batched, not capped

Limit the VOLUME of interrupts without punishing curiosity — those are different things, and conflating them produces silence.

 The rule
MechanismBATCHING, not a cap. Questions go in the EOD report or a scheduled block; they are not interrupt-driven.
During briefingUnlimited during briefing. That is the cheapest possible moment to resolve ambiguity.
Why there is no hard cap. A limit on questions asked is a limit on problems surfaced. The failure mode is not a noisy team — it is finding out on Thursday what was known on Monday. Batching preserves velocity; a cap buys silence and calls it focus.

The Executive Manager’s authority

The EM is not an administrator of this framework — they are the gate it runs through, and the seat carries real authority that must be written down or it will be exercised inconsistently.

The seat holdsThe seat does not hold
  • WRITTEN APPROVAL ON EVERY PAYMENT. No disbursement without it — this is the strongest lever in the structure.
  • Sole source of the insight the Chairman uses when granting an exception. A deduction reversal starts with the EM's escalation, not with the individual's appeal.
  • Owns which KPIs are agreed in sprint planning — so the EM defines the thing people are measured against.
  • Judges quality against the documented baseline, and decides what is a genuine gate failure versus a bad brief.
  • Termination — that is the Chairman's
  • Discretionary override of a deduction — the EM escalates, the Chairman decides
  • Setting the deduction schedule itself
And the obligation that comes with it. Because approval gates pay, the EM must run sprint planning so KPIs are SPECIFIC and AGREED IN WRITING. A vague KPI approved by nobody becomes a deduction dispute, and the EM owns that failure.

The full consideration

THE STIPEND IS THE COMPENSATION. Said in those words, because the post-season seat is discretionary and a candidate who reads “the seat is the real prize” and then finds it is at someone's discretion was caught off guard — the one thing this framework forbids. State the rest of the consideration too, plainly and without inflating it: paid training on a real production system, 65 episodes of public portfolio they keep permanently, and a discretionary shot at a seat. A candidate who understands that can accept the rate; one who discovers it later feels misled, and that is the difference between a hard programme and an unfair one.

Round 1 is the agreed figure-the agreed figure/hour depending on hours worked. The requirements demand subject-matter mastery and compressing a two-week full-stack build to 2-4 days. Those attract different people. The resolution is not more cash — it is stating the FULL consideration honestly: paid training on a real system, 65 episodes of public portfolio, and the seat at the end.

What you are actually paid in 
Paid training on a real production systemNot a course and not a simulation — the machine that runs this office, while it is running
Public portfolio65 episodes, published, with your work in them — kept permanently, including if you are eliminated
A shot at the seatDiscretionary, not guaranteed — see immediately below, and read it as the whole of what it says

The weekly stipend itself is on the show page. It is not restated here.

DiscretionaryA 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.
Because the seat is not guaranteed, THE STIPEND IS THE COMPENSATION: the agreed figure-the agreed figure over 13 weeks depending on track, and less if eliminated early. This must appear in the offer in these terms. A candidate who reads 'the seat is the real prize' and then finds it discretionary was caught off guard, which is the one thing the framework forbids.

SET by the Chairman 2026-08-09. NO LONGER BLOCKING. This clause previously blocked every offer because the post-season seat value was unset; the Chairman set it on 2026-08-09 as a discretionary offer, which completes the disclosure. Retained rather than deleted because it records WHY the wording below is what it is: the disclosure was completed by making the answer honest, not by quantifying a prize. Counsel review of this file remains the standing blocker.

Expect this to filter for candidates motivated by the work, the public portfolio and the training rather than by the money. That is a legitimate trade, but it is a trade: the strongest senior applicants run the arithmetic and will discount the offer.

What was decided, and what was considered

Selected: Framework as written — Chairman, 2026-08-08. The framework as written is CANONICAL. Job descriptions, agreements, role pages and the office all render from it. The record-weighted variant is retained below as the alternative that was considered and not taken — kept so counsel sees the choice that was made rather than only the outcome.

Amendments carried into it

The alternative, for the record: Record-weighted variant — RECOMMENDED. The strongest consequence already exists: elimination, decided by a record read from the system. Reserve MONEY for things with a real attributable cost; let the record handle performance. A discretionary fine is a judgment wearing a number — the same objection already raised against a points economy, and less defensible than plainly saying it was a judgment. It is also the version that survives the classification question best, because it asserts less control over method. Not taken.

The acknowledgement

Required from every contractor or team member. It must state:

Sequencing. Sits alongside the participant release. Both are counsel items, and nobody is on camera before both are signed.

What counsel still has to review

StatusDRAFT — NOT IN FORCE. Counsel review is already the longest-lead blocker before anyone goes on camera; this belongs in that same review, not after it.
Read this page as the proposed terms. Nothing here binds anyone until counsel has reviewed it and it is signed, and no offer goes out while the post-season seat is unquantified.

The show and the programme · the roles this applies to · the Executive Manager brief · the Producer’s runbook