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.