Prioritization Model¶

This document defines how every catalog candidate is scored and classified into a priority tier. It is written for product and architecture leads sequencing investment. Tiers reconcile with the existing Core Platform Wave and Tier-1 prioritized list.

Scoring Dimensions¶

Each candidate is scored 1-10 across ten dimensions:

Foundation importance (does the platform depend on it?)
Cross-industry reusability
Revenue potential
Delivery complexity (inverted - simpler scores higher feasibility)
Strategic differentiation
Dependency criticality (how many things need it)
Compliance / security importance
AI leverage
Market demand
Build feasibility

The catalog stores a single composite score per item (see the machine-readable catalog); the dimensions above are the rationale behind it.

Tiers¶

Tier	Meaning	Typical wave
Tier 0	Mandatory foundation - nothing ships without it (Tenant, Identity, Config)	Phase 1
Tier 1	Core platform - billing, notifications, audit, API, infra	Phase 1-2
Tier 2	High-value horizontals and AI factory	Phase 2-3
Tier 3	Priority verticals and finance ops	Phase 4
Tier 4	Secondary verticals and governance	Phase 5-6
Tier 5	Future / research	Phase 6+

How Tiers Are Assigned¶

The generator assigns a base tier from the item's category, then promotes foundational items (those whose names contain identity/tenant/billing/config/audit/entitlement keywords) toward Tier 0-1. The composite score is derived from the tier and adjusted by classification (platforms and microservices score slightly higher than modules and libraries).

Note

Tiers are an input to sequencing, not a contract. The authoritative delivery order lives in the roadmaps; this model explains why items sit where they do.

Reconciliation With Existing Prioritization¶

Core Platform Wave == catalog Tier 0-1 in Phase 1.
Tier-1 prioritized platforms == the highest-scoring Tier 0-1 items (Identity, Config, Audit, Billing, Notifications, SaaS Solution Platform).
5 SaaS cycles map to Phases 2-5 - see roadmap alignment.