--- id: TST-PFM-SEC-158 title: Policies.queries 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/persistence/policies.queries.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/persistence/policies.queries.integration.spec.js#security persistence: the security_policies reads - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#getPolicy - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers a customer's policy with every column it has mapped to its wire property - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#leaves out every column the row does not have, rather than answering null for it - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers what a copy was copied from, which is how a copy can report what it lacks - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers nothing for an id of the right grammar that names no policy - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#findPolicyByProductKey - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers a built-in by the reconciler's stable key, whole, and nothing for a key nobody published - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers an archived built-in too, because the reconciler has to find the row it retired - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#listPolicies: the customer scope - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers the customer's own active policies and Rhythm's active built-ins, in name order, each whole - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#leaves out an archived product policy, the row a raw disjunction leaks - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#leaves out the customer's own archived policy and every other customer's - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers the customer's archived policies and Rhythm's when they are asked for, still in name order - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers another customer only its own policy beside Rhythm's, which is how the scope isolates them - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#listPolicies: the product and the unscoped list - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers Rhythm's active built-ins alone, and no customer's policy - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers every active policy of every owner when no scope narrows it - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers every policy of every owner, archived ones included, when both are asked for - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#listPoliciesPage - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers the customer's own and Rhythm's in name order, whole, with the cursor of the next page - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers the rest of the list after that cursor, and names no next page at the end of it - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#orders a built-in and a customer's policy of the same name by their id, so a page boundary never repeats or skips one - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#narrows to a search of the name whatever case it is typed in - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#narrows to Rhythm's built-ins, and to one app, which is how the editor filters the list - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#leaves out the archived rows of both owners until they are asked for - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers another customer nothing of this one's, however it is paged - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#listPoliciesPage: the counts of a row - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#counts the rules a policy holds and the roles of this customer that reference it, and nothing of another customer - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#copiedSourceOfPolicy - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers the source's reference, name, the version copied and the source's version today - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers the id with no name for a source that is no longer there, and nothing at all for a policy that was not copied - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#resolvePolicyReference - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers the built-in a key names, whole - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers the customer's own policy an id names, whole - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#refuses a built-in key nobody published, and offers the near keys of the same app - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#refuses a built-in key the catalog has retired, saying so rather than saying it never existed - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#refuses another customer's policy as not found, so an id cannot be learned by trying it - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#refuses a built-in named as if it were the customer's own, which is the one way a built-in could be mistaken for one - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#security persistence: the staff-only built-in policies a customer never reads - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#names the policy granting only staff-only keys as staff-only, and neither the mixed one nor a customer built-in - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#leaves the staff-only policy out of a customer's policies page and keeps every other built-in - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#does not count a staff-only role among the roles that reference a policy a customer sees - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#answers Rhythm's own customer the staff-only policy on its policies page - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#refuses the staff-only policy named by its built-in key as not found, never as unknown or retired - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#still resolves the mixed policy by its key for a customer, and the staff-only one for Rhythm's own customer - provenance: test source: >- services-platform:modules/security/tests/integration/services/persistence/policies.queries.integration.spec.js#never offers the staff-only key among the near matches of a mistyped key of its app 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/persistence/policies.queries.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/persistence/policies.queries.integration.spec.js explicit_no_doubles: true identified_double_boundaries: [] --- # Policies.queries 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 policies.queries. ## 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.