Frozen document. Dates and status refer to its original source. Private resources and unreviewed images are unavailable.

Durable submission lifecycle

Status: owner-approved design, September 30, 2026. Implementation remains blocked by the acceptance gates linked below.

The first extraction puts submission acceptance, outbox dispatch, Camunda receipt recording, and recovery observation behind one internal case-operation lifecycle interface. HTTP routes and the Camunda adapter remain thin boundaries. This records the owner's approved design following the architecture assessment.

The change proceeds in small, behavior-preserving steps. Public BFF and Camunda contracts, persisted record shapes, authorization, owner revisions, idempotency, and uncertain-operation recovery remain unchanged. ADR 0005 continues to govern acceptance and delivery. This internal extraction does not introduce a new architectural decision.

The first tracer bullet is Extract the durable submission lifecycle behind one case-operation interface. It is a sub-issue of Assess deep-module opportunities before product wave and is blocked by that assessment gate and Recover an uncertain case operation. Decision and information-response extraction follow separately after submission converges.

Use TDD through the new lifecycle interface, with the existing integration and end-to-end recovery behavior as acceptance guards. Tests must distinguish durable acceptance from completion and exercise duplicate submission, owner-revision conflict, lost responses, and receipt reconciliation. Record red and green command evidence, run the approved local integrated seam at convergence, and obtain Standards, Spec, and Greptile review before merging. The audit finding remains open until the implementation and its evidence are accepted.