TECHNICAL REPORT / METHODOLOGY DIGITIZATION

Digitizing MECD v2.0

Record of an automated digitization run over the Gold Standard methodology for metered and measured energy cooking devices, from the published consultation draft to Guardian-importable schemas and a verified emission reduction calculation.

GOLD STANDARDGS4GG PAA M400-XXHEDERA GUARDIANCONSULTATION DRAFT

SOURCE OF FIGURESAll figures in this report are read from the run artefacts listed in section 01, including those recording a failed check. The report is regenerated whenever the run is repeated.

Methodology: METERED & MEASURED ENERGY COOKING DEVICES
Standard: Gold Standard
Source: MECD-v2.0-PAA.pdf, MECD-v2.0-VandV.pdf
Engine: dgz 0.1.0
Run: 2026-08-06 08:18 UTC
Wall clock: 2 seconds

01.0 / SCOPE AND RESULTS

Scope

The methodology comprises 75 pages and cites 39 external tools and guidance documents. The verification and validation requirements document was supplied alongside it. No calculation workbook has been published for this draft.

Inputs to the procedure are limited to the methodology document, the tool documents it cites, and the standard’s calculation workbook where one exists. Outputs are a parameter and equation registry, three Guardian schema workbooks, a reference calculation implementation, and the findings recorded below.

Results

28/28

Equations found and mapped

100%

22/22

Parameter blocks mapped

100%

28/46

Applicability clauses mapped

61%

309

Schema fields emitted

three workbooks

2/3

Fixtures agreeing

1 disagree

Open gaps for a human

typed and page-anchored

02.0 / PROCEDURE

Stages and checks

The procedure comprises 9 stages, of which 8 are followed by an automated check that halts the run on failure. Two stages use a language model and the remainder are deterministic. No output of a model-assisted stage is carried forward without passing a deterministic check.

Three points require review by a named methodology engineer before the policy may be published: disposition of the unresolved items in section 04, approval of the generated schemas, and final review of the assembled policy.

deterministic model-assisted review point

03.0 / TRACEABILITY

Source items and their disposition

Each item located in the source document is listed with the page on which it appears and whether a corresponding registry entry exists. Selecting a row displays the quoted source text.

Equations are matched on the equation number printed in the document. Parameters and applicability clauses are matched by token overlap against the registry entry, and the score for each decision is recorded in the row so that the matching may be independently recomputed. The threshold is 0.45.

unmatched only

Source item	Page	Disposition	Basis
Eq. 1	p.27	mapped	matched on printed equation number
Eq. 2	p.28	mapped	matched on printed equation number
Eq. 3	p.29	mapped	matched on printed equation number
Eq. 5	p.30	mapped	matched on printed equation number
Eq. 6	p.30	mapped	matched on printed equation number
Eq. 7	p.31	mapped	matched on printed equation number
Eq. 8	p.31	mapped	matched on printed equation number
Eq. 9	p.32	mapped	matched on printed equation number
Eq. 10	p.43	mapped	matched on printed equation number
Eq. 11	p.33	mapped	matched on printed equation number
Eq. 12	p.34	mapped	matched on printed equation number
Eq. 13	p.34	mapped	matched on printed equation number
Eq. 14	p.34	mapped	matched on printed equation number
Eq. 15	p.34	mapped	matched on printed equation number
Eq. 16	p.35	mapped	matched on printed equation number
Eq. 17	p.35	mapped	matched on printed equation number
Eq. 18	p.38	mapped	matched on printed equation number
Eq. 19	p.37	mapped	matched on printed equation number
Eq. 20	p.37	mapped	matched on printed equation number
Eq. 21	p.38	mapped	matched on printed equation number
Eq. 22	p.38	mapped	matched on printed equation number
Eq. 23	p.39	mapped	matched on printed equation number
Eq. 24	p.39	mapped	matched on printed equation number
Eq. 25	p.39	mapped	matched on printed equation number
Eq. 26	p.40	mapped	matched on printed equation number
Eq. 44	p.29	mapped	matched on printed equation number
Eq. 85	p.31	mapped	matched on printed equation number
Eq. 186	p.35	mapped	matched on printed equation number

04.0 / UNRESOLVED ITEMS

Items referred for review

18 items were not resolved automatically. Each is classified by type, carries a page reference to the source document, and remains open until dispositioned by a methodology engineer. Items in this register are not inferred or defaulted.

