---
id: ADR-ACC-BAT-009
title: Model intake configuration as Batch facets
product_area: accounting
module: batches
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  The live Batch concept supplies the single domain-object home for streams and
  routing, while their physical records retain independent identities, versions
  and permissions.
constrains:
  - DOM-ACC-BAT-001
  - STATE-ACC-BAT-002
  - SVC-ACC-BAT-batches
  - SCR-ACC-BAT-005
  - SCR-ACC-BAT-006
origin: >-
  The planning layer's supersession of the recurring batch concept into the
  batch (specs/accounting/batches/planning/concepts/CON-ACC-BAT-002, status
  superseded)
alternatives:
  - option: Allocate a separate Recurring Batch domain object.
    why_not: >-
      The associated concept is superseded, so it does not supply an active
      same-number object.
  - option: Store stream configuration inside each collection row.
    why_not: >-
      A stream persists across collections and already has distinct identity and
      scheduling ownership.
consequences:
  - The superseded concept number is not reused for an active domain object.
  - >-
    Stream scheduling remains a state model associated with the Batch logical
    object.
  - >-
    The service contract and responsibility map express ownership through the
    Batch object.
supersedes: []
evidence:
  - >-
    rhythm-v2-docs:
    specs/accounting/batches/planning/concepts/CON-ACC-BAT-002-recurring-batch.md,
    CON-ACC-BAT-001-batch.md
  - >-
    services-accounting at f47cb263:
    modules/batches/db/recurring-batches.table.ts,
    batch-assignment-settings.table.ts
---

# Model intake configuration as Batch facets

## Context

Planning superseded the separate recurring concept. This decision follows that existing modeling choice rather than allocating another concept-equivalent object.

## Decision

The decision field restates the existing recorded direction for this design boundary. This examination does not grant a new 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.