# Customer request journey 2

Saved 7 November 2026. The original `/request-order/` files are unchanged. New public entry: `/request-order-2/`; role links use `?role=crafter` and `?role=designer`. The frontend index lists both versions.

## Scope and decisions

- Keep the design manual typography, controls, cards, spacing, roles and supplied imagery. New composition is in `journey.css`; no parallel component system.
- Customer starts from an existing paid pattern, requests an approved adaptation, or commissions an original design. The idea input performs a small labelled demonstration match against the one recorded Permin pattern, not AI generation.
- Three request steps; collect only delivery area initially. Full address/email at checkout and optional private measurements before making.
- Designer proposal, separate simulated design payment, delivery, one included revision and explicit design approval precede the making request. Designer attribution and specification carry through.
- Reserve → quote → customer approval → maker confirmation → successful full payment → assigned commission. Reservation is not assignment. The 24-hour quote reservation is a proposed policy.
- Paid → preparation → making → ready → dispatched → customer receipt → explicit acceptance/release → provider-confirmed payout. Delivery, elapsed time and silence never release making payout.
- Decline/reopen clears the previous reservation and agreement. Revised quotes require approval again. Failed payment leaves the request unassigned. A support issue pauses the project; no automatic refund or resolution is simulated.
- Closing an unassigned making request after design approval keeps paid design access/history; it does not imply a refund.

## Prototype boundaries and launch requirements

This is an interactive frontend review, not a transactional service. State is in `localStorage` key `krafthub-request-journey-2-v1`, scoped separately from the original. Workspace switching is a review control, not authentication. Do not enter real personal or payment information. No messages leave the browser. The default maker Ingrid Solheim and original-work designer Maren Studio are example profiles; Permin participation or permission to adapt is not established by the preview.

1. Persist accounts and projects server-side with per-role authorisation and optimistic locking. Reservation/expiry and transitions need atomic enforcement, idempotency and server time. Client guards demonstrate the intended order only.
2. Connect an opted-in designer directory, permitted adaptations and licensed catalogue. Search must use actual eligible patterns. Confirm licence and ownership terms, designer fees, payout/refund milestones and included revisions before launch.
3. Replace the textual designer handoff with versioned files and structured, validated size, gauge, construction and yarn requirements. Both customer and maker must see the exact approved version. An adaptation’s material plan must be reconciled with the base pattern, not silently reused.
4. Replace sample retailer quotes with price/stock snapshots for exact quantities/colours, including both deliveries. The current fixture uses Kamma NOK 95, Angel NOK 79, custom yarn NOK 1,000 and combined delivery NOK 199 only after the reviewer attaches a labelled example quote. These are not live retailer facts. Pattern NOK 49 comes from the retained reference, not a new live-price verification.
5. Connect secure payment provider events, separate design and making ledgers, receipts and idempotent assignment. Preserve existing illustrative customer fee 10% and crafter deduction 10% only if commercial policy confirms them. Design fee payout terms are intentionally not invented here.
6. Share delivery and fit information only with the assigned maker; designers do not get customer street addresses in the UI. Real access restrictions must be enforced by the backend.
7. Add real notifications, shipping/tracking, evidence upload and human support resolution. Define cancellation/refund/change-order handling; issue state is a handoff, not a resolved dispute.

## Source and validation

Entry: `entry.ts` → `journey.tsx`. State machine: `journey-model.ts`. Original shared assets, material data, UI components and styles are retained as source dependencies; legacy composition files are not the new entry.

Use Node, install with `npm ci`, then `npm run dev` or `npm run build`. The build uses relative asset paths for the nested preview folder. `public/review.html` and `public/HANDOFF.md` travel with the build.

Validation: TypeScript check and Vite production build; 44 lifecycle checks covering roles, required details, designer approval/revision, reservation expiry, failed/duplicate payment guards, assignment, issue handling and payout order. Browser walkthrough of existing-pattern request and new-design commission; the latter exercised all three roles, failed and successful simulated checkout, making updates, dispatch, receipt, explicit acceptance and provider-confirmed payout. Desktop and 390/320 px narrow-layout review. Original request-order file hashes verified unchanged before publication.
