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.