[Epic] Back Office & Administration — incremental delivery container

[yacosta738]

Context

Profile Tailors needs an internal Back Office capability so routine operational actions no longer depend on direct database access, ad-hoc scripts, or engineering-only intervention. This issue groups the milestone backlog defined by the Back Office RFC and keeps scope aligned with current operational needs rather than speculative enterprise administration.

Goal

Track the incremental delivery of the Back Office capability across architecture foundations, invitations, waitlist operations, user administration, notification operations, governance integration, operational configuration, and the first admin UI slices.

Scope

• Establish the issue container for Back Office delivery.
• Group the child issues required for the first meaningful operational milestone.
• Keep dependencies explicit between foundation, domain, API, and UI slices.

Out of Scope

• Collapsing the entire RFC into one implementation issue.
• Enterprise IAM, CRM, billing administration, impersonation, or speculative future administration capabilities.

Domain Rules

• Back Office is another client of application capabilities.
• Administrative operations must use application use cases.
• The initial release may map permissions to one admin role, but permission boundaries must exist.

Acceptance Criteria

1. This issue groups the Back Office delivery slices for the milestone.
2. Child issues cover the minimum operational path from waitlist and invitation through registration and user control.
3. Dependencies are encoded only where technically justified.

References

• RFC — Profile Tailors Back Office & Administration
• Related overlap: [P0] Private beta invite and activation operations #652

[linear-code]

DALLAY-560