GAP-001highunenforced conditionp.8
Applicability clause not captured: a. Electric cookstoves (including induction, infrared, hot plates, rice cookers) using…
Under '3| SCOPE, APPLICABILITY, AND ENTRY INTO FORCE', page 7. Closest registry entry scored 0.23.
Open. Referred for methodology review.
GAP-002highunenforced conditionp.8
Applicability clause not captured: b. Electric Pressure Cookers (EPCs) equipped with smart metering.
Under '3| SCOPE, APPLICABILITY, AND ENTRY INTO FORCE', page 7. Closest registry entry scored 0.14.
Open. Referred for methodology review.
GAP-003highunenforced conditionp.8
Applicability clause not captured: c. Metered LPG, biogas, or bio-ethanol cookstoves (e.g., utilizing Pay-As-You-Go systems).
Under '3| SCOPE, APPLICABILITY, AND ENTRY INTO FORCE', page 7. Closest registry entry scored 0.40.
Open. Referred for methodology review.
GAP-004highunenforced conditionp.8
Applicability clause not captured: d. Stoves using processed fuels (e.g., pellets) where consumption is tracked via…
Under '3| SCOPE, APPLICABILITY, AND ENTRY INTO FORCE', page 7. Closest registry entry scored 0.36.
Open. Referred for methodology review.
GAP-005highunenforced conditionp.9
Applicability clause not captured: 3.2.2.1 | The activity is implemented by a developer and can include additional activity…
Under '3| SCOPE, APPLICABILITY, AND ENTRY INTO FORCE', page 8. Closest registry entry scored 0.33.
Open. Referred for methodology review.
GAP-006highunenforced conditionp.10
Applicability clause not captured: a. Replacing the unit with comparable or better technology; or
Under '3| SCOPE, APPLICABILITY, AND ENTRY INTO FORCE', page 9. Closest registry entry scored 0.40.
Open. Referred for methodology review.
GAP-007highunenforced conditionp.10
Applicability clause not captured: a. Explain the proposed method for distribution of the project stove in the PDD/VPA-DD…
Under '3| SCOPE, APPLICABILITY, AND ENTRY INTO FORCE', page 9. Closest registry entry scored 0.25.
Open. Referred for methodology review.
GAP-008highunenforced conditionp.10
Applicability clause not captured: b. Ensure project devices are identified with a unique identifier affixed to the device…
Under '3| SCOPE, APPLICABILITY, AND ENTRY INTO FORCE', page 9. Closest registry entry scored 0.20.
Open. Referred for methodology review.
GAP-009highunenforced conditionp.10
Applicability clause not captured: c. Clearly communicate its ownership rights and intention of claiming the emission…
Under '3| SCOPE, APPLICABILITY, AND ENTRY INTO FORCE', page 9. Closest registry entry scored 0.25.
Open. Referred for methodology review.
GAP-010highunenforced conditionp.10
Applicability clause not captured: d. Inform and notify the end-users that they cannot claim emission reductions from the…
Under '3| SCOPE, APPLICABILITY, AND ENTRY INTO FORCE', page 9. Closest registry entry scored 0.33.
Open. Referred for methodology review.
GAP-011highunenforced conditionp.11
Applicability clause not captured: b. Activities should employ household-level tagging or registry systems, and the VVB…
Under '3| SCOPE, APPLICABILITY, AND ENTRY INTO FORCE', page 10. Closest registry entry scored 0.23.
Open. Referred for methodology review.
GAP-012highunenforced conditionp.11
Applicability clause not captured: a. Option 1: Accounting Exclusion Documentation demonstrating that the jurisdictional…
Under '3| SCOPE, APPLICABILITY, AND ENTRY INTO FORCE', page 10. Closest registry entry scored 0.30.
Open. Referred for methodology review.
GAP-013highunenforced conditionp.11
Applicability clause not captured: b. Option 2: Attribution Agreement A formal statement, Nesting Agreement, or Letter of No…
Under '3| SCOPE, APPLICABILITY, AND ENTRY INTO FORCE', page 10. Closest registry entry scored 0.33.
Open. Referred for methodology review.
GAP-014highunenforced conditionp.11
Applicability clause not captured: 3.2.8.4 | To make claims on SDG 3.9.1 contributions, the activity developer may apply the…
Under '3| SCOPE, APPLICABILITY, AND ENTRY INTO FORCE', page 10. Closest registry entry scored 0.22.
Open. Referred for methodology review.
GAP-015highunenforced conditionp.12
Applicability clause not captured: 3.3.1 GS4GG Requirements: The activity shall adhere to the GS4GG…
Under '3| SCOPE, APPLICABILITY, AND ENTRY INTO FORCE', page 11. Closest registry entry scored 0.15.
Open. Referred for methodology review.
GAP-016highunenforced conditionp.12
Applicability clause not captured: 3.3.3 Health and Safety: Activities shall comply with health and safety requirements at…
Under '3| SCOPE, APPLICABILITY, AND ENTRY INTO FORCE', page 11. Closest registry entry scored 0.33.
Open. Referred for methodology review.
GAP-017highunenforced conditionp.12
Applicability clause not captured: 3.3.4 Contractual Obligation: The activity developer shall, by means of direct ownership…
Under '3| SCOPE, APPLICABILITY, AND ENTRY INTO FORCE', page 11. Closest registry entry scored 0.33.
Open. Referred for methodology review.
GAP-018highunenforced conditionp.12
Applicability clause not captured: 3.4.1 The date of entry into force is 30 days from the publication date of this…
Under '3| SCOPE, APPLICABILITY, AND ENTRY INTO FORCE', page 11. Closest registry entry scored 0.20.
Open. Referred for methodology review.

