schoolshow.network -- the livestream

Honest about what is wired, and honest about what is not.

Grandparents three states away. A deployed parent. A sibling stuck in the hospital. The broadcast layer that could one day put them in a front-row seat is real, and this page states plainly how far it is wired today: an adviser or admin can schedule a PRIVATE broadcast, a fully-wired round trip. Public playback -- what a family outside the school would actually watch -- is honest-off end to end. There is no player on this page, because there is nothing to play yet.

Book a conversation See the full three-piece map

Current state

No public livestream is available on schoolshow.network today.

This is not a countdown or a coming-soon teaser -- it is the exact, current state of two named backend routes. A school's adviser or admin can schedule a PRIVATE broadcast today; that path is a real, tested round trip. Publishing a broadcast beyond private, and every path to public playback, is honest-off: refused with a plain not-provisioned response, never a fabricated video address, never a player that looks live and is not.

What is wired, what is not

Four capabilities, each named to the exact route that runs it

Every status label below matches the named route's real, current behavior -- never softened, never strengthened.

1 · Schedule a private broadcast

An adviser, co-adviser, or admin can create and manage a scheduled broadcast for their school, gated behind a per-school module toggle -- a school where the module is off looks byte-identical to today. A minor account (a coarse 'student' role) is hard-denied from scheduling or managing a broadcast, fail-closed, because a broadcast can capture student images. A private broadcast's status advances scheduled to live to ended, or to canceled from either open state; an illegal transition is refused. This is the fully-wired path: real data, stored and read end to end, for a private audience.

Built and wired -- module-gated, adviser/admin only, minors hard-denied

Named contract: apps/api/src/routes/livestream-broadcast.ts

2 · Publish a broadcast beyond private

Moving a broadcast to unlisted or public exposes student images and is consent-gated at the platform's canonical publication chokepoint. That chokepoint is not provisioned in this wire-up, so a non-private schedule is refused outright today -- nothing is stored, nothing is published. This is a deliberate, fail-closed hold, not a bug: enablement of public broadcasting waits on that consent chokepoint being wired, not on this page's copy.

Honest-off -- refused, nothing stored, pending the consent chokepoint

Named contract: apps/api/src/routes/livestream-broadcast.ts

3 · The ticket-gate check in front of playback

Before a byte of video would ever be served, a viewer's opaque ticket gate code is decoded and re-validated against the real box-office order snapshot -- a stream ticket is honored only when its bound order is paid. The box office's live payment rail is honest-off everywhere in the family, so every viewer is correctly and honestly denied an unpaid entitlement today. There is no preview or allow-anyway path.

Built and wired -- correctly denies every viewer while the box office is honest-off

Named contract: apps/api/src/routes/stream-entitlement.ts

4 · Public playback itself

No playback rail -- no HLS, no RTMP, no manifest -- is provisioned anywhere in the platform. The playback endpoint returns a plain not-provisioned response, never a fabricated video address, even for a viewer who is fully entitled and fully consent-cleared. This page renders no video element, no player shell, and no watch-now control, because there is genuinely nothing to play.

Honest-off -- no rail provisioned, no address ever returned

Named contract: apps/api/src/routes/stream-entitlement.ts

Get started

Tell us where your program stands on streaming

There is no pricing commitment and no signup on this page. A conversation shows the current, honest state of the broadcast layer and what it would take to move a piece forward.

To book: email [email protected].

FAQ

Common questions about the livestream

Can a family outside the school watch a livestream today?

No. No playback rail is provisioned anywhere in the platform. The playback endpoint returns a plain not-provisioned response, never a fabricated video address, for anyone.

Can an adviser schedule a broadcast today?

Yes, for a private audience. Scheduling and managing a private broadcast is a real, tested round trip, gated to an adviser, co-adviser, or admin. A minor account is hard-denied from scheduling or managing a broadcast.

Why can a broadcast not be made public yet?

Publishing beyond private exposes student images and requires consent clearance at the platform's canonical publication chokepoint. That chokepoint is not provisioned in this wire-up, so a non-private schedule is refused outright today -- a deliberate, fail-closed hold, not a bug.

If I have a ticket, can I watch the stream?

Not today. Every viewer's stream entitlement is checked against a real, paid box-office order -- and the box office's live payment rail is honest-off everywhere in the family, so no order is paid yet. The entitlement check is correctly and honestly denying every viewer right now.

Is there a demo player or preview on this page?

No, and there will not be one until a playback rail is actually provisioned. This page names the real, current state of the two routes behind it rather than showing a player that looks live and is not.

What happens to a student's on-camera image in a private broadcast?

It stays private to the scheduling school -- the private path never crosses the consent chokepoint because it never leaves private visibility. A minor account cannot schedule or manage a broadcast at all, and any move to a wider audience is refused until the consent gate is wired.