flowchart TB
co_s1["File the final report"]
co_s2["Hand over the database"]
co_s3["Issue the conformance statement"]
co_s1 --> co_s2
co_s2 --> co_s3
NCGS Project Close-out Workflow
The implementing partner files the final report and hands the ledger export to the funder, both as anchored evidence items; once every horizon the statement will name has its monitoring visits verified, Independent Impact issues the conformance statement for the project version. A statement of process, never a certificate of impact (ADR-0014).
1. File the final report
The close-out record is opened against the registered project version with the final integrated report as an evidence item of type report.
Prerequisite checks
The design is approved with its latest validation approved, and the design it supersedes, if any, is withdrawn
Smart function check.
Completion checks
CloseOutRecordShape
SHACL shape.
- A close-out carries exactly one closing date.
- A close-out carries its final report and its ledger export as evidence items by content address (ADR-0007).
- A close-out carries the final integrated report as an evidence item of type report.
- A close-out carries the ledger export handed to the funder as an evidence item of type ledger export.
- A close-out closes exactly one registered project version.
- A close-out closes a registered (approved) project version.
- Instance data must not use the standard’s namespace https://nova.org.za/ncgs/ (ADR-0002: instances are urn:uuid: IRIs).
EvidenceItemShape
SHACL shape.
- A document tag is the UUID printed on the document’s QR sticker, at most one.
- An evidence item must carry exactly one content address. The anchor syntax is fixed by the platform binding profile in force.
- An evidence item must carry exactly one type from the NCGS evidence-types scheme.
- A photograph used as evidence must carry a geotag (photo latitude and longitude).
SubmittedArtifactIdentityShape
SHACL shape.
- A submitted artifact version identifies at most one submission anchor topic. Its syntax is fixed by the platform binding profile in force.
- A submitted artifact version identifies at most one submission consensus timestamp.
- A submitted artifact version must identify exactly one Hedera topic ID in shard.realm.num form.
- A submitted artifact version must identify exactly one artifact author.
- A submitted artifact version must identify exactly one content CID.
- A submitted artifact version must identify exactly one submission consensus timestamp.
- A submitted artifact version must identify exactly one workflow subject.
Step detail
Questions asked: NCGS close-out questions
2. Hand over the database
The ledger export, a query over the project ledger in whatever structure the funder asks for, is added as an evidence item of type ledger export; both items are anchored on the platform.
Prerequisite checks
Completion checks
The final report and the ledger export carry content addresses (anchoring is the platform’s to confirm)
Smart function check.
Step detail
No form is filled in at this step.
3. Issue the conformance statement
Terminal: Independent Impact issues the conformance statement for the project version, naming the horizons whose monitoring visits at the project’s sites were verified; the statement is the one artifact NCGS issues (ADR-0014).
Prerequisite checks
For every horizon the statement names, the project version’s plan reaches it and a monitoring visit declaring it at a site of the project version has an approved verification review
Smart function check.
Completion checks
ConformanceStatementShape
SHACL shape.
- A conformance statement carries only what ADR-0014 names: the project version, the standard version, the validated design’s content address and review outcome, the horizons verified, the date issued, the issuer, the credential, the approved-claims query and its identity contract. Nothing else, and no indicator value (ADR-0014).
- A conformance statement carries exactly one date issued.
- A conformance statement carries, as text, the query over approved claims that is the funder’s report; the statement itself carries no values (ADR-0014).
- A conformance statement is about exactly one registered project version (ADR-0014).
- A conformance statement is issued by Independent Impact, the platform’s agent (ADR-0014).
- A conformance statement is issued only over a validated design: its review outcome is approved.
- A conformance statement names at least one horizon at which monitoring was verified, from the observation-horizon scheme (ADR-0010).
- A conformance statement names the full release the project version was validated against, never a pre-release: only production supports a claim (ADR-0017, ADR-0024).
- A conformance statement references exactly one verifiable credential through the platform’s credential property (ADR-0014).
- A conformance statement carries no indicator value: counts, rates, states and measurements live in the approved claims the statement’s query returns, never on the statement (ADR-0014). Any property whose domain is a tree state, tree observation, tree individual, site preparation record, stewardship record, audience count, consignment line, stratum allocation or quantified target is refused.
- Every horizon verified is one the project version’s monitoring plan reaches for some stratum: a statement cannot name a horizon the monitoring period never reached (ADR-0012, ADR-0014).
- Every horizon verified was declared by a monitoring visit at a site of the project version, made inside its monitoring period (ADR-0010, ADR-0012, ADR-0014).
- Instance data must not use the standard’s namespace https://nova.org.za/ncgs/ (ADR-0002: instances are urn:uuid: IRIs).
- The statement is about a registered (approved) project version.
- The statement’s reviewed content address is the validated design’s: the content address of the project version it is about.
- The statement’s standard version is the one the project version’s design names.
ReviewedArtifactIdentityShape
SHACL shape.
- A review artifact must carry exactly one outcome from the NCGS review outcome scheme.
- A review artifact must identify the exact reviewed artifact content CID.
Step detail
No form is filled in at this step.
Review requirements
No review requirement in the corpus names a record this workflow produces.