Apply review decisions from Submissions exactly once

Purpose

What Submissions decides about a seat application, a nomination, an appointment proposal or a disclosure takes effect in Committees once, and Submissions is told.

How It Works

Submissions runs the forms behind seat applications, nominations, appointment proposals and conflict-of-interest disclosures, and delivers its review decisions to Committees. Each decision is applied once, however often it is delivered. A seat applicant decided appoint is offered the seat, pending their acceptance; one decided alternate is recorded as an alternate on the opening for staff to call on; a decline is recorded. A nomination can be slated or declined, an appointment proposal approved or rejected, and a disclosure accepted or flagged. An outcome the kind does not declare is refused rather than guessed. When Submissions changes its mind, a superseding decision undoes the earlier one where that is still possible and is refused where it is not, such as an appointment already accepted. Committees tells Submissions what happened to every decision, retrying until it is heard. Submissions is not deployed for Committees yet, so this runs only against stand-ins today.

Relationships

Relates to CAP-CMT-MTG-016 because seat applications belong to an opening.
Relates to CAP-CMT-MTG-018 because Submissions may slate or decline a nomination.
Relates to CAP-CMT-MTG-014 because Submissions reviews disclosures.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Every review decision applied exactly onceSuperseded decisions undone where they can beSubmissions told what happened
Surfaces: jobapi
Preconditions: Submissions delivers a version 1 decision document.
Postconditions: Each applied decision is acknowledged to Submissions.
Intent sources: services-committees:docs/milestones/CMTE-M5-openings-and-nominations.md#What is built today

Controls

29 controls apply, from the corpus control catalogue.

TC-IAM-006 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-006 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-SEC-001 TC-SEC-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-AVL-004 TC-MON-001 TC-MON-002 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-PRV-001 TC-PRV-002

Permissions

Key	Checked at	Scope
`committees.openings.read`	api	tenant

Business Rules

10 rules, 8 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	A delivered decision is applied once per decision, and a redelivery changes nothing. no proof recorded yet	invariant	service, database	test services-committees:modules/recruitment/tests/integration/services/submission-decisions.integration.spec.ts#makes no second appointment on the replay
`02`must prove Proposed	A seat application decided appoint makes a pending appointment awaiting the applicant’s acceptance for an open or closed opening, and an applicant who is not a contact is refused. no proof recorded yet	lifecycle	service	test services-committees:modules/recruitment/tests/integration/services/submission-decisions.integration.spec.ts#makes a pending appointment awaiting the applicant’s acceptance, sourced from the decision
`03`must prove Proposed	A seat application decided alternate records the applicant as an alternate on the opening, and one decided decline only records the outcome. no proof recorded yet	lifecycle	service	test services-committees:modules/recruitment/tests/integration/services/submission-decisions.integration.spec.ts#records the alternate on the opening
`04`must prove Proposed	A nomination decided slate or decline is slated or declined, and an appointment proposal approved or rejected appoints or declines its pending appointment. no proof recorded yet	lifecycle	service	test services-committees:modules/recruitment/tests/integration/services/submission-decisions.integration.spec.ts#applies all five
`05`must prove Proposed	An outcome the subject’s kind does not declare is refused and acknowledged as rejected by the owner, saying why. no proof recorded yet	validation	service	test services-committees:modules/recruitment/tests/integration/services/submission-decisions.integration.spec.ts#refuses a code the kind does not declare, recorded refused
`06`must prove Proposed	A superseding decision undoes the earlier one where it can: a still-pending appointment is declined, an alternate withdrawn, a slate withdrawn unless its decision carried, a declined nomination reopened; where it cannot, the supersession is refused and the earlier decision stands. no proof recorded yet	lifecycle	service	test services-committees:modules/recruitment/tests/integration/services/submission-decisions.integration.spec.ts#declines the pending appointment the superseded decision made
`07`must prove Proposed	Each decision’s acknowledgement is queued in the same step that applies it and sent afterwards, retried until Submissions takes it. no proof recorded yet	invariant	service, database, job	test services-committees:modules/recruitment/tests/integration/services/submission-decisions.integration.spec.ts#enqueues the acknowledgement processed, naming the appointment, in the same transaction
`08`must prove Proposed	A decision document that is not version 1, or misses its decision or acknowledgement link, is failed naming the field. no proof recorded yet	validation	service	test services-committees:modules/recruitment/tests/integration/services/submission-decisions.integration.spec.ts#answers the document that is not v1 failed, naming the field
`09` Proposed	Staff read an opening’s alternates that still stand.	policy	api	observed services-committees:modules/recruitment/aws/api/recruitment.routes.ts:listCommitteeOpeningAlternates
`10` Proposed	The Submissions intake and Volunteers are not deployed for Committees, so these decisions arrive only from stand-ins today.	policy	service	documented services-committees:docs/milestones/CMTE-M5-openings-and-nominations.md#What is built today

Scenarios

Id	Given	When	Then	Provenance
`01`	Submissions decides a seat applicant should be appointed	The decision is delivered	The applicant is offered the seat pending acceptance and Submissions is told it was processed	test services-committees:modules/recruitment/tests/e2e/submissions.e2e.spec.ts#acknowledges the decision to the engine, processed, naming the appointment

Planning

Apply review decisions from Submissions exactly once ​

Purpose ​

How It Works ​

Relationships ​