Bytes
Media and asset management surface for uploads, organization, review, and sharing.
Documentation Map
What It Is
Media and asset management surface for uploads, organization, review, and sharing.
Architecture
Owners: media-platform
Source repos:
Dependencies: topolo-auth, applications-packages
Repo shape
No repo surface entries were detected from the registered repo paths.
Runtime Surfaces
Hosts:
https://bytes.topolo.app https://bytes-api.topolo.app https://bytes.stg.topolo.us https://bytes-api.stg.topolo.us No wrangler surface was discovered under the registered repo paths.
API Reference
Coverage: curated
Source: PlatformApplications/TopoloDocs/src/content/public/applications/bytes.mdx
Source exists in repo: no
Canonical Bytes coverage now lives in the docs application, the browser launcher lane now reads Auth-owned catalog data through same-origin /api/auth/* on the Bytes host, the browser callback delegates one-time `sso_code` exchange to the shared Auth client without exposing a legacy `/sso?token=` route or app-local `/sso/exchange` parser, accepts a compact exchanged-token payload, and SPA-navigates after auth update events so the memory-only token survives protected-route hydration. First-party embedded password login also completes through Bytes-owned router navigation after shared Auth token persistence. Closed lazy panels and modals are deferred until opened so `/browse` startup is not held behind hidden Suspense loaders. The worker now requires Topolo Auth validation for all operator bearer tokens with no Bytes-local JWT secret path. Bytes keeps app identity in the repo-level app-identity module and resolves the concrete Auth service id from the canonical topolo-bytes slug at runtime for browser headers, worker permission checks, API-key management, notification emission, and widget responses. Bytes exposes `GET /api/widget` with the shared `@topolo/sdk` widget response contract for TopoloOne live workspace.
App API page: /reference/apps/topolo-bytes
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_JUFXzHBX4eWq API key scopes
Manage Bytes machine credentials
Resource pattern: none
Delete files and folders
Resource pattern: none
View and download files
Resource pattern: none
Upload and edit files
Resource pattern: none
View folder structure
Resource pattern: none
Create and organize folders
Resource pattern: none
View stored media assets and metadata
Resource pattern: none
Upload, update, and delete media assets
Resource pattern: none
Invoke media-processing pipelines
Resource pattern: none
View shared files and permissions
Resource pattern: none
Share files and manage permissions
Resource pattern: none
View storage usage and analytics
Resource pattern: none
Service permissions
api_keys:write, files:delete, files:read, files:write, folders:read, folders:write, media:read, media:write, pipelines:invoke, sharing:read, sharing:write, storage:read
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/TopoloDocs/src/content/public/applications/bytes.mdx
- Neither OpenAPI nor README-derived interface detail was found.
Debugging Runbooks
Start with these entrypoints:
- PlatformApplications/TopoloDocs/src/content/public/applications/bytes.mdx
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.