---
id: ADR-ACC-BKS-006
title: Explicit Submissions exclusions for configuration and maintenance
product_area: accounting
module: books
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Every examined Books and maintenance operation is excluded from Submissions
  with its own reason. None has an implemented intake binding for an external
  business request.
constrains:
  - SVC-ACC-BKS-books
  - SVC-ACC-BKS-maintenance
  - RESP-ACC
origin: 'R2-ARCH-002 (publish or say why not), as applied by other corpus modules'
alternatives:
  - option: Publish unit or term creation as intake.
    why_not: An intake process and capture contract would have to be designed first.
  - option: Omit publication declarations.
    why_not: >-
      The cited architecture standard requires either publication or an
      explanation.
consequences:
  - Each service operation records why it is unpublished.
  - >-
    A future form-driven setup process needs a separate capture and permission
    design.
supersedes: []
evidence:
  - >-
    services-accounting at f47cb263: modules/books/aws/api/*.routes.ts;
    modules/maintenance/aws/api/scheduling.routes.ts (no Submissions bindings)
---

# Explicit Submissions exclusions for configuration and maintenance

## Context

The service operations maintain setup, return information or perform internal lifecycle work. The publication standard requires a disposition for each operation.

## Decision

Every examined Books and maintenance operation is excluded from Submissions with its own reason. None has an implemented intake binding for an external business request.

## Alternatives Considered

Publish unit or term creation as intake. An intake process and capture contract would have to be designed first.

Omit publication declarations. The cited architecture standard requires either publication or an explanation.

## Consequences

Each service operation records why it is unpublished.

A future form-driven setup process needs a separate capture and permission design.