05.0 / CALCULATION VERIFICATION

Comparison of implementations

Each test fixture was evaluated by a reference implementation in Python and by the policy’s customLogicBlock, and the results compared field by field. The Python implementation is treated as the control. This comparison is material because customLogicBlock suppresses exceptions at runtime, so a calculation returning a non-finite value can be issued into a credential without raising an error.

Fixtures are drawn from the ATEC eCook programme, GS11817, covering the three quantification methods the methodology provides.

GS11817-VPA02-Y3-M1

pass

9 comparison(s) agree; two-way only, the standard supplied no expected values

Quantity	Published	Reference	Policy block	Agreement
Baseline, unadjusted	—	1,467.9622	1,467.9622	yes
After the consumption cap	—	1,467.9622	1,467.9622	yes
After the downward adjustment	—	1,467.9622	1,467.9622	yes
Business as usual	—	1,467.9622	1,467.9622	yes
Crediting baseline	—	1,467.9622	1,467.9622	yes
Activity emissions	—	224.1467	224.1467	yes
Leakage, total	—	50.3763	50.3763	yes
Emission reductions	—	1,193.4392	1,193.4392	yes

GS11817-VPA02-Y3

pass

9 comparison(s) agree; two-way only, the standard supplied no expected values

Quantity	Published	Reference	Policy block	Agreement
Baseline, unadjusted	—	1,488.2802	1,488.2802	yes
After the consumption cap	—	1,488.2802	1,488.2802	yes
After the downward adjustment	—	1,488.2802	1,488.2802	yes
Business as usual	—	1,488.2802	1,488.2802	yes
Crediting baseline	—	1,488.2802	1,488.2802	yes
Activity emissions	—	224.1467	224.1467	yes
Leakage, total	—	50.7827	50.7827	yes
Emission reductions	—	1,213.3509	1,213.3509	yes

GS11817-VPA02-Y3-M3

fail

3 of 10 fields disagree beyond 1e-06

Quantity	Published	Reference	Policy block	Agreement
Baseline, unadjusted	—	0	0	yes
After the consumption cap	—	0	0	yes
After the downward adjustment	—	0	0	yes
Business as usual	—	0	0	yes
Crediting baseline	—	0	0	yes
Activity emissions	—	224.4154	448.562	no
Leakage, total	—	25.5	25.5	yes
Emission reductions	—	-249.9154	-474.062	no

Agreement is assessed on relative difference to 1e-6. The published column is empty for all fixtures because no calculation workbook accompanies this consultation draft. These are therefore two-way comparisons between the reference implementation and the policy calculation block, and are recorded as such.

Divergence between the declared and executed forms of Eq. 1

The policy carries an audit mathBlock holding 35 equations in LaTeX, presented as the reviewable statement of the calculation. Equation 1 in that block weights each fuel by its proportion and divides by that fuel’s efficiency. The JavaScript that computes the issued quantity applies a further weighting by daily fuel usage and net calorific value.

Both forms were implemented and evaluated against the same fixture. The resulting difference in baseline emissions is given below.

Fixture	EF, executed form	EF, declared form	Difference	Effect on baseline
atec-gs11817-m1-electric	896.084	860.236	-4.00%	-58.7 tCO2e

