Resource catalog
Draft · protocol 3.0.0-draft
Resource types use the pattern trp.<name>. The schema version is carried in the schema_version field, not in the type string.
| Resource | Key relationships | Purpose |
|---|---|---|
Claim |
property, parties, jobs, estimates | Stable root record |
Property |
location, buildings, hazard context | Geographic and engineering context |
Job |
claim, contractor, activities | Restoration or rebuild work unit |
Estimate |
revisions, line items | Original scope and financial basis |
EstimateLine |
material requirements, work activities | Granular scope extraction |
MitigationEvent |
job, area, equipment, readings | Drying, cleaning and stabilization work, with moisture and equipment evidence |
MaterialRequirement |
function, quantity, constraints | What must be repaired or replaced |
Product |
SKU, supplier, environmental declaration | A specific material option |
EnvironmentalDeclaration |
PCR, module values, validity | EPD and LCA provenance |
WasteEvent |
material stream, weights, facility | Debris and disposition facts |
TransportEvent |
vehicle, route, cargo, fuel | Movement impacts |
EnergyEvent |
equipment, metering, energy | Site and equipment energy use |
ContentsEvent |
item, treatment, outcome | Contents repair, reuse, replacement, disposition |
Evidence |
linked resources, hash, custody | Audit trail |
Factor |
method, geography, vintage | Reproducible calculation inputs |
Scenario |
baseline, alternatives, impacts | Comparison context |
OptionAssessment |
cost, carbon, constraints, resilience | Decision support |
Decision |
approver, selected option, rationale | Human accountability |
ImpactResult |
domain, boundary, factors, uncertainty | Calculation outputs |
ClaimReport |
snapshots, rollups, exclusions | External exchange |
Schema coverage in this draft
Section titled “Schema coverage in this draft”Machine-readable JSON Schemas are published for a first subset: the common envelope, Claim, MitigationEvent, WasteEvent, MaterialRequirement, OptionAssessment and ClaimReport. The remaining resources are described here and will gain schemas in later drafts. See JSON Schemas.
Estimate-native model
Section titled “Estimate-native model”An Estimate has an ID, revision, source platform and document, currency, price region and date, loss type, scope status and one or more EstimateLine records. Each line retains the original description, code, quantity, unit, unit price, labor, material, equipment, tax, overhead and profit, room or location, action (remove, replace, repair, clean, install, salvage) and source confidence.
Never discard the original estimate text after automated extraction.
A MaterialRequirement is distinct from an EstimateLine. A line may imply several material layers and activities, and several lines may refer to one assembly. Flooring includes underlayment, adhesive and trim; drywall includes board, compound, tape and paint. Record an explicit mapping with evidence and uncertainty rather than assuming one-to-one.
Quantity takeoff and conversion
Section titled “Quantity takeoff and conversion”Store these as distinct values: original estimated quantity and unit, waste allowance, coverage and overlap assumptions, thickness, density, area-to-volume conversion, package size, installed quantity, ordered quantity and discarded quantity. 100 m2 of gypsum board does not imply a mass without thickness, product specification and density. Preserve the source of every assumption.