--- id: FAS-PFM-LLM-06 title: Organization AI Usage acceptance feature: FEAT-PFM-LLM-06 product_area: platform module: llm revision: 1 status: proposed product_intent: proposed source_sha: services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f rhythm-v2-docs: 9b95399181c8ec6670ce3d12d700e59643668692 capabilities: - CAP-PFM-LLM-017 - CAP-PFM-LLM-018 scenarios: - id: FAS-PFM-LLM-06-01 title: Customers see their own credit position kind: behaviour exercises: - CAP-PFM-LLM-017 - CAP-PFM-LLM-018 relies_on: - ATS-PFM-LLM-017-01 - ATS-PFM-LLM-017-02 - ATS-PFM-LLM-018-01 preconditions: An authorized local administrator has a warned period with a known local reset date. steps: Read the summary and compare its message with customer allowance guidance. expected: 'The position and renewal are local, and customer wording omits money, model and provider details.' negative: false data_needs: >- An isolated workspace with stated usage, callers, clock instants and a separate workspace for scope checks. bound_to: [] provenance: proposed source: - >- rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-017-let-an-organization-s-administrators-see-their-own-ai.md - >- rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-018-tell-a-person-why-an-ai-feature-refused-them.md - id: FAS-PFM-LLM-06-02 title: Switch changes alter availability and guidance together kind: interaction exercises: - CAP-PFM-LLM-017 - CAP-PFM-LLM-018 relies_on: - ATS-PFM-LLM-017-04 - ATS-PFM-LLM-018-01 preconditions: The feature’s only operation is enabled and credits remain. steps: Disable the operation and read feature availability alongside its customer refusal sentence. expected: Both identify the feature restriction and support guidance rather than implying exhausted allowance. negative: false data_needs: >- An isolated workspace with stated usage, callers, clock instants and a separate workspace for scope checks. bound_to: [] provenance: proposed source: - >- rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-017-let-an-organization-s-administrators-see-their-own-ai.md - >- rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-018-tell-a-person-why-an-ai-feature-refused-them.md - id: FAS-PFM-LLM-06-03 title: Renewal replaces pause with the new month’s position kind: lifecycle exercises: - CAP-PFM-LLM-017 - CAP-PFM-LLM-018 relies_on: - ATS-PFM-LLM-017-02 - ATS-PFM-LLM-018-01 preconditions: The earlier local month is exhausted and the next month is unused. steps: 'Read the paused summary, advance into the local renewal and read again.' expected: Current position and wording follow the new month while earlier usage remains in history. negative: false data_needs: >- An isolated workspace with stated usage, callers, clock instants and a separate workspace for scope checks. bound_to: [] provenance: proposed source: - >- rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-017-let-an-organization-s-administrators-see-their-own-ai.md - >- rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-018-tell-a-person-why-an-ai-feature-refused-them.md - id: FAS-PFM-LLM-06-04 title: Customer and HQ identities do not substitute for local authority kind: permission exercises: - CAP-PFM-LLM-017 - CAP-PFM-LLM-018 relies_on: - ATS-PFM-LLM-017-01 - ATS-PFM-LLM-017-03 preconditions: 'Anonymous, unkeyed, foreign-workspace and HQ-only callers are available.' steps: Request the local summary as each and compare with a keyed local administrator. expected: Only the local authorized caller succeeds and its response retains the customer vocabulary boundary. negative: true data_needs: >- An isolated workspace with stated usage, callers, clock instants and a separate workspace for scope checks. bound_to: [] provenance: proposed source: - >- rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-017-let-an-organization-s-administrators-see-their-own-ai.md - >- rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-018-tell-a-person-why-an-ai-feature-refused-them.md - id: FAS-PFM-LLM-06-05 title: Active exemptions expose availability disagreement kind: regression exercises: - CAP-PFM-LLM-017 - CAP-PFM-LLM-018 relies_on: - ATS-PFM-LLM-017-05 - ATS-PFM-LLM-017-04 preconditions: A feature’s operation is disabled and an active exemption permits admission. steps: 'Read customer availability and its restriction sentence, then request admission.' expected: >- The current feature list remains restricted while admission allows the exempted operation; this discrepancy remains visible for product resolution. negative: true data_needs: >- An isolated workspace with stated usage, callers, clock instants and a separate workspace for scope checks. bound_to: [] provenance: proposed source: - >- rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-017-let-an-organization-s-administrators-see-their-own-ai.md - >- rhythm-v2-docs:specs/platform/llm/planning/capabilities/CAP-PFM-LLM-018-tell-a-person-why-an-ai-feature-refused-them.md evidence: - artifact: CAP-PFM-LLM-017 provenance: documented source: >- specs/platform/llm/planning/capabilities/CAP-PFM-LLM-017-let-an-organization-s-administrators-see-their-own-ai.md - artifact: CAP-PFM-LLM-018 provenance: documented source: specs/platform/llm/planning/capabilities/CAP-PFM-LLM-018-tell-a-person-why-an-ai-feature-refused-them.md - provenance: documented source: 'rhythm-v2-docs:specs/CONVENTIONS.md#5.3 Feature Acceptance Suite' execution_gap: FND-PFM-LLM-081 --- # Organization AI Usage acceptance ## What the Feature Must Do as a Whole An authorized local administrator has a warned period with a known local reset date. Read the summary and compare its message with customer allowance guidance. The suite compares the feature outcome with its capability prerequisites and keeps partial proof visible. ## Interactions Between Capabilities The feature’s only operation is enabled and credits remain. Disable the operation and read feature availability alongside its customer refusal sentence. The interaction scenario checks what changes across that shared boundary. Lifecycle, permission and regression scenarios preserve the wider feature obligations. ## Regression Record | Revision | Change | Scenario | Why | |---|---|---|---| | 1 | initial | all | Establish cumulative feature acceptance from the pinned capability and design baseline. |