---
id: ADR-PFM-LLM-016
title: Exclude These Operations From Configurable Intake
product_area: platform
module: llm
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Retain explicit nonpublication reasons for staff inspection and controls, customer usage reads, internal
  execution and console prototype history operations.
constrains:
  - SVC-PFM-LLM-llm
  - SVC-PFM-LLM-console-agent
origin: >-
  R2-ARCH-002 v2.0, rule 1: publish or say why not (Andrew, 2026-10-22)
  (services-platform:docs/standards/submission-compatible-operations.md#1. The rule).
alternatives:
  - option: Publish a form-triggered foundation operation
    why_not: 'No recorded product requirement establishes its question, validation or domain effects.'
consequences:
  - No examined route declares a Submissions binding.
  - A future intake AI feature should belong to the domain that validates and applies its answer.
supersedes: []
evidence:
  - >-
    services-platform at ad3f6a6: modules/llm/aws/api/llm-usage.routes.ts (no binding declarations);
    docs/standards/submission-compatible-operations.md.
---

# Exclude These Operations From Configurable Intake

## Context

The intake architecture requires each operation to publish a compatible binding or explain its exclusion.

## Decision

Retain explicit nonpublication reasons for staff inspection and controls, customer usage reads, internal execution and console prototype history operations.

## Alternatives Considered

Publish a form-triggered foundation operation: No recorded product requirement establishes its question, validation or domain effects.

## Consequences

No examined route declares a Submissions binding. A future intake AI feature should belong to the domain that validates and applies its answer.