| Two-sided/networked offer hypothesis | Customer Journey models contribution and receiving sides separately and records acquisition on each side. | Customer & Exchange Journey |
| Manual coordination of a few matches or transactions | No automated marketplace is built. The Minimum Proof Builder and Operations Map center manual matching and exception handling. | Minimum Proof · Operations |
| “Unsent”, “Map”, and “Exchange” must change customer expectation | A three-axis Promise Lab makes those meanings explicit and propagates implications into proof and risk. | Promise Lab |
| Recruitment effort, failed matches, trust/dispute friction, support workload, fee/price assumptions, repeat intent | Those fields become first-class observation categories across the ledger, operations map, scenario lab, and decision gate. | Evidence Desk · Scenario Lab |
| $0–$1,000 is a startup-capital planning band | The band appears as provenance with repeated warnings that it is neither ICU price nor target spend. | Every route header · Economics |
| Unknowns remain decision inputs rather than blank values | Unknowns are a separate ledger state and affect the Next Evidence Gate instead of defaulting to zero. | Evidence Desk · Next Gate |
| Stop / revise / proceed outcome | The completion view produces stop, revise/repeat, or one-next-test states, never a “validated” badge. | Next Evidence Gate |