Define a parcel-level sewer-capacity verification path
The corrected artifact identifies 13,346 included parcels that intersect a mapped capacity-constrained sewer-system area and need review against actual available capacity.
- Scale
- 13,346
- 8% of 171,778
- Geography
- Seattle
- citywide
- Constraint codes
- verification_sewer_capacity_unreviewed
Missing capability
A documented route from the mapped trigger to a current, parcel-level capacity or connection determination.
Current routes
- Mapped capacity-constrained sewer-system layer
- Side-sewer record and SPU capacity review
Next required artifact
An infrastructure evidence memo defining authoritative records, access constraints, update cadence, parcel matching, and the conditions that resolve the review flag.
Success: A parcel can move from unreviewed to a dated, source-linked sewer determination without treating absence of evidence as available capacity.
Source artifact: gap-atlas:backyard-cottage:v1
The mapped capacity constraint is an evidence need, not a sewer denial or a project failure. Counts can overlap with physical, financial, environmental, and other verification conditions. No utility approval or connection cost is inferred by this brief. Gap-dadu-v1.6 preserves the separation between capacity-constrained parcels and combined-sewer-overflow basins; those are different review triggers and must not be reported as one sewer-failure count.
Published 9/4/2026