--- id: TST-PFM-SEC-242 title: First administrator database and service checks kind: integration product_area: platform module: security revision: 2 status: draft source_sha: services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 repository: services-platform files: - modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js implements: [] environment: local implementation_state: implemented latest_result: not-run latest_run_at: null latest_run_ref: null conformance: not-verified estimated_minutes: 3 isolation: Use the prepared test database and suite-owned fixture rows; retain shared seed records. assertion_evidence: - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#the first administrator of a new customer - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#when nobody in the customer holds the address - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#answers that it inserted the administrator - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#leaves an invited console user of the customer holding the address - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#grants that user the Administrator role at the customer, waiting on their acceptance - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#sends them one invitation - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#when the invited administrator is already there - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#invited them the first time (premise) - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#answers that it adopted the administrator - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#sends no second invitation - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#leaves the customer with the one console user it already had - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#when the administrator accepted and is active - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#is asked about an active user (premise) - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#answers that it adopted the administrator - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#sends no second invitation - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#leaves the active grant it adopted them for - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#when the address belongs to an active user who does not administer the customer - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#holds no administration for that user any more (premise) - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#refuses the job rather than reporting an administrator the customer does not have - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#names the refusal so the operator sees it on the job - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#sends nothing and leaves the customer with the one user it had - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#when the address belongs to a suspended user - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#is asked about a suspended user who still holds the role (premise) - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#refuses the job, naming the person, the customer and what has to be done - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#sends nothing and writes no second user - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#when the address belongs to a revoked user - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#is asked about a revoked user (premise) - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#answers that it inserted the administrator, because inviting them back is what it did - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#invites them back on the row they already had, rather than writing a second user - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#grants them the Administrator role again, waiting on their acceptance - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#sends them one new invitation - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#when the invited first administrator accepts - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#accepts the link the provisioning sent, activating the one grant it carried - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#leaves the person an active console user of the new customer - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#leaves them holding the Administrator role at the customer, in force - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js#records on the invitation the exemption that let it be accepted without an inviter to re-judge dependency_evidence: >- The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here. The suite controls Cognito, message delivery at the declared seams; those collaborators remain outside its live proof. evidence: - >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js - >- Static review at the recorded source revision; executable results remain not-run and conformance remains not-verified. binding_note: >- The file has no scenario binding established by this examination. Its executable checks remain registered without assigning them broader acceptance coverage. examiner: codex examined_at: '2026-10-23' final_text: OpenAI dependency_review: provenance: test source: >- services-platform:modules/tenants/tests/integration/services/lifecycle/first-administrator.integration.spec.js explicit_no_doubles: false identified_double_boundaries: - Cognito - message delivery --- # First administrator database and service checks ## Verification Boundary The file exercises database or service behavior through the local integration harness. The assertion references identify the source checks for first administrator. ## What This Suite Proves The file supplies executable engineering checks for the named subject. No complete acceptance scenario is inferred from the file’s existence. ## What It Does Not Prove This examination does not run the suite. Passing behavior, deployed conformance and the behavior of substituted dependencies require separate execution evidence. ## Real Dependencies and Test Doubles The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here. The suite controls Cognito, message delivery at the declared seams; those collaborators remain outside its live proof. ## Must Not Be Doubled Keep the queried database, applicable constraints and transaction boundaries real. Provider substitutes cannot establish delivery, cloud execution or cross-service recovery.