Export

What It Models

The export concept joins two delivery designs: query and report files, including recurring delivery, and complete workspace packages. Their different service owners remain explicit.

Identity and Attributes

File requests have requester-scoped outcomes. Schedules keep recurrence and recipients separately from occurrence runs. Workspace admission copies settings into an execution that is independent of later settings edits.

Relationships

Source references support provenance and deletion rules without making exported content the owner of application records.

Invariants

The invariant rows distinguish deployed file processing from workspace-package persistence helpers. Stored schemas alone do not establish generation, cleanup or delivery orchestration.

How It Is Stored and Shared

The query service owns files and schedules. The data export service owns workspace definitions, coverage and package foundations. External storage and Communications implement separate integration boundaries.

Open Design Questions

The queued workspace export blockage, temporary binding store and proposed concept split remain open. No completed package flow is established at these source revisions.