Platform orchestrates Accounting lifecycle participants

Context

Accounting provides bounded lifecycle steps across its records. Platform owns the workspace and the jobs that order and repeat those steps.

Decision

Participants answer provisioning, verification, inventory, purge and export calls. Configuration provisions five system payment methods; purge removes one table batch with change capture suppressed and requires deleting standing. Export applies recognized-secret checks before staging. No participant supports reset.

Alternatives Considered

Run an independent Accounting deletion loop. That proposed design would require coordination with Platform’s cross-application progress and continuation.

Provision a default chart. The examined provisioning step creates no unit or chart; choosing customer accounting setup would require a separate product decision.

Provide a reset operation. The registered lifecycle contract excludes reset and retains configuration during imported-data reset.

Consequences

Committed purge batches are irreversible; continuation resumes from remaining rows rather than restoring deleted data.

Participants and export readers are declared beside several owning modules and registered by maintenance.

The declared participant coverage check catches an undeclared table during build verification.