Taxonomy — Marketplace Protocol reference

Marketplace taxonomy — the ONE classification of a listed package. Reference for every Taxonomy property with its type and default.

Marketplace taxonomy — the ONE classification of a listed package.

A package used to carry a single category, and that one value had to say two different things at once: who the package is FOR (a business function) and what it IS (a full app, a template, a connector). The platform declared it as a closed enum on the listing (MarketplaceCategorySchema) and as an open string on the package (PackageCategorySchema), the cloud catalog kept a third list, and the scenario library copied the third — four lists that agreed on five values. A connector filed under integrations lost the business function it served; one operations value held three functions.

The maintainer's ruling replaced it with three facets and one separate flag, defined here once and read by every surface — the CLI publish path, the cloud catalog and the console marketplace — so there is no second list to drift:

Facet	Key	Arity	Required
Business function	`businessFunctions`	1–3, ordered, the first is primary	to submit to the marketplace
Industry	`industries`	0–3	never — absent means cross-industry
Solution type	`solutionType`	one	no — absent means `app`
Maturity (not a facet)	`maturity`	one	no — absent means `stable`

Filtering semantics the catalog applies: OR inside one facet, AND across facets. Free-text tags stay for search only and generate no filter.

Every value is a lowercase identifier (SystemIdentifierSchema, the grammar of SelectOptionSchema.value): words joined by _, never -, so a select field — the cloud catalog's facet columns, a console filter — can carry the facet as its options unchanged.

Released values are append-only. Renaming or removing a released value is an ADR-0087 retirement with a data migration; a value no release has shipped yet can still be respelled without one. Adding one needs a real listed package, or a ruled scenario card, that needs it, and the console's labels in the same change. Keep each facet near a dozen values; merge before you grow.

What is deliberately absent

No general / cross-industry industry: absence already means that, and a catch-all value is the one every author (an AI author first) would tick.
No theme solution type: ADR-0019 lists only apps, and a theme ships inside one.
No company-size facet: nothing in the catalog or the scenario library uses one.
No other value anywhere: an unclassifiable package is a question for its author, never a bucket.

Source: packages/spec/src/marketplace/taxonomy.zod.ts

TypeScript Usage

import { MarketplaceBusinessFunctionSchema, MarketplaceBusinessFunctionsSchema, MarketplaceIndustriesSchema, MarketplaceIndustrySchema, MarketplaceSolutionTypeSchema, PackageMaturitySchema } from '@objectstack/spec/marketplace';
import type { MarketplaceBusinessFunction, MarketplaceBusinessFunctions, MarketplaceIndustries, MarketplaceIndustry, MarketplaceSolutionType, PackageMaturity } from '@objectstack/spec/marketplace';

// Validate data
const result = MarketplaceBusinessFunctionSchema.parse(data);