04. User Journeys and Handoffs¶

Journey 1: Lead to prototype request (public)¶

1. User enters data on /get-swapps/.
2. Frontend sends lead payload.
3. User can trigger prototype generation for that lead.

Status: Implemented.

Journey 2: Plan selection to payment¶

1. User opens /platform/.
2. Frontend loads plans.
3. User submits checkout form; backend creates Stripe session.
4. User is redirected to Stripe.

Status: Implemented.

Journey 3: Payment to account provisioning and activation¶

1. Stripe sends checkout completion webhook.
2. IDK syncs subscription and payment state.
3. If needed, provisioning creates client/user/company contract.
4. Activation email with signed token is sent.
5. User completes /sign-up/<token>/.

Status: Implemented.

Journey 4: Activated user to managed customer area¶

1. User logs into IDK.
2. Navigates to modules (tickets, sites, etc.).
3. Access to sites is constrained by feature/limit checks.

Status: Implemented.

Journey 5: Prototype to operational site entity¶

Observed:

• Prototype trigger exists in public flow.
• Site entity and site CRUD views exist in IDK.

Missing/unclear:

• explicit, deterministic bridge that creates or links a Site from prototype output and preserves traceability across systems.

Status: Partial.