Customer job + reason to switch
Define one segment, one occasion, the substitute, and why “unsent map exchange” changes the expected outcome.
Legacy concept universe · Future Concept
Venture Anatomy
Inspect the connected customer, matching, trust, operations, capacity, economics, and decision dependencies that the source Asteroid class requires.
Status Future ConceptLegacy ID VU-G01-V001-SS01-AS01Planning band $0–$1,000, not a required spendCommercial availability None verified
Browse this universe
OverviewOpenVenture AnatomyCurrentCustomer & Exchange JourneyOpenPromise LabOpenMinimum Proof BuilderOpenEvidence & Unknowns DeskOpenOperations & Capacity MapOpenEconomics Scenario LabOpenRisk, Rights & ReviewOpenVariants & PivotsOpenNext Evidence GateOpenProvenance & Source FidelityOpenRelated ICU WorldsOpen
Venture anatomy map
Eight connected systems, one evidence gate.
A Connected/Asteroid plan only earns its name when these systems affect one another. A plausible card for each function is not enough.
Contribution and receipt
Name who supplies the exchangeable artifact, who receives value, and whether those are the same people at different moments.
Manual coordination
Recruit, qualify, pair, confirm, deliver, and record failures before building automation.
Consent + dispute handling
Define what can be shared, what stays private, what can be rejected, and how a failed or uncomfortable match is handled.
Measure each side separately
A channel that recruits contributors may not recruit recipients. Record source, effort, and commitment for each side.
Minutes become a constraint
Manual review, matching, follow-up, rematching, refunds, and support expose the work that software might later reduce.
Unknowns stay non-zero
Fees, payment costs, labor time, acquisition effort, failed matches, reserves, and fixed costs belong in sensitivity scenarios.
Stop / revise / repeat / proceed
The output is a decision about one next evidence cycle, not a declaration that the venture is validated.
Source-specific implementation decision: the universe makes manual matching a central operating object because the preserved Minimum Proof requires it. It does not jump directly to marketplace software, recommendation algorithms, or automated fulfillment.