# Latest PZT extraction audit

Source: `14-10-2026 PZT.dwg`, SHA-256 `486f322f87a902b22c6a3e99baea92e0ac5aa4a10a8e8fc4aacbb1ab2bbbc30c`. Only this drawing was read. Re-run with `python3 walkthrough/scripts/extract-site.py` (LibreDWG `dwgread`), or pass `--decoded` pointing at its JSON output. No Python dependencies.

Selected Model plot frame: handle 1763488; site INSERT 1713177, BLOCK 1713109. The block name contains an earlier working date but its entities belong to the latest supplied DWG, including October driveway/island edits 1786103/1786114/1786381. Four placements reference this same block: 1713177, 1773632, 1782002, 1784207. Selecting one avoids rendering duplicate plots. The other copies share exactly the same underlying site geometry.

Boundary: handle 1761878, 3002.176 m², about 48.85 × 61.61 m. Conversion is centimetres to metres, corroborated by matching the house's 7.40m garage exterior and full 14.35 × 19.25m footprint. House alignment uses all ten exterior finish corners of polyline 1752308, maximum residual 0.010000 m: two PZT indentation corners lie at x2.91m versus architectural finish x2.90m. The original coordinates are retained and the garage anchor matches exactly. The house masonry corner corresponds to block origin [32384.717149334, -4576.294515719]. World CAD placement and rotation are preserved in source metadata, while the exported scene is aligned with the architectural house plan.

15 surfaces were extracted from actual source hatch rings and two documented waste pads. HATCH 1757997 retains its two paving holes; HATCH 1752384 contains two disjoint terrace exteriors and a separate grass hole, assigned by containment. Complete duplicate hatch 1786103 replaces coincident 1786102. Incomplete duplicate outlines 1757991/1757994 are covered by 1757995. Clockwise HATCH arc angles are decoded with their clockwise convention; matching ARC 1786107 confirms the 1.59m-radius island corner. Arcs are tessellated to under 1mm chord error.

Legend material evidence: 1759041 / annotation 1759027 identifies green index 85 as biologically active area; 1759069 / 1759026 identifies index 36 as paved pedestrian/vehicle paths; 1759042 / 1759068 identifies index 41 as terrace (paving/composite). No tree, shrub, bed, court, greenhouse, or conceptual garden data is included. Existing obsolete unfilled stepping outlines inside the replaced driveway are not reintroduced as separate objects.

Visible infrastructure: well circle 1762242 (radius .60m), three near-circular .30m sanitary covers 1762122/1762123/1762127. Underground installation rectangles and their protection radii are not modelled as structures. The SVG contains geometry only and no title-block personal data.

Vertical limits: the source labels establish house ±0.00 = 93.30m, terraces -0.02, intermediate steps -0.17 and adjacent ground -0.32. Surface polygons are horizontal at these simplified levels; driveway and terrain grades (1%/5%) and garage driveway transition are not reconstructed. Two intermediate exterior steps are reconstructed at -0.17m: the entry strip bounded by LINE1752376/1756238 (x0.91–1.41m, z7.20–13.65m; label1756267), and the rear/side perimeter bounded by1756237/1752302/1756235/1756236 (labels1758466/1758458). Terrace hatches are subdivided along these drawn edges to avoid obscuring the lower treads. Source spot levels and this limitation remain explicit in JSON. Grass is a disclosed rendering convention for unspecified planting. The plan SVG is a trace of exported geometry, not an exhaustive raw-DWG overlay.