flowchart TB
reg_s1["File the design"]
reg_s2["Validation review"]
reg_s3["Register the project version"]
reg_s1 --> reg_s2
reg_s2 --> reg_s3
NWSS Project Registration Workflow
An implementer files a project design; the standards body’s validation review, its seat open to any qualified reviewer who is not the author, checks that every parameter the standard leaves to the project is set in the design and nowhere else and samples the records the design rests on; an approved review registers the project version. A change of scope is a new design that supersedes the registered one, never an edit.
The process graph
Every workflow, step and check the file states, and how they connect.
Open the interactive view on its own page. Drag to move, scroll to zoom, hover for details.
1. File the design
The design is filed by its author with its content address and declares at least one service area coded to a geography scheme, the implementer by role and a monitoring plan. A parameter with a methodology default (service period, carry-forward, newly-placed, follow-up and visit windows, eligibility criteria, deployment success criterion, material category level, accumulation period) may be left unset. A parameter with none is declared: the time zone, the monitoring sample size, the contamination audit sample size and, where a generation-based rate is reported, the characterisation sample size. A design that claims no diverted stream makes no diversion claim. A value set anywhere other than the design does not count (ADR-0010).
Prerequisite checks
The design names its author and carries its content address (anchoring is the platform’s to confirm)
Smart function check.
Completion checks
The design declares the parameters that have no methodology default: its time zone, its monitoring plan’s sample size and contamination audit sample size, and, where it reports a generation-based rate, its characterisation sample size
Smart function check.
The design declares at least one service area, every one coded to a geography scheme, an implementer by role and a monitoring plan
Smart function check.
2. Validation review
Seat: any reviewer meeting the validation-review KSR rule in every knowledge domain the design’s applied methodologies require, who is not the design’s author (nwss-vvr:validate-project-design, ADR-0012). The reviewer samples the enumeration, enrolment and deployment records in the declared service areas; none is reviewed one by one.
Prerequisite checks
At least one service point in a declared service area has an enumeration record that is not withdrawn
Smart function check.
No validation review of the design is by its author (the reputation requirement per knowledge domain is the platform’s to enforce)
Smart function check.
Completion checks
The latest validation review of the design’s content address under validate-project-design is approved
Smart function check.
3. Register the project version
Terminal: the design’s approval status becomes approved and it is the project version claims are made under; the design it supersedes, if any, becomes withdrawn.
Prerequisite checks
Completion checks
The design is approved with its latest validation approved, and the design it supersedes, if any, is withdrawn
Smart function check.
Review requirements
No review requirement in the corpus names a record this workflow produces.