HyGOAT

HyGOAT Public Evidence Methodology

What Green Hydrogen Public Evidence Can Establish

A source-led method for separating published facts, unresolved conflicts, and evidence that still requires project-owner confirmation.

Methodology reviewed 4 August 2026.

01 · Boundary

Public evidence mapping versus an assessment

The observatory maps what eligible public sources say about a bounded project profile. It records a fact, a source conflict, or the absence of sufficient public support. It does not inspect owner records, calculate a scheme outcome, or substitute for an indicative SCREEN assessment.

Practical reading rule

A missing public record is a boundary, not a verdict

“Not publicly evidenced” describes the reviewed public record within a stated window. It is not a statement that a project lacks the evidence privately or that an owner cannot supply it for a subsequent review.

02 · Source hierarchy

Source tiers

A

Official programme or government source

Primary public records such as a ministry project or programme table.

B

Official developer source

Company releases and documents, kept explicitly attributed and scope-specific.

C

Independent or institutional source

A credible third-party source that can add context but requires provenance review.

D

Context-only source

Secondary material used for discovery or context, not as sole support for a material project fact.

03 · Evidence states

Five public evidence states

Publicly evidenced

A cited eligible source supports the item within the review window.

Not publicly evidenced

The reviewed public sources do not sufficiently support the item; private evidence may still exist.

Conflicting public sources

Eligible sources materially differ and the claim remains unreconciled.

Review due

The source is outside the review window or may have been superseded.

Not applicable

The domain does not apply to the stated project pathway.

04 · GHCI lens

Nine GHCI-relevant public evidence domains

These domains organize the public profile so a reviewer can see where a source speaks directly, where sources conflict, and where owner-held material is still needed.

01

Project identity

What the source names and how the project boundary is described.

02

Project stage

Whether a source describes an award, construction, commissioning, or another stage.

03

Location and facility scope

The location and facility context directly stated by the source.

04

Production pathway

Public descriptions of the production route, technology, or conversion pathway.

05

Capacity scope

Published production and power values, preserving their source units and boundaries.

06

Renewable electricity

Public statements about the electricity source or renewable generation arrangement.

07

GHG method

Project-specific public information about emissions accounting or methodology.

08

Traceability and MRV

Public descriptions of monitoring, reporting, verification, and evidence custody.

09

Programme and end use

Public programme links, product descriptions, and stated end-use context.

05 · RFNBO overlay

Export intent is the gate for an RFNBO public lens

An RFNBO lens is included only when an Indian project has a sourced public statement of export intent. The statement remains attributed to its publisher; it does not establish an owner-held evidence file or an outcome under an export scheme.

Public pre-certification language is displayed as a source claim with its publisher and date. HyGOAT does not restate it as a HyGOAT conclusion, and profiles without sourced export intent do not receive an RFNBO domain section.

06 · Reconciliation rules

Conflict, staleness, and non-inference rules

  • Keep materially different source values as separate claims with their source scope and units.
  • Mark a domain as conflicting when eligible sources differ; do not average or silently reconcile it.
  • Mark a source as stale when it falls outside the review window or may have been superseded.
  • Use null or “not publicly evidenced” when the public record does not establish a value; do not infer location, technology, offtake, export intent, or owner operations.
  • Every displayed material fact carries a source ID, tier, publisher, access date, and method note in the internal data contract.

07 · Private boundary

What remains private and what SCREEN adds

Owner-held evidence

Project boundaries, contracts, meter and operating records, emissions calculations, traceability records, and other supporting material remain private until an owner chooses to share them through the appropriate review path.

Indicative SCREEN handoff

SCREEN gives an owner a project-specific workflow for adding private evidence and receiving an indicative GHCI or RFNBO result. The observatory does not create or populate that assessment record.

08 · Follow-up note

Request the concise methodology note

The public method is complete on this page. A founder-assisted follow-up can provide the source hierarchy, evidence-state model, and public/private boundary for internal circulation.

Request the concise methodology noteReceive the source hierarchy, evidence-state model, and public/private boundary for internal circulation.

Methodology disclaimer