Skip to content

CAP-SUB-SUB-008Administer clarification and changes to an application's lifecycle

Markdown

CAP-SUB-SUB-008

Administer clarification and changes to an application's lifecycle

Markdown
  • DocumentDraft
  • Product intentProposed
  • ImplementationObserved

KindCapabilityProduct areaSubmissionsModuleSubmissions, Intake, Review and OutcomesRevision1

Read atservices-submissions 64236c19react-console baf6dae3

The Formal Contract

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

Outcomes
Information waits retain their question and answerWithdrawal and closure cancel current workReopening and correction preserve earlier executions
Surfaces
portalapi
Intent sources
services-submissions:docs/milestones/README.md#The milestone plan

Controls

42 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-CRY-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 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 TC-SEC-001 TC-SEC-002 TC-SEC-003 TC-SEC-004 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004

Permissions

KeyChecked atScope
submissions.submissions.manageapitenant
submissions.submissions.readapitenant
submissions.application.accessapitenant

Business Rules

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

IdRuleKindEnforced atProvenance
01must prove
Proposed
An assignee on the current stage or authorized staff can open one information request, putting the run and application into an applicant wait and refusing another concurrent request.
no proof recorded yet
lifecycleservicetest
services-submissions:modules/review/tests/integration/services/views/reviewer-views.integration.spec.js#an assignee’s information request is anonymous, moves the run and the submission to awaiting the applicant, and a second is refused
02must prove
Confirmed
Applicant waits pause internal-clock timers and extend them by the waiting interval when resumed, while wall-clock timers continue.
no proof recorded yet
calculationservicetest
services-submissions:modules/review/tests/integration/services/workflow/stage-timers.integration.spec.js#pauses its internal-clock timers and not its wall-clock ones; the answer resumes them later by the wait, its service target too
03
Confirmed
Blind-stage reviewer requests conceal the reviewer, whereas unassigned staff can issue applicant-visible requests.
policyservicetest
services-submissions:modules/review/tests/integration/services/views/reviewer-views.integration.spec.js#staff ask without being assigned, the request naming the applicant as its audience
04must prove
Proposed
Answering preserves the working answers in a clarification revision linked to the request, restricts requested-field edits and returns the application to review.
no proof recorded yet
validationservicetest
services-submissions:modules/intake/tests/integration/services/submissions/submission-lifecycle.integration.spec.js#writes the working payload as revision 2, a clarification response naming the request
05must prove
Proposed
A continuing revision policy reopens and rechecks the asking run; the default restart cancels the current open run and starts the asking stage again with fresh assignments.
no proof recorded yet
lifecycleservicetest
services-submissions:modules/intake/tests/e2e/seam.e2e.spec.js#cancels the run that asked and opens the approval stage again as run 2
06must prove
Proposed
Answers are rejected when the application version is stale, the request already answered or the caller lacks participation rights.
no proof recorded yet
validationservicetest
services-submissions:modules/intake/tests/e2e/seam.e2e.spec.js#answers 409 to an answer at a version the submission is no longer at, and to a second answer
07must prove
Proposed
Policy-permitted withdrawal by an applicant, representative, staff member or owner cancels the current run, expires assignments and cancels queued actions and timers; withdrawal cannot be repeated.
no proof recorded yet
lifecycleservicetest
services-submissions:modules/intake/tests/e2e/seam.e2e.spec.js#answers 200, the submission withdrawn and its open run cancelled
08must prove
Proposed
Authorized staff or the owner can close an unfinished application and cancel its run, while applicants cannot close it.
no proof recorded yet
permissionapi, servicetest
services-submissions:modules/intake/tests/e2e/seam.e2e.spec.js#answers 403 to the applicant, who may not close it
09must prove
Proposed
Staff reopening starts a new first-stage run and preserves cancellations; reopening a decided application retires its decision and cannot return it to draft.
no proof recorded yet
lifecycleservicetest
services-submissions:modules/intake/tests/e2e/seam.e2e.spec.js#reopens into review on a new run, run 2, the cancelled run left cancelled
10must prove
Proposed
Administrative answer corrections add a labeled revision without changing the application's status.
no proof recorded yet
lifecycleservicetest
services-submissions:modules/intake/tests/integration/services/submissions/submission-lifecycle.integration.spec.js#writes the correction as a revision of reason administrative_correction, the status unmoved
11must prove
Proposed
Closing, reopening and correcting require management authority and refuse staff who possess reading rights alone.
no proof recorded yet
permissionservicetest
services-submissions:modules/intake/tests/integration/services/submissions/submission-lifecycle.integration.spec.js#refuses a staff member without submissions.submissions.manage, as AccessDenied once they may read it
12
Proposed
An information request past its response deadline raises an attention item for review operations.
policyserviceobserved
services-submissions:aws/submissions.attention.ts:SUBMISSIONS_ATTENTION_DEFINITIONS
13
Proposed
The lifecycle operations are available through APIs and service integrations, with no console controls at the pinned revision.
policyconsoleobserved

Scenarios

IdGivenWhenThenProvenance
01Clarification uses a restart revision policy.A reviewer requests missing material and the applicant answers.The first run remains cancelled and a second execution uses the new revision.test
services-submissions:modules/intake/tests/e2e/seam.e2e.spec.js#cancels the run that asked and opens the approval stage again as run 2
02An applicant has withdrawn an entry.Staff invoke the permitted reopening action.A new run begins review without reviving the earlier cancelled execution.test
services-submissions:modules/intake/tests/e2e/seam.e2e.spec.js#reopens into review on a new run, run 2, the cancelled run left cancelled

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.