---
id: ADR-PFM-CSH-015
title: Consumed Reads Are Excluded From Intake
product_area: platform
module: console-shell
revision: 1
status: proposed
design_intent: proposed
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
decision: >-
  Record the seven consumed identity, placement and configuration reads as
  excluded from configurable intake with explicit reasons.
constrains:
  - SVC-PFM-CSH-console-shell
  - SVC-PFM-CSH-tenant-applications
origin: >-
  services-platform:docs/standards/submission-compatible-operations.md#1. The
  rule (R2-ARCH-002 v2.0, approved 2026-10-22)
alternatives:
  - option: Publish the administrator's application read as a binding
    why_not: An overview read has no intake capture or persistence result.
consequences:
  - Both contracts make their non-publication reasons explicit.
  - A future feedback write requires a separate intake-compatibility evaluation.
supersedes: []
evidence:
  - >-
    services-platform at ad3f6a6:
    docs/standards/submission-compatible-operations.md
---
# Consumed Reads Are Excluded From Intake

## Context

Configurable intake requires a published business binding, not merely an accessible route.

## Decision

Record the seven consumed reads as not published, with reasons tied to their identity, placement or configuration purpose. They have no intake bindings in the inspected declarations.

## Alternatives Considered

Publishing the administrator overview as intake would provide no capture or business persistence outcome.

## Consequences

Both contracts make exclusion visible. Any future feedback delivery operation must be evaluated when its write behavior is designed.