SFC correctness example

Author: andreibesleaga

ADOPTION.md

@@ -347,7 +347,7 @@ never positioning against it.
 
 ## 8. Possible objections — each pre-empted in the draft text
 
-*(Revision **-04** is the latest — being submitted; schema label `"2.0"`. It renames the
+*(Revision **-04** is the latest — posted to the Datatracker, under ISE review; schema label `"2.0"`. It renames the
 requested suffix to `sustainability-data`, adds the optional `target-type` member, and
 applies a final audit round: a CORS recommendation (`Access-Control-Allow-Origin: *`) for
 browser clients, an all-or-none array rule for `target-type`, client tolerance for
@@ -380,9 +380,9 @@ for redirects, revalidation, and rate limiting. Every answer below reflects -04.
 
 ## 9. Readiness evidence (in this repository)
 
-- Draft at **draft-besleaga-sustainability-wellknown-04** — the latest revision, being
-  submitted; the prior -03 (posted to the Datatracker 2026-07-23) is under ISE review as
-  an Independent Submission. The series continues and replaces the
+- Draft at **draft-besleaga-sustainability-wellknown-04** — the latest revision, posted
+  to the Datatracker and under ISE review as an Independent Submission (the prior -03 was
+  posted 2026-07-23). The series continues and replaces the
   draft-besleaga-green-sustainability-wellknown -00–-05 series, with the Datatracker
   "Replaces" relationship recorded. Revisions build strict-clean (`xml2rfc --strict`,
   0 warnings; idnits **0 errors**); all references verified against authoritative sources,
@@ -399,13 +399,13 @@ for redirects, revalidation, and rate limiting. Every answer below reflects -04.
 - **Dual formal schemas** (JTD + CDDL) with two independent validation toolchains (the
   Python `jtd` package; the Ruby `cddl` gem) — 5 repository examples and 6 in-draft
   examples, each passing both validators.
-- A **production reference gateway** (TypeScript, a 120-test suite, all passing) with adapters for
+- A **production reference gateway** (TypeScript, a 128-test suite, all passing) with adapters for
   static/computed, Kepler/Prometheus, Climatiq, CO2.js and the carbon.txt hosted API
   (Green Web Foundation), Salesforce NZC, Microsoft Sustainability Manager, and Watershed —
   every adapter's output validates against both schemas, and the gateway enforces the
   draft's MUSTs that schemas cannot express (sci-score/functional-unit coupling, array
   ordering and uniformity, single-object response rules, deterministic noise).
-- A **reference client** (`consumer/`, TypeScript, a 127-test suite, all passing; also
+- A **reference client** (`consumer/`, TypeScript, a 148-test suite, all passing; also
   published to npm as
   `sustainability-wellknown-consumer`) that complements the publisher: it fetches,
   defensively validates, transforms (CSV/NDJSON/flatten/trend), and conformance-checks a
@@ -414,6 +414,24 @@ for redirects, revalidation, and rate limiting. Every answer below reflects -04.
   **two independent, interoperating implementations** (producer and consumer), not just one.
 - CI that rebuilds the draft and cross-validates generated documents.
 
+- **Independent research-framework symbiosis (a working correctness example).** The draft
+already serves as the disclosure layer for an independently defined, ACM accepted-to-be-published
+evaluation framework: Sustainability-First Consensus (SFC, DOI 10.1145/3809296) sets
+measurable sustainability criteria for distributed-ledger systems — an annualized energy
+cap, hardware-lifecycle responsibility, GHG Scope 2/3 carbon accountability, and
+CSRD/ESG-compatible auditability — and that last criterion is satisfied *directly* by
+publishing a conformant `/.well-known/sustainability-data` document, while the energy cap
+becomes mechanically checkable from the document's own members (an annual
+`reporting-period` with `energy-consumption` < 1 and `energy-unit: "GWh"`). The
+field-level mapping is worked out member-by-member in
+[sfc-compliance/SFC.md](sfc-compliance/SFC.md) and implemented by the reference
+publisher's adapters and unit normalization — evidence of two things reviewers care
+about: the schema is expressive enough to carry an external framework's requirements
+without any extension to the specification, and the draft functions as neutral
+infrastructure that independent research and evaluation frameworks (not just this
+author's) can build on. One RFC, many frameworks — the well-known document is the common
+disclosure surface they all lack today.
+
 ## 10. Process fit: the Independent Submission Stream
 
 - **Right stream (RFC 4846).** An individual, application-layer convention with no IETF WG
@@ -548,8 +566,8 @@ model of the specification:
    with IETF work"; process detail in §10).
 7. **Running code, both sides of the wire.** Two interoperating reference
    implementations (publisher with nine adapters; consumer/validator), dual
-   independent schema validators (JTD and CDDL), 247 automated tests (120 publisher +
-   127 consumer, all passing, verified 2026-07-26), real nginx/Apache deployment
+   independent schema validators (JTD and CDDL), 276 automated tests (128 publisher +
+   148 consumer, all passing, verified 2026-07-27), real nginx/Apache deployment
    configurations exercised in CI, and every example in the draft validated against
    both schemas on every commit (details in §9). Few well-known registrations arrive
    with this much implementation evidence.

README.md

@@ -61,7 +61,7 @@ Sustainability data about digital services exists today — inside enterprise ca
 
 * **Nothing in the IETF/IRTF space defines this.** No active or expired Internet-Draft or RFC specifies an application-layer sustainability disclosure format or well-known URI: the GREEN WG *excludes* carbon accounting and reporting by charter (its scope is network-device YANG management), and the adjacent expired drafts (sustainability-insights, green-metrics) were network-telemetry proposals with no disclosure endpoint. This draft is the only proposal of its kind on the Datatracker.
 * **The nearest neighbor is complementary, not competing.** carbon.txt (Green Web Foundation) is a discovery *index* — a TOML file of links to disclosure documents that, in its own maintainer's words, "contains no quantitative metrics." This proposal publishes the metrics themselves; the two specs cross-reference each other by design.
-* **First in the registry's history.** The IANA Well-Known URIs registry has never contained a sustainability, carbon, green, energy, or ESG entry, and this registration request (issue #95, June 2026) is the first sustainability-related request ever filed there — it creates the category's anchor rather than joining a crowd.
+* **First in the registry.** The IANA Well-Known URIs registry has never contained a sustainability, carbon, green, energy, or ESG entry, and no other sustainability-related request was found in the registry's public review queue — this registration request (issue #95, June 2026) creates the category's anchor rather than joining a crowd.
 * **Everything else is proprietary, regulated-filing-shaped, or advisory.** Enterprise carbon platforms (Salesforce, Microsoft, Watershed) expose per-vendor, authenticated APIs with incompatible shapes; regulatory formats (ESRS/XBRL filings, the DPP) are entity-level compliance documents, not web-discoverable machine endpoints; the W3C's Web Sustainability Guidelines are guidance, not a data format. None of them gives an arbitrary consumer a fetchable, validated document at a known URL.
 * **Most complete by construction.** No other effort combines, in one specification: fixed-location discovery *and* the quantitative metrics themselves; a declared reporting subject that spans organizations, sites, paths, devices, cloud tenants, and products; a mandatory methodology link plus optional signed attestations; dual formal schemas (CDDL + JTD); full security *and* privacy treatment (DoS caps, path-disclosure defense, fingerprinting noise, consumer hardening); explicit legacy compatibility and collision-proof extensibility; and two interoperating open-source implementations with 276 automated tests proving both sides of the wire. It arrives not as an idea but as a finished, running system.
 * **Future-compatible with everything — by design, not by promise.** The must-ignore rule plus open schemas mean any future metric (water use, hardware lifecycle, embodied carbon, whatever the next regulation demands) can be added by anyone, immediately, without touching the RFC or IANA: vendors extend today via collision-proof reverse-domain member names (`com.example.pue`), future revisions extend via the reserved undotted namespace, and the change-controlled `version` label records provenance without ever gating processing. The same tolerance rules that absorb the future also absorb the past — historical 1.x documents remain readable by current clients. Publishing the RFC freezes the text, not the ecosystem: nothing that matters is locked in, and no deployed client is ever stranded.
@@ -115,7 +115,7 @@ rfc-sustainability-wellknown/
 ├── publisher/               # Production publisher/gateway (TypeScript): adapters → conformant /.well-known/sustainability-data
 ├── consumer/                # Reference client (TypeScript): fetch, validate, transform a /.well-known/sustainability-data document
 ├── discovery/               # Product discovery: market scan, opportunity, problem, requirements, PRD, spec
-├── sfc-compliance/              # SFC framework compliance matrix (relationship to the ACM SFC framework)
+├── sfc-compliance/              # SFC framework alignment (relationship to the ACM SFC framework)
 └── ADOPTION.md              # The case for RFC/IANA adoption (business, technical, regulatory benefits)
 
 ```
@@ -324,7 +324,7 @@ same lifecycle against the current (schema-`2.0`-model) sources.
 ## Discovery & SFC compliance
 
 * [discovery/](discovery/) — product discovery suite (market scan, opportunity assessment, problem statement, requirements, PRD, technical spec) framing the gateway against the enterprise carbon-accounting ecosystem, plus [a deep-research companion to the draft](discovery/07-greenweb-carbontxt-integration.md) on the Green Web Foundation / carbon.txt / CO2.js integration.
-* [sfc-compliance/SFC.md](sfc-compliance/SFC.md) — additional optional appendix on how this draft and the publisher relate to the Sustainability-First Consensus (SFC) framework, with a field-level compliance matrix.
+* [sfc-compliance/SFC.md](sfc-compliance/SFC.md) — additional optional appendix on how this draft and the publisher relate to the Sustainability-First Consensus (SFC) framework, with a field-level mapping (article concept → draft member).
 
 
 ## CHANGELOG