Social Studio
Hybrid desktop and web production surface for social planning, generation, review, and export. This is the only live Studio-branded application in the suite.
Documentation Map
What It Is
Hybrid desktop and web production surface for social planning, generation, review, and export. This is the only live Studio-branded application in the suite.
Architecture
Owners: socialize
Source repos:
Dependencies: topolo-auth, applications-packages, topolo-nexus
Repo shape
No repo surface entries were detected from the registered repo paths.
Runtime Surfaces
Hosts:
https://studio.topolo.app https://studio-api.stg.topolo.us https://studio.stg.topolo.us No wrangler surface was discovered under the registered repo paths.
API Reference
Coverage: curated
Source: PlatformApplications/TopoloSocialStudio/package.json
Source exists in repo: no
Canonical public and internal docs now cover the hybrid desktop, worker, and Nexus-backed AI generation model. The marketing web and desktop shells delegate browser login handoff and one-time sso_code callback redemption to the shared Topolo auth client through the Social Studio application wrapper, with callback effects kept single-pass so one status update cannot cancel the active exchange/bootstrap. The authenticated web and desktop shells render through `TopoloAppShell`, inheriting the shared account, launcher, account-menu Improve Topolo, and TopoloNotify chrome while keeping Studio project navigation product-owned and avoiding standalone floating report controls. Nexus owns the org-wide image-generation default and allowed model catalog for Studio workspaces, while the generate step may expose per-run inline overrides only to callers with the required workspace authority. Social Studio owns the stable Auth service slug `topolo-social-studio`; workers and browser shells resolve the concrete service id from Topolo Auth at runtime through `/api/service-identity`.
App API page: /reference/apps/topolo-social-studio
This system currently relies on a curated or README-derived contract surface instead of a source-controlled OpenAPI spec.
Auth and Permissions
Depends on Topolo Auth: yes
Service IDs:
srv_nmuJvGQiOnnI API key scopes
Manage Social Studio machine credentials
Resource pattern: none
Approve and route creative work
Resource pattern: none
View creative assets and generated outputs
Resource pattern: none
Upload and manage creative assets
Resource pattern: none
View creative briefs and production requests
Resource pattern: none
Create and manage creative briefs
Resource pattern: none
View export history and delivery status
Resource pattern: none
Start and manage generation workflows
Resource pattern: none
Manage workspace and delivery settings
Resource pattern: none
Load creative workspace state and planning queues
Resource pattern: none
Manage workspace setup and operating workflow
Resource pattern: none
Service permissions
api_keys:write, approvals:write, assets:read, assets:write, briefs:read, briefs:write, exports:read, generation:write, settings:write, workspace:read, workspace:write
Data Ownership
No storage bindings were derived from wrangler configuration.
Queues / Cron / Workflows
Queue bindings:
No queue bindings were detected.
Cron triggers
No cron triggers were detected.
Workflow signals
No explicit queue/workflow script or cron signal was discovered.
Environment Variables and Bindings
Environment variables:
No environment variables were derived from wrangler configuration.
All wrangler bindings
No bindings were derived from wrangler configuration.
Deployments
Deployment environments: default only or not declared
Routes: workers.dev or Pages-only delivery
Observability enabled: no explicit setting found
Failure Modes
- No wrangler.toml surface was discovered under the registered repo paths.
- The registered contract source is missing: PlatformApplications/TopoloSocialStudio/package.json
- Neither OpenAPI nor README-derived interface detail was found.
Debugging Runbooks
Start with these entrypoints:
- PlatformApplications/TopoloSocialStudio/package.json
Change Log / Verification
Lifecycle: active
Last verified: 2026-05-14
Any code change to this system is expected to update the canonical docs in PlatformApplications/TopoloDocs and refresh the verification date.