Topolo Home

What It Is

Topolo Home is part of the Topolo personal application suite.

Architecture

The application uses the shared Topolo landing page, shared login page, auth callback handling, and shared Topolo shell 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 planned production host is https://home.topolo.app, with public entry at /, sign-in at /login, and callback completion at /auth/callback.

API Reference

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

Auth and Permissions

Signed browser and API requests use Topolo Auth through app id app_hE6HBldVzjth, supplied to the Worker as APP_ID rather than resolved through a runtime Auth slug lookup.

Data Ownership

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

Deployments

The planned production host is https://home.topolo.app. Development and staging mirror the scaffold at https://home.topolo.dev and https://home.stg.topolo.us.

Failure Modes

• service registration and app routing can drift while the product is still planned
• household-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 Home 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-home --json
topolo actions --service topolo-home --json
topolo actions capabilities --service topolo-home --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 Home 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.

• Reconciled this page against apps/TopoloHome origin/staging 31487e5a043b 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/TopoloHome commits through 5daa1ba; reviewed 12 commits since 2026-06-26, including 5daa1ba chore(deps): roll @topolo-io/* pins to latest (fleet currency self-heal); 8dd7491 chore(deps): refresh @topolo-io/app-shell pins (package.json + lockfile); efced3c Stop blocking startup on i18n readiness; 8195702 Adopt canonical Topolo typography.

• Scaffold generated on 2026-05-06; first-party scaffolding now uses restricted topolo-platform apps scaffold.