The two forms differ by 4.00 percent on the emission factor, equivalent to 58.7 tCO2e of baseline emissions on this fixture. Resolution requires a determination by the standard as to which form is normative.

06.0 / DEFECT SCAN

Known defect classes

Each rule corresponds to a defect class previously identified during manual review of a deployed methodology. The scan covers the Gold Standard MECD v2.0 bundle and the Verra VM0047 UAT bundle. 16 findings were recorded, of which 3 are classified critical.

Findings are reported against the bundle as exported. They are not assertions about issued credits, and confirmation requires review of the affected calculation against the methodology text.

mecd-v2.0

blocks: 259
schemas: 175
findings: 14
critical: 3

vm0047

blocks: 248
schemas: 385
findings: 2
critical: 0

F001criticalmecd-v2.0mecd_er_formula_audit_math, mecd_monitoring_report_formula_audit_math
35 declarative formulas across 2 block(s) produce 0 outputs.
mecd_er_formula_audit_math (31 formulas); mecd_monitoring_report_formula_audit_math (4 formulas)
A formula block that declares equations but produces no outputs does not participate in the calculation. The reviewed statement and the executed calculation are then separate artefacts.
E001criticalmecd-v2.0mrv_device_gate
mrv_device_gate performs 10 divisions and never tests a result for finiteness before done().
1,589 chars, no isFinite/isNaN guard
customLogicBlock suppresses runtime exceptions. Without a finiteness check, a non-finite result is issued into the credential without error.
E001criticalmecd-v2.0admin_change_recipient_to_pp
admin_change_recipient_to_pp performs 3 divisions and never tests a result for finiteness before done().
1,972 chars, no isFinite/isNaN guard
customLogicBlock suppresses runtime exceptions. Without a finiteness check, a non-finite result is issued into the credential without error.
U001highmecd-v2.0175 schema files
1,112 numeric fields across 175 schemas, none carrying a unit.
Multiple Devices GS.annualFuelUsageByDevice_Pp_d_y; Multiple Devices GS.projectFuelNetCalorificValuePerTonne_NCVp_i; Multiple Devices GS.projectDeviceEnergyEfficiency; Multiple Devices GS.projectFuelEmissionFactorTco2PerTJ_EFp_i; Multiple Devices GS.fuel_share_j; Multiple Devices GS.ef_p_j_co2
A quantity without a declared unit cannot be validated, converted between systems, or compared against a published default.
L001highmecd-v2.07 customLogicBlock(s)
143,669 characters of JavaScript against 35 reviewable formulas.
declarative payload 24,437 chars
Where the declared formulas represent a small proportion of the executing code, review of those formulas covers a correspondingly small proportion of the calculation.
F002highmecd-v2.0mecd_er_formula_audit_math, mecd_monitoring_report_formula_audit_math
4 formula bodies appear in more than one place.
2x mecd_er_formula_audit_math:BEcrediting; 2x mecd_er_formula_audit_math:DeltaDAF; 2x mecd_er_formula_audit_math:LEtotal; 2x mecd_er_formula_audit_math:ERnet
A correction must be applied to each copy. An unamended copy diverges without raising an error.
S001highmecd-v2.0calculate_report_fields
calculate_report_fields assigns 1 field(s) that the output schema does not declare; additionalProperties is false.
er_y
Guardian sets additionalProperties to false on every schema. A document carrying an undeclared field is rejected at submission without a reported error.
S001highmecd-v2.0prepare_monitoring_report
prepare_monitoring_report assigns 1 field(s) that the output schema does not declare; additionalProperties is false.
er_y
Guardian sets additionalProperties to false on every schema. A document carrying an undeclared field is rejected at submission without a reported error.
U001highvm0047385 schema files
2,642 numeric fields across 385 schemas, none carrying a unit.
Data / Parameter: CWP-woody-AB,t.year; Data / Parameter: CWP-woody-AB,t.CWPwoodyABt; Data / Parameter: CWP-woody-AB,t.CWPwoodyABtZero; land use conversion.year_t; land use conversion.FPj,t; land use conversion.LMj_t
A quantity without a declared unit cannot be validated, converted between systems, or compared against a published default.
A001mediummecd-v2.0Emission Reduction Document GS
3 field keys share the label 'project emissions'.
project_emission_electricity, project_emission_fossil_fuel, project_emission_renewable_fuel
Two keys for one quantity divide the supporting evidence and allow the calculation to read a name the schema does not accept.
A001mediummecd-v2.0Emission Reduction Document GS
2 field keys share the label 'what are the final baseline emissions in year y?'.
BE_y, be_y
Two keys for one quantity divide the supporting evidence and allow the calculation to read a name the schema does not accept.
A001mediummecd-v2.0GS Validation Report
2 field keys share the label 'additional information (max ~500 words)'.
additional_information_max_500_words, additional_information_max_500_words_2
Two keys for one quantity divide the supporting evidence and allow the calculation to read a name the schema does not accept.
A001mediummecd-v2.0GS Monitoring Report
3 field keys share the label 'project emissions'.
project_emission_electricity, project_emission_fossil_fuel, project_emission_renewable_fuel
Two keys for one quantity divide the supporting evidence and allow the calculation to read a name the schema does not accept.
A001mediummecd-v2.0GS Monitoring Report
2 field keys share the label 'what are the final baseline emissions in year y?'.
BE_y, be_y
Two keys for one quantity divide the supporting evidence and allow the calculation to read a name the schema does not accept.
P001lowmecd-v2.0175 schemas
1,112 of 1,112 numeric fields cite no equation or section.
Without a reference to the methodology text, a reviewer cannot confirm that the field corresponds to the parameter the methodology defines.
P001lowvm0047385 schemas
2,642 of 2,642 numeric fields cite no equation or section.
Without a reference to the methodology text, a reviewer cannot confirm that the field corresponds to the parameter the methodology defines.

