ALL PORTFOLIO (8)CC.
DEMO DATA — ILLUSTRATIVE ONLY
Workshop 1 · Studio 05 · Aaron

PROOFFOUNDRY STUDIO

Vertical founders and developers must be able to use Bankabil without understanding the entire kernel or building evidence infrastructure from scratch.

ALL STUDIOSNEXT → CAREPROOF FIELDOPS
Founder AaronPlatform / SDKStage Revenue

MVP Use Case

A developer selects a starter workflow, installs the Rails integration, calls the Rust kernel, issues a receipt, verifies it locally and exports an example Evidence Room.

COMPANY COMMANDFOUNDER PROFILE

Phase 1 Artifacts

  • ·Developer journey
  • ·Starter-application taxonomy
  • ·Component inventory
  • ·Rails-engine boundary
  • ·Native-gem installation experience
  • ·Documentation design
  • ·Open-core conversion thesis

MVP Artifacts

  • ·Rails starter application
  • ·Native Rust kernel gem
  • ·Receipt creation form
  • ·Local verifier
  • ·Component gallery
  • ·Three vertical example schemas
  • ·Five-minute quickstart
  • ·Hosted demonstration environment

V1 Artifacts

  • ·Generator commands
  • ·Vertical Rails engines
  • ·Schema registry
  • ·Receipt component library
  • ·Test-vector distribution
  • ·Developer accounts
  • ·Metered hosted services
  • ·ProofMail integration
  • ·Evidence Room templates
  • ·Community contribution process

VC-Readiness Proof

  • ·Installation completion rate
  • ·Time to first verified receipt
  • ·Number of starter projects created
  • ·Developer retention
  • ·Open-source-to-paid conversion
  • ·Number of third-party vertical integrations

Investor Narrative

ProofFoundry is the developer adoption company inside Cohort 1. It turns the shared evidence kernel into recipes, starter applications, components and self-service product experiences.

Gate Path

  • G1Gate 1 — Thesis ReadyThe specific workflow · The evidence failure · The developer user · The economic buyer · Why the founder is suited to solve it · Why the startup should exist independently
  • G2Gate 2 — MVP ReadyOne Rails workflow · One Rust receipt family · One local verification path · One Evidence Room export · One developer quickstart · One design-partner use case
  • G3Gate 3 — Pilot ReadyExternal acceptance criteria · Integration documentation · Measurable baseline · Commercial terms · Claims boundaries · An explicit end-of-pilot decision
  • G4Gate 4 — V1 Venture ReadyProduct functionality · Developer adoption · External workflow completion · Verified artifacts · Willingness to pay · Repeatability and expansion potential · Capital requirements

Phase Timing

  • Phase 0 — Founder-Market ThesisWorkshop kickoff9 artifacts
  • Phase 1 — Pre-MVP Venture Thesis PackWeeks 1-210 artifacts
  • Phase 2 — MVP Artifact PackWeeks 3-620 artifacts
  • Phase 3 — Pilot-Ready Artifact PackWeeks 6-923 artifacts
  • Phase 4 — V1 Venture-Readiness PackWeeks 9-1231 artifacts