Topolo Design

Standalone brand-governed design workspace for static assets and short animated creative clips.

publicverified 2026-08-10designcreativeanimationbrand

What It Is

Topolo Design is a standalone design workspace for creating brand-governed static assets and very short animated clips such as animated ad banners. It remains useful without Social Studio or Socialize.

Architecture

Topolo Brand owns mutable brand kits and immutable published versions. Design reads a published version and records that exact version in each composition. Design owns projects, editable compositions, lightweight per-layer motion, rendering, export metadata, and generated media bytes.

Social Studio remains the richer multimedia production surface. Socialize owns social media libraries, posts, channels, schedules, and publishing. Design can hand a ready asset descriptor to either application without making either one a prerequisite and without publishing a post itself.

Static And Animated Exports

Design exports SVG, PNG, JPEG, and MP4. Short MP4 clips may run from 0.5 to 15 seconds at 12, 24, or 30 frames per second. Layer motion includes fade, slide-up, slide-left, zoom-in, and pulse presets with configurable timing and easing.

The export panel calculates a deterministic estimated file size before rendering. Ready exports retain both that estimate and the actual uploaded byte size so people and agent workflows can compare expected and completed output.

SVG is rendered by the service. PNG, JPEG, and MP4 use a create, bounded binary upload, and ready lifecycle. Browser MP4 export fails explicitly when the browser cannot record a native MP4 stream.

Runtime Surfaces

  • design.topolo.app is the production application.
  • design.stg.topolo.us is the staging verification surface.
  • design.topolo.dev is the development surface.
  • Protected API routes cover projects, export estimation, export creation and retrieval, media upload, social handoff, widgets, bootstrap, and privacy lifecycle.

Auth and Permissions

Topolo Auth owns organization, application access, workspace identity, and the selected authorized workspace. Design persists only an identity mirror required for referential integrity and scopes every project and export to the verified organization and workspace.

Data Ownership

One environment-specific D1 database stores project and export metadata. One private R2 bucket stores generated PNG, JPEG, and MP4 bytes. Object content is reachable only through authenticated Design routes. Brand is consumed through a read-only service binding.

API Reference

Design publishes 16 credential-scoped actions. Read-only discovery covers widget and workspace bootstrap, available Brand versions, project list/get, export-size estimation, export retrieval, and privacy export. Confirmed mutations cover project create/update/archive/restore, export creation and upload, provenance-preserving handoff, and workspace erasure.

Discover the current contract instead of guessing routes:

topolo services --query topolo-design --json
topolo actions --service topolo-design --json
topolo actions capabilities --service topolo-design --json
topolo actions get app_topolo_design.exports.estimate --json

The Agent Actions reference exposes the same schemas, effects, confirmation rules, examples, verification, and recovery guidance.

Deployments

The same source tip promotes through isolated development, staging, and production Workers. Each environment has its own D1 database, R2 bucket, API Worker, web Worker, Brand service binding, Auth registration, and Developers action projection.

Privacy Lifecycle

privacy.export returns the selected workspace's Design projects and export metadata. Confirmed privacy.erase removes those records and their generated R2 objects for the same organization and workspace. The operation does not alter the referenced immutable Brand version or data owned by Social Studio or Socialize.

Failure Modes

  • no authorized Design workspace is selected
  • a referenced published Brand version cannot be resolved
  • a composition contains invalid motion timing or an unknown layer reference
  • an MP4 duration or frame rate is outside the supported bounds
  • the browser does not support native MP4 recording
  • uploaded media has the wrong type or exceeds the 25 MiB bound
  • a handoff is attempted before the export reaches ready state

Debugging

Start with /api/health, then verify the Auth identity, organization, selected workspace, and current action permission. For animation failures, inspect clip duration, fps, layer references, and motion timing. For missing media, compare the export row, status, MIME type, and tenant scope with its private R2 object.

Use It

Open Topolo Design for the product surface. The system handbook records runtime topology, storage, permissions, action ownership, and verification evidence.

Change Log / Verification

  • 2026-08-10: verified standalone animated creative, deterministic export-size estimation, the complete 16-action catalog, schema-valid published examples, and canonical notification-producer behavior against released TopoloDesign source 79e61a639b89a81c9233e21ef6126963b1381957. Development, staging, and production passed the canonical build, typecheck, 102-test, 100%-coverage, changed-line coverage, and workspace conformance gates; both Workers, health checks, headless observation, and migration 0004_animated_exports.sql were healthy at the exact released tip.