Hardscaping Gardens · Fredy Montoya — contractor record to build (parked 2026-05-26)

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

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

New contractor for the pa.gf.cx /contractors/ substrate. Fredy Montoya, LLC trading as Hardscaping Gardens, contactable at artscapeoutdoorliving@gmail.com. Two successful jobs on record at PA. Resume when the current cycle (mDrive page) closes, or whenever Dan wants the next contractor entry built out.

Dan 2026-05-26: “I have another contractor, Hardscaping Gardens - Fredy Montoya artscapeoutdoorliving@gmail.com with 2 successful jobs. Is an LLC. Likely invoice in Harvest under PA”

What to build

A contractor record at ~/Code/home-projects/pa/contractors/hardscaping-gardens/ following the gold-standard structure from feedback_contractor_page_gold_standard.md (7 canonical elements, Junk Elves pattern).

What I have so far

What to do when resuming

1. Harvest pull — grep the Harvest invoice export (or ~/bin/harvest_* substrate tools) for invoices addressed to / from Fredy Montoya / Hardscaping Gardens / Artscape Outdoor Living. Lift the invoice numbers, dates, line items, totals.
2. Email substrate — search Mail.app + Fastmail for the artscapeoutdoorliving@gmail.com thread to capture context, before/after notes, photos.
3. Photo capture — any before/after job photos in iCloud / Desktop captures from those dates? Land them in the contractor record with SEO slugs (per feedback_seo_rewrite_for_dropped_images.md).
4. LLC verification — quick PA Dept of State business-entity search to confirm exact LLC name + standing.
5. Build the record — pa/contractors/hardscaping-gardens/index.html with the 7 gold-standard elements:
6. Identity header (kicker + name)
7. Verdict / recommendation banner
8. Summary stats (jobs, total spend, scope class, last engagement)
9. Contact + entity details
10. Job history (per-job rows: date, scope, amount, outcome, photos)
11. Cross-references (Harvest invoice URLs, before/after photos, related contractors)
12. Steward actions (any open items, future scope opportunities)

Cross-references

• feedback_contractor_page_gold_standard.md — the 7-element pattern to follow
• feedback_dropzone_pattern_shipped.md — add a dropzone on the record for future invoice/photo capture
• project_harvest_api_integration_parked.md — if Harvest API hookup is desired before pulling invoices
• feedback_pa_scope_icon_asset_library.md — assign the “contractors” scope icon to the kicker

Resume trigger

• mDrive cycle closes (current)
• Dan signals “next contractor record” or names this one explicitly
• A third job from Fredy is booked / quoted — prompts the record to anchor the history