---
id: ADR-PFM-TNL-018
title: Application-Owned Export Contributions
product_area: platform
module: tenant-lifecycle
revision: 1
status: proposed
design_intent: proposed
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: Let application participants classify and stream their export datasets while the export coordinator owns
  execution, packaging and delivery.
constrains:
- DOM-PFM-TNL-003
- WF-PFM-TNL-017
- SVC-PFM-TNL-crm-tenant-lifecycle
- SVC-PFM-TNL-commerce-tenant-lifecycle
- SVC-PFM-TNL-membership-tenant-lifecycle
- SVC-PFM-TNL-submissions-tenant-lifecycle
- SVC-PFM-TNL-websites-tenant-lifecycle
origin: services-platform:docs/proposals/tenant-data-export/20-risks-tradeoffs-decisions.md#D-02 (decided as recommended);
  OQ-PFM-TNL-004 (open, recommendation A)
alternatives:
- option: Platform reads every application's tables itself
  why_not: Centralized application-table reads would couple the coordinator to every source schema.
- option: Specify participant contributions with exports
  why_not: Moving contribution contracts requires resolving the planning ownership question; its current recommendation
    retains them here.
consequences:
- Dataset coverage can be compared with participant resource declarations.
- Committees and Marketing have no export operation; Websites exports changes while content is deferred.
supersedes: []
evidence:
- 'services-platform at ad3f6a65: docs/proposals/tenant-data-export/20-risks-tradeoffs-decisions.md.'
- 'services-crm, services-commerce, services-membership, services-submissions, services-websites: modules/tenant-lifecycle
  export services.'
---

# Application-Owned Export Contributions

## Context

Business owners know their schemas and withholding rules. Lifecycle declarations provide one place to account for each participant’s resources.

## Decision

Let application participants classify and stream their export datasets while the export coordinator owns execution, packaging and delivery.

## Alternatives Considered

Platform reads every application's tables itself: Centralized application-table reads would couple the coordinator to every source schema. Specify participant contributions with exports: Moving contribution contracts requires resolving the planning ownership question; its current recommendation retains them here.

## Consequences

Dataset coverage can be compared with participant resource declarations. Committees and Marketing have no export operation; Websites exports changes while content is deferred.