Rhythm 2.0 Specifications

Appearance

CAP-SUB-SUB-011Complete a stage once on an accountable basis

Markdown

CAP-SUB-SUB-011

Complete a stage once on an accountable basis

Markdown
  • DocumentDraft
  • Product intentProposed
  • ImplementationObserved

Planning

Feature
FEAT-SUB-SUB-03
Exercised by
FAS-SUB-SUB-03-01, FAS-SUB-SUB-03-03, FAS-SUB-SUB-03-05, FAS-SUB-SUB-05-01, FAS-SUB-SUB-05-05
Key concepts
CON-SUB-SUB-003
Actors
ACT-SUB-003, ACT-SUB-001, ACT-SUB-007, ACT-SUB-008
Journeys
JNY-SUB-SUB-002, JNY-SUB-SUB-003
Depends on
CAP-SUB-SUB-010
Related
CAP-SUB-SUB-013, CAP-SUB-SUB-014, CAP-SUB-SUB-008
Proved by
ATS-SUB-SUB-011

Implementation

Executable suites
TST-SUB-SUB-251, TST-SUB-SUB-501, TST-SUB-SUB-503, TST-SUB-SUB-504, TST-SUB-SUB-505, TST-SUB-SUB-522

KindCapabilityProduct areaSubmissionsModuleSubmissions, Intake, Review and OutcomesRevision1

Read atservices-submissions 64236c19react-console baf6dae3

Complete a stage once on an accountable basis ​

Purpose ​

Stage completion turns the configured review count or authorized intervention into one recorded transition.

How It Works ​

Each response updates the evidence available to the counting rule. The engine evaluates that evidence while holding the application's and stage's locks in order. When the rule is satisfied, completion records its basis and performs the next configured action. A completed run stays as part of review history. Administrator intervention can close a stage early or waive a requirement with an explanation. Ordinary staff authority does not imply those override powers. Requirement waits also depend on integrations that are not all available in the pinned product.

Relationships ​

The Formal Contract

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

Outcomes
Completion rules establish a reproducible basisConcurrent final answers produce one transitionExceptional completion records accountable intervention
Surfaces
consoleapijob
Intent sources
services-submissions:docs/milestones/plans/SUBM-M1-plan.md#D7services-submissions:docs/milestones/plans/SUBM-M1-plan.md#S06services-submissions:docs/milestones/plans/SUBM-M1-plan.md#S11services-submissions:docs/milestones/plans/SUBM-M1-plan.md#D8

Controls

38 controls apply, from the corpus control catalogue.

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

Permissions

KeyChecked atScope
submissions.stages.overrideapitenant
submissions.stages.completeapiglobal

Business Rules

12 rules, 12 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.

