Technology Catalog
The catalog is the single most consequential setting in the product: it is the list of technologies generation is allowed to choose from. A design never invents a product; it selects from what your organization has approved, and anything the catalog cannot cover surfaces as a gap for a human decision.
What an Entry Carries
| Field | Why It Matters |
|---|---|
| Name and vendor | The identity generation selects and contracts match against |
| Status | Approved entries are selectable; draft entries are staged; forbidden entries are never selected and the design review will not recommend them |
| Capabilities | The functional capabilities the technology provides; this is how a technology gets matched to the capability slots a design needs |
| In Use | Marks technologies already running in your estate; generation prefers them, and components show an "already in use" chip |
| Tags | Free-form labels for search and matching |
New organizations start with a curated reference library, so the catalog is useful before you have tuned it.
How Entries Get In
- Deliberately, here in Settings: add, edit, and status entries as your standards evolve.
- Through gap decisions: approving a technology for an open gap adds it, recorded against the capability it was approved for, which is what makes decisions stick on every later run.
Keep It Honest
The catalog is a governance surface, so treat it like one: mark superseded products forbidden rather than deleting them (existing designs reference them), keep capabilities accurate because slot matching depends on them, and set in use truthfully because it biases selection toward reuse. Catalog changes ripple: affected packages re-evaluate so designs never age against stale rules.