Rhythm 2.0 Specifications

Appearance

CAP-SUB-SUB-010Complete an assigned assessment using the scoring sheet

Markdown

CAP-SUB-SUB-010

Complete an assigned assessment using the scoring sheet

Markdown
  • DocumentDraft
  • Product intentProposed
  • ImplementationObserved

Planning

Feature
FEAT-SUB-SUB-03
Exercised by
FAS-SUB-SUB-03-01, FAS-SUB-SUB-03-02, FAS-SUB-SUB-03-03, FAS-SUB-SUB-03-04, FAS-SUB-SUB-03-05, FAS-SUB-SUB-06-04
Key concepts
CON-SUB-SUB-003, CON-SUB-SUB-002
Actors
ACT-SUB-003
Journeys
JNY-SUB-SUB-002, JNY-SUB-SUB-003
Depends on
CAP-SUB-SUB-009, CAP-SUB-SUB-003
Related
CAP-SUB-SUB-011, CAP-SUB-SUB-012, CAP-SUB-SUB-008
Proved by
ATS-SUB-SUB-010

Implementation

Executable suites
TST-SUB-SUB-294, TST-SUB-SUB-338, TST-SUB-SUB-376, TST-SUB-SUB-477, TST-SUB-SUB-479, TST-SUB-SUB-482, TST-SUB-SUB-503, TST-SUB-SUB-522

KindCapabilityProduct areaSubmissionsModuleSubmissions, Intake, Review and OutcomesRevision1

Read atservices-submissions 64236c19react-console baf6dae3

Complete an assigned assessment using the scoring sheet ​

Purpose ​

Reviewers read their assigned content, provide judgment and preserve the submitted assessment.

How It Works ​

The reviewer opens work from My reviews. The assignment shows the submitted application projection and the selected scoring sheet. They can accept the work, save partial answers and return before submitting. Stage policy controls whether stepping aside or delegation is offered. Submission uses the supplied review body and reports whether that write also completed the stage. Amendments retain earlier submitted content rather than editing it in place. Work submitted after completion follows the explicit late-review policy.

Relationships ​

The Formal Contract

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

Outcomes
The review queue contains the person's own workAllowed reviewer actions follow stage policySubmitted judgments retain scored content
Surfaces
consoleapi
Intent sources
services-submissions:docs/milestones/plans/SUBM-M1-plan.md#2. Scopeservices-submissions:docs/milestones/plans/SUBM-M1-plan.md#D9services-submissions:docs/milestones/plans/SUBM-M1-plan.md#D7services-submissions:docs/milestones/plans/SUBM-M1-plan.md#S10services-submissions:docs/milestones/SUBM-M1-staff-review-in-the-console.md#E1

Controls

34 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-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-004 TC-IAM-005 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.application.accessapitenant

Business Rules

