SINE Strategy Wiki

Pathfinder Network Vision Paper (WBCSD/PACT, June 2022)

15 min read

Source: sources/standards/2026-10-29-pact-network-vision-paper/2026-10-29-pact-network-vision-paper.md (Markdown twin of 2026-10-29-pact-network-vision-paper.pdf, retrieved 2026-10-29 from wbcsd.github.io/tr/websitedocs/PACT_network_vision_paper.pdf, supplied by Martin Pompéry). Title page: “Pathfinder Network — Enabling standardized emissions data exchange.” Copyright line: © WBCSD, June 2022. 11 pages plus covers.

⚠ Conversion note. Marker rendered the Figure 5 table as a garbled word-salad paragraph (“The Network can accommodate the | full diversity …”). Do not cite that paragraph. Its real content was recovered by rendering page 9 of the PDF as an image and is reproduced in full below. Figures 1, 2 and 4 survive only as extracted JPEGs in the Markdown twin’s directory; 1 and 4 were read natively and are transcribed here. Figure 2 was not transcribed.

What kind of document this is

The founding vision paper for the Pathfinder Network — written while the Network did not yet exist. Its own status language is unambiguous: the Pathfinder Framework’s “second version [is] in development”, the Pathfinder Network is “(in development)”, and the FAQ says plainly “The Pathfinder Network is still under development.” It describes an intended system and the process for building it.

That makes it the earliest primary PACT source in this wiki and, more usefully, a baseline document: everything later — the February 2023 Technical Specifications v2, Methodology v3 (2025), the ICC Landscape Review (2026) — can be read as outcome against stated intent. See Pathfinder Network § What was promised in 2022.

SINE’s formal role

The back matter lists PACT as “hosted by WBCSD and supported by its knowledge partner, McKinsey Sustainability, as well as its technology partner, SINE Foundation.” The collaborator page (p. 2) repeats the two designations under the headings Technology partner (SINE wordmark) and Knowledge partner (McKinsey Sustainability).

This is the first primary source in the wiki giving SINE a named role title inside PACT rather than the wiki’s own paraphrase (“co-built with”). The document also carries SINE’s own 2022 self-description verbatim — “a tech for good organization founded by progressive entrepreneurs, academic experts, and software engineers” — which matches the SINE Foundation page’s framing.

Core collaborators (p. 2)

38 organizations are named as “core collaborators in the Partnership for Carbon Transparency (PACT) and the development of the Pathfinder Network”, by logo only:

Aptar · Arkema · BASF · Bayer · BMW Group · Bühler · Catena-X · CDP · Chevron · CircularTree · Clariant · CLG Europe · ClimateWorks Foundation · Colgate · Continental · Dow · Eaton · EcoVadis · Givaudan · Green x Digital Consortium · IBM · iPoint · Microsoft · OCP · Open Footprint Forum (The Open Group) · P&G · RMI · Roche · Sage · SAP · Shell · Siemens · Sika · Solvay · Takeda · Together for Sustainability · Unilever · Yara.

Two entries matter beyond the roster:

  • Catena-X is a core collaborator here, in June 2022. The wiki files Catena-X under market-competitors as a “parallel carbon/data-exchange effort in the same landscape.” Both are true and the sequence is the point — see that page’s new note.
  • Green x Digital Consortium is the Japanese counterpart initiative (under JEITA). Its presence in PACT’s 2022 founding roster is the earliest PACT–Japan link in the wiki, and it sits next to the Hitachi engagement and the CVP strand without any documented connection between them. ⟨Open: no source in the wiki says whether Green x Digital’s PACT involvement persisted.⟩

The problem statement (pp. 3–4)

Three causes of the Scope 3 data deficit, in the paper’s own headings:

  1. Data accounting — “room for interpretation and inconsistency in existing methods and standards.” ISO, GHG Protocol, PCRs and PEF “further leave room for interpretation”; general-purpose emission-factor databases fill the primary-data gap with averages that “are often not specific enough.”
  2. Data access and exchange — “Product-level data is often competitively relevant and highly confidential. Organizations that strive for transparency therefore face a data-sharing dilemma.” Plus: no visibility beyond tier 1, and ERP systems that cannot exchange emissions data across company boundaries, “resulting in high transaction costs for manual efforts, in the form of surveys or spreadsheets.”
  3. Ecosystem alignment — many parallel efforts, “lacking […] integration and harmonization.”

