---
id: ADR-PFM-TNL-005
title: Static Participant Planning and Platform Enablement
product_area: platform
module: tenant-lifecycle
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  services-committees: 36129c24daeaadcdb339218c38cdeaff9861359d
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  services-submissions: 64236c19be89579ef5897aad7de3925ed3ce03bf
  services-websites: 5fc6823c69d5e6f208c21dba8c0eb3132f8bdc4c
  services-marketing: d071a159fe9782bb71ff246d5c67d5bbfe07fbfa
decision: Plan lifecycle work from Platform’s static participant declarations, compare live participant order before
  execution and let Platform control remote inclusion.
constrains:
- DOM-PFM-TNL-003
- SVC-PFM-TNL-tenants
- SVC-PFM-TNL-crm-tenant-lifecycle
- SVC-PFM-TNL-commerce-tenant-lifecycle
- SVC-PFM-TNL-committees-tenant-lifecycle
- SVC-PFM-TNL-membership-tenant-lifecycle
- SVC-PFM-TNL-submissions-tenant-lifecycle
- SVC-PFM-TNL-websites-tenant-lifecycle
- SVC-PFM-TNL-marketing-tenant-lifecycle
- WF-PFM-TNL-002
- WF-PFM-TNL-013
origin: services-platform:docs/tenants/tenant-lifecycle-plan.md#§6.1 Registration, §6.4 (approved 2026-10-09)
alternatives:
- option: Plan from the live declarations at submission time
  why_not: Submission would otherwise require every remote service to answer immediately.
- option: Let each application decide its own inclusion
  why_not: Remote enablement alone could change the orchestration catalog unexpectedly.
consequences:
- New integration remains disabled until Platform includes it; Websites is currently excluded.
- Order disagreement refuses construction or purge publication.
- Resource and seed drift can survive the order-only comparison.
supersedes: []
evidence:
- 'services-platform at ad3f6a65: modules/tenants/services/lifecycle/{participants, remote-participants, remote-participant-manifests}.ts.'
---

# Static Participant Planning and Platform Enablement

## Context

The job catalog needs a plan before runtime. Remote declarations supply live evidence but must not enable work Platform has not integrated.

## Decision

Plan lifecycle work from Platform’s static participant declarations, compare live participant order before execution and let Platform control remote inclusion.

## Alternatives Considered

Plan from the live declarations at submission time: Submission would otherwise require every remote service to answer immediately. Let each application decide its own inclusion: Remote enablement alone could change the orchestration catalog unexpectedly.

## Consequences

New integration remains disabled until Platform includes it; Websites is currently excluded. Order disagreement refuses construction or purge publication. Resource and seed drift can survive the order-only comparison.