---
id: TST-PFM-SEC-122
title: Amend grant 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/membership/amend-grant.integration.spec.js
implements:
  - ATS-PFM-SEC-010-04
  - ATS-PFM-SEC-010-09
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/membership/amend-grant.integration.spec.js#security:
      amending a console user’s grant
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/amend-grant.integration.spec.js#refuses
      a narrowing of the scope for an editor who is not allowed the key the grant was denying
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/amend-grant.integration.spec.js#records
      the refused amendment on the trail with its machine reason
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/amend-grant.integration.spec.js#refuses
      a validity window that would end a grant carrying a deny, for the same editor
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/amend-grant.integration.spec.js#refuses
      a condition added to a grant carrying a deny, for the same editor
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/amend-grant.integration.spec.js#allows
      the same narrowing to an editor who is themselves allowed the key the deny was holding back
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/amend-grant.integration.spec.js#allows
      an editor allowed nothing to lift a condition from the grant, because the deny then applies
      more often
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/amend-grant.integration.spec.js#allows
      an editor allowed nothing to extend the grant, because a grant that lasts longer denies for
      longer
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/amend-grant.integration.spec.js#answers
      a grant of another person as not found, and leaves it standing
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/amend-grant.integration.spec.js#security:
      amending a Rhythm Administrator’s platform-scope grant
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/amend-grant.integration.spec.js#refuses
      a window that would have ended the staff grant, naming where such a change is made
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/amend-grant.integration.spec.js#refuses
      taking the staff grant’s scope off the platform
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/amend-grant.integration.spec.js#refuses
      a condition added to the staff grant
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/amend-grant.integration.spec.js#leaves
      the grant exactly as it was granted, so the authority is still in force
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/amend-grant.integration.spec.js#records
      each refused amendment on the trail with the staff refusal’s machine reason
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/amend-grant.integration.spec.js#security:
      amending an ordinary grant onto the platform
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/amend-grant.integration.spec.js#refuses
      the promotion, because granting staff authority is Rhythm HQ’s act
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/membership/amend-grant.integration.spec.js#leaves
      the grant at the customer it was granted at
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/membership/amend-grant.integration.spec.js
  - >-
    Static review at the recorded source revision; executable results remain not-run and conformance
    remains not-verified.
binding_note: >-
  Each binding names the scenario to which this file contributes assertions. A binding is not a
  recorded pass and does not extend the file’s dependency boundary.
examiner: codex
examined_at: '2026-10-23'
final_text: OpenAI
dependency_review:
  provenance: test
  source: >-
    services-platform:modules/security/tests/integration/services/membership/amend-grant.integration.spec.js
  explicit_no_doubles: true
  identified_double_boundaries: []
---
# Amend grant 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 amend grant.

## What This Suite Proves

The source assertions support the observations named in the bound scenarios. A scenario spanning multiple files must retain the other files’ contributions.

## 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.