The interoperability argument is made with the email analogy: without it, “organizations can only access each other’s data if they use the same technology solution. This would be akin to only being able to send emails to people with the same email provider — unimaginable.”

⟨The diagnosis is the one the Data Commons whitepaper makes two months earlier in general form; this is its sector-specific statement, and the two share the confidentiality-vs-transparency framing almost word for word.⟩

The vision sentence, decomposed (Figure 1, p. 5)

“An open and global network of interoperable solutions for the secure peer-to-peer exchange of accurate, primary and verified product emissions data — across all industries and value chains”

Figure 1 defines each term. Transcribed:

TermDefinition given
Open and global”Data exchange is based on open guidelines and technical specifications that can be used by all organizations globally”
Interoperable”Data is exchanged via different solutions that ‘speak the same language’, meaning data formats can be read by any solution”
Secure”Data cannot be accessed or manipulated by third parties during exchange and only the minimum necessary amount of data is exchanged”
Peer-to-peer”Data is shared directly between two companies in a decentralized manner, with no need for a central intermediary”
Accurate”Data is calculated consistently in accordance with the Pathfinder Framework”
Primary”Data is specific to the company exchanging it, rather than based on industry averages or proxies”
Verified”Data is verified either automatically or by third parties, e.g., to check calculation methodology”
Product data”Data has the highest possible granularity and relates to the individual products of a company”
All industries”Data relating to any product can be exchanged — independent of industry or value chain”

Note what “secure” is defined as: transport confidentiality plus data minimisation. Not cryptographic proof. See § Confidentiality without cryptography below.

The architectural exclusion (p. 6)

The paper draws an explicit boundary around what the Network is not:

“The Pathfinder Network should not be thought of as a technology solution, but rather as a necessary piece of infrastructure and a prerequisite for emissions transparency […] In contrast to individual technology solutions or platforms — which, for example, can support organizations with their emissions data management, including storage, calculation, visualization and analysis — the Pathfinder Network cannot be used to calculate a carbon footprint or to store any individual footprint data.”

And, from the FAQ: “Is PACT setting technological standards? No. We are defining the specifications, guidelines and profiles necessary for the resolution of the transparency challenge.” Plus the minimal-infrastructure clause: “PACT may in the future operate minimal network infrastructure strictly necessary for and limited to fulfilling the essential objectives of our mission.”

The sentence that follows the exclusion is the origin of the phrase the wiki uses throughout: “our aim is to create the ‘internet for emissions data’ — the common nexus for all organizations to seamlessly connect, exchange and derive insights from emissions data.” (The 2025 iLEAP framing on the SINE page renders it “Internet of Emissions Data”; this is the earlier form.)

⟨Inference, load-bearing: no storage, no calculation, no central intermediary, not a standard is a strong and deliberate architectural commitment, made before a line of the Network was built. The ledger architecture the ICC proposes in 2026 requires conserved quantities that persist and reconcile — i.e. precisely the stateful layer PACT ruled out of its own scope here. The ICC’s Table 4 charge therefore does not describe a shortfall against PACT’s own goals; it describes a different system. That makes open task 1 sharper: SINE’s response is not “we will add that”, it is either a defence of the boundary or a decision to move it.⟩

Five design principles (pp. 6–7)

Verbatim headings, with the load-bearing clause of each:

  1. Data confidentiality and sovereignty — “Each organization is the sole owner of and exercises sovereignty over its data, with full data control over who has access to any data point. […] The technology is accompanied and supported by a governance framework that further strengthens the data sovereignty of each stakeholder.”
  2. Data quality and integrity — data “cannot be manipulated by third parties and protects organizations from any possible back-tracing of product-specific information. Agreed rules and fraud prevention measures, on a technical as well as on a governance level, are put in place.”
  3. Scalability and diversity — global scale across sizes and product categories; “Open-source technology is provided to connect the separate technology solutions, significantly decreasing the transaction costs for new joiners.”
  4. Equality — “a network of, by and for its users. All participating organizations have equal rights independent of size or type.”
  5. Openness — open to every business adhering to its standards and rules; “Technological, financial, knowledge and other barriers are kept to a minimum. […] Open-source software is the go-to where possible.”

