pa.gf.cx /well-water/ — promote to top-level category (parked 2026-05-26)

DARE.CO.UK · PARKED SKETCH · 2026-05-26

Mirrored from ~/.claude/.../memory/parked_sketch_pa_gfcx_well_water_top_level_category_2026-05-26.md. This is a design sketch parked for future build — read for context, not as a current deliverable.

Dan signalled that “well-water” should be a top-level category on pa.gf.cx (sibling to /contractors/, /technology/, /home-insurance/, etc), not a fact field on individual contractor pages. New Hope sits on a private well, so the whole well-water stack (well pump, pressure tank, softener, filtration, water-quality testing, contractors, test reports, equipment inventory) earns its own substrate. Resume when next prompted, or when a third well-related touchpoint (job, vendor, equipment swap) lands.

Dan 2026-05-26: “https://pa.gf.cx/ well-water is top level category” — preceded by “Well water should cover water-service and I have 2 names of well companies, to audit/review”.

What to build

~/Code/home-projects/pa/well-water/ — new top-level category folder with index.html landing + structured sub-substrate. Sibling to existing top-level folders.

Structure sketch

pa/well-water/
├── index.html                          (landing: well system overview, sub-system links, contractor links)
├── equipment/                          (current installed kit + history)
│   ├── well-pump/
│   ├── pressure-tank/
│   ├── softener/
│   ├── filtration/
│   └── test-reports/                   (water-quality reports by date)
├── contractors/                        (well-water vendors — could cross-ref from /contractors/ instead)
│   ├── certified-water-services/       (Patrick Raimondo — already built at /contractors/certified-water-services/)
│   ├── <well-company-A>/               (one of the 2 audit/review names, TBD)
│   └── <well-company-B>/               (other audit/review name, TBD)
└── issues/                             (open + closed water-system problems)
    └── _bulk-source/                   (dropzone landing for invoices, photos, reports)

Open architectural question — vendor placement

When /well-water/ exists AND /contractors/ already has contractor records, where does Certified Water Services actually live?

Three options:

Default recommendation: Option A. Contractors live in /contractors/; scope categories (/well-water/, /landscaping/, /electrical/) link OUT to the contractor records. Categories are views into the contractor substrate, not duplicate homes.

The 2 well companies for audit/review

Dan mentioned 2 well-company names pending audit/review. Once provided, build either: - 2 individual contractor records under /contractors/<slug>/ with YELLOW (pre-engagement) signal — the right move if either looks like a future candidate for actual work. - A shortlist page at /contractors/well-water-shortlist/ (matching the existing garden-maintenance-shortlist, basement-waterproofing-shortlist, etc. pattern) — the right move if both are “comparison only” and one is to be selected from.

Pre-engagement signal block, BBB lookup, website HEAD-check, PA Dept of State entity verification per the standard vetting checklist. Pattern: feedback_contractor_page_gold_standard.md.

Sub-substrate to seed at landing time

When the well-water category lands, the landing page should include:

1. System overview — what’s installed (well-pump model, pressure-tank size, softener kit, filter sizes, RO stages) with photos
2. Service cadence — softener salt refill, filter change, water test (typical: annual bacterial + every 3 years comprehensive)
3. Last service date + cost
4. Active vendor — Certified Water Services (cross-link)
5. Test-report archive — water-quality reports chronologically with delta notes
6. Open issues — anything currently degraded or being investigated
7. EOD-style horizon per major component — well-pump 15-25 yrs, pressure tank 5-10 yrs, softener 10-15 yrs (per the new tech-record EOD pattern, applied to well-water equipment)
8. Dropzone — pa-well-water context for invoices, photos, test reports

What to do when resuming

1. Get the 2 well-company names from Dan — gates the contractor-record builds.
2. Inventory the installed well-water kit — Dan would need to either photograph the equipment (well-pump nameplate, pressure-tank, softener brand/model, filter housings) OR confirm specs from existing service invoices.
3. Pull water-test reports — anything Dan has from prior testing, drop into equipment/test-reports/.
4. Scaffold the category — index.html landing + dropzone + cross-link to Certified Water Services contractor page.
5. Apply the EOD + stewardship-posture pattern per feedback_tech_record_eod_and_stewardship_posture.md to each major component, treating the well system like any other piece of long-lived household infrastructure.

Cross-references

• feedback_contractor_page_gold_standard.md — for the well-company vendor records when names land
• feedback_tech_record_eod_and_stewardship_posture.md — apply to well-pump, pressure tank, softener, filtration units
• feedback_asset_value_estimation_axis.md — every tangible asset gets a value estimate; well-pump replacement cost is non-trivial
• feedback_dropzone_pattern_shipped.md — primitives for the category’s invoice + report drops
• parked_sketch_water_service_patrick_raimondo_contractor_record_2026-05-26.md — Certified Water Services parked → SHIPPED at /contractors/certified-water-services/ on 2026-05-26
• feedback_last_touched_freshness_pattern.md — landing page footer should date itself

Resume trigger

• Dan provides the 2 well-company names
• Or: a third well-water touchpoint surfaces (job, equipment swap, test report)
• Or: Dan signals “build the well-water category now”