SWITCHBOARD standard

Switchboard applies four independent gates to every stream: mechanical checks on the phone, a picture review, a speech review that never sees the picture, and an audience gate that acts only on statistical evidence. All four must hold at once, every one defaults to deny, and a review that errors or expires is a rejection rather than a pass. This page is generated from the same constants the gates apply, so it cannot drift from them, and every clause has a stable id a ruling can cite.

The standard

Version v1.1.0, in force since 2026-08-29. Served as JSON at /api/standard.json, and by every broadcast node at /api/standard. This version, frozen.

This page is generated from the constants the gates apply, at build time, so it cannot describe a rule the code does not enforce. 1 of the 17 numeric thresholds below has been measured; the rest were chosen ahead of a field test and are marked unmeasured one by one.

Four gates. A feed reaches air only when every one of them holds at once, and never reaches air because a check failed to run: an error is a rejection carrying the error.

What this undertakes to do

These are the two principles the reviewer is given, verbatim, above every clause below. They are published as the reviewer reads them rather than rewritten for this page, so there is one copy and it cannot drift: the second person is addressed to the reviewer, not to you.

1. The default is NOT to broadcast. If you are unsure, reject. Going dark is a
   normal, acceptable outcome here and carries no penalty. Putting something
   unacceptable to air is the only real failure.
2. You are judging THIS material, not the operator. Do not speculate about
   intent, and do not reject for being amateurish. Shaky, plain and dull is
   fine. Community broadcast is supposed to look like the community.

1. Mechanical

Judged on the publisher's own device, once a second.

2. Picture

Judged on key frames, server side, with no transcript.

Held off air for any of these:

And explicitly NOT grounds to refuse a feed:

A picture clause holds the PICTURE. Nothing that stream is showing reaches air, and if no other stream qualifies the blue screen does. Its sound may still be used, because the speech gate reviewed that separately and a clause governs its own modality: the two reviewers never see each other's material, so neither can overturn the other.

3. Speech

Judged on the transcript, server side, with no frames.

Held off air for any of these:

And explicitly NOT grounds to refuse a feed:

A speech clause holds the SOUND and not the picture. A stream whose picture cleared and whose sound did not goes to air without its audio, and the audio is not sent rather than muted in the player: what the standard refused does not leave the building. What a viewer sees.

4. Audience

Judged on viewer ratings, after the fact. This is the only gate that cannot prevent first harm, because people can only rate what they have already seen. It never acts on one rating.

The gap here is consent, not minors. The standard already carries a clause protecting a minor from being named in a negative, accusatory, mocking or sexualised way, and nothing in it refuses a school game. What is missing is a consent flow for anybody who ends up on camera, which is as true of an adult rec league as of a school one, and until it exists this should not be pointed at an event where the people in frame have not agreed to be broadcast.

The footage the picture gate was measured on is a different matter and is why the figure can be published at all: it is public-access archive that already aired, licensed to permit adaptation, so testing against it points a camera at nobody.

How the rules are enforced

The 60-second hold, and how it got there

A verdict about a moment arrives after that moment. Holding the public output behind live is what makes the picture and speech gates preventive rather than commentary: the cut lands before the material is shown, as long as the hold covers the delay.

The hold was 20 seconds. An audit this project runs against its own delay found that 20 did not cover measured gate latency, which meant the gates were retrospective while the system said otherwise. Nobody outside noticed and nothing forced the change. It is 60 seconds now, above a derived floor and inside a ceiling read from the media plane's own configuration.

The remaining limit, stated rather than omitted: at nine simultaneous feeds the worst gate measured 35.9 seconds, and no hold that fits the streaming window covers that. The binding constraint there is how many feeds one machine can review, not the delay.

Version history

Rulings cite the version they were made under. This is that list, so a citation resolves rather than dangling.

Each version is frozen at its own URL, so a ruling made under one still resolves after the rules change: that is what makes a clause id citable rather than a pointer to whatever the standard says today. When a version bumps, cached verdicts taken under the old one are DROPPED rather than carried forward, because a verdict is an answer to the standard that was in force when it was made.

These are change notes and not computed diffs, and the distinction is deliberate: the previous version's clause text is not kept, so nothing here can derive what moved. It can only report what the people who moved it said. A rendered diff built from prose would be a fabrication in a diff's clothes.

A ruling you can look at

A blurred, featureless pale tan surface filling the whole frame. No people, no court, no detail: what a phone sees face down on a bench or hard against a wall.
The frame, at the size the gate reviewed it. Mat-Su Valley Community Media (MRVTV), Houston vs. Palmer boys basketball, 7 January 2017, archive.org/details/HU_Boys_Basketball_1-7-17, CC BY-NC-SA 4.0.

Ruled 2026-08-30 under v1.1.0 through the shipped review path, 5 of 5 draws rejected.

What the reviewer said, in its own words: Frame is an out-of-focus blur of a flat tan surface (wall/floor) with no discernible subject or event content, the camera is not showing anything. Default is to reject when no coverage of the event is visible.

Held off air under visual.not-the-event. Held off air. Nothing about the game, the operator or the picture quality the rest of the time: only whether the camera was doing its job in that window.

Drawn five times before being published, because one draw cannot tell a ruling from a coin flip. The first candidate for this slot was a photograph this team owns, and the gate approved it thirteen times in fourteen: publishing its single rejection would have presented a seven percent outcome as the standard's behaviour.

And one we may not show you

Kept deliberately. The difference between these two entries is the argument for owning your evidence: this one is on footage belonging to somebody else, so the frame can only be described, and you are asked to take the most consequential example on this page on trust. That is the posture switchboard exists to argue against, which is why it is no longer the only one here.

Ruled 2026-08-30 under v1.1.0. The frame is not shown: the footage is somebody else's and we may not republish it.

The material: a moment from a real high school varsity basketball game, from a public access television archive, where a spectator walks in front of the camera and roughly seventy percent of the frame becomes an out-of-focus back.

What the reviewer said it saw, in its own words: The image appears to be mostly blank with some dark areas and faint light reflections. There are no discernible objects or text that can be clearly identified due to the lack of detail and clarity.

Why it held the feed: The description states the image is 'mostly blank' with 'no discernible objects or text', which meets the criteria for 'showsSomething' being false. Clause visual.not-the-event.

Outcome: Held off air. The camera was not doing its job in that window, which is what the clause is about. It is not a judgement about the game, the operator, or the quality of the picture the rest of the time.

Appealing a ruling

There is no appeal route yet, and this page will not pretend otherwise. A published address that nobody reads is worse than none: it costs somebody the effort of writing and returns silence. Rulings carry an appeal field that is deliberately left empty for the same reason, so the code and this page say the same thing.

What a ruling does carry today is the clause it was made under, the version of these rules in force at the time, and which reviewer ruled. That is enough to argue with, and it is what an appeal route would need as its input.