Nexus Verified Water Standard — master standard

DRAFT FOR CONSULTATION. NVWS v0.1 (October 2026). This is a proposed Nexus Water DAO LLC standard. It is not approved, adopted or independently assured. The methods have not been approved by an independent technical council. No Verified Water Credits (VWC) have been issued, and none are offered for sale. References to WRI, AWS, Gold Standard, ISO, EPA, FTC, SEC, CFTC or any other organization are not endorsements. Comments: josh@nexuswater.xyz

Version 0.1 · 2026-10-03 · Nexus Water DAO LLC

Status: proposed Nexus policy / technical draft. Not an approved or independently assured credit standard.

Purpose and scope

Nexus finances, measures, verifies, records and retires specified water outcomes. Its initial commercial offer is program administration and defensible evidence-backed reporting. Market acceptance of a Nexus unit must be earned through projects, contracts, independent review and buyer acceptance; a registry or token alone does not create it.

This V0.1 establishes a proposed standard and an engineering contract. “STANDARD REQUIREMENT” identifies normative requirements inside this draft, not enacted law or an already adopted international standard. All such requirements remain PROPOSED NEXUS POLICY until the technical governance process approves a release. FACT identifies externally sourced statements. HYPOTHETICAL EXAMPLE identifies illustrative projects, numbers and economics. The names NVWS and VWC are working marks; trademark registration and clearance have not been established.

Environmental unit

STANDARD REQUIREMENT: One volumetric VWC represents one cubic meter of an eligible, specified water benefit under an approved methodology. One m³ is 1,000 liters. The initial unit precision is whole m³; calculations retain six decimal places and issuance rounds down. Residuals remain unissued and cannot be rolled into another vintage without an approved aggregation rule. Whole-unit precision is Nexus policy, not a hydrological fact.

The unit passport binds class, outcome metric, source and destination catchments, project boundary, monitoring period, baseline, activity, project owner, environmental-attribute allocation, methodology version, evidence commitment, verification report and issuance batch. A physical meter reading, contracted forecast or installed capacity is not an issued unit.

Water stress, ecosystem importance, technology, access and carbon co-benefits do not increase physical volume. Quality/access metrics that lack a defensible volumetric basis remain non-volumetric outcome records. A generic “water credit” total cannot imply that unlike classes satisfy the same target.

Normative hierarchy

Applicable law controls legal obligations. Official hydrological and regulatory data, relevant standards, WRI/CEO Water Mandate guidance, AWS, ISO, peer-reviewed hydrology, accepted engineering and documented project evidence inform technical decisions according to their actual applicability. This is not a mechanical ranking that makes an unsuitable general document override better site-specific evidence. Nexus policy cannot override physical reality, actual permit conditions or contracts. A conflict is documented and resolved by a qualified reviewer before issuance; the stricter valid eligibility boundary applies until resolved.

References are catalogued in the Nexus reference library (publication pending). WRI guidance informs quantification but does not certify NVWS. AWS site stewardship certification is not VWC certification. ISO water-footprint assessment is not a water-credit registry. Gold Standard has an existing WBC precedent; no transfer of its recognition is implied.

Issuance prerequisites

1. An approved, effective methodology version for the project, metric, jurisdiction and activity.
2. A registered outcome boundary, legal entity, source catchment and monitoring vintage; public-sensitive coordinates may be generalized.
3. A documented baseline/counterfactual approved before relying on the measured result, with change control for normalization.
4. Additionality decisions, safeguards, community engagement and legally sufficient environmental-attribute rights.
5. Ex-post evidence with quality controls; a completed monitoring period; no unresolved material fraud or missing-data issue.
6. A reproducible calculation with documented exclusions, adverse effects, uncertainty and allocation.
7. A conflict-screened independent verification opinion and separate registry review.
8. A uniqueness search and allocation reconciliation, with previous issuance across all methods and registries disclosed.
9. Valid legal, operational and security release gates; approvals bound to the exact evidence/calculation version.

No real issuance is permitted under these draft methodologies.

Accounting model

The initial calculation contract is: eligible = max(0, gross eligible benefit − conservative uncertainty deduction − attributable adverse-effect/leakage deduction) × allocated share. Each methodology defines gross benefit and the deduction boundaries. The order and dimensions are fixed before verification; do not apply the same uncertainty or attribution adjustment twice.

“95% confidence” is not synonymous with multiplying by 0.95. A statistical confidence level needs a valid error model and specified bound; a five-percent discount is a policy deduction that needs a defensible technical basis. Evidence tiers alone provide neither. The hotel example of 16,800 × 0.95 = 15,960 is arithmetic, not validation of that discount.

Every batch maintains lifetime issued ≤ its verified eligible cap. Issued = active + retired + cancelled for distinct, non-overlapping serials. Invalidated retired units remain historically retired, with their claim invalidated separately; otherwise the same serial would be counted twice. Claims against invalidated records are suppressed and affected parties notified.

Governance and accountability

Create a technical council with hydrology, groundwater, utility operations, quality, WASH, metering, environmental markets, legal, buyer and verifier expertise. Publish actual appointments only after acceptance. Proposed quorum: five non-conflicted members including hydrology, assurance and claims expertise; two-thirds approval of eligible voters; documented minority opinions. These are governance design proposals, not appointments.

Methodology lifecycle: draft → technical review → 45-day consultation (30–60 day policy range) → comment disposition → council decision → controlled pilot → performance review → final publication. Publish versions, effective dates, geographic applicability and migration treatment. No silent retroactive formula replacement. Material scientific errors trigger a hold and incident process even for older vintages.

Separate commercial, scientific and registry authority. Token ownership cannot approve scientific rules, overturn verifier findings or erase fraud evidence. Disclose success-fee conflicts; verifier compensation must not depend on issued volume or approval. Registry staff cannot approve their own issuance request. Maintain complaints, appeals and sanctions with an independent adjudicator.

Lifecycle and financing

Project design, validation and registration do not equal verification or issuance. Annual or shorter defined vintages require fresh monitoring. A future outcome can be financed under a forward agreement, but forecasts remain separate from verified units. A funded project can fail to produce eligible VWCs; contracts allocate that risk without relabeling forecasts.

Registry ownership is a contractual environmental-attribute record, subject to applicable law and disputes. It is not a water right, delivery entitlement, discharge permit, carbon offset, compliance credit, tax deduction, equity, yield or guaranteed investment return. Retirement records identify the beneficiary, allocation, quantity, location, method and purpose. A financing contribution and an exclusive outcome claim are different products.

Information stewardship

Retain append-only public identifiers and correction history. Preserve evidence for the applicable contractual/legal period with encrypted backups, access controls and tested restoration. Do not promise that all raw personal or sensitive evidence will be public or kept forever. A lawful deletion/redaction may remove payloads while leaving a minimal permitted tombstone and record of the action; hashes themselves may be identifying and need review.

Blockchain anchors are optional, asynchronous proof of a commitment’s inclusion, not proof of environmental truth. Registry issuance and retirement remain correct when XRPL is unavailable. Tokenization is a later, separately authorized release.

Release gates and success

The first success is a paid evidence/MRV pilot with an agreed catchment, accepted method, authorized data and independent reviewer. A real batch is a later gate, never a day-90 promise. Publish the standard as a draft; recruit reviewers and test buyer claims. Promote to V1 only after the Nexus acceptance criteria pass and all live-issuance gates have named approvers and evidence.