IdRuleKindEnforced atProvenance
01must prove
Proposed
Concurrent final reviews required by a counting rule are both retained with one stage completion and decision, while reviews after an earlier completion obey the late-response policy.
origin: services-submissions:docs/milestones/plans/SUBM-M1-plan.md#SUBM-M1-S06
proved by ATS-SUB-SUB-011-01, TST-SUB-SUB-505
invariantservice, databasetest
services-submissions:modules/review/tests/integration/services/stage-runs/completion-concurrency.integration.spec.js#records both responses, completes the run once, and records one decision
02must prove
Proposed
Repeated completion changes nothing and is refused; database constraints also prevent concurrent open runs and multiple current decisions for an application.
origin: services-submissions:docs/milestones/plans/SUBM-M1-plan.md#SUBM-M1-S06
proved by ATS-SUB-SUB-011-02, TST-SUB-SUB-505
invariantservice, databasetest
services-submissions:modules/review/tests/integration/services/stage-runs/completion-concurrency.integration.spec.js#is refused as StaleObject and changes nothing
03must prove
Proposed
An all-assigned stage completes after all remaining live work answers, excludes declined, recused and revoked assignments and flags an empty panel as short.
origin: services-submissions:docs/milestones/plans/SUBM-M1-plan.md#D7
proved by ATS-SUB-SUB-011-03, TST-SUB-SUB-522
calculationservicetest
services-submissions:modules/review/tests/unit/services/completion/completion-rule.spec.ts#is met when nobody is pending, with the counts as its basis
04must prove
Proposed
A count rule completes at its required response count, retains responses from subsequently removed reviewers and flags a panel unable to reach that count.
origin: services-submissions:docs/milestones/plans/SUBM-M1-plan.md#D7
proved by ATS-SUB-SUB-011-04, TST-SUB-SUB-522
calculationservicetest
services-submissions:modules/review/tests/unit/services/completion/completion-rule.spec.ts#is met at the minimum, whoever is still pending
05must prove
Proposed
An any-one rule completes on its first submitted response and takes a rejecting recommendation as non-approval.
origin: services-submissions:docs/milestones/plans/SUBM-M1-plan.md#D7
proved by ATS-SUB-SUB-011-05, TST-SUB-SUB-522
calculationservicetest
services-submissions:modules/review/tests/unit/services/completion/completion-rule.spec.ts#is met by the first response, rejecting when it rejects
06must prove
Proposed
Unanimous approval fails at the first non-approving response, including an abstention.
origin: services-submissions:docs/milestones/plans/SUBM-M1-plan.md#SUBM-M1-S11
proved by ATS-SUB-SUB-011-06, TST-SUB-SUB-522
calculationservicetest
services-submissions:modules/review/tests/unit/services/completion/completion-rule.spec.ts#is met, not approving, at the first rejection, others still pending
07must prove
Proposed
A majority rule completes when remaining work cannot change the result, requiring more than half and treating a final even split as non-approval.
origin: services-submissions:docs/milestones/plans/SUBM-M1-plan.md#SUBM-M1-S11
proved by ATS-SUB-SUB-011-07, TST-SUB-SUB-522
calculationservicetest
services-submissions:modules/review/tests/unit/services/completion/completion-rule.spec.ts#is met, approving, when approvals are more than half of those expected, others pending
08must prove
Proposed
Completion expires outstanding assignments unless late responses are allowed and atomically advances review or records the decision.
origin: services-submissions:docs/milestones/plans/SUBM-M1-plan.md#D7
proved by ATS-SUB-SUB-010-12, ATS-SUB-SUB-011-08, ATS-SUB-SUB-011-12, ATS-SUB-SUB-011-13, ATS-SUB-SUB-011-14, ATS-SUB-SUB-013-12, ATS-SUB-SUB-014-11, ATS-SUB-SUB-015-11, ATS-SUB-SUB-016-15, TST-SUB-SUB-504
lifecycleservicetest
services-submissions:modules/review/tests/integration/services/stage-runs/approval-not-approved.integration.spec.js#advances to the next stage on an approving result, whichever choice was made
09must prove
Proposed
Only administrators can end stages early, recording their reason, identity and current counts with any optional decision.
origin: services-submissions:docs/milestones/plans/SUBM-M1-plan.md#D8
proved by ATS-SUB-SUB-011-09, TST-SUB-SUB-251
permissionapi, serviceobserved
services-submissions:modules/review/services/stage-runs/staff-actions.ts:closeEarly
10must prove
Proposed
Requirement stages wait for fulfillment or an authorized waiver; external completion uses a staff-only route, while the Commerce participant remains unavailable.
proved by ATS-SUB-SUB-011-10, TST-SUB-SUB-501
lifecycleapi, servicetest
services-submissions:modules/review/tests/integration/services/requirements/contributions.integration.spec.js#completes the wait with the counts as they stand, the key still short, who and why
11must prove
Proposed
Ended-stage mutations refuse draft saves, review submissions and assignment or staff actions according to their service guards.
proved by ATS-SUB-SUB-011-16, TST-SUB-SUB-503
validationserviceobserved
services-submissions:modules/review/services/responses/response-actions.ts:saveDraft
12must prove
Proposed
Re-entering the same stage assigns the next run number for that application and stage.
proved by ATS-SUB-SUB-008-13, ATS-SUB-SUB-009-14, ATS-SUB-SUB-011-11, ATS-SUB-SUB-011-15, ATS-SUB-SUB-012-08, ATS-SUB-SUB-013-10, ATS-SUB-SUB-016-13, ATS-SUB-SUB-018-10
calculationservicetest
services-submissions:modules/review/tests/integration/services/stage-runs/open-stage-run.integration.spec.js#takes the next run_number of that stage for the submission

Scenarios

IdGivenWhenThenProvenance
01The award requires both assigned reviews.Priya supplies the final response.Completion occurs immediately and the configured aggregate selects the result.test
react-console:acceptance/submissions/playwright/journeys/review/SUB-ACC-0329.spec.ts#SUB-ACC-0329

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software