Topolo Flow

Public overview of Topolo Flow in the Topolo application suite.

publicverified 2026-07-31flowapplication

What It Is

Topolo Flow 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://flow.topolo.app. Staging mirrors it at https://flow.stg.topolo.us with a staging build that keeps Auth calls inside the staging installation.

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 app id app_GBCuKkHhnRXv.

Data Ownership

Flow owns organization-scoped flow definitions and execution records. Nexus owns stored provider connections and their lifecycle status; Flow does not override that status when it supplies connection credentials and metadata.

Mobile Experience

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

Published permissions: workspace:read, workspace:write.

  • /flows uses /api/flows with the record.list template and flow.flows.list data source.
  • /flows/:id uses /api/flows/:id with the record.detail template and flow.flows.detail data source.
  • /runs uses /api/runs with the record.list template and flow.runs.list data source.
  • /runs/:id uses /api/runs/:id with the record.detail template and flow.runs.detail 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://flow.topolo.app.

Failure Modes

  • service registration and app routing 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 Flow 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-flow --json
topolo actions --service topolo-flow --json
topolo actions capabilities --service topolo-flow --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 Flow 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 Nexus connection-status ownership boundary against apps/TopoloFlow origin/staging e4e6da045f87 on 2026-07-31.

  • 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 4 published route(s) against apps/TopoloFlow origin/staging 53f367d8e0ad on 2026-07-27.

  • Reconciled this page against apps/TopoloFlow origin/staging c75288452658 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/TopoloFlow commits through d9d27ff; reviewed 344 commits since 2026-05-14, including d9d27ff chore(deps): refresh @topolo-io/app-shell pins (package.json + lockfile); b82cc49 Adopt canonical Topolo typography; 6714eed Lazy load Flow startup routes; 5c4cfd6 Roll out ui-kit capture startup split.

  • Verified Flow staging origin isolation on 2026-04-30.

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

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