DreamBorn Founder Pitch Page — Design Spec
internal prototype · canonical JSON + Dreamborn Forge HTML
internal generated
design_doc · markdown

DreamBorn Founder Pitch Page — Design Spec

DreamBorn Founder Pitch Page — Design Spec Date: 2026 04 27 File: docs/dreamborn founder deck.html Status: Approved Purpose A single page founder pitch document explaining what DreamBorn has built — the pull model, consensus backed company OS. Audience: investors, technical founders, early partners. Not a marketing page; a technical pitch that earns credibil...

DreamBorn Founder Pitch Page — Design Spec

Date: 2026-04-27 File: docs/dreamborn-founder-deck.html Status: Approved

---

Purpose

A single-page founder pitch document explaining what DreamBorn has built — the pull-model, consensus-backed company OS. Audience: investors, technical founders, early partners. Not a marketing page; a technical pitch that earns credibility by showing the live system.

---

Brand
  • Company: DreamBorn
  • Palette: Crimson (#8C1A13), Lime (#8DC63F), Taupe (#6B5F54), Warm white (#FAF8F5), Dark (#0F0B0A)
  • Typography: System sans-serif (-apple-system, BlinkMacSystemFont, Segoe UI)
  • Logo: DreamBorn wordmark + mark, embedded as base64 PNG (no external deps)
  • Section rhythm: Alternating light (warm white) and dark (#0F0B0A) sections
  • No external CDN dependencies — fully self-contained HTML file

---

1. Hero — "The Company OS That Runs on Consensus"
  • Live status badge: LIVE · CONSENSUS NETWORK · roles.developer · 0.0.8730503
  • DreamBorn mark (mix-blend-mode: multiply on warm cream background)
  • Headline split across 3 lines; "Consensus" in lime
  • Subtext: "Every handoff. Every decision. Every claim. Not a log file — cryptographic proof on the global consensus network."
  • CTA: "Verify live on HashScan →"
2. The Broken World — "Everyone else built pipelines."
  • Push (red card) vs Pull (green card) comparison diagram
  • Push: orchestrator → assigns → Agent A/B/C; "Orchestrator down = everything down. Scale = add routing logic."
  • Pull: work queue on-chain → agents claim; "Scale = run more agents. No routing logic. No orchestrator needed."
3. The Atomic Claim — "Work claims itself."
  • Explains task.claim atomic message; consensus makes conflicting claims impossible
  • Live demo: quinn claims first, quinn@2 sees "already claimed", quinn@N "idle — next task"
  • Real topic: ROLES.DEVELOPER · 0.0.8730503
  • Terminal block showing consensus timestamp resolution (1.6ms window)
4. What Consensus Means — "Not a log file. Not a database. Cryptographic truth." (dark)
  • 9-nanosecond precision consensus timestamp
  • On-chain message type glossary: task.available, task.claim, task.complete, task.blocked, task.cancelled
  • "Every message carries agent, cost_usd, duration_seconds."
  • HashScan deep link: hashscan.io/testnet/topic/0.0.8730503
5. Parallel Orchestration — "Not sequential. Fan-out with on-chain dependency tracking."
  • Engine fan-out diagram: 0.0.8727762 → roles.developer / roles.architect / roles.ba simultaneously
  • Dependency declared on-chain in task.created; Engine checks every 30s
  • Terminal block showing real depends_on array with topic IDs
6. Trigger Model — "Work enters three ways. All of them on-chain."
  • Three cards: Direct Dispatch (green border), Event-Driven (crimson border), Scheduled (neutral)
  • Real examples in each: Justin → roles.exec, Resend webhook → roles.crm, Iris governance every 5min
  • Unifying principle callout: every trigger produces task.available; agents don't know or care
7. Agent Team — "The agent team — running right now." (light)
  • Grid of all live agents with green/amber status dots, real topic IDs:
  • Quinn (Developer), Vikram (Architect/Reviewer), Priya (BA/Spec)
  • Claire (Coordinator), Engine (Workflow state machine), Mindy (Product Manager)
  • Iris (Governance daemon), Arlo (CRM), Zara + Luna (UX + QA)
  • Footer bar: definitions topic, listener sync interval, VPS IP
8. Structural Moat — "Six things you cannot replicate without rebuilding from scratch." (dark)

1. Pull model — nobody else has this 2. True parallel orchestration 3. Consensus proof — cryptographic audit trail 4. Infinite scale — bounded by the network, not us 5. Full company OS — not dev tooling 6. Human in the loop — by design, not afterthought

---

Design Decisions
  • No Hedera branding — removed throughout; consensus network is the capability, not a brand claim
  • HTML entities for arrows (→) — prevents encoding corruption across environments
  • base64 logos — no external image dependencies; file opens offline
  • Real topic IDs everywhere — builds credibility; every ID is verifiable on HashScan
  • Dark terminal blocks — #0F0B0A background, lime/crimson syntax highlighting; shows real message schemas
  • Forge aesthetic — dense, technical, founder-to-founder; not a SaaS marketing page

---