Test protocol 03 · Chimney service

Does the record survive from one flue to the next season?

The benchmark covers property hierarchy, multi-flue history, condition photos, report retrieval, repair estimates, signatures, and seasonal recurrence without making inspection-code claims.

Chimney inspector documenting the interior of a masonry flue — Illustrative field context

Canonical scenario

The two-flue inspection

One synthetic property with two flues and two connected appliances
Eight condition photographs and one cleaning service
One repair estimate and customer-facing report
An annual reminder retrieved by a different technician next season

Evidence captured

What earns a claim

Hierarchy: Property, flue, and appliance records without destructive overwrites.
Inspection: Mobile fields, photographs, annotations, findings, and signatures.
Report: Synthetic customer PDF quality and attachment retrieval.
Recurrence: Reminder creation, history visibility, and next-season handoff.

Publication queue

Evidence first. Article second.

Each item remains queued until its synthetic job, source packet, and deterministic checks pass.

01
Flue-history and report benchmark
QUEUED
02
Multi-flue data-architecture comparison
QUEUED
03
Annual-cycle retrieval test
QUEUED