Phase 2, Logic Design

Purpose

Phase 2 turns the Phase 1 foundation into a working logic model.

Phase 1 defined what the Eprenz OS is.

Phase 2 defines how the OS decides what should happen next.

Two Tracks

Track	Question	Output
Founder route	After Compass, where should the founder go next?	OS surface routing
Partner supply	When needs repeat, which partners should Eprenz find, onboard, or place?	Partner demand and placement logic

Main Flow

flowchart TD
  A[Founder completes Compass] --> B[Need or problem detected]
  B --> C{Best first surface}
  C --> D[Learning]
  C --> E[Network]
  C --> F[Event]
  C --> G[Partner]
  C --> H[Advisor or Team]
  D --> I[Action]
  E --> I
  F --> I
  G --> I
  H --> I
  I --> J[Progress signal]
  B --> K[Partner demand signal]
  K --> L{Do we have the right partner?}
  L --> M[Use existing partner]
  L --> N[Find or onboard partner]
  M --> O[Place partner in right surface]
  N --> O

Phase 2 Scope

• Define founder need routing.
• Define problem taxonomy.
• Define partner demand and gap logic.
• Define partner placement across OS surfaces.
• Define how knowledge, events, and network support routes.
• Add country and compliance assumptions.
• Define progress signals.
• Define what belongs in Phase 3.

Phase 2 Non-goals

• Do not build the backend yet.
• Do not finalize UI yet.
• Do not clean the affiliate sheet row by row.
• Do not create John and Diksha SOPs yet.
• Do not onboard more partners without structure.
• Do not write every knowledge module.
• Do not create the full operating process yet.

Core Principle

A Compass answer should route to the best OS surface first.

Partner placement should happen when implementation support is useful.

Partner outreach should happen when founder demand reveals a missing or weak solution area.