Story: Party provisioning saga

Table of Contents

This page documents a story in Sprint 16. It captures the goal, current status, acceptance criteria, and the tasks that compose it.

Goal

provision_parties_workflow executor; per-party Inactive status trigger; correlation IDs across services; ores.workflow.service + PartyProvisionPage UX.

Status

Field Value
State DONE
Parent sprint Sprint 16
Now Completed 2026-03-31.
Waiting on None.
Next None.
Last touched 2026-03-31

Acceptance

  • All tasks complete; PR-by-PR breakdown in git log.

Tasks

Task State Start End Description
Add provision_parties_workflow executor DONE 2026-05-20 2026-03-31 Saga-based workflow for provisioning parties + associated IAM accounts; NATS messaging infrastructure; workflow instance + step tracking; concrete provision_parties_workflow implementation.
Display provision correlation ID on tenant summary DONE 2026-05-20 2026-03-31 TenantProvisioningWizard summary page shows the provision correlation ID for cross-referencing service logs.
Per-party status trigger + correlation IDs + PartyProvisionPage DONE 2026-05-20 2026-03-31 Replace global party_setup_mode flag with per-party Inactive status; Nats-Correlation-Id header for distributed tracing; PartyProvisionPage replaces AccountSetupPage in tenant provisioning wizard.
Workflow service + correlation IDs + PartyProvisionPage UX fixes DONE 2026-05-20 2026-03-31 ores.workflow.service microservice; standardised correlation ID logging via log_handler_entry; PartyProvisionPage UX improvements; rewrite PartyProvisioningWizard to remove party-creation logic; party-scoped report definition uniqueness.

Decisions

Final v0 sprint
capture everything landed under v0 honestly; this is the closing chapter of v0.

Out of scope

  • Anything explicitly carried forward to v1.

See also

None.

Emacs 29.1 (Org mode 9.6.6)