Documentation overview

Understand the product boundaries before integration.

A practical map of the public demonstration, local platform foundation, and work required before production access. This is an orientation, not a promise of a generally available service.

Public demonstration

The workspace tour runs with fictional browser-memory records. Its role selector previews behavior rather than signing in a user. Reloading or restarting restores the fixtures. Demo scenarios, commands, and limitations are documented in the web repository README.

  • Application details, requirements, customer tasks, and reviews.
  • Simulated carrier acknowledgement and event integrity diagnostics.
  • A CSV mapping preview that does not import production records.

Local platform foundation

The platform implementation is separate from the public demo. Its foundation includes PostgreSQL records, transaction-scoped tenant context, validated bearer identities and organization memberships, event processing, audit records, and an outbox. Local test evidence belongs to the platform repository; it does not certify a deployed environment.

Preparing a technical evaluation

Review the developer approach and the platform README with your integration team. Agree on identity-provider configuration, allowed organizations, environment access, API contracts, and operational responsibilities. Production customer requests, document handling, and external carrier access need their own verified controls.