Cyan Eclipse Greenwash

Vendor: Cyan Eclipse Technologies · Platforms: MCP over stdio

What it does

• Novel mechanism (SPEC §2.1, verbatim) — every sustainability claim an agent emits is bound to its source-data pointer at emission time; unbound claims are flagged in the message itself.
• The pointer limit (SPEC §11.2, verbatim, on every surface): A binding proves a source-data pointer existed and resolved at emission time — NOT that the claim is true, not that the source data supports the claim, and not that the source data is accurate, current, or complete. A flag states the absence of a pointer at emission — never that a flagged claim is false. Greenwash flags; it does not censor: flagged claims are emitted with their text unaltered.
• Decisive fixture F-G14 stands from the bench record — a harness-authored stream with harness-authored source entries verifies in a fresh subprocess from the pack + keys alone: bound claims resolve in the emission-time snapshot, both unbound claims carry in-message flags. A pointer attached after emission is a downgraded annotation (binding: false on its face), never a binding; annotations never convert a flag, never edit an emitted message, and are rejected by the §6.4 verifier as bindings. Sub-range packs are labelled verifiable: false / downgraded: true on their face (genesis-anchor reason) — exports that cannot be recomputed are labelled downgraded, never upgraded.
• Delta re-bench of v0.1.1 (wave4/rebench-greenwash.md): defects D-GW-1..4 all CLOSED on independent fixtures; conditions C1–C4 satisfied (C1/C3/C4 as implemented — claim_id uniqueness enforced at emission via the accepted coined code DUPLICATE_CLAIM_ID, LEDGER_APPEND_FAILED as a literal typed refusal, both binding signatures over record_hash; C2 via the labelling branch). No new defect found; builder suite 34/34 re-run by the bencher.
• Rollback fence: the v0.1 store is pure local file state anchored by its signed store head and SET anchors — any verdict caps at PASS-CONDITIONAL (local/fixture); an external anchor is required before any live or multi-party use.
• Counsel gate (SPEC §10) — named, unbuilt: binding, flagging, or certifying claims in real published content — marketing, product pages, regulatory filings, ESG reports — is out of v0.1, hard, until counsel clears that use (packet covers FTC Green Guides, SEC climate/ESG disclosure rules, EU green-claims regime; disclosure-duty and defamation/disparagement exposure of in-message flags; the legal meaning that may attach to the word "bound"). There is no dormant live path in v0.1.1 to flip: the startup fence refuses non-local endpoints, channel/publication integration strings, live source-data keys, and non-fixture modes by name.
• Signing is an HMAC fixture stand-in for Herald RS256, disclosed on every artifact face as signature_scheme; verification keys are pinned out-of-band by fixed key ref. Herald (signing pattern), Meter (metering grammar), Till (mandates — v0.1 fixtures run mandate-free), and Docket (pack shape) are consumed by grammar/reference only. Source-data stores are consumed as pointer targets, never assessed: resolution means only that the named entry exists in the cited snapshot.

Tools

Problems it addresses

• Agent-generated sustainability claims go out with no evidence discipline at all: the claim text is emitted, and whether any source data ever stood behind it is unknowable afterwards — the exact shape of greenwashing risk
• I need every sustainability claim bound to its source-data pointer at emission time — claim hash ↔ pointer ↔ emission time, hash-chained and counter-signed — and every unbound claim flagged in the message itself, adjacent to the claim, so no reader can miss that it carries no binding
• I need the honesty limits on the face of the product: a binding proves a pointer existed and resolved at emission — not that the claim is true; a flag states the absence of a pointer — never that the claim is false; and a pointer attached later is a downgraded annotation, never a backdated binding

Not tested

• Real published content — binding, flagging, or certifying claims in real marketing, product pages, regulatory filings, or ESG reports is SPEC §10 counsel-gated and UNBUILT (FTC Green Guides, SEC climate/ESG rules, EU green-claims regime; flag defamation/disparagement exposure); no real publication is touched in v0.1.1
• Claim truth — a binding proves a pointer existed and resolved at emission time, NOT that the claim is true, supported, accurate, current, or complete; source-data stores are consumed as pointer targets, never assessed
• Free-text claim detection in arbitrary prose — v0.1.1 handles structured claim objects in a fixture emission stream only; no prose detection is claimed or implied
• External anchoring / multi-party reliance — the pure local file store caps any verdict at PASS-CONDITIONAL (local/fixture); an external anchor is required before live or multi-party use
• Production key custody — signing is an HMAC fixture stand-in for Herald RS256 (fixture keys in keys/, gitignored, mode 600); a live phase would need real Herald signing and a re-bench