Rule set: 8 of 11 rules recorded a finding

Rule	Checks for	Severity	Fired
`U001`	Numeric field carries no unit	high	2
`C001`	One constant, two values	critical	0
`F001`	Declarative formula layer produces nothing	critical	1
`F002`	Formula definition duplicated across blocks	high	1
`F003`	Two renderings of the same equation disagree	critical	0
`L001`	Procedural logic dwarfs the declarative layer	high	1
`E001`	Calculation block can sign a non-finite number	critical	2
`S001`	Calculation writes a field the schema does not declare	high	2
`A001`	Two field keys for one concept	medium	5
`R001`	Result cannot be recomputed from its own record	critical	0
`P001`	Schema field has no normative reference	low	2

07.0 / GUARDIAN INTERFACE

Endpoints used by the procedure

Every step of the procedure corresponds to a Guardian REST endpoint, including schema workbook import and policy test execution, which are commonly carried out through the policy editor. All 6 probed routes responded on the instance used for this run.

The routes are wrapped in a command line interface, gdn, which holds credentials for a named instance and returns JSON. The same interface is used by the procedure and by an operator working by hand, so a step performed automatically and a step performed manually leave the same record.

Procedure step	Route	Command	Requires the editor
Import schema workbook	`POST /schemas/{topicId}/import/xlsx`	`gdn schema import`	no
Preview schema workbook	`POST /schemas/import/xlsx/preview`	`gdn schema preview`	no
Create draft policy	`POST /policies`	`gdn policy create`	no
Import policy bundle	`POST /policies/import/file`	`gdn policy import`	no
Validate policy config	`POST /policies/validate`	`gdn policy validate`	no
Switch to dry run	`PUT /policies/{id}/dry-run`	`gdn policy dry-run`	no
Create virtual user	`POST /policies/{id}/dry-run/user`	`gdn user create`	no
Read produced documents	`GET /policies/{id}/dry-run/artifacts`	`gdn policy artifacts`	no
Submit to a workflow block	`POST /policies/{id}/tag/{tag}/blocks`	`gdn block send`	no
Replay a recorded test	`POST /policies/{id}/test/{testId}/start`	`gdn test start`	no
Read test result	`GET /policies/{id}/test/{testId}/details`	`gdn test details`	no

08.0 / DOWNSTREAM USE

Submission against the digitized methodology

The generated schemas define what a project developer submits. Project documents and monitoring spreadsheets are mapped onto the following targets in the developer workspace, and the procedure described above is not visible to the developer.

MECD V2.0 Project Design · 255 fields · schemas/project-design.xlsx
MECD V2.0 Monitoring Report · 21 fields · schemas/monitoring-report.xlsx
MECD V2.0 Emission Reduction · 33 fields · schemas/emission-reduction.xlsx

3 worked examples are distributed with the package, allowing a first submission to be checked against known values.

Developer workspace →