Apply Submissions Review Outcomes
What It Does
The Submissions consumer delivers versioned review documents to the remote owner handler. Supersession is conditional on what can still be reversed. An irreversible effect is refused rather than silently contradicted. Staff visibility is limited to logs, and operation-binding publication remains a proposed boundary decision.
The Flow
Validate the delivery envelope and each document’s version and required links. When needed, read disclosure answers from the revision before beginning the consequence transaction. Skip a seen decision; otherwise reverse supported supersession, apply the owner consequence, insert the ledger row and enqueue acknowledgement together. Send queued owner acknowledgements after commit.
When Something Fails
Reject a malformed envelope or return the invalid document as failed. No business consequence is applied. Unavailable answers supply no new summary; an unexpected exception escapes this stage. An accepted disclosure can retain an old summary or have no summary. Record a business refusal in a separate transaction with rejection; retry other failed consequences. Submissions can retain a reviewer outcome that Committees refused to enact. Retain unsuccessful rows for a later delivery or hourly drain. The reviewer system waits for reconciliation.
Open Design Questions
Supersession is conditional on what can still be reversed. An irreversible effect is refused rather than silently contradicted. Staff visibility is limited to logs, and operation-binding publication remains a proposed boundary decision.