Business Platform Requirements
Table order = build order. Top row is what engineering builds next. Each PRD advances features from the RaaS catalog.
New features = new PRD, never expanding an existing one. The Commissioning Dashboard tracks every feature by catalog ID.
Spark → Idea → Venture → Proof
A spark is a felt problem. An idea compresses it into a story worth building. A venture finds its pipes. Proof is the Value Story running in reality.
What we are building right now
The top-ranked requirement's Value Stories — the felt moments that justify the build. Read the methodology to see how these get developed.
Requirements by Piping Generation
Every requirement advanced the platform's capability to pipe information, value, or intent. Use the generations to see where a requirement sits in the stack.
Read the Protocol →Gen 1: Information
Removing permission to publish. Hyperlinks pipe documents and APIs.
Gen 2: Value
Removing permission to transact. Smart contracts pipe assets and proofs.
Gen 3: Intent
Removing permission to delegate. Agent protocols pipe decisions and negotiation.
Prepare
2.0–2.910 PRDsSales CRM
Vertical CRM for construction — native entities, pipeline visibility, follow-up tracking.
ETL Data Tool
Data acquisition + readiness platform.
RFP Engine
Compounding answer library — answer once, auto-fill forever, win rate climbs.
Multi-Tenant Routing
Customer org signs in and sees only their data via URL-scoped routes.
Protocol Coverage
GAUGEEvery protocol interface provably correct — trust computed, not claimed.
Prompt Deck
Pitch+prompt conviction engine — inner sell then outer sell.
Marketing Sites
Hybrid sites + trojan horse diagnostics for qualified lead capture.
Walked DePIN Product
Per-unit custody proof: hive to shelf, every hand signs, scan resolves full chain.
Sales Dev Agent
AI-powered demand generation.
Prediction Game (Sui)
Atomic settlement proof: PTBs, zkLogin, oracles, Dynamic NFTs.
Incubate
1.0–1.94 PRDsBetter Practice
Purpose & project planning app — roadmap, predictions, method. One URL replaces every conversation.
Design System
Proving ground: unified forms, standard process, composition stress test.
Demand Signal Scoring
Score audience response signals into typed demand (latent/active/validated) that patches creator PowerIndicators.
Time + Mind
Archetype-mode calendar: intention vs attention.
Process
Research demand versus capability to execute. Balance attention vs intentions to optimize where you focus time and energy.
| Step | What | Link |
|---|---|---|
| 1. Frame | Extract core pain, vision, metrics, appetite | JTBD Framework |
| 2. Spec | SIO + Story Contract + Build Contract + Screen Contracts | PRD Development |
| 3. Score | 5P Priority (Pain x Demand x Edge x Trend x Conversion) | Scoring Algorithm |
| 4. Commission | L0→L4 maturity model, flight readiness | Commissioning |
Context
- Dream Engineering — The thesis: standard interfaces make pipe dreams buildable
- Ventures — The factory's output: pipe dreams that found their pipes
- Business Factory — The golden path from friction to compound
- Smart Contracts — Intelligent hyperlinks: the piping technology
- A&ID Template — Agents, instruments, feedback loops
- Standards — Where interfaces graduate to
- Flow Engineering — Maps that produce code artifacts
- Progress — Five Ps: picture it, qualify it, then quantify it
Questions
What capability are you building by hand today that should be shared infrastructure tomorrow?
- If every venture on this network could compose from the same primitives, what would you build that's currently impossible?
- Which row in the Active table would you kill — and what does that reveal about your actual priorities?
- What's the cost of the gap between what's specified and what's commissioned?