Monday overview
What a partner operations lead sees first: pipeline state, blocked launches, training gaps, and the one thing that is not negotiable — the content gate.
Pipeline by status
Clubs move requested → vetted → approved → active → paused. Nothing enters active while its launch checklist has an open blocker.
Blocked on the gate
- Curriculum library: 0 approved items — awaiting partner-supplied approved curriculum.
- Materials versioning: no v1 can be published without an inventory row.
- Public statements: none permitted; trademark licence not on file.
- Child-facing surface: none built, by design.
Nine doors in this room
Read / ask / practice / reflect / join a safe event / continue-after-publication are operable as structure. Listen and watch are transcript-only. Verify-sources waits on the rights schedule.
Club roster
Filter the pipeline, then open a club to work its launch checklist. Region granularity is deliberate: a club resolves to a region code, never to an address or a pin.
| Club | Triple Lens | Setting | Region | Status | Leaders vetted | Launch | Blocker |
|---|
Launch checklist
Per-club, eleven steps, three of them hard gates that cannot be ticked in this prototype. A club cannot be set active until every hard gate is cleared with evidence.
—
Hard gates
These three rows are locked. They require artefacts that do not exist yet, so the software will not let an operator fake readiness.
- Approved curriculum package received
- Trademark usage approval for club naming
- Signed school / guardian permission set
Set club active
Disabled by design while hard gates are open.
Leader training
Vetted-adult training tracks with progress that advances as a leader completes a module. Every module that would carry a video or a voice ships a transcript panel — the transcript is the artefact here; no recorded media is claimed to exist.
Module transcript — Safeguarding basics
Captions / transcript stand-inUnder Motion mode → Minimal this animation stays available with an explicit play/pause control, because it is instructional rather than decorative.
Event planner
Adult-controlled entry only: every event requires a named vetted lead, a guardian consent method and a stated ratio. Locations are stored as venue type and region.
| Date | Event | Club | Lead | Ratio | Consent | State |
|---|
Events remain in draft in this prototype. Publishing an event to families requires the approval workflow and school permissions from the partnership gate.
Moderated storytelling queue
Young people's writing is never published by this system. Review states move submitted → screened → redacted → approved for internal use → closed. Anything flagged sensitive stops at screening and its text is not rendered anywhere, including here.
Sealed submissions expose only: an ID, an age band, a submission date and a sensitivity category. No text, no author name, no club. A sealed record cannot be unsealed from this console — it routes to the safeguarding lead outside the product.
Curriculum library
This is the shape of the library, empty on purpose. Items enter only from a partner-supplied authoritative catalog and rights schedule, one row at a time, with a rights status attached.
| Item | Type | Age band | Track | Rights status | Approved by | Version |
|---|
Ingest rules the software enforces
- No item without a catalog ID from the partner schedule.
- No item without a rights status and an owner.
- No item without a named partner approver and a date.
- No free-text authoring inside the product — the product is not a curriculum editor.
- Superseded versions are retained and marked, never silently overwritten.
What a filled row will look like
SAMPLE STRUCTURE — not approved BRAVE contenttrack: <track from partner taxonomy>
rights: cleared / limited / not cleared
approver: <named partner role> · date: <iso>
version: v1 · supersedes: —
Angle brackets are placeholders. Nothing in this box is BRAVE content.