Commercial Presentation Dictionary Report

Date: 2026-07-29

Scope: Commercial Presentation Layer only Status: COMPLETE

Outcome

A universal presentationRegistry is now the single source of user-facing Commercial registry presentation. API bindings retain transport coordinates only; they no longer define labels, descriptions, empty states, actions, icons, colors, status copy, or table columns.

Every resolved registry presentation contains:

Persian singular and plural labels
English label
Business description
Icon and accent color
Navigation and section titles
Empty-state title and description
Create, edit, delete, publish, and archive copy
Shared localized status map
Business-facing table columns

Covered registry kinds

Products, bundles, pricing, plans, capabilities, business types, recommendation rules, assessment schemas, assets, extensions, automation packs, metadata, policies, usage plans, subscriptions, licenses, entitlements, promotions, coupons, currencies, taxes, notifications, announcements, transactions, invoices, trial rules, subscription templates, discount campaigns, regional pricing, languages, marketplace visibility, release channels, support levels, and activation processes.

Aliases such as product, price, tax-classes, recommendations, and underscore-form registry names resolve through the same dictionary.

Consumers

Admin Commercial dashboard cards
Admin resource navigation
Admin list headers, columns, empty states, create/edit dialogs, and delete confirmation
Recursive registry and metadata renderer
Product, bundle, capability, plan, pricing, invoice, transaction, and license presentation
Pricing, Discover, Billing, Apps, Dashboard, setup, recommendations, and marketing surfaces

Naming examples

Runtime identifier	Presented name
`price.restaurant.starter.monthly`	پلن رستوران — نسخه شروع (ماهانه)
`bundle.restaurant.starter`	بسته شروع رستوران
`product.restaurant`	سیستم رستوران
`capability.loyalty`	باشگاه مشتریان

Runtime identifiers remain available internally for lookup, routing, React keys, and API calls, but are not rendered as user-facing copy.

Scope confirmation

No backend, Core Runtime, database, API, contract, registry schema, ADR, or Commercial Runtime adapter was changed.

2.4 KiB Raw Blame History