Act one is not a mock: it is the shape of what EWP's settle→retire pipeline already does on Base mainnet. Act two is the one concept addition: a CRCF activity-category tag on the receipt, shown against the taxonomy Carbon Gap's own tracker already publishes.
A bounded work packet: log water-table depth at three fixed dip-wells before and after a drainage-ditch-blocking intervention, photograph the blocked ditch with GPS, count Sphagnum/sedge re-establishment along a fixed transect.
A human or agent claims the packet, does the fieldwork, and submits proof: photo, GPS coordinate, and the three dip-well readings plus the vegetation transect count, the exact evidence shape a peatland-rewetting MRV visit requires.
Proof approved; the packet settles on-chain against the EWP contract, wage paid, a computed ecological footprint carried alongside it.
The same gasless relay EWP already runs hourly on a gas-gated cron, no new integration for this packet type.
Everything in Act One runs today under our own generic standard_ref field (VCS-style). The concept below is one added cross-reference: pointing the same field at the CRCF activity category Carbon Gap's own tracker defines, so the receipt is legible against that taxonomy without changing anything about how it settles or retires.
{
"workId": 51203,
"standard": "peatland_rewetting_mrv_v1",
"standard_ref": "internal library only"
}
# no cross-reference to any EU regulatory
# taxonomy — a CRCF-interested reader has
# to already know our internal naming
{
"workId": 51203,
"standard": "peatland_rewetting_mrv_v1",
"standard_ref": {
"internal": "peatland_rewetting_mrv_v1",
"crcf_activity": "carbon-farming/peatland-organic-soil-rewetting",
"crcf_regulation": "EU 2024/3012",
"crcf_delegated_act_date": "2026-07-10"
}
}
# same receipt, same settlement, same retirement —
# now legible against the taxonomy Carbon Gap's
# own tracker.carbongap.org/policy/crcf/ defines
This concept field changes nothing about how the packet is funded, proved, settled, or retired: it only adds a citation. It does not claim CRCF-recognized-methodology status; that recognition process (opened 7 May 2026) is a separate, formal certification-scheme step this brief does not claim to have taken.
→ See the drafted schema and method-template files themselves in the Agent Kit
← Back to the hub