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.
Community Mesh launch analytics
Owner-visible report for the 6G Community Mesh Studio link. Proved actors can be counted when the session proves them; unproved visitors stay aggregate. Interest capture now reads from the Studio runtime projection; Corpus and Flow refs are alpha evidence until the shared adapters are connected.
Opens
1 sessions
Proved actors
Signed or otherwise proved
Anonymous aggregate
Not deanonymized
LinkedIn inbound
Referrer or launch seed
Owner contextual link
Generates a short Studio URL for The Paradox of Power. The link record stores the piece, seed, community, journey, public-safe prompt/context, owner Thing, and alpha Flow/Corpus/Chronicle evidence refs.
Live runtime mesh
This view joins the local runtime rows that exist now: contextual links and opens, interest choices, public discussion metadata, share events, reBe invocation events, and member-message metadata rows when they exist. Private message bodies stay out of owner-safe analytics, public projection, Corpus envelopes, and party-line reports; shared Corpus/Flow/Chronicle service writes remain unavailable until those runtimes land.
Short links
Owner-created seeded links
Link opens
Fresh/return visitor opens
Interest choices
Accepted visitor lenses
Comments
Public discussion events
Share edges
Send/share/link creation evidence
reBe invokes
Ask reBe launch events
Member messages
Private-message metadata rows
No short contextual links have been opened yet. Create one above, open it in a fresh browser, then this becomes the first share-chain edge.
member-messages
member-messages
Member-message Flow contract is integrated, but no allowed or denied message.sent runtime rows exist for this piece yet.
shared-service-write
Studio currently reads local runtime materialization. Shared Corpus/Flow/Chronicle production service writes are not verified live.
The launch link or piece route was opened.
The visitor opened, commented, or replied in the Studio discussion layer.
The visitor followed a Studio branch into another piece.
The visitor explicitly invoked reBe from the piece.
The visitor copied or opened a contextualized send/share path.
No branch opens recorded yet. Studio branch links are counted when they carry `branchFrom`.
1 events · 1 sessions · 1 proved actors
1 events · 1 sessions · 1 proved actors
Producer Console
Keep the working area focused on the piece. This rail shows what is ready, what still needs proof, and what Studio has actually recorded.
Current piece
Media Intelligence inputs
Missing
No transcript is linked yet. Add owner-supplied text/file now, or request Media Intelligence once that capability route is available.
Missing
No image description, OCR text, or frame notes are linked yet. Studio will consume these outputs from Media Intelligence when available.
Studio only displays and links these outputs. Transcription, image description, OCR, embeddings, and provider routing belong to Media Intelligence, Flow, Corpus, Keyring, and PolyAgent.
Upload readiness
Uploads write into the canonical Studio bucket for this Network, Owner, and Piece.
This Piece is contributed by the Owner Thing into the Network. The public page can be simple, but the storage, Community thread, provenance, invite, and future economics stay scoped by Network + Owner + Piece.
Publish readiness
{
"slug": "the-paradox-of-power",
"title": "The Paradox of Power",
"description": "The first Concept to Reality piece: why the next digital world has to be machine-first and sovereignty-first, and why power should move through owned Things instead of platform dependency.",
"type": "video",
"tags": [
"enterprise",
"gov"
],
"tier": "free",
"audiences": [
"enterprise",
"gov"
],
"minio_url": "",
"thumbnail_url": "/og-default.png",
"source_notes": "Source media staged at /Users/mnichols/Downloads/studio-content-notebooklm/The_Paradox_of_Power.mp4. Upload should target networks/cyos/owners/thing_m1a2n7x/pieces/the-paradox-of-power/ and remain labeled staged until media, transcript, thumbnail, manifest, context pack, and receipts exist.",
"access": {
"publicMedia": true,
"publicTranscript": false,
"memberTranscript": true,
"memberSourceNotes": true,
"memberDiscussion": true,
"memberRebePath": true,
"workingRoom": false,
"publicTranscriptExcerpt": "Prepared public excerpt only. Canonical transcript, thumbnail description, manifest, context pack, and projection receipts are still pending production ingestion.",
"memberSourceNotesText": "Source media staged at /Users/mnichols/Downloads/studio-content-notebooklm/The_Paradox_of_Power.mp4. Upload should target networks/cyos/owners/thing_m1a2n7x/pieces/the-paradox-of-power/ and remain labeled staged until media, transcript, thumbnail, manifest, context pack, and receipts exist.",
"guidedRebePrompts": [
"Explain The Paradox of Power in plain language for a first-time CyOS reader.",
"Why does a machine-first digital world need ownership by Things instead of platform accounts?",
"What should I ask next if I care about sovereignty, identity, Corpus, and reBe continuity?"
]
}
}Start here
Pick the main video, audio, PDF, slides, or image. Then upload as owner, or upload and request public publish in one step.
Required. Choose the video, audio, PDF, slides, markdown, text, or image that becomes the Studio piece.
Studio storage is not ready yet.
Main artifacts can be up to 250 MB. Upload creates the Studio asset URL automatically; you normally do not need to paste bucket links by hand.
Generated Studio URLs
These are public HTTPS object URLs served from the Studio content bucket. The published Studio page uses them to render the artifact; they are not the final Studio page URL.
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.