Platform · Product Registry
Nothing is sellable until it’s verifiably real.
The Product Registry is the platform’s source of truth: every product, its verified maturity, its dependencies, and its plans — and it gates commerce, not marketing.
Executive overview
Every product lives in one registry with a maturity status verified against code and deployments, not asserted by a slide. Licensing reads the registry before it allows anything: a product below licensable maturity cannot be sold, whatever a sales page might wish.
The registry also carries each product’s dependency graph and plan limits, so what a license permits is defined in the same place that defines whether the product is real enough to license at all.
Core capabilities
Verified maturity
Six internal maturity statuses, each verified against code and live deployments.
Commerce gating
Licensing consults the registry on every grant — maturity is a gate, not a label.
Dependency graph
Products declare what they build on; the ecosystem map renders straight from it.
Plans and limits
What a license permits is registry data, enforced at approval time.
Honest visibility
Products marked non-public have no public routes at all — they 404, they are never “coming soon.”
Why enterprises care
No shelfware risk
You cannot be sold something that isn't verifiably real — the gate is in the vendor's own code.
Claims you can audit
Maturity is stated, derived, and visible — not asserted in a pitch and forgotten in a contract.
Dependency clarity
What builds on what is declared up front, so licensing decisions come with their blast radius attached.
How it governs the workforce
The tier chips across this site — on every workforce role and every product — derive from registry state at request time. Demote a product internally and its public chip demotes with it, immediately. The roster can never advertise a capability the registry hasn’t verified.
- Maturity-gated
- Request-time chips
- Dependency-aware
The chip vocabulary a visitor sees is a deliberate three-word contract, collapsed from the six internal statuses so internal rollout mechanics never leak to a public page.
See the contract explained →Across the ecosystem
See it run a workforce.
A demo walks the module on live platform data — no slide deck.