---
id: ADR-ACC-BAT-008
title: Keep current batch operations unpublished to Submissions
product_area: accounting
module: batches
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  The examined service contract records no current Submissions publication and
  supplies a reason for every operation; this remains a proposed publication
  boundary.
constrains:
  - SVC-ACC-BAT-batches
  - RESP-ACC
origin: 'R2-ARCH-002 v2.0 (Andrew, 2026-10-22) rule 1: publish or say why not'
alternatives:
  - option: Publish collection creation or accounting completion as intake operations.
    why_not: >-
      The current operations serve internal accounting work and have no examined
      Submissions binding.
consequences:
  - Each operation explicitly records the reason for remaining unpublished.
  - >-
    Future intake-to-document integration needs its own binding decision;
    current routing alone does not establish such a binding.
supersedes: []
evidence:
  - 'services-accounting at f47cb263: modules/batches/aws/api/*.routes.ts'
---

# Keep current batch operations unpublished to Submissions

## Context

The architecture requires visibility of publication or its absence. The available route surface describes staff accounting, configuration and reads rather than an intake binding.

## Decision

This record describes the proposed boundary in its decision field. Its observed implementation does not constitute Andrew’s approval.

## Alternatives Considered

The alternatives above identify the competing implementation choices and their consequences. They preserve the distinction between a recorded product ruling and a proposed engineering boundary.

## Consequences

The consequence rows describe obligations and known implementation limits at this boundary. Related artifact references retain the affected design homes.