08. Risks and Recommendations

Top risks

  1. Prototype-to-site identity discontinuity
  2. Risk: lost traceability between what was generated and what was delivered/maintained.
  3. Cross-system state fragmentation
  4. Risk: support and operations need manual correlation across leads, checkout, subscriptions, sites, and tickets.
  5. Business-doc drift
  6. Risk: engineering implementation and product expectations diverge when BRD/workstream references are missing or outdated.
  1. Introduce a canonical journey_id propagated from lead creation through provisioning and site creation.
  2. Enforce explicit linkage keys on site records (lead/prototype/subscription references when applicable).
  3. Add a lightweight event timeline API for customer lifecycle observability.
  4. Publish and version this map in team rituals (architecture review + product ops cadence).
  5. Recover and attach missing BRD/workstream docs to this package for requirement traceability.

Quick wins (2–4 weeks)

  • Add linkage fields and event emission at provisioning boundaries.
  • Add operational dashboard filter by journey_id.
  • Add automated regression checks for checkout→provisioning→activation path.