Evidence ledger

What is proven, and what is not.

Most company sites tell you what the team believes. This page records what the portfolio has actually demonstrated inside QA, what is still open, and what we refuse to claim until a gate produces the artifact.

Last reviewed 22 Oct 2026 Ventures 4 Status Internal QA Claims No market validation

How to read a row

Every venture is measured at a gate. A gate answers one question, and it only passes when there is an artifact a stranger could inspect: a build, a capture, a log, a signed agreement, a paid transaction.

The left column is the promise. The middle column is the proof we hold today. The right column is the honest gap. If a row has nothing in the middle, we say so instead of filling it with adjectives.

QA is not traction. Captures are produced with demo or mock data inside an isolated build. They show that surfaces work, not that a market wants them. We keep the two separate on purpose.

Private QA

PoseLane

v01.00.00.1909 · creative collaboration

Proven in QA

  • Portfolio and discovery surfaces render and navigate
  • Project terms and the request flow complete end to end
  • Consent-led assistant review is wired into the flow

Next to prove

  • Public availability
  • Real users and repeat usage
  • Transactions and unit economics
Working product

EatCue

0.0.9+24 · everyday food decisions

Proven in QA

  • Gallery and ordering flow run on device
  • Distance-aware discovery returns local results

Next to prove

  • Verified local catalog
  • Pilot usage and retention
Research

CareTrip

Pre-build · non-clinical care journeys

Proven in QA

Nothing yet. There is no build to test.

Next to prove

  • Problem interviews with families and coordinators
  • Map of the non-clinical care journey
  • Trust and consent model before any build
Research

StudyBase

Pre-build · tutoring and supplementary learning

Proven in QA

Nothing yet. There is no build to test.

Next to prove

  • Tutor and student workflow map
  • Scope of AI assistance, reviewed for safety
  • Pilot design with a single tutoring cohort

What this ledger does not show

A ledger is only credible if its limits are explicit. Today the portfolio does not have the following, and no page on this site should be read as if it does.

  • RevenueNo paid transactions have been recorded.
  • RetentionNo cohort has returned over time.
  • Market fitNo external user base exists yet.
  • CustomersNo customer logo, quote or case study is claimed.
  • AuditQA is internal; no third party has reviewed it.

How a claim gets into this ledger

The operating model behind each gate is documented on the method. Portfolio context lives on the portfolio page.

Inspect the work, not the deck.

The private overview walks through the same evidence with the artifacts open: the QA build, the gate sheet, and the capital plan with its assumptions.