Play canopy design memory
Page jobs
/play/ Invent businesses + run them on shared digital mycelium (intent).
/play/lab/ Invention engine — cultivate → compare → test → evolve onto Process recipes.
/play/ventures/ Example requirements for the shared ops bed; inspect experiments honestly.
Play carries one dual thesis: Lab invents through Process recipes; Ventures + Artifacts + Stackmates show how running works on a shared substrate (“digital mycelium” — metaphor, under development). Dream Seed is tertiary. Global navbar label: Play.
Reader sequence
global Play
→ grasp invent + run (first viewport)
→ system map (Lab/recipes · Ventures/Artifacts/Stackmates)
→ open the lab (/play/lab/) or inspect ventures (/play/ventures/)
→ optional Dream Seed (/play/#dream-seed)
→ evidence returns to the next human-owned decision
Presentation
Spend the persuasive weight on brand-level Play, the dual-intent H1, one supporting sentence, and the Lab / Ventures CTA pair. The system map is the crossing picture — not a three-card door stack.
| Route | H1 / lead job | Picture |
|---|---|---|
/play/ | Invent businesses. Run them on shared digital mycelium. | Invent vs Run system map |
/play/ventures/ | Example requirements for shared ops — honest experiments. | Network + operator spine |
/play/lab/ | Business idea engine wired to Process recipes. | Loop + recipe links per stage |
- One local strip on all three routes: Play · Ventures · Lab.
- Play matches
/play/exactly so child routes do not steal its active state. - Pictures are informing diagrams with HTML labels; no essential text lives inside the image.
- Venture cards stay the catalogue visual. Do not invent proof, tokens, clinic CTA, Attention/COMMIT, or futarchy fundraising claims.
- Mycelium language stays soft: shared substrate intent, not verified adoption.
Proof boundaries
A click is not a joined adventure. A loop diagram is not a proven method. Experiments remain experiments. Mycelium is metaphor + navigation, not platform proof. Render 320 / 375 / 768 / 1440.