Topolo People

Public overview of Topolo People in the Topolo application suite.

publicverified 2026-07-29peopleapplication

What It Is

Topolo People is part of the Topolo business application suite. It manages org-scoped employee records, configurable onboarding workflows, HR task tracking, and employee document generation in TopoloCompose from People context.

Architecture

The application uses the shared Topolo shell, Topolo Auth, and a People-owned D1 employee and onboarding record store.

Employee document actions open TopoloCompose with the document type, style, audience, prompt, and selected employee source material already prepared.

Onboarding templates define required fields, required documents, task templates, and signature requirements. People creates TopoloSign envelopes for signature requirements when an onboarding session starts and tracks the Sign envelope id on each related onboarding task.

New hires enter through a dedicated onboarding landing and scoped shell, while organization users retain the People operations landing and workspace shell. Both surfaces use the shared Topolo authentication and landing contracts.

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://people.topolo.app.

API Reference

Authenticated People APIs expose dashboard, employee record, onboarding template, onboarding session, and onboarding task routes under /api/* and validate requests through Topolo Auth.

Employee document generation uses a People-to-Compose browser intent rather than a People-owned backend document API.

Auth and Permissions

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

Data Ownership

Topolo People owns employee and onboarding records in D1 and scopes every row by authenticated organization. Compose receives selected employee fields as source material for generation.

Mobile Experience

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

Published permissions: workspace:read, workspace:write.

  • /employees uses /api/employees with the record.list template and people.employees.list data source.
  • /employees/:id uses /api/employees/:id with the record.detail template and people.employees.detail data source.
  • /onboarding uses /api/onboarding/sessions with the record.list template and people.onboarding.sessions.list data source.
  • /onboarding/:id uses /api/onboarding/sessions/:id with the record.detail template and people.onboarding.sessions.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://people.topolo.app.

Failure Modes

  • service registration and app routing can drift while the product is still planned
  • Compose URL intent fields can drift from the TopoloCompose browser contract
  • D1 migrations must be applied before deploying Worker code that depends on new employee tables
  • employee APIs must preserve the authenticated organization boundary
  • signature tasks can be blocked when the employee has no work email or the current user cannot create envelopes in TopoloSign

Debugging

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

Use It

Open Topolo People 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-people --json
topolo actions --service topolo-people --json
topolo actions capabilities --service topolo-people --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 People 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

  • Verified the dedicated new-hire onboarding landing and scoped-shell entry policy against apps/TopoloPeople origin/staging f16ae19e9825 on 2026-07-29.

  • 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/TopoloPeople origin/staging cb4dc5312ad9 on 2026-07-27.

  • Reconciled this page against apps/TopoloPeople origin/staging 78d2d4b84200 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/TopoloPeople commits through f2c9a55; reviewed 361 commits since 2026-05-14, including f2c9a55 chore(deps): refresh @topolo-io/app-shell pins (package.json + lockfile); 6b8db4a Stop blocking startup on i18n readiness; 3659a3e Adopt canonical Topolo typography; b2909bd Lazy load People shell.

  • Added configurable onboarding templates, onboarding sessions, onboarding tasks, and employee document placeholders on 2026-04-27.

  • Added D1-backed employee records and dashboard APIs on 2026-04-27.

  • Added one-click employee document launch into TopoloCompose on 2026-04-27.

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

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