Getting Started¶
This page gives each reader the fastest path into FlowClaw without needing to read every product page first.
Start Here By Role¶
Merchant Client¶
Start with Merchant Portal.
You only need to understand route requests, recommendation review, required action, proof prompts, assigned pilot cases, and Accept Route.
Platform Admin¶
Start with Admin And Operator Portal, then read Architecture And Security.
You need tenant controls, operator oversight, evidence quality, audit log, route review cases, and merchant visibility controls.
Desk Operator¶
Start with Admin And Operator Portal.
You need route cases, quotes, proof evidence, manual route comparison, controlled review forms, session workbench, and operator queue.
Application Surfaces¶
| Surface | Route | Audience | Purpose |
|---|---|---|---|
| Platform Admin / Desk Operator console | /index.html |
Platform Admin, Desk Operator | Operate sessions, validation cases, proof, readiness, controlled probes, runtime assistant, and audit log. |
| Merchant Portal | /merchant.html |
Merchant Client | Request routes, review recommended route, accept route, and see merchant-safe pilot visibility. |
| Legacy Merchant route | /customer.html |
Merchant Client | Backward-compatible route serving the same merchant portal. |
| Control API | Backend API | Portals, future integrators | Auth, session, route, runtime, case, artifact, provider, and governance APIs. |
Role Names¶
The product language is newer than some code enums.
| Product name | Legacy code enum | Plain English |
|---|---|---|
| Platform Admin | admin |
Administrative user with governance control. |
| Desk Operator | operator |
Operator Company staff member handling cases and proof. |
| Merchant Client | customer |
Importer or merchant receiving route recommendations. |
| Settlement Agent | verified_agent |
Assigned proof provider for a controlled settlement or route-review leg. |
Product Orientation¶
FlowClaw is a route intelligence and operator workflow system. It helps merchants request supplier-payment routes, gives operators a structured route review console, and gives developers an API surface for building around sessions, evidence, artifacts, and tenant-aware access.