Built from live registry counters and Isometric's own homepage claims this session, cross-checked against EWP's own proof-hash code state. Every claim below cites its source and a re-runnable command.
Isometric's registry homepage states plainly: "Explore the Registry to see the full provenance and data behind each certificate." Combined with a real live registry scale, 145,260 certificates issued, 39,535 retired, this is the concrete transparency bar we hold every registry review to. It is also the exact standard EWP's own on-chain proof isn't fully meeting yet (see finding 4 below, internal, not about Isometric).
Isometric describes its certification workflow as one where "AI agents work alongside human verifiers, reviewing every data point." The platform has raised $40M and lists Google, Boeing, Veolia, Anglo American, and Microsoft among its trusted users, genuine institutional traction for a company founded in 2022. Its Biochar Production and Storage protocol v1.0 was ICVCM/CCP-approved in August 2025 (confirmed via earlier public research), a real independent-standards seal of approval.
Isometric's stated evidence sources for certification include sensor data, video footage, field measurements, satellite imagery, LiDAR, manifests, and lab results. EWP's proof packet, a photo (content-hash + EXIF cross-checked), geofenced GPS, and a one-time actor signature (EOA ecrecover or fail-closed ERC-1271/6492 for contract wallets), is a genuinely narrower, cheaper evidence set built for sub-dollar single-task settlement, not project-scale certification. Neither substitutes for the other; the honest bridge is EWP field-capture data as one input among Isometric's named evidence types, never a replacement for lab results or sensor telemetry.
isometric.com ships a real robots.txt (200) and sitemap.xml (200, 13,036B), the files that tell search engines what to index. But llms.txt (the file AI assistants read first), ai.txt, and openapi.json all return a TRUE 404 (26,209B, byte-identical to a nonsense-path control). Separately, every /.well-known/* path (agent-card.json, ai-plugin.json, security.txt) returns a DIFFERENT, distinct 404 body (88 bytes), the identical Webflow-reserved-namespace behavior we documented earlier on Carbonfuture, a different Webflow-hosted target. Independently confirming the same platform quirk twice is itself a small useful data point: it's a Webflow-wide behavior, not something either company configured.
