---
id: ADR-ACC-BAT-004
title: Use named lifecycle commands for ordinary batches
product_area: accounting
module: batches
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Ordinary HTTP creation starts Open, and subsequent lifecycle changes use named
  commands or accounting outcomes rather than detail-field patches.
constrains:
  - DOM-ACC-BAT-001
  - STATE-ACC-BAT-001
  - SVC-ACC-BAT-batches
  - SCR-ACC-BAT-003
  - SCR-ACC-BAT-004
origin: >-
  Andrew's UI brief of 2026-10-15 ("status as actions"), recorded at
  services-accounting:docs/migrations/transaction-processing/batches/README.md
  and modules/batches/services/actions/batch-actions.ts (header)
alternatives:
  - option: Keep status editable on the details form.
    why_not: >-
      A field replacement can bypass the admission and side effects of the
      intended lifecycle command.
consequences:
  - >-
    The console derives action availability from the service rather than
    assigning lifecycle states itself.
  - >-
    Post and Unpost actions prepare the same durable jobs, with additional
    action admission before submission.
  - System accounting is excluded from ordinary batch actions.
supersedes: []
evidence:
  - >-
    services-accounting at f47cb263:
    modules/batches/services/actions/batch-actions.ts;
    aws/api/batch-records.routes.ts; aws/api/batches.schemas.ts
---

# Use named lifecycle commands for ordinary batches

## Context

A free status field obscures the difference between permitted transitions. The recorded interface direction moves those changes into explicit actions.

## 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.