Product Sustainability

Governed by the integration rule document. Core scope: PEF/OEF, PEFCR/OEFSR and EF datasets; ESPR/Digital Product Passport; Batteries Regulation; and CBAM. PPWR and product-specific ecodesign measures remain second-tier until a material integration decision is recorded.

2026-W38 authority register

ID	Finding	Authority / disposition
PS-01	Commission transitional EF dataset guidance of 14 July 2026 governs how limited EF-compliant dataset availability should be handled during the 2025–2028 transition.	OFFICIAL_GUIDANCE; bounded method/data-policy input, not a universal product-footprint law.
PS-02	The guidance preserves valid PEFCR/OEFSR rules and, where its fallback conditions apply, prefers EF-compliant data, then ILCD-EL alternatives with documentation; where neither exists, omission/limitation must remain explicit.	DATASET_CHANGE, CALCULATION_CHANGE, EVIDENCE_CHANGE; integrate through existing Method Profile/factor-resolution governance.
PS-03	ORBIT remains an EU-funded research/implementation project rather than normative authority.	RESEARCH; WATCH.
PS-04	ESPR/DPP, Batteries and CBAM remain distinct product-regulatory profiles with separate category, method, evidence, date and delivery rules.	LEGAL_ACT families; no cross-method equivalence inferred.

Canonical PEF/LCA reconciliation

The current canonical PEF / LCA Implementation Roadmap already establishes:

• governed Method Profiles;
• factor/dataset registries and rights;
• explainable factor resolution;
• supplier-data escalation;
• uncertainty and sensitivity;
• replayable CalculationRuns and FootprintResults;
• EPU Product Graph as product-system substrate;
• TrustGate/verifier integration;
• weekly research-to-architecture governance.

It also states that a footprint result is a replayable evidence graph rather than merely a number.

Therefore the July 2026 Commission guidance does not create a new PEF architecture. It is a concrete authority input to the existing method/dataset-resolution contract.

Required roadmap integration

The PEF/LCA roadmap should be reviewed for an explicit regulatory fallback policy containing:

• applicable method profile;
• PEFCR/OEFSR presence and version;
• selected dataset and version;
• dataset compliance class;
• fallback level;
• geographic/temporal/technology fit;
• rights/licence eligibility;
• selection justification;
• omission record where applicable;
• comparability/disclaimer requirement;
• source authority/version;
• supersession watch and recalculation trigger.

This should be represented as part of the existing Method Profile / Factor Resolution Receipt family rather than a WSI-specific receipt object.

Disposition: CANONICAL_REVIEW_REQUIRED; unregistered candidate: method and dataset resolution receipts is absorbed into the existing PEF/LCA roadmap and should not become a duplicate Need.

Product-regulatory profile decisions

ESPR / Digital Product Passport

Maintain product-category and applicable-act resolution separately from generic passport infrastructure. Passport identity, content requirements, access rights, carrier/identifier and delivery adapter must remain separable. Product-specific delegated acts can change content without redefining canonical product identity.

Disposition: WATCH / AWAIT_TECHNICAL_SPEC until the relevant product-specific act/schema is concrete.

Batteries

Battery passport and carbon-footprint rules must remain separate governed obligations. Guidance can help field preparation but cannot replace the binding Regulation and applicable secondary acts. Do not copy one battery passport date across all carbon-footprint obligations.

Disposition: CANONICAL_REVIEW_REQUIRED for existing Carbon Passport/DPP architecture when a supported battery category is selected.

CBAM

CBAM requires its own CN/product scope, installation/importer evidence, calculation method, actual/default-value logic, verification and reporting/submission profile. PEF/LCA data may be reusable input evidence but a PEF result is not automatically a CBAM embedded-emissions declaration.

Disposition: PROPOSED_DELTA only where current CBAM profile is missing; inspect canonical CBAM assets before Need creation.

Acceptance criteria

Scenario	Expected behavior
Valid PEFCR/OEFSR governs the study	Generic transitional fallback cannot override the category/sector rule.
Eligible EF dataset is unavailable and ILCD-EL alternative is used	Preserve fallback class, authority, justification and downstream comparability limitations.
Neither permitted dataset class exists	Preserve omission/limitation; never fabricate a factor.
Better dataset later becomes available	Identify affected calculations for governed recalculation review while retaining original replay.
Dataset is technically suitable but rights prohibit intended use	Factor/dataset resolver must fail or constrain use according to canonical rights policy.
Same product has PEF, battery-footprint and CBAM results	Preserve separate method profiles, functional units/boundaries and verification states.
DPP field becomes mandatory for one product category	Update that category profile without making it universally mandatory.

