Network catalog
Visible/static + published pieces
Producer Console
Update copy, access, transcript state, and guided prompts for pieces this owner can manage.
Add the artifact, transcript, thumbnail, access layer, and publish request.
Smoke public, member, owner, seeded-link, and reBe paths before promotion.
Network catalog
Visible/static + published pieces
Public catalog
Visible without member grant
Member catalog
Grant-required pieces
Staged catalog
Catalog items needing review
Catalog totals describe the public Network catalog. Production-complete Studio pieces should all appear as DB-backed owner-managed records in Pieces; any count gap means legacy static catalog materialization remains.
Owner Pieces
Every production piece should be an owner-managed DB record. Pick a piece to edit public description, member/source notes, access metadata, prompts, and transcript state. New uploads stay in the Upload section.
Owner-managed
Editable by this owner
This list is the owner-editable source of truth. If the public catalog count is higher, legacy static pieces still need catalog materialization before they are production-complete.
Loading owner-managed pieces...
Planned capabilities
These areas are part of the Studio product model, but they are not primary working areas yet. The active console today is Dashboard, Pieces, Upload, and Launch/Test.
Group pieces into public paths, member journeys, courses, rooms, or launch bundles.
The access model lives here: visitor, member, producer, signed invites, grants, and collaborator capability.
Separate public, member, and owner context packs with source contracts and visibility checks.
Paying members, producer collaborators, roles, grants, Stripe status, renewal risk, and value received.
Stripe customer references, subscriptions, invoices, total paid, failed payments, refunds, and producer payout views.
What members watched, asked, shared, saved, joined, decided, and where reBe helped them get value.