Zones · Severity · CanonOne convention. One severity model. One record.
The registry uses a single zone vocabulary, a single severity ladder, and a versioned canon for documentation specs. The vocabulary is the same across visits, contractors, and years — so the record reads coherently for the life of the property.
Z-01 — Z-06. Canonical.
Every photo, reading, and finding pins to a zone. Z-03 means the same thing across visits, contractors, and years.
Front-perimeter zone. Photos, readings, and findings tied to the front of the crawlspace.
Right-perimeter zone. Side wall along the right elevation.
Rear-perimeter zone. Photos, readings, and findings tied to the rear of the crawlspace.
Left-perimeter zone. Side wall along the left elevation.
Interior structural zone. Girders, joists, piers, and central framing.
Access and utility zone. Hatches, vents, drainage exits, mechanical penetrations.
Monitor → Service → Priority → Safety → Review.
Every finding carries a level — and the level determines the route. Service-tier work auto-routes to verified trade members; Safety and Review tiers hold for admin sign-off.
Documented. No action this cycle. Re-check at scheduled interval.
Auto-route to verified trade members in service area. Routine scope.
Homeowner action required. Schedule before next maintenance cycle.
Active hazard. Held until reviewed. Electrical, gas, pest activity, IAQ.
Structural & safety-coded. Held for admin sign-off before routing.
Canon-linked. Versioned. Not negotiated per visit.
Specs reference the Crawl-Space Connect registry canon. Versioning sits on the canon, not on the visit — so a 2025 reading and a 2027 reading can be compared without renegotiating the spec.
Target relative humidity 48–55%. Quarterly RH logs are recorded against this target band; sustained deviation routes IAQ correction work.
Drainage runs, sump configurations, and grading notes reference the Crawl-Space Connect registry canon — versioned and not negotiated per visit.
Hatch dimensions, clearance, vapor and mechanical penetrations recorded against canonical access definitions, so subsequent visits read the same record.