TopoloCompose

What It Is

TopoloCompose is the Topolo workspace for creating, reviewing, revising, and exporting formal documents with AI.

The Compose workspace is a document-first workbench with a separate two-column Plan surface and a wide Review draft canvas with focused document-side inspectors. It combines brief templates, inspectable generation briefs, editable document-type draft plans, draft-readiness preflight planning, selected source-pack evidence, imported text/Markdown/CSV/JSON evidence files, source material, generated drafts, review/edit modes, markdown autosave, citation intelligence, private suggestion previews with change review, selectable document sections, focused-section revision, citation-aware quality checks, targeted revision actions, Word/HTML/Markdown/RTF/text/print export controls, and share actions without forcing source setup and draft editing into the same body.

Topolo People can open Compose with employee document context so common HR documents can be drafted from People in one action.

Architecture

The application uses the shared Topolo shell, Topolo Auth, and Nexus-backed AI model routing.

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 production host is https://compose.topolo.app.

API Reference

Authenticated document generation, private suggestion, and revision routes live under /api/documents/*.

People-to-Compose document requests use authenticated Compose sessions and prefilled document intents from Topolo People.

Auth and Permissions

Signed browser and API requests use Topolo Auth through the app id resolved from the stable topolo-compose service slug.

Data Ownership

TopoloCompose owns document workflows, document-domain state, mode-separated planning/review/export presentation, inspectable generation-brief assembly, editable document-type draft planning, draft-readiness preflight scoring, selected source-pack evidence, imported file evidence in the browser planning session, markdown draft editing, citation-coverage analysis, selectable section focus, private suggestion approval and change review, quality review presentation, source-review preparation, and client-side export actions. Nexus owns outbound AI provider invocation and model preference routing.

Mobile Experience

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

Published permissions: workspace:read, workspace:write.

• /documents uses /api/documents with the record.list template and compose.documents.list data source.
• /documents/:id uses /api/documents/:id with the record.detail template and compose.documents.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 production host is https://compose.topolo.app.

Failure Modes

• generation fails when Nexus rejects or cannot route the caller's authenticated AI request
• employee document generation does not start when a People intent is missing required prompt context
• service slug resolution or deployment Auth-origin metadata can drift while the product is still planned
• durable document persistence is not introduced until the org-scoped document model lands

Debugging

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

Use It

Open Topolo Compose 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-compose --json
topolo actions --service topolo-compose --json
topolo actions capabilities --service topolo-compose --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 Compose 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 2 published route(s) against apps/TopoloCompose origin/staging 3bd51606ef58 on 2026-07-27.

• Reconciled this page against apps/TopoloCompose origin/staging 468820b46a11 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/TopoloCompose commits through af31198; reviewed 187 commits since 2026-06-13, including af31198 chore(deps): refresh @topolo-io/app-shell pins (package.json + lockfile); bdb88b5 Stop blocking startup on i18n readiness; 4927e67 Adopt canonical Topolo typography; 59d9a75 Lazy load Compose shell.

• Upgraded the Compose workspace on 2026-06-13 into a document-first workbench with a separate two-column Plan surface, a wide Review draft canvas with focused revision inspector, and an Export inspector; brief templates, inspectable generation briefs, editable document-type draft plans that shape generation before the model call, draft-readiness preflight scoring with unresolved evidence-gap checklisting, source-pack controls and imported text/Markdown/CSV/JSON evidence files that attach selected evidence to generation and revision, citation intelligence for supported/unsupported claims, private suggestion previews with line-level change review and explicit accept/discard, selectable outline sections, focused-section revisions, review/edit modes, markdown autosave, citation quality gates, source-review actions, targeted revisions, multi-format client-side exports, share actions, and responsive desktop/mobile layout checks.

• Centralized runtime app identity on 2026-05-13 so Compose resolves the topolo-compose slug instead of compiling concrete app ids.

• Added TopoloPeople employee document launch support on 2026-04-27.

• Added the initial TopoloCompose product surface on 2026-04-27.

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