--- id: TST-PFM-SEC-087 title: Security context by id 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/security/tests/integration/services/access/security-context-by-id.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/security/tests/integration/services/access/security-context-by-id.integration.spec.js#security context by tenant id (through the handler) - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#a tenant the caller reaches - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#answers the context evaluated in that tenant - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#answers the whole security context, the same document the tenant route answers - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#normalizes the id asked for, so a capitalised, padded one finds the same tenant - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#answers no requested_tenant, the tenant itself being the context’s tenant - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#answers no-store, as every document about the caller does - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#a tenant the caller cannot reach - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#refuses a customer’s user 403 tenant_access_denied, and they may not ask for access - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#names no tenant in the refusal’s details to a customer’s user - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#refuses Rhythm staff holding no grant 403 tenant_access_denied, naming the tenant they may ask access to - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#answers no context and no default tenant instead, though the caller has one - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#refuses a caller with no relationship to a disabled tenant as any unreachable tenant, telling them nothing of its status - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#a disabled tenant the caller would reach were it open - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#answers a member 403 TenantUnavailable, as the service routes do - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#an id no tenant has - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#answers 404 tenant_not_found - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#answers 404 for a value that could never be an id, rather than refusing its shape - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#the request - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#refuses naming the tenant both strictly and as a preference 400 - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#evaluates a preferred tenant the caller reaches, the control for the strict read - provenance: test source: >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.integration.spec.js#refuses an anonymous caller dependency_evidence: >- The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here. The file declares no substituted collaborators. evidence: - >- services-platform:modules/security/tests/integration/services/access/security-context-by-id.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/security/tests/integration/services/access/security-context-by-id.integration.spec.js explicit_no_doubles: true identified_double_boundaries: [] --- # Security context by id 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 security context by id. ## 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 file declares no substituted collaborators. ## 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.