Topolo Docs Topolo Platform
Open workspace

Pulse

Public overview of Topolo Pulse in the Topolo application suite.

What It Is

Topolo Pulse is part of the Topolo business application suite.

Architecture

The application uses the shared Topolo landing page, shared login page, auth callback handling, and shared Topolo shell from the outset.

Runtime Surfaces

Pulse is non-production-only. The canonical development host is https://pulse.topolo.dev, and the canonical staging host is https://pulse.stg.topolo.us, with public entry at /, sign-in at /login, and callback completion at /auth/callback.

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 slug topolo-pulse.

Data Ownership

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

Deployments

Pulse runs only on https://pulse.topolo.dev and https://pulse.stg.topolo.us - there is no production deployment.

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 Pulse 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-pulse --json
topolo actions --service topolo-pulse --json
topolo actions capabilities --service topolo-pulse --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 Pulse 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 workspace verification on 2026-06-28 against system-apps/TopoloPulse commits through 7736d12; reviewed 10 commits since 2026-06-26, including 7736d12 chore(deps): refresh @topolo-io/app-shell pins (package.json + lockfile); f9ba9a0 Stop blocking startup on i18n readiness; c3993a1 Adopt canonical Topolo typography; afe9fc0 Roll out ui-kit capture startup split.

  • Scaffold generated on 2026-05-01 from topolo apps scaffold.

  • Updated the public Pulse overview on 2026-06-26 for development and staging runtime Auth app identity resolution from slug topolo-pulse.

  • Added the isolated development Worker target on 2026-06-26 and the isolated staging Worker target on 2026-05-01.