SoC + bounded context
Each context has explicit inputs, outputs, owner, and non-goals to avoid overlap with youtourer transport domain.
Capture route and place intent before transport booking. Inputs: search, city, date/time, interest tags. Outputs: qualified route intent, place shortlist.
non-goals: dispatch, ride booking lifecycle, payment capture
Manage place catalog, offer inventory, and campaign distribution. Inputs: venue catalog, offer rules, campaign budget. Outputs: offer exposure, redemption candidate.
non-goals: wallet accounting, bank payout orchestration
Verify venue visits and eligibility for reward claims. Inputs: check-in signal, trip completion hint, merchant confirmation. Outputs: verified_visit event, rejected/flagged verification.
non-goals: legal arbitration, chargeback processing
Store assisted conversion and reward claim attribution trails. Inputs: assisted_booking, verified_visit, campaign context. Outputs: reward_claim_requested, attribution statement.
non-goals: global loyalty balance source of truth, card processing
Protect ecosystem quality with trust labels and fraud/risk signals. Inputs: moderation events, abuse reports, risk heuristics. Outputs: trust labels, risk flags.
non-goals: transport ops governance, driver licensing control
Project global membership tier and benefits into creatingroute surfaces. Inputs: member tier, benefit eligibility, wallet status snapshot. Outputs: personalized perks view, benefit usage hints.
non-goals: tier policy engine, global reward ledger ownership
Handoff qualified transport intent to youtourer via contract. Inputs: route intent, party size, schedule preference. Outputs: deep link, assisted_transport_booking event.
non-goals: fare calculation, dispatch decisions