Cross-regime collisions

X-04 — carbon-method conflation. Corporate GHG, PEF, Batteries and CBAM can share source data while retaining separate calculation authority.

X-05 — footprint/claim. Send result and limitations to Claims & Market Communication; do not auto-authorise wording.

X-07 — passport rights. Reuse canonical Pergamum Pulse rights and EPU permissions before exposing supplier evidence through a public passport.

Canonical specs reviewed / requiring follow-up

Reviewed:

• PEF / LCA Implementation Roadmap v0.2.1;
• EPU Supplier Contribution Architecture;
• Pergamum Pulse rights vocabulary.

Follow-up:

• exact PEF roadmap section for 2026-W38 regulatory fallback insertion;
• Carbon Passport / DPP canonical specs;
• current CBAM implementation assets;
• supported battery-category contracts;
• PPWR promotion criteria.

No PEF/LCA roadmap file was modified by this WSI cycle because the governing rule requires identifying canonical impacts before casually editing other canonical specifications.

Weekly cohort history

Cohort	Intelligence retained	Integration decision
2026-W36	July EF transitional guidance	Candidate factor/dataset fallback governance.
2026-W37	ORBIT research signal	WATCH; research creates no normative method delta.
2026-W38	Product domain expanded to ESPR/DPP, Batteries, CBAM	Integrated 2026-09-15: canonical PEF roadmap already owns the required architecture; July guidance becomes a bounded roadmap/policy review, not a new subsystem or Hecate Need.

What changed in ZAYAZ? No product calculation or dataset was changed. The integration cycle confirmed that the existing PEF/LCA roadmap already contains the right architecture; the new regulatory action is to feed the July EF fallback rules into that governed method/dataset policy and keep product-specific regimes as separate profiles.

2026-W39 Architecture Integration

Authority recheck

No new PEF/OEF methodology release was identified that supersedes the Commission's 14 July 2026 transitional EF dataset guidance. The current rule remains:

valid PEFCR/OEFSR → follow that rule

otherwise, where the guidance applies:

EF-compliant dataset → ILCD-EL-compliant dataset → documented omission.

The Commission also preserves the comparability disclaimer condition where non-EF-compliant data exceed the stated contribution threshold to the overall score.

Architecture decision

This remains a policy/profile update inside the existing PEF/LCA roadmap, not a new WSI architecture.

W39 therefore leaves unregistered candidate: method and dataset resolution receipts closed as a duplicate candidate. The next legitimate action is a canonical PEF/LCA roadmap update through its own Friday/Saturday governance cycle or a separately reviewed regulatory-policy insertion.

ORBIT remains RESEARCH / WATCH. ESPR/DPP, Batteries and CBAM remain separate product-regulatory profiles.

Cross-regime effect from EmpCo

Because EmpCo applies on 27 September, Product Sustainability should expose method limitations, fallback status, uncertainty, verification and comparability constraints in a machine-consumable way to the Claims domain. A valid footprint result must not be simplified into claim authority.

Acceptance criteria

• PEF result produced with fallback data exposes fallback/disclaimer state to downstream claim review.
• Product claims cannot suppress dataset limitations recorded in the footprint receipt.
• A future EF 4.0 release can supersede the policy prospectively without rewriting historical calculations.

W39 history

What changed in ZAYAZ? No PEF calculation architecture changed. The main new integration consequence is stronger downstream propagation of footprint limitations into the imminent EmpCo claims-governance path.

W39 source/evidence register

All entries below were retrieved/rechecked 2026-09-22.

Finding	Authoritative source	Locator
Transitional EF dataset policy	European Commission DG ENV — Transitional guidance on limited availability of EF-compliant datasets	Published 14.07.2026; valid PEFCR/OEFSR precedence; EF-compliant → ILCD-EL → documented omission hierarchy; >10% non-EF overall-score disclaimer condition.
EF method baseline	European Commission — Environmental Footprint Methods	Commission EF methods landing page and current method news inventory.