Boundaries and perspectives

Draft · protocol 3.0.0-draft

A number without a boundary is not a result. Every TRP report declares what it includes, from whose point of view, and how overlaps are handled.

Data domains

TRP organizes claim data into domains. These are data domains, not additive accounting scopes.

Domain	Covers
Mitigation	Drying, cleaning, stabilization, moisture and equipment evidence
Waste and debris	Measured mass, stream composition, disposition, transport, facility evidence
Contents	Repair, reuse, replacement and disposition of damaged contents
Equipment and operations	Drying equipment, generators, temporary power, fleet and site energy
Reconstruction materials	Installed product and material impacts, with lifecycle modules declared
Contractor operations	Organization-level emissions and allocations to a claim

The same diesel fuel or electricity may appear in a contractor’s organizational inventory and in a job-level footprint. Aggregation MUST deduplicate shared activity and apply a declared perspective.

Reporting perspectives

A TRP report MUST state its reporting_perspective:

• claim_physical_footprint
• contractor_corporate_inventory
• insurer_value_chain_estimate
• property_owner_inventory
• portfolio_operational_metrics
• scenario_comparison

The perspective determines ownership, allocation, attribution, exclusions and category mapping. A contractor’s direct emissions do not automatically become an insurer’s value-chain category without analyzing the transaction and the applicable reporting rules.

Lifecycle modules

Where environmental impacts are reported, TRP uses recognized EN 15978 and EN 15804 lifecycle-module concepts, with source-specific limitations.

Module	Meaning in TRP	Initial treatment
A1 to A3	Raw material supply, transport to manufacturing, manufacturing	Primary comparison boundary for materials
A4	Transport to construction site	Optional, location and route specific
A5	Construction and installation	Optional, measured or modeled waste and energy
B1 to B7	Use-stage impacts, maintenance, repair, replacement, operational energy and water	Scenario-only unless supported by a declared methodology
C1 to C4	Deconstruction, transport, processing, disposal	Waste and end-of-life evidence and modeling
D	Potential benefits and loads beyond the system boundary	Reported separately, never silently netted against A to C

An environmental declaration’s declared unit, product category rules, program operator, geography, modules and product scope must be captured. Two values with different rules, boundaries, declared units or functions can be misleading even when the numerical units match. Environmental declarations are not a universal commodity dataset.

Baseline and scenario definitions

For each decision, retain: baseline_option_id, candidate_option_ids, selected_option_id, baseline_basis, functional_unit, functional_equivalence_constraints, scope_boundary, service_life_assumptions, uncertainty, approval and decision_timestamp.

A baseline is not automatically the insurer’s original estimate. It may be a documented incumbent specification or a verified installed product. Baselines MUST be frozen and versioned when comparisons are issued.

Impact accounting (conceptual)

• Activity impact = quantity in compatible unit × factor in matching denominator unit, with optional conversion and uncertainty.
• Scenario impact = sum of in-boundary, non-duplicated activity impacts plus explicitly defined process effects.
• Scenario difference = baseline scenario impact minus candidate scenario impact, for identical functional scope and lifecycle boundaries.
• Cost difference = candidate total installed cost minus baseline total installed cost, with currency, date, tax, labor, freight and exclusions declared.

Avoided emissions are a comparative scenario result, not a negative physical-emissions line item. Never automatically net scenario savings against reported gross emissions. Do not conflate biogenic carbon storage, recycling substitution credits, Module D benefits, actual process emissions or carbon-credit retirements.

Deduplication checks

Implementations SHOULD detect:

• duplicate activities and duplicate facility tickets;
• the same material counted as demolition waste and as replacement material without a separate lifecycle boundary;
• shared equipment electricity counted in both a utility record and an equipment reading;
• fleet fuel counted both in an organizational inventory and as job transport;
• transport already included in a supplier’s cradle-to-gate factor;
• recycling credits counted in both waste treatment and material substitution.