---
id: ADR-ACC-CLS-011
title: Close Operations Have No Submissions Publication
product_area: accounting
module: close
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  The ten declared operations have no Submissions binding, and each contract row
  states its proposed reason for remaining unpublished.
constrains:
  - SVC-ACC-CLS-fiscal-close
  - RESP-ACC
origin: 'R2-ARCH-002 v2.0 (Andrew, 2026-10-22) rule 1: publish or say why not'
alternatives:
  - option: Publish a form binding for month closure.
    why_not: >-
      That would need a designed authority and review contract; the inspected
      routes declare no such binding.
consequences:
  - Every contract operation states its unpublished reason.
  - >-
    An automated trigger needs a separate approved process and authority
    decision.
supersedes: []
evidence:
  - >-
    services-accounting at f47cb263: modules/fiscal-close/aws/api/*.routes.ts
    (no Submissions binding declared).
---

# Close Operations Have No Submissions Publication

## Context

The adopted publication standard requires visibility of each operation’s intake status. Accounting commands need an explicit authority boundary if they become form-triggered work.

## Decision

Record the observed unpublished operations and their proposed boundary explanations. The direct close API already permits requests without the console’s readiness review; publication policy cannot be justified by assuming that review is enforced there.

## Alternatives Considered

Publish a form binding for month closure. That would need a designed authority and review contract; the inspected routes declare no such binding.

## Consequences

Every contract operation states its unpublished reason. An automated trigger needs a separate approved process and authority decision.