Social Studio

Authority

Service IDs:

Repos:

Hosts:

Dependencies: topolo-auth, applications-packages, topolo-nexus

Depends on Topolo Auth: yes

Contract Source

Type: curated

Source: PlatformApplications/TopoloSocialStudio/package.json

Source exists: 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`.

API key scopes in Auth catalog: 11

Auth Requirements

No global OpenAPI security scheme is declared.

• api_keys.write
• approvals.write
• assets.read
• assets.write
• briefs.read
• briefs.write
• exports.read
• generation.write
• settings.write
• workspace.read
• workspace.write

Runtime and Deployment

Wrangler surfaces: none detected

Environment variables: none derived

Routes: workers.dev or Pages-only delivery

Observability enabled: no explicit signal found