ageni · store product · value proposition

One sale, five stages, one stream.

The store is a brand's sale point. It does not reimplement commerce — it composes existing ageni teams into one point-of-sale pipeline (commercialize → promote → sell → fulfill → report) and emits every sale onto the universal five-measure revenue stream. Third-party rails are reached only through one.

watch a product flow the line — each station lights, composes its team, and the sale lands on the stream as V# · V$ · C$ · M$ · r
V# V$ C$ M$ r
01 commercialize→ 02 promote→ 03 sell→ 04 fulfill→ 05 report ⇒ V# · V$ · C$ · M$ · r

One rail law — every third-party rail is reached only through one

Payment, shipping, tax and every other external rail are never embedded in the store. They are owned by agenihub/one, the unified API / MCP / CLI integration product. The store calls one; watch every packet pass through the single gateway before it ever reaches a rail.

Scaffold only — this surface dramatizes the product boundary. The event-sourced store team is authored on top via /ageni:team; each stage becomes a Task on the store Expert reaching its rail through one. Package @agenihub/store · v0.3.0.