FT FixTrustOpen MVP
End-to-end operational spec

Every step from registration to payout.

This page mirrors the code workflow and gives a product manager / engineer the exact checkpoints to implement.

1. Registration and identity

  1. Customer creates account or uses demo login: name, email, phone, language, property profile.
  2. Pro creates account: name, languages, service areas, categories, hourly floor, payment onboarding status.
  3. Admin can verify ID, background, license, insurance and payment status. Verification unlocks higher-risk categories.
  4. The MVP stores identity in localStorage; production moves to Auth provider plus compliance checks.

2. Customer request intake

  1. Customer enters address, category, budget range and preferred access window.
  2. Customer can dictate the request by voice using browser SpeechRecognition; fallback demo transcript exists.
  3. Customer uploads close-up and context photos. Mock AI tags every image and stores it in Evidence Vault.
  4. Request stays problem-first: customer describes what is broken; platform converts it into scope language.

3. AI scope and risk gate

  1. AI combines text, voice transcript and photo metadata to infer title, included items, excluded items, questions and price range.
  2. Risk Engine classifies request as green, yellow or red based on category, budget threshold and text red flags.
  3. Green jobs can route to minor repair pros; yellow jobs route to verified/licensed pros; red jobs require admin/licensed routing.
  4. Scope is locked before offers so customer and pro are negotiating the same work definition.

4. Offer selection

  1. Compatible pros see open requests and may submit offers freely. No penalty for not bidding.
  2. Customer chooses offer by trust, price, schedule, language, license/insurance status and category history.
  3. Selecting an offer generates a Work Order: pro, schedule, labor price, fees, scope, evidence requirements and claim window.

5. Work Order and mock protected payment

  1. Customer confirms the Work Order and mock payment authorization is created.
  2. Payment state moves from Not authorized to Authorized, but no real Stripe call is made in v0.7.
  3. The Work Order is the transaction control surface: scope, photos, acceptance criteria, materials policy and guarantee cap.

6. Pro execution protocol

  1. Pro marks on the way, arrived, uploads before photos, then starts work.
  2. Before photos are required because they establish baseline condition before payout can be justified.
  3. If hidden conditions appear, pro requests a Change Order with photo evidence and amount; customer must approve before extra work is payable.
  4. Pro submits completion notes, after photos and receipts. Job moves to Customer review.

7. Customer acceptance or dispute

  1. Customer reviews completion photos and checklist.
  2. Customer can accept work, rate the pro and move the job to Payout pending.
  3. Customer can open a structured dispute: reason, desired outcome, description and photos.
  4. Opening dispute moves payment to Payout held and creates a case for Admin review.

8. Admin payout or resolution

  1. Admin sees risk queue, dispute queue and payout queue.
  2. For Payout pending jobs, Admin releases mock payout and job becomes completed.
  3. For disputes, Admin can release payout, require rework, approve partial refund or approve full refund.
  4. Every action writes an audit log entry and updates internal ledger where relevant.

9. Repair Record and trust score

  1. Completed job keeps permanent Repair Record: scope, photos, Work Order, payment state, review and dispute history.
  2. Pro Trust Score updates from rating, photo compliance, dispute rate, completion history and verification.
  3. Internal token ledger is not crypto; it tracks behavioral incentives: trust score deltas, shield reserve, repair credits, reliability strikes and category unlocks.