The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | enterHqTenantLoading | Open the implementation workspace for loading with an explanation. | CAP-PFM-TNL-011 | The load records its operator, opening time and reason. | test services-platform:modules/tenants/tests/e2e/hq-tenant-loading.e2e.spec.js#records who opened the load and why, which is what the row is evidence of |
| 2 | /contacts/{tenantId}/data_jobs | Submit import work and compare ordinary customer access. | CAP-PFM-TNL-005 | Data-job routes remain admitted and ordinary customer routes close. | test services-crm:modules/tenant-lifecycle/tests/e2e/tenant-availability.e2e.spec.js#is served the submission of a bulk contact job, which is what the import is made of |
| 3 | resetHqTenant | Confirm the workspace identifier and request correction by reset. | CAP-PFM-TNL-012 | The response supplies the job that will empty selected data. | test services-platform:modules/tenants/tests/e2e/hq-tenant-loading.e2e.spec.js#is accepted for a staff member holding hq.data-runs.manage: 202, naming the tenant and the job that empties it |
| 4 | getHqTenantReset | Inspect reset progress until it settles. | CAP-PFM-TNL-012 | Its result reports participant removals while loading continues. | test services-platform:modules/tenants/tests/e2e/hq-tenant-loading.e2e.spec.js#is followed by the reset read to the job it answered, succeeded |
| 5 | activateHqTenant | Activate the corrected load using activation authority. | CAP-PFM-TNL-011 | The workspace returns to active, retaining implementation status and load history. | test services-platform:modules/tenants/tests/e2e/hq-tenant-loading.e2e.spec.js#is served to a staff member holding hq.tenants.activate, returning the tenant to active |
| 6 | patchHqTenant | Change business status on the agreed go-live date. | CAP-PFM-TNL-006 | Authorized staff make the separate live-status decision. | test services-platform:modules/tenants/tests/e2e/tenant-deletion-requests.e2e.spec.js#lets Rhythm staff change the same status |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 3 | A reset already has an open job. | Reject the competing request and identify the existing run. | The operator follows the recorded reset. | test services-platform:modules/tenants/tests/e2e/hq-tenant-loading.e2e.spec.js#refuses the second 409, naming the reset that is running |
| alternate | 4 | Removal stopped and the reset has settled failed. | Submit another reset request. | Remaining selected records are removed by the fresh attempt. | test services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#accepts a second reset once the first has settled, and the second succeeds |
| failure | 5 | The import-only caller requests activation. | Refuse the missing activation authority. | The workspace remains loading. | test services-platform:modules/tenants/tests/e2e/hq-tenant-loading.e2e.spec.js#refuses the staff member who ran the import, activation being the other key |
| failure | 1 | The workspace is already in live business mode. | Reject entry into initial loading. | Its current status and lifecycle remain intact. | test services-platform:modules/tenants/tests/e2e/hq-tenant-loading.e2e.spec.js#refuses a live tenant, an initial import going only into an implementation tenant |
| Id | Statement | Provenance |
|---|---|---|
01 | Reset preserves classified kept tables and leaves implementation loading open. | test services-platform:modules/tenants/tests/integration/services/reset/reset-tenant.integration.spec.js#keeps every table of every participant it does not empty, row for row |
02 | Activation restores ordinary availability without deciding live business mode. | test services-platform:modules/tenants/tests/e2e/hq-tenant-loading.e2e.spec.js#leaves the status where it was, going live being the separate decision |
03 | Loading closes ordinary customer routes while retaining data-job and authorized system staff access. | observed services-platform:modules/tenants/services/access/tenant-availability.ts:tenantAvailabilityOf |
End-to-end policy: required: The outcome crosses lifecycle operations and warrants end-to-end verification; the current bindings establish backend fixtures, while screen and deployed-service coverage remain separate gaps.