Communications
—
Stored intake records
BAR TV SPORTS · AI OPERATIONS
Master Control
Operational review, evidence, approvals and verified closure.
Checking system…
Nothing else is open to operators yet.
Findings
—
Structured interpretations
Open operational cases
—
Every case not closed: all dates, parked ones included
Workers
—
Live of total (ok now; stale, error and unknown are not live)
MAIN AI INTERFACE
Ask BarTV AI
The orchestrator chat will sit here. Operational review is now handled below using durable cases and explicit human actions.
DAILY OPERATIONS BOARD
Production priorities
Current readiness and open cases, ranked deterministically. No AI prioritisation.
PREPARE, NEVER COMPLETE
Prepared actions
Changes the system has prepared with evidence and reasoning. Nothing is applied until an admin approves; approved Master Control corrections go to the mirror sheet only.
Select a prepared action
Inspect the evidence, the exact cells that would change, the impact on the operator and kit, then approve or deny with feedback.
DECIDED WITHOUT FULL INFORMATION
Decisions
What the bot, Claude under delegation or an admin decided when the information was incomplete: the question, the evidence, what was missing and the cautious default taken. Confirm what is right, overturn what is wrong with a reason. A confirmed decision is precedent for the same question and scope; a provisional one is context only. Nothing here changes a rule by itself.
Select a decision
See what was decided, on what evidence, what was missing and why the default was chosen; then confirm or overturn it.
OPERATOR RATINGS · MANAGERS ONLY
Biggest movers
Skill ratings Claude moved on evidence (a manager's message or a RunSheet note), one point at a time, written to the mirror's bot page before anyone approved them. Each region reviews its movers here, up and down, largest movement first: uphold what is right, or overturn it to the level you choose with a reason. Your level wins and is written to the bot page under your name. A change nobody reviews stays here: nobody looked is not agreement. Every overturn goes to the product owner as feedback; two against the rule's changes for the same rule and skill pause that rule, which then asks instead of moving anything until an all-regions admin clears the pause. A write that was interrupted or could not be put back is listed under Needs attention until an admin settles it. A rule in shadow mode records what it would have changed or asked, and writes nothing. Claude never reviews its own changes. Operators never see any of this.
Loading movers
ORGANISER LIAISON · DRAFTS ONLY
Organiser drafts
Weekly confirmation emails prepared for the owning manager: the weekend's Master Control rows in the team's format, any differences the fixture sources show, and the evidence. The bot never sends these; check the text and send it yourself. Parked drafts have no confirmed owner; an unknown recipient is shown as unknown.
Select a draft
See the email text, who it is for, the rows and differences it covers, and what is missing.
FIXTURE SOURCES · READ-ONLY
League feeds
The fixture sources the schedule watcher reads every three hours: Cricket Australia, the A-Leagues website, MySideline associations, Touch Football Australia and Sporty match centres. Each row shows when it was last read, when it last changed and how many fixtures it holds. Sources the configuration expects but the database lacks are listed as missing.
Loading feeds
OPERATOR WEEKEND EMAILS · DRAFTS ONLY
Operator emails
One email per operator for the coming weekend: every shift with the row's fixture columns, the crew as resolved names, notes on extra requests (height, big screen, commentary), only the kit identifiers the row names, and the standing reminder. Remarks in the Operator cell, the Equipment free text, kit cells that are not identifiers and ute lines naming other people are held back from the operator; they are shown with each draft as managers only, with the raw Operator cell per shift. A draft never sends by itself and the system never creates a Gmail draft. A message goes only as an approved send under Prepared actions: its signing manager opens the whole message and approves it with their own send code, one at a time, and only for a kind that is switched on. Unknown facts are written as unknown.
Select an email
See the text, who it is for, the shifts it covers and what is missing.
CONTACT REGISTER · EVERY FACT WITH ITS SOURCE
Contacts
Organisers, club contacts and league mailboxes. A person named by the product owner is verified; an address counts only with mail evidence (a sender header or signature), shown on each fact. Senders and signatures of incoming mail become proposals for an admin to verify or reject here. Staff contacts stay on the Staff tab: the register lists staff by name and role and says whether details are on file.
Select a contact
See each fact, where it came from, and verify or reject it.
GEAR CONFIRMATIONS · A PERSON MAKES THE FACT
Gear confirmations
What an operator answered about the gear an upcoming job needs, as the reader read it. Nothing here is a fact until you verify it, and the reader never verifies its own reading. Verifying covers every item of that reply. A "no" is already a task for the region's manager.
Loading gear confirmations
HUMAN CONTROL LAYER
Operational case review
Select a case
Choose an operational case to inspect evidence, history and allowed human actions.
CANCELLATIONS THE SHEET CANNOT SETTLE · NOTHING HERE IS CLOSED
Unresolved cancellations
Rows that left Master Control where the sheet does not settle whether the game was renumbered or deleted. They are kept out of the queue and none of them is closed: a person decides. A Key is a row position, never the game: each row is shown by the game's own details.
Loading unresolved cancellations
INTAKE EXCEPTIONS
Intake escalations
INFORMATION IN
Recent communications
THE BOT'S WORKERS
Agents
AUDITABLE FLOW
Recent event activity
ACCESS
Accounts
YOUR ROWS
Notices from your co-managers
QUIET ITEMS