Keep a shared catalogue of customization points and events

Purpose

Applications describe the points they expose for customization and the business events they publish.

How It Works

Applications declare the places where customers may customize their behaviour. Registration makes those places and their contracts available to administrators. The same intake maintains business-event types and native subscribers. Later deploys reconcile the registry with what the application now declares. Retired points leave configuration visibly orphaned for review. Browse operations combine shared declarations with the workspace’s own binding counts. The present intake trusts a submitted service name after invocation admission. The product should require an explicit application-identity boundary before accepting that replacement authority. Console browsing remains sample-backed rather than connected to this registry.

Relationships

Connects with apply tested customizations where an application allows them through shared integration records.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: The registry reflects the customization points and events applications currently declare.Point retirement exposes orphaned configuration rather than silently hiding it.
Surfaces: apijobconsole
Intent sources: services-platform:docs/proposals/extensibility/decision-log.md#A7services-platform:docs/proposals/extensibility/decision-log.md#A2

Controls

30 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-CHG-001 TC-CHG-002 TC-CHG-003 TC-CHG-004 TC-CHG-005 TC-CHG-006 TC-DAT-004 TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-MON-001 TC-PI-001 TC-PI-003 TC-PI-005 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

Permissions

Key	Checked at	Scope
`platform.extension-points.read`	api	tenant

Business Rules

9 rules, 9 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	Registration validates the complete declaration before writes, including declaration version, service and point naming, workspace-ending scope order, known kinds and policies, a thirty-second timeout ceiling, one current version, object schemas and no unexpected properties. proved by `ATS-PFM-INT-016-01`, `TST-PFM-INT-473`, `TST-PFM-INT-476`	validation	service	test services-platform:modules/extensions/tests/integration/services/registration/register-service-extensions.integration.spec.js#refuses a malformed fragment as ObjectInvalid, naming the path
`02`must prove Proposed	Declarations cannot claim keys owned by another service or subscribe to unregistered event types; refusal names the conflict and preserves the existing owner’s records. proved by `ATS-PFM-INT-016-02`, `TST-PFM-INT-473`	validation	service	test services-platform:modules/extensions/tests/integration/services/registration/register-service-extensions.integration.spec.js#refuses a key another service declares, naming that service
`03`must prove Proposed	An omitted contract version becomes deprecated with a timestamp if an enabled binding references it, otherwise retired. proved by `ATS-PFM-INT-016-03`, `ATS-PFM-INT-016-08`, `TST-PFM-INT-473`, `TST-PFM-INT-475`	lifecycle	service	test services-platform:modules/extensions/tests/integration/services/registration/register-service-extensions.integration.spec.js#deprecates a version no longer declared that an enabled binding still names
`04`must prove Proposed	Omitting a point retires it and its versions, orphans all customer bindings and logs the count; re-declaration revives the point without repairing orphaned bindings. proved by `ATS-PFM-INT-016-04`, `ATS-PFM-INT-016-08`, `ATS-PFM-INT-016-09`, `ATS-PFM-INT-017-15`, `TST-PFM-INT-473`	lifecycle	service	test services-platform:modules/extensions/tests/integration/services/registration/register-service-extensions.integration.spec.js#orphans every binding of a retired point, in every tenant, whatever its status
`05`must prove Proposed	Neutral outputs are restricted to resolver and transformer versions, reject JSON null and permit other values including empty objects, arrays and strings. proved by `ATS-PFM-INT-016-05`	validation	service	observed services-platform:modules/extensions/services/registration/registration-manifest.ts:neutral_output
`06`must prove Proposed	Event and native-subscriber declarations are replaced with the same registration, retiring subscribers the service omits. no proof recorded yet	lifecycle	service	test services-platform:modules/extensions/tests/integration/services/registration/register-service-extensions.integration.spec.js#replaces the service’s subscribers: the kept one updated, the dropped one retired
`07`must prove Proposed	The global registry is written through registration and browsed with extension-point read, returning contracts, event types and the current workspace’s binding counts. proved by `ATS-PFM-INT-016-06`, `TST-PFM-INT-459`, `TST-PFM-INT-477`	permission	api, database	test services-platform:modules/extensions/tests/e2e/extensions.e2e.spec.js#admits the catalogue with platform.extension-points.read alone
`08`must prove Proposed	Registration keeps deployment logs and record stamps as its trace rather than writes a separate audit event. no proof recorded yet	policy	service	documented services-platform:docs/extensions.md#3. The registration intake
`09`must prove Proposed	Invocation policy admits extension registration callers, while the submitted service name chooses whose entries are replaced without comparison to an authenticated application principal. proved by `ATS-PFM-INT-016-07`	permission	service	observed services-platform:modules/extensions/aws/lambda/REGISTRATION.handler.ts:registerExtensionsManifest

Scenarios

Id	Given	When	Then	Provenance
`01`	Commerce’s deployment declares a pricing customization point.	The declaration is registered.	The catalogue exposes its contract alongside this workspace’s binding counts.	test services-platform:modules/extensions/tests/e2e/extensions.e2e.spec.js#reads one point with its contract and examples

Planning

Implementation

Keep a shared catalogue of customization points and events ​

Purpose ​

How It Works ​

Relationships ​