Phygital Mycelium

The unseen network that makes everything happen.

Mycelium is the underground network. Mushroom caps are the ventures that pop up wherever conditions are right. PRDs describe capabilities — shared primitives that any venture can compose from. Today there are seven mushroom caps. If this works, there will be millions.

Capabilities​

Each PRD describes a Mycelium capability — a shared lib that any mushroom cap can use. The capability owns the job definition and success criteria. The venture owns the business model and the customer.

Active​

Priorities: Table order = build order.

Top row is what the engineering team builds next. Blocked platform items go first — they block everything downstream.

Backlog​

AI-Native Production​

We operate with software economics in a service-delivery world.

This protocol is documented in the AI-Native Agency playbook.

Commissioning Dashboard​

One view of every capability — what's specified, what's built, what's proven. Maturity levels from L0 (spec only) to L4 (independently verified). Flight readiness gates. Kill criteria. Revenue readiness.

Product Layers​

Each PRD must define the minimum feature set needed to run one complete fair-trade loop: question -> problem -> trade -> proof -> feedback.

Feature Gate​

Before a PRD is considered build-ready:

1. Workflow proof: One end-to-end user workflow with measurable before/after.
2. Entity proof: Core entities and links are explicit (who, what, where, value).
3. Loop proof: Feedback metric exists and updates behavior.
4. Business proof: Pricing and acquisition assumptions are testable this cycle.
5. Trust proof: Safety and settlement model are explicit (especially if tokenized).

The Factory​

PRDs are the specification layer. The engineering repo is the execution layer. The team that builds it never validates it.

DREAM REPO (this)                    ENGINEERING REPO (stackmates)
─────────────────                    ─────────────────────────────
1. Write PRD spec            →  RFP  →  2. Architecture + build
                                         3. Ship feature
4. Commission (validate)  ←  DELIVERY ←  "Ready for inspection"
   Agent reads spec
   Agent opens browser
   Agent checks features,
   functions, outcomes
   against PRD criteria
5. Pass / Fail + evidence

In factory engineering, the team that builds a system is never the team that commissions it. The builder knows what they intended. The commissioner checks what actually shipped. A seed phrase got deleted because nobody independently verified. The Sui Wallet PRD exists so that won't happen again.

Build-to-Revenue Sequence​

PRDs are not product wishlists. They are business development instruments.

The Ecosystem Compound​

The mycelium is not a metaphor. It's an economic structure. Same infrastructure, different revenue surfaces.

Each new product costs less than 20% of the first because the horizontal layer (auth, CRM, pipeline, analytics, workflow) is shared. The vertical layer is what makes each product defensible — domain knowledge that generic tools can't replicate.

SHARED INFRASTRUCTURE (build once)
    ├── ETL (data readiness)
    ├── RFP (sales intelligence)
    ├── Agents (orchestration)
    └── Content (distribution)
         │
         ▼
    EACH PRODUCT'S DATA IMPROVES THE OTHERS

PRD Standard​

Every PRD must include before build handoff:

• Job + Trigger — what event causes demand now
• Feature / Function / Outcome — explicit mapping
• Business Dev — ICP, offer, channels, conversion, retention
• Commissioning — status by component
• Risk + Kill Signal — what would invalidate the thesis fast
• Context — links to horizontal SaaS, vertical SaaS, industry, token layers

Starting Today​

1. Pick a PRD that pulls you — Wallet Safety or Prompt Deck if you want a challenge, a Starter from the backlog if you want to ease in
2. Read the spec — understand the job, the patterns, the success criteria
3. Build — follow the spec, ship something
4. Verify — does what shipped match what was specified?
5. Feed back — update the commissioning table, update the PRD with learnings

Not positive thinking. Positive doing. Optimism is a muscle. Building is the gym.

Context​

• Products — Best practice methodology for what we build
• Jobs To Be Done — Demand validation framework
• Flow Engineering — Maps that produce code artifacts
• Standards — Where safety patterns graduate to
• Mushroom Caps — The ventures growing from this network
• Business Flow — Idea → Strategy → Operations → Growth