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.
Ship Now
≥ 3.02 PRDsProject Management System
SYSTEMTrack state of things across cadences so we can plan days, weeks, months and know if we're on track.
CLI Platform
INSTRUMENTOne binary (drmg) with shared platform lib, repository-only DB access, agent-grade contracts.
Prepare
2.0–2.911 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.
Agent Platform
PUMPIdentity, memory, scaffold generators, boundary enforcement — the PUMP that powers the factory.
Protocol Coverage
GAUGEEvery protocol interface provably correct — trust computed, not claimed.
Prompt Deck
Pitch+prompt conviction engine — inner sell then outer sell.
Decision Tracer
GAUGEDurable traces of the 'why' behind every priority change.
Marketing Sites
Hybrid sites + trojan horse diagnostics for qualified lead capture.
Sales Dev Agent
AI-powered demand generation.
Prediction Game (Sui)
Atomic settlement proof: PTBs, zkLogin, oracles, Dynamic NFTs.
Autoresearch Loop
CONDUCTORChain skills into overnight autonomous loops.
Incubate
1.0–1.93 PRDsDesign System
Proving ground: unified forms, standard process, composition stress test.
Automated Commissioning
CONTROLLERTest-driven feature matrix — states computed from test results, not hand-edited.
Time + Mind
Archetype-mode calendar: intention vs attention.
Inner Loop
The control system between Dream and Engineering. These run continuously — the PUMP, GAUGE, and CONTROLLER of the factory P&ID.
| Role | PRD | Function | Status |
|---|---|---|---|
| SYSTEM | Project Management System | things-table PM across cadences | L2-partial |
| INSTRUMENT | CLI Platform | One binary (drmg) with shared platform lib, repository-only DB access, agent-grade contracts. | L4 |
| PUMP | Agent Platform | identity, memory, comms, dispatch | L2 |
| GAUGE | Decision Tracer | durable traces of the 'why' | L0 |
| CONDUCTOR | Autoresearch Loop | chains skills into overnight loops | L0 |
| CONTROLLER | Automated Commissioning | test results → feature states | L0 |
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?