docs: name the compose-from-blocks family (Hex, Hexicon, Prisma Compose, Prisma Data)

[wmadden-electric]

Here's the whole proposal in one breath — how a developer builds an app in this vocabulary:

You build an App by snapping together Hexes — reusable building blocks you install from Hexicon — wired together by Prisma Compose. Your data lives in Prisma Data.

npx hexicon add auth
# → installs an auth Hex from the registry, and Prisma Compose wires it
#   into your app's topology; Prisma Data owns its schema

What we're deciding

This PR adds product documentation (agent-os/product/naming.md) that settles how we name the compose-from-blocks product family, under a single rule: name every piece for the value the user gets from it, not the machinery that delivers it.

That rule picks the words above — "App" and "Data" (what the user says) over "Topology" and "Contract" (how it works underneath).

The product family

The primitives a developer composes into an app, each named for its role:

Primitive	Role	The value to the user
Prisma Postgres	persist	my data has a home
Prisma Compute	execute	my code runs
Prisma Data (← Prisma Next)	data	I model, access, and manage my data
Prisma Compose (← MakerKit)	compose	my app comes together from parts
Durable Streams	stream	my events flow and survive
Connection	connect	my services reach each other

How Prisma Compose fits

The other primitives each deliver one capability. Compose is the one that assembles the others into a running app — and it introduces its own small vocabulary: App (what you build), Hex (a building block), Hexicon (the registry at hexicon.dev), and Topology (the machinery it produces, which the user never has to say).

How Hexes are distributed

Hosting and discovery are split: npm hosts the Hexes (ordinary TypeScript libraries — semver and tooling for free), and Hexicon is a thin named directory on top (search, ranking, trust, one-command install). This is the skills.sh shape, with one difference — Hexicon's install composes the Hex into your topology; it doesn't just copy files.

Status

Hex and Hexicon are settled. The Prisma renames — Prisma Data (← Prisma Next) and Prisma Compose (← MakerKit) — are proposed.

Alternatives considered

• Filing this as an ADR — it describes current product truth, not a point-in-time decision with a status, so it lives in agent-os/product/ rather than docs/design/90-decisions/.
• Bare "Hex" for the registry — collides with hex.pm (the Elixir/Erlang package manager — a same-category clash) and hex.tech.
• "Hexal" as a public brand — its domains are camped or guarded by Hexal AG (pharma; owns hexal.com).
• "Model" or "Contract" for the data layer — each names the authoring step or the machinery, not the user's actual value (data access), and each is more useful kept as a sub-concept: model is the PSL construct, a Contract is what models compile to.

🤖 Generated with Claude Code