Topolo Sign

Public overview of Topolo Sign in the Topolo application suite.

publicverified 2026-07-28signapplication

What It Is

Topolo Sign is part of the Topolo business application suite. It manages electronic-signature templates, envelopes, recipient signing links, and signature audit records for generated or uploaded documents.

Architecture

The application uses the shared Topolo shell and Topolo Auth for authenticated workspace users. Recipient signing sessions use token-scoped public links so external signers do not need a Topolo account.

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 workspace is live at https://sign.topolo.app. Recipient signing links are served at /sign/:token.

API Reference

Authenticated workspace routes manage templates and envelopes under /api/templates and /api/envelopes. Token-scoped recipient routes are available under /api/signing/:token.

Auth and Permissions

Signed browser and API requests use Topolo Auth through app id app_Bd8pRw5ZqRBT, supplied to the Worker as APP_ID rather than resolved through a runtime Auth slug lookup. Recipient links are scoped by signing token rather than platform login.

Data Ownership

Topolo Sign owns organization-scoped signature templates, envelopes, recipients, and audit events in its production D1 store.

Mobile Experience

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

Published permissions: workspace:read.

  • /envelopes uses /api/envelopes with the record.list template and sign.envelopes.list data source.
  • /envelopes/:id uses /api/envelopes/:id with the record.detail template and sign.envelopes.detail data source.
  • /templates uses /api/templates with the record.list template and sign.templates.list data source.
  • /templates/:id uses /api/templates/:id with the record.detail template and sign.templates.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

Production is live at https://sign.topolo.app.

Failure Modes

  • source applications should not mark a document signed until the Sign envelope and recipient statuses confirm completion
  • signed-PDF/certificate artifact generation is not yet part of the first Sign implementation

Debugging

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

Use It

Open Topolo Sign 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-sign --json
topolo actions --service topolo-sign --json
topolo actions capabilities --service topolo-sign --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 Sign 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 4 published route(s) against apps/TopoloSign origin/staging 238b280f702a on 2026-07-27.

  • Reconciled this page against apps/TopoloSign origin/staging 5d7d0adb756b 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/TopoloSign commits through f66da1b; reviewed 311 commits since 2026-05-14, including f66da1b chore(deps): refresh @topolo-io/app-shell pins (package.json + lockfile); 59cf23d Stop blocking startup on i18n readiness; 5df6127 Adopt canonical Topolo typography; 63b818f Fix Sign web deploy build command.

  • Added durable signature envelopes, templates, recipient links, and audit records on 2026-04-27.

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

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