12 rules, 10 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
My reviews resolves only the signed-in staff user's assignments, showing process and action policy and withholding applicant names on blind stages.
origin: services-submissions:docs/milestones/plans/SUBM-M1-plan.md#D9
proved by ATS-SUB-SUB-010-01, TST-SUB-SUB-338, TST-SUB-SUB-477, TST-SUB-SUB-479
permissionservice, consoletest
services-submissions:modules/review/tests/e2e/review.e2e.spec.js#finds the assignment in the staff reviewer’s queue, read by user
02must prove
Proposed
The reviewer role grants assignment-based access and refuses staff-wide application reads even for assigned applications.
origin: services-submissions:docs/milestones/plans/SUBM-M1-plan.md#D9
proved by ATS-SUB-SUB-010-02, ATS-SUB-SUB-020-09, TST-SUB-SUB-477
permissionapitest
services-submissions:modules/review/tests/e2e/review.e2e.spec.js#is refused every staff-wide read of a submission they are not assigned to
03must prove
Proposed
Requests for another person's assignment return an absent-record response.
origin: services-submissions:docs/milestones/plans/SUBM-M1-plan.md#D9
proved by ATS-SUB-SUB-010-03, TST-SUB-SUB-477
permissionservicetest
services-submissions:modules/review/tests/e2e/review.e2e.spec.js#refuses one staff user the other’s assignment, as if it did not exist
04must prove
Proposed
Assignment reads provide projected submitted answers, the scoring sheet and the reviewer's response, without exposing other reviewers' scores.
origin: services-submissions:docs/milestones/plans/SUBM-M1-plan.md#D7
proved by ATS-SUB-SUB-010-04, TST-SUB-SUB-477
permissionservicetest
services-submissions:modules/review/tests/e2e/review.e2e.spec.js#opens the assignment with the reviewer view, the rubric and an empty draft
05must prove
Proposed
Reviewers can accept work or decline with a configured reason and note; declining removes their live work and voids a draft.
origin: services-submissions:docs/milestones/plans/SUBM-M1-plan.md#SUBM-M1-S10
proved by ATS-SUB-SUB-005-07, ATS-SUB-SUB-009-15, ATS-SUB-SUB-010-05, ATS-SUB-SUB-010-11, ATS-SUB-SUB-012-09, TST-SUB-SUB-482
lifecycleservicetest
services-submissions:modules/review/tests/integration/services/assignments/assignment-actions.integration.spec.js#moves the assignee’s assignment to accepted, with the instant
06must prove
Proposed
Stage policy determines whether reviewers can recuse with a conflict or delegate to a non-participant; prohibited actions are rejected and hidden in the console.
proved by ATS-SUB-SUB-010-06, TST-SUB-SUB-294, TST-SUB-SUB-376, TST-SUB-SUB-482
policyservice, consoletest
services-submissions:modules/review/tests/integration/services/assignments/assignment-actions.integration.spec.js#refuses a delegation on a stage that does not allow one
07must prove
Proposed
Draft review saves allow partial answers, require the version read and reject unknown fields, out-of-range scores and changes to already submitted work.
origin: services-submissions:docs/milestones/plans/SUBM-M1-plan.md#2. Scope
proved by ATS-SUB-SUB-010-07, TST-SUB-SUB-477, TST-SUB-SUB-503
validationapi, servicetest
services-submissions:modules/review/tests/integration/services/responses/response-actions.integration.spec.js#is saved with a partial answer at the version the reviewer read
08must prove
Proposed
Submitting validates the supplied review strictly, calculates its scores, completes the assignment and reports stage completion, while rejecting repeat submission.
origin: services-submissions:docs/milestones/plans/SUBM-M1-plan.md#2. Scope
proved by ATS-SUB-SUB-003-09, ATS-SUB-SUB-010-08, ATS-SUB-SUB-010-12, ATS-SUB-SUB-010-14, ATS-SUB-SUB-011-12, TST-SUB-SUB-477, TST-SUB-SUB-503
validationservicetest
services-submissions:modules/review/tests/integration/services/responses/response-actions.integration.spec.js#stores the response scored by the rubric, completes the assignment, and says whether it completed the stage
09must prove
Proposed
A review arriving after completion is refused unless a count rule explicitly permits late responses below its maximum, in which case it is retained without revising the result.
origin: services-submissions:docs/milestones/plans/SUBM-M1-plan.md#D7
proved by ATS-SUB-SUB-010-09, TST-SUB-SUB-503, TST-SUB-SUB-522
policyservicetest
services-submissions:modules/review/tests/integration/services/responses/response-actions.integration.spec.js#is refused as StaleObject after another response completed the stage, and records nothing
10must prove
Proposed
Submitted content is frozen, and amendments while the stage remains open add a superseding response while retaining both versions.
proved by ATS-SUB-SUB-010-10, ATS-SUB-SUB-010-13, ATS-SUB-SUB-010-15, TST-SUB-SUB-503
invariantservice, databasetest
services-submissions:modules/review/tests/integration/services/responses/response-actions.integration.spec.js#cannot be changed by any statement: the freeze trigger refuses it with RHS03
11
Proposed
Peer response sharing and applicant feedback release are unavailable, and the sharing control is disabled.
origin: services-submissions:docs/milestones/plans/SUBM-M1-plan.md#A13
policyservice, consoledocumented
services-submissions:docs/milestones/SUBM-M1-staff-review-in-the-console.md#Status history
12
Proposed
Database privileges allow the application role to change draft scores; the submitted-content freeze does not protect drafts.
invariantdatabaseobserved
services-submissions:modules/review/db/review-responses.table.ts; services-submissions:modules/review/tests/integration/services/persistence/review-responses.integration.spec.js

Scenarios

IdGivenWhenThenProvenance
01Sam and Priya hold the award's assignments.They submit Impact and Service scores of 5 and 4, then 4 and 4.Both responses persist and Priya's write completes the stage.test
react-console:acceptance/submissions/playwright/journeys/review/SUB-ACC-0329.spec.ts#SUB-ACC-0329

Edge Cases

IdGivenWhenThenProvenance
02The reviewer keeps the same assignment open in two browser tabs.A second acceptance and an outdated save reach the service.Duplicate acceptance and stale saving are rejected without duplicating the assessment.documented
react-console:acceptance/submissions/journeys/review/SUB-ACC-0281.json

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