Direct Answers to the Strongest Objections

That question deserves a direct answer, not a defensive one. Greenwashing works by using environmental language to obscure the absence of substantive accountability. The Green Code is designed to make that kind of obscuration structurally impractical — not by claim, but by mechanism.

The framework requires open API-level resource disclosure for every major AI inference event, meaning water and energy use are cryptographically verifiable in near-real-time rather than disclosed retrospectively in annual ESG reports that are impractical to audit independently. It also mandates absolute resource caps — not efficiency targets that can be undermined by scale increases — and includes an ecological kill-switch that triggers automated compute throttling if aquifer recharge thresholds are exceeded.

The honest caveat is this: these mechanisms are PROPOSED in the current framework. The pilot phase in Texas County, if authorized and executed, will produce the first independent field validation. Until that data exists, the framework is a serious and detailed governance proposal — not a certified practice. We say so explicitly on every page where it matters.

The Jevons Paradox is one of the most significant structural risks to any efficiency-based governance framework: as resource use becomes more efficient, total consumption tends to increase because scale expands to absorb the savings. A framework that only sets efficiency targets without absolute limits will fail against this paradox.

The Green Code addresses this through three specific structural mechanisms:

• Absolute resource caps — efficiency gains cannot be reinvested into unlimited scale. The 50 MW compute node ceiling is a hard cap, not an average.
• The Compute Dividend — the financial equivalent of resource savings must be transferred to the host community, making rebound economically unattractive for operators.
• The Ecological Kill-Switch — if local aquifer recharge is exceeded, compute is throttled automatically, regardless of contract terms.

These mechanisms are PROPOSED. Their effectiveness against Jevons rebound under real-world conditions has not yet been field-tested. The pilot phase is designed to generate this data.

This is the most important question a reviewer can ask. Here is a clear breakdown:

Every page on this site that contains a quantitative claim carries a visible status label. See the Claims Register for the complete indexed list.

NBR = B_v / C_r, where B_v is independently verified social and ecological benefit value, and C_r is quantified aggregate resource burden.

The formula is simple. The hard work is in operationalizing it — defining what counts as Bv, how baselines are established, how attribution is assigned, and what verification process qualifies a benefit as "independently verified."

The full methodology is documented on the NBR Methodology page, including:

• Candidate Bv categories (water recovery, carbon offset, thermal reuse, community economic benefit)
• Baseline and counterfactual logic
• Attribution rules for operator NBR vs system NBR
• Confidence levels and verification requirements
• How NBR is expected to change across pilot phases

The current NBR framework is PROPOSED. Field application will require adaptation based on what data can actually be collected at the pilot site.

Any ROI, payback period, or efficiency ratio associated with the Green Code framework should be understood as an engineering model output — not a measured field result. These numbers are derived from computational simulations based on reference engineering parameters. They represent what the system is designed to achieve, not what has been demonstrated in deployment.

All such figures carry a PROJECTED or SIMULATED label on the pages where they appear. Any document, press summary, or external source that presents these figures as measured outcomes is misrepresenting the current state of the framework.

The pilot phase is designed precisely to convert projected figures into verified ones. Until that happens, treat all performance numbers as design targets with engineering-grade methodology behind them, not audit-grade validation.

GCTS-1 (Green Code Technical Standard, version 1) is the measurement and disclosure standard that makes NBR calculation possible. It defines:

• What must be measured (energy, water, hardware lifecycle, idle overhead)
• At what granularity (per-inference as well as aggregate facility level)
• With what frequency (API-accessible, near-real-time for water and energy)
• Under what audit thresholds (G-level classification determines audit intensity)
• With what evidence artifacts (what documentation satisfies a verification claim)

In summary: GCTS-1 is the data collection protocol. NBR is the evaluation framework that uses GCTS-1 data to produce a governance decision. You cannot compute a credible NBR without GCTS-1-compliant data.

Full documentation is on the GCTS-1 Methodology page. Both standards are currently PROPOSED — published for review and piloting, not yet independently certified.

The Green Code framework specifies an independent auditor accreditation system as part of the governance design. Under this model, verification is performed by auditors who meet published independence criteria — not by the framework authors, not by the operator, and not by an entity with a financial interest in the outcome.

The auditor framework is currently PROPOSED. No accredited auditors exist yet because the framework has not yet completed the institutional formation required to accredit them. The Green Code Foundation (501c3) — currently in incorporation — is the planned body that will establish and enforce auditor independence standards.

Until that body exists and accredits its first auditors, claims labeled VERIFIED on this site reflect verification against the published methodology by the framework authors and, where applicable, third-party engineering review. We do not represent this as fully independent audit.

Audit capture is a serious and well-documented problem across financial, environmental, and technical auditing. The framework addresses it through several structural mechanisms:

• Auditor rotation requirements — the same auditor cannot certify the same facility for consecutive cycles beyond a defined limit
• Open API data access — GCTS-1 requires that raw measurement data be accessible to any accredited party, not just the commissioned auditor, making it structurally impractical to suppress inconvenient readings
• Public reporting — audit findings are published, not held privately between operator and auditor
• Conflict-of-interest disclosure — auditors must declare and publish any financial relationship with the entity being audited
• Community challenge rights — municipalities and civil society organisations have standing to challenge audit findings and trigger re-review

These mechanisms are PROPOSED. Their actual enforcement depends on the governance infrastructure being built. We encourage scrutiny of this aspect in particular.

Existing standards are designed for different purposes. The Green Code is complementary to them, not competitive with them. Specifically:

• GRI (Global Reporting Initiative) — covers voluntary ESG disclosure at the organizational level, using self-reported annual data. The Green Code requires mandatory, real-time, API-accessible disclosure at the facility and inference level. These operate at different granularities.
• CDP (Carbon Disclosure Project) — focuses on carbon. The Green Code also governs water, hardware lifecycle, and community economic impact, and requires API-level disclosure rather than annual questionnaire response.
• EU AI Act — governs AI system risk categories and fundamental rights impacts but does not address physical infrastructure resource consumption, water extraction, or local ecological accountability. The Green Code is designed to fill this gap.
• ISO 14001 / environmental management standards — process standards, not outcome standards. They govern how an organization manages environmental impact, not whether the impact meets a measurable threshold.

The Standards Crosswalk page documents these relationships in detail, including where The Green Code overlaps, extends, or defers to adjacent frameworks.

No — not yet. The Texas County pilot is currently a formal proposal submitted to the relevant municipal and county parties. The proposal documents are public and linked below.

The pilot will move to active status when the following conditions are met:

• Municipal or county authorization granted
• Funding secured for sensor deployment (Phase 0)
• EPA SDWA §1431 petition filed or waived by relevant authority
• At least one data center operator enrolled in the pilot protocol

The Pilot Status page tracks the current phase, verified facts, projected assumptions, and what is needed to move from proposal to active deployment.

Texas County sits above the Ogallala Aquifer, one of the largest and most stressed freshwater reserves in the Western Hemisphere. The aquifer's recharge rate in the region is measured in fractions of an inch per year. AI data center cooling systems can consume millions of gallons annually.

The communities of Guymon and Hooker, Oklahoma are directly exposed to both the economic opportunity and the resource risk that large-scale AI infrastructure would bring. The pilot is designed to test whether a governance protocol can enable communities to make informed, sovereign decisions about that tradeoff — rather than having the decision made for them by market forces or state-level permitting processes that don't account for local aquifer stress.

The pilot also serves as a test case for the EPA Safe Drinking Water Act §1431 petition pathway — a mechanism that municipalities can use to trigger federal oversight of local water contamination risk. The Green Code proposes this pathway as a replicable model for other jurisdictions facing similar pressure.

Not yet. The Green Code is a published governance framework and technical standard in active development. It does not currently hold certification from ISO, IEEE, NIST, or any national standards body.

The path toward formal recognition is staged: the Green Code Foundation (501c3, in incorporation) will publish the framework for comment, run the Texas County pilot to generate field validation data, and then submit GCTS-1 and the NBR methodology for independent peer review. Formal standards body submission is a Phase 3 objective — not a current claim.

Municipalities and operators who wish to pilot the framework today can do so under a voluntary adoption model. The Governance page explains how voluntary adoption works and what commitments it entails.

Municipalities have more authority than they typically use. Several concrete pathways exist:

• Procurement standards — cities that operate public utilities or purchase AI services can require GCTS-1 disclosure and NBR documentation as procurement conditions, independent of federal regulation
• Voluntary certification requirements — municipalities can adopt Green Code compliance as a condition of data center operating permits within their jurisdiction
• Municipal ordinance — cities can pass local water extraction ordinances that reference NBR thresholds and aquifer recharge data as trigger conditions for permit review
• EPA SDWA §1431 petitions — municipalities can petition the EPA under the Safe Drinking Water Act for emergency orders when contamination or depletion risk to public water sources is demonstrated
• Pilot enrollment — joining the Texas County pilot protocol as an observing or co-piloting jurisdiction generates the field data that supports eventual state-level regulation

The Governance page documents these implementation channels in detail.

Rights protections in The Green Code operate at three levels:

• Ecological sovereignty — the Kill-Switch mechanism gives communities (via the protocol) the ability to override compute demand with ecological reality. No contract can waive this.
• Community standing — the governance framework explicitly grants host communities standing to challenge audit findings, request re-review, and participate in revision processes for standards that affect them
• Transparency rights — GCTS-1 data is required to be publicly accessible, not held privately. Communities have the right to see what is being consumed from their commons.

These protections are currently PROPOSED. Their enforceability depends on the governance infrastructure (Green Code Foundation, accredited auditors, and eventually regulatory adoption) being built. The framework does not claim to have enforcement authority it does not yet possess.