REEVE

Who it is for — not yet measured. The node states it directly: 'Founder authors and decides; no customer, insurer, or installer has been contacted.' Its SAM names a market slice (elder-care / companionship + home-monitoring), but naming a slice is not naming a customer…

What it is: A concept node for a fail-closed home-steward robot, plus a generated landing and companion console demo. No build date, no pilot, no ship date. — source: products/xml/reeve.xml <what> and <when>

Why now: Household and domestic service robots are compounding at ~17-19%/yr toward ~$24-34B by 2030, and the safety contract is the part nobody has solved. But nothing here is timed: the node records no build date, no pilot and no ship date. — source: products/xml/reeve.xml#investor-model/market-sizing/tam (~$12.9-14.6B 2025 → ~$24.0-34.1B 2030) + the node's own <when> ('Authored 2026-07-26

The opportunity: Fail-closed behaviour in a home robot is unsolved and is the barrier to trusting one around an elderly person. This node explores whether a compiler-carried safety contract can be that guarantee. — source: products/xml/reeve.xml <what> ('a concept node for a fail-closed home-steward robot') and <why>

SOM — not yet measured. [FOUNDER] atom, and the node's reason is the bluntest in the portfolio: no hardware exists, and a robot with no bill of materials cannot have a serviceable obtainable market. A TAM without a BOM is a market, not a plan.

LTV — not yet measured. No hardware, no bill of materials, no price. Every unit-economics row here is downstream of a product that has not been built.

CAC — not yet measured. No product to acquire customers for.

LTV:CAC — not yet measured. Both inputs UNMEASURED.

Churn — not yet measured. Undefined — no customers.

Year-1 ARR — not yet measured. Undefined — no build date, no pilot, no ship date.

Where it lives: reeve.reaveslabs.ai — allocated, not deployed · elder-care / companionship and home-monitoring — source: product-registry url + stage='internal

GTM strategy — not yet measured. The node states no customer, insurer or installer has been contacted, and elder-care hardware routes through all three. There is no route to market to describe.

Why us: It exists to test whether the RLL compiler can carry a physical-agent safety contract. The safety spine is the idea under test, not the hardware. — source: products/xml/reeve.xml <why> ('Explores whether the RLL compiler can carry a physical-agent safety contract; the safety spine is the idea und…

Right in front of us — not yet measured. Nothing is in flight. A generated landing and a companion console demo exist; no build date, no pilot, no ship date, and nobody contacted.