Network catalog
1
Visible/static + published pieces
Edit existing piece
Update copy, access, transcript state, and guided prompts for pieces this owner can manage.
Upload new piece
Add the artifact, transcript, thumbnail, access layer, and publish request.
Launch/Test
Smoke public, member, owner, seeded-link, and reBe paths before promotion.
Public catalog
1
Visible without member grant
Member catalog
0
Grant-required pieces
Staged catalog
0
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.
Network: cyosOwner: owner pendingDraft only · not publishedAuthority proof: pending
Producer Console
Status and guidance.
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
The Paradox of Power
Artifactneeded
TranscriptMissing
Image/OCR contextMissing
Publish4/6
Media Intelligence inputs
Transcript
Missing
No transcript is linked yet. Add owner-supplied text/file now, or request Media Intelligence once that capability route is available.
Image description / OCR
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
Checking Studio storage.
Uploads write into the canonical Studio bucket for this Network, Owner, and Piece.
How publishing works
1Choose Upload as owner so Studio can prove the publishing Thing and role grant.
2Choose the main artifact; Studio auto-fills title, slug, and type.
3Optionally add thumbnail or transcript material.
4Set free/member boundaries.
5Upload as owner, then Publish as owner only when owner/admin proof is accepted.
Tenancy and storage details
network: cyosowner thing: owner pendingrealm: realm pendingpiece: the-paradox-of-powerstorage: networks/cyos/owners/{ownerThingId}/pieces/the-paradox-of-power/community: studio://cyos/owners/{ownerThingId}/pieces/the-paradox-of-powerconfigured role grants: policy not visible yet
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
4/6 checks ready.
Named artifactThe Paradox of Power · the-paradox-of-power
Generated asset URLUpload the artifact file to generate the Studio bucket URL.
Free visitor valueAt least one public layer should be useful before anyone pays.
Studio Pass valueDefine what $49/mo will unlock: notes, transcript, member discussion, guided reBe path, or source trail.
Transcript/source planSet a transcript state or use a document/slides artifact.
Working Rooms separatedKeep $149/mo rooms marked coming soon unless that room is genuinely available.
Free vs paid: make the public piece useful on its own, then reserve full transcripts, source notes, member discussion, guided reBe paths, and later working rooms for the coming member layer.
Smoke links
public: https://studio.cyos.io/cyos/studio/the-paradox-of-powerowner: https://studio.cyos.io/cyos/studio/owner/pieces?piece=the-paradox-of-powerseeded: https://studio.cyos.io/cyos/studio/the-paradox-of-power?seed=launch-linkedin&to=Recipient%20Name&from=Producer&org=cyos&role=Reviewer&invite=owner-smokejourney checklist: https://studio.cyos.io/studio/test-journeys
1. Open public in a fresh profile and confirm useful content appears before payment.2. Open owner tools after proof and confirm upload readiness is green.3. Open seeded in a fresh profile and confirm the invite banner and reBe seed context appear.
Launch rule: this path must prove a signed Thing, a Studio role grant, and the requested action before upload or public publish. Curated launch pieces can still be committed into the static manifest for Git chronicle permanence.
Advanced: content item JSON
{
"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
Choose the artifact file.
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
Upload a draft to generate the Studio asset URL.
asset: generated after uploadthumbnail: optionaltranscript: optional
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.
Recovery / advanced: paste existing Studio bucket URLs
Planned capabilities
Roadmap, not active navigation.
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.
Coming soon
Journeys and rooms
Group pieces into public paths, member journeys, courses, rooms, or launch bundles.
Coming soon
Rules and grants
The access model lives here: visitor, member, producer, signed invites, grants, and collaborator capability.
Coming soon
reBe context packs
Separate public, member, and owner context packs with source contracts and visibility checks.
Coming soon
Members and producers
Paying members, producer collaborators, roles, grants, Stripe status, renewal risk, and value received.
Coming soon
Revenue and payments
Stripe customer references, subscriptions, invoices, total paid, failed payments, refunds, and producer payout views.
Coming soon
Value signals
What members watched, asked, shared, saved, joined, decided, and where reBe helped them get value.