Encounter the promise
Record channel and what the person thinks “unsent map exchange” means before explanation.
Legacy concept universe · Future Concept
Customer & Exchange Journey
Trace both sides of the proposed exchange from discovery through commitment, matching, delivery, support, and repeat intent.
Status Future ConceptLegacy ID VU-G01-V001-SS01-AS01Planning band $0–$1,000, not a required spendCommercial availability None verified
Browse this universe
OverviewOpenVenture AnatomyOpenCustomer & Exchange JourneyCurrentPromise LabOpenMinimum Proof BuilderOpenEvidence & Unknowns DeskOpenOperations & Capacity MapOpenEconomics Scenario LabOpenRisk, Rights & ReviewOpenVariants & PivotsOpenNext Evidence GateOpenProvenance & Source FidelityOpenRelated ICU WorldsOpen
Two-sided journey
The same match has two acquisition stories and one shared failure surface.
Use these steps as an observation map. They are not claimed conversion funnels.
Consent to the rules
Clarify artifact boundaries, privacy, acceptable content, timing, and what happens if no match is found.
Take an observable action
Use a lawful commitment signal appropriate to the prototype: participation, reservation, or paid pilot only if justified.
Coordinate manually
Log match criteria, time, mismatch reasons, rematches, and unfilled attempts.
Complete the exchange
Track handoff, questions, disputes, refunds if applicable, and support minutes.
Ask about repeat intent
Record behavior and stated intent separately. Do not extrapolate from a tiny pilot.
What must be learned
- Why contribute instead of keep or share directly?
- What effort is acceptable to make the map exchangeable?
- What privacy or ownership expectations attach to the artifact?
- What makes a match feel fair?
What must be learned
- What is valuable about receiving an unsent map?
- What context is needed to interpret it safely?
- What would make someone reject or dispute a match?
- What would justify repeating the experience?