⟨Note for Data Commons: the PACT page maps “PACT’s own values” onto the Data Commons triad Reciprocity/Security/Openness. The primary source has five principles, and the mapping is a three-to-five compression made by the whitepaper, not by PACT. Equality ↦ Reciprocity and Openness ↦ Openness are clean; Security absorbs both principles 1 and 2, and Scalability and diversity has no counterpart in the triad at all.⟩

Core functionalities — and what was already specified (Figure 4, p. 8)

Five named pillars, “which will be extended as the Network evolves”: identity management, authentication mechanism, plausibility and error-checking mechanism, auditing mechanism, security and fraud prevention mechanism.

Their descriptions are ambitious. Authentication “helps attribute PCFs to an issuing organization and provides the ability to trace, track and audit these and their underlying accounting methodologies.” Plausibility checking “reduces additional burden, such as manual checking or validation of alignment with the Pathfinder Framework, enabling full trust in the data once part of the Network.” Auditing: “ex ante and ex post verification processes can be performed through software or by accredited auditors in order to establish full transparency on and trust in the application of carbon accounting methodology and correctness of data.”

Figure 4 then says how much of this existed. It maps the basic user journey to the functionalities, with a legend marking which were “Already specified by PACT” (green) as of June 2022. Transcribed:

User-journey stepFunctionalitiesAlready specified?
Logs into solution— “implemented in tech solutions – specification not in scope of Network”n/a
Joins the Pathfinder NetworkIdentity management; Security and fraud preventionno
Requests and receives PCF from suppliersData exchange mechanism; Identity management; Authenticationonly data exchange
Assesses quality of received PCFPlausibility and error-checking; Identity managementno
Calculates own PCF— “implemented in tech solutions – specification not in scope of Network”n/a
Exchanges PCF with customersData exchange mechanism; Identity management; Authenticationonly data exchange
Add-on features: identifies whether received PCF was auditedAuditing mechanismno

Two things are visible here and nowhere else in the wiki:

  1. Exactly one of the six mechanisms was specified in June 2022 — the data exchange mechanism. The five trust mechanisms were intent.
  2. Auditing is filed under “Add-on features”, below the core user journey, by PACT’s own layout.

⟨Inference, the main finding of this source: the ICC Review’s 2026 charge sheet — exchanges data rather than accountable quantities, no verified transfer — lands on the boxes that were already white in PACT’s own 2022 figure. Methodology v3 (2025) still carries verification as a two-horizon roadmap, not a shipped mechanism (see PACT Data Quality & Verification). So across roughly three and a half years, the one mechanism that was specified at vision time is the one that shipped and scaled, and the trust mechanisms around it did not. That is not drift and it is not an external critic’s framing: it is PACT’s own plan, with the delivery pattern visible against it. Whether the cause is difficulty, demand or governance is not answerable from this source.⟩

What the Tech Specs did with the other five ⟨answered 2026-11-06⟩

The question this section left open — what the exchange layer would do with the five unspecified mechanisms — is answered in writing by Technical Specifications v2.2.0 (April 2024), §7.2.1, which declares out of scope: footprint calculation; authentication and access management (“the act of deciding and setting which product footprint may be accessed by each data recipient”); credentials management (generation, exchange, rotation, revocation); and logging (“access logs and audit trails”). Plausibility and error-checking appear nowhere in the document. What is specified is the transport half of authentication — how a recipient obtains a Bearer token — and nothing about what that token entitles it to.

⟨Inference: the white boxes of Figure 4 became scope exclusions. Conforming host systems are called solutions and “add further functionality on top of this standard”, so the trust mechanisms were not abandoned — they were pushed down to implementers, where they are by construction not interoperable. Auditing’s placement under “Add-on features” in 2022 is the same decision made two years earlier in layout rather than in prose.⟩

Confidentiality without cryptography

The document states the confidentiality requirement at full strength — the “data-sharing dilemma”, “sole owner […] full data control over who has access to any data point”, and “protects organizations from any possible back-tracing of product-specific information.”

The instruments it reaches for: a governance framework, legal frameworks (“technological mechanisms and legal frameworks must be put in place”), identity management and fraud prevention, and data minimisation (Figure 1: “only the minimum necessary amount of data is exchanged”). The words cryptography, encryption, zero-knowledge, multi-party computation and proof do not occur in the document.

⟨Inference: this is a fourth instance of the pattern tracked in open task 19 — a community that states the confidentiality requirement precisely and never reaches for the cryptographic instrument. It is the most uncomfortable of the four, because SINE is the named technology partner on the document, and because SINE’s own first project (March 2021, Cozero) was a secure-MPC carbon benchmarking tool. Whichever reading of item 19 is right, this instance cannot be explained by “the instrument was outside the community’s vocabulary” — it was inside the technology partner’s.⟩

Contradiction, held open. The 2022 Data Commons whitepaper, via the PACT page, describes the Pathfinder Network as protecting data sovereignty through a “decentralized approach + strong encryption”. This document, two months later and from PACT itself, describes the same protection as governance plus minimisation and does not mention encryption. Both are in sources/. Not resolved here.

Development approach (Figure 5, p. 9)

“A community-led standardization process”, the community “consisting of users and technology solution providers”. Six approach/benefit pairs — recovered from the page image after the conversion failure noted above:

ApproachBenefit
Bottom-up — “The Network will grow in scope based on the definition and agile execution of specific use-cases with a clear business value for users.”Diversity of solutions and users — accommodates “the full diversity of users and technology solutions at very high speed.”
User driven — “designed and implemented with the continuous input and feedback of users.”Applicability and usability — for all relevant use-cases; “Stakeholders have a clear incentive to participate.”
Multi-stakeholder — “leverages the demands and expertise of all relevant stakeholders from the beginning.”Synergies and buy-in — “duplication and redundancy are avoided. Buy-in can be created, serving as a basis to quickly scale the Network.”
Open-source — “All knowledge and technical specifications will be publicly available.”Operationality — providers “can operatively use relevant specifications and have access to the Network.”
Iterative — “developed in an iterative cycle of building, testing and refining.”Best-in-class — “Quick updates and improvements allow for a best-in-class standards approach.”
Lean standardization — “standardized approaches with a focus on interoperability, creating viable solutions that can be scaled.”Speed — “The process can move fast and run in parallel to other regulatory standards.”

⟨Inference: “lean standardization […] run in parallel to other regulatory standards” is the explicit strategic bet — move faster than the regulator and be there when the regulation arrives. Read against product-level carbon regulation and against the ICC’s 2026 move to define the accounting layer above PACT, the bet looks half-won: PACT arrived first at the exchange layer and is credited with it, and a differently-governed coalition is now setting the pace one layer up.⟩

The third pillar: Pathfinder Ecosystem

The FAQ names three focus areas, not two: “Together the Pathfinder Framework, Pathfinder Network and Pathfinder Ecosystem provide the necessary foundations for the creation of emissions transparency.” The Ecosystem is described functionally rather than defined — “close exchange with a broad range of global industry-specific initiatives, disclosure organizations, standard-setting bodies and regulators”, “creating exchange, alignment and integration between these stakeholders.”

⟨The wiki has tracked Framework and Network and has no page or section for the Ecosystem pillar. Noted on the PACT page; not made into its own page, because this source defines it only by activity. Whether the term survives into later PACT material is a question for the Methodology v2 and Tech Specs v2.2 ingests that follow this one.⟩ ⟨2026-11-06: it does not survive into the Tech Specs — “ecosystem” occurs zero times in the 2,421 lines of v2.2.0. The third pillar has no technical expression.⟩

Cross-references

Graph View

Backlinks