Topolo Inventory

Public overview of Topolo Inventory, the Topolo item, location, and stock movement workspace.

publicverified 2026-07-28inventoryapplication

What It Is

Topolo Inventory is the Topolo application for managing item records, locations, stock adjustments, and low-stock visibility inside an authenticated operational workspace.

Architecture

The application uses the shared Topolo shell and Topolo Auth for authenticated operator workflows. A Cloudflare Worker serves the workspace and authenticated API surface, backed by an app-owned D1 database.

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

  • Shared landing page at https://inventory.topolo.app/
  • Staging mirror at https://inventory.stg.topolo.us/
  • Shared login page at https://inventory.topolo.app/login
  • Shared auth callback at https://inventory.topolo.app/auth/callback
  • Authenticated workspace at https://inventory.topolo.app/ once signed in
  • Authenticated inventory APIs under /api/items, /api/locations, /api/movements, and /api/dashboard

API Reference

The current production v1 exposes:

  • GET /api/health
  • GET /api/bootstrap
  • GET/POST /api/items
  • GET/PATCH/DELETE /api/items/:id
  • GET/POST /api/locations
  • GET/POST /api/movements
  • GET /api/dashboard

Auth and Permissions

Authenticated browser and API requests use Topolo Auth through app id app_hmvjbv3ZxDnh, supplied to the Worker as APP_ID rather than resolved through a runtime Auth slug lookup. Signed-out operators land on the shared Topolo landing and login screens before entering the workspace. There are no public unauthenticated data collection routes in the v1 inventory product.

Data Ownership

Topolo Inventory stores organization-scoped items, locations, and stock movement rows in its own D1 database. Quantity on hand is derived from the movement ledger rather than edited as a separate mutable balance.

Mobile Experience

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

Published permissions: workspace:read, workspace:write.

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

Topolo Inventory is deployed on Cloudflare Workers with Workers Static Assets at https://inventory.topolo.app, with shared landing, login, and callback pages on the browser surface plus the authenticated inventory workspace after sign-in.

Failure Modes

  • inventory balances drift if writes bypass the stock movement ledger
  • archived items continue accepting stock movement rows
  • item or location identifiers drift from the D1 uniqueness guarantees enforced in migrations

Debugging

  • use the internal handbook for operational detail
  • verify the system registry entry before deployment or service-registration changes
  • smoke dashboard, item, location, and movement routes after deploy when stock logic changes

Use It

Open Topolo Inventory 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-inventory --json
topolo actions --service topolo-inventory --json
topolo actions capabilities --service topolo-inventory --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 Inventory 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/TopoloInventory origin/staging f543e06d9fa7 on 2026-07-27.

  • Reconciled this page against apps/TopoloInventory origin/staging 41593f200928 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/TopoloInventory commits through 37f35f7; reviewed 322 commits since 2026-05-14, including 37f35f7 chore(deps): refresh @topolo-io/app-shell pins (package.json + lockfile); 9a642d7 Stop blocking startup on i18n readiness; f96c326 Fix Inventory required workspace loading; 06d8ca4 Adopt canonical Topolo typography.

  • Implemented the first production v1 with D1-backed items, locations, stock movements, derived quantity-on-hand, and low-stock dashboard on 2026-04-23.

  • npm run typecheck

  • npm test

  • npm run build

  • npm run validate in TopoloDocs