Topolo Success

Public overview of Topolo Success in the Topolo application suite.

publicverified 2026-07-28successapplication

What It Is

Topolo Success is part of the Topolo business application suite.

Architecture

The application uses the shared Topolo shell and Topolo Auth boundary from the outset.

Workspace Management

The shared Topolo workspace control reads and manages app-scoped workspace identity through Topolo Auth: authenticated users can list, create, rename, choose a default, and delete an eligible workspace. Workspace IDs and slugs remain stable and exactly one default is explicit. The selected platform workspace scopes this application's app-owned records; the app retains only domain-specific deletion guards for default or non-empty workspaces.

Runtime Surfaces

The scaffold baseline is live at https://success.topolo.app.

API Reference

The generated API baseline exposes authenticated workspace routes under /api/* and validates requests through Topolo Auth.

Auth and Permissions

Signed browser and API requests use Topolo Auth through the app id resolved from the stable topolo-success service slug.

Data Ownership

The generated baseline has no durable domain data yet. Future data must be organization-scoped at the backend boundary.

Mobile Experience

The checked-in mobile experience contract is approved in native_capability mode. Its fallback route is /dashboard/workspace, its offline policy is read_through_cache, and it requires organization context.

Published permissions: workspace:read.

  • /dashboard/workspace uses /api/widget with the record.detail template and success.workspace.summary data source.

The native clients consume this manifest as an explicit rendering contract. A web mode record intentionally opens the product web experience; native_capability publishes the listed native routes and actions. Do not infer unlisted native behavior.

Deployments

The scaffold baseline is live at https://success.topolo.app.

Failure Modes

  • service registration and app routing can drift while the product is still planned
  • service slug resolution or deployment Auth-origin metadata can drift while the product is still planned
  • organization-scoped data models are not implemented until domain work begins

Debugging

  • use the matching internal handbook for operational details
  • verify the system registry entry before deployment or service-registration changes

Use It

Open Topolo Success for the human product surface. The system handbook records its current hosts, ownership, Auth scopes, storage, deployment, failure modes, and machine artifact.

Discover the credential-scoped automation surface before making an API call:

topolo services --query topolo-success --json
topolo actions --service topolo-success --json
topolo actions capabilities --service topolo-success --json

Choose an action, inspect it with topolo actions get <action-id> --json, then validate and plan a published example. The Agent Actions reference exposes the same public schemas, effects, examples, verification, and recovery guidance.

Example workflow:

  1. Confirm the active identity and organization with topolo whoami --json.
  2. Discover Topolo Success and select one published action rather than guessing a route.
  3. Inspect its input/output schemas and published example.
  4. Validate and plan the exact payload; obtain confirmation for a mutation.
  5. Execute and perform every published verification step.

Change Log / Verification

  • Reconciled the 2026-07-28 fleet audit closure against the source-pinned action, route, workspace, package, and test evidence; no unrepresented human-facing capability was found.

  • Verified the native_capability mobile experience contract and its 1 published route(s) against apps/TopoloSuccess origin/staging 00e4162aa834 on 2026-07-27.

  • Reconciled this page against apps/TopoloSuccess origin/staging d40706517883 on 2026-07-24 after reviewing every docs-relevant commit since its previous verification watermark. Dependency-only currency commits were checked by the fleet production-dependency gate and did not change this page's product contract.

  • Reconciled workspace verification on 2026-06-28 against apps/TopoloSuccess commits through 98dc18e; reviewed 303 commits since 2026-05-14, including 98dc18e chore(deps): roll @topolo-io/* pins to latest (fleet currency self-heal); 457b0c4 chore(deps): refresh @topolo-io/app-shell pins (package.json + lockfile); af53cd1 Stop blocking startup on i18n readiness; 1931224 Adopt canonical Topolo typography.

  • Centralized runtime app identity on 2026-05-13 so Success resolves the topolo-success slug instead of compiling concrete app ids.

  • Deployed Worker/static-assets baseline to https://success.topolo.app on 2026-04-23.

  • Scaffold generated on 2026-04-23 from topolo apps scaffold.