10-phase restructure of /dev-iq/our-process/ after Shane + Kelli meeting

What was done

The structural change

The Bailey process moved from 9 phases to 10. The bundled “Entitlements” phase was split — concept and pre-application moved to a trimmed Phase 3, and a new Phase 4 (Preliminary Plat → staff/PZ/council) was inserted. Old Phase 4 “Conceptual Design Services (CDS)” was renamed to “CDS — Construction Document Set” (matching what site.ts and the services pages already called it) and renumbered to Phase 5. All downstream phases shifted by +1.

Old #	New #	Phase
1	1	Site Identification & Feasibility
2	2	Land Control (Bailey N/A)
3	3	Planning / Entitlements (trimmed: concept + pre-app + feedback)
—	4	Preliminary Plat (PP) (NEW — staff/PZ/council)
4	5	CDS — Construction Document Set (renamed)
5	6	Submittal & Approvals (SAs)
6	7	Construction (Bailey N/A)
7	8	As-Builts / Record Drawings
8	9	Final Plat Routing & Recording
9	10	Vertical Development / Sale (Bailey N/A)

Bailey-delivered phases shift from [1, 3, 4, 5, 7, 8] (6 phases) to [1, 3, 4, 5, 6, 8, 9] (7 phases — gained Preliminary Plat as a discrete deliverable). Bailey-excluded phases shift from [2, 6, 9] to [2, 7, 10].

Editorial changes on /dev-iq/our-process/

• Hero title: “Nine phases.” → “Ten phases.”
• Hero sub now leads with developer-intent language per the saved project_primary_audience_developers memory.
• Phase 3 (Planning/Entitlements) reframed as concept + pre-application + agency feedback only.
• Phase 4 (Preliminary Plat) introduced with explicit outcomes: staff report, PZ recommendation, City Council decision (approval, denial, or continuance), DA if required. (“Approval / Denial” language softened to “decision” per Ryan’s direction.)
• Phase 5 (CDS) summary now names the coordination role: Bailey produces civil line work + product fit exhibit, and coordinates the landscape architect (planting per code) and surveyor (final plat) into one document set. Client redline rounds added.
• Phase 6 (SAs) clarified: legals + easements + final plat are surveyor deliverables coordinated by Bailey (per the saved project_legals_easements_ownership memory). Outcome: stamped + approved CDs.
• Phase 7 (Construction) split visually into “Bailey’s role” (CO reports, agency coordination, punch list) and “On the parcel (contractor):” (clearing, grading, utility install, road construction). Sharper boundary on engineer-of-record scope.
• Phase 8 (As-Builts) clarified: surveyor measures, Bailey draws record drawings, agency reviews for conformity. Punch list called out.
• Phase 9 (Final Plat Routing): kept the Idaho-specific agency timing matrix (Health, ACHD, County Surveyor, City, Plat Review, Treasurer, Recorder, Addressing). Added inspection / punch list final round.
• Phase 10 (Vertical) explicitly frames Bailey’s engagement as ending after Phase 9.

Schema enforcement updated

• src/data/site.ts processPhases array: 9 → 10 items.
• src/content/config.ts Zod literal union for project phases: 1|3|4|5|7|8 → 1|3|4|5|6|8|9. Build will now reject any project file using old numbering.
• src/components/ProcessCallout.astro: “9-phase” → “10-phase” in three places (doc comment, default heading, link text).
• HowTo JSON-LD on /dev-iq/our-process/ auto-regenerates with 10 HowToStep entries since it maps the phases array.

Site-wide propagation

• 6 project markdown files — phases array updated to new numbering.
• 23 services pages — ProcessCallout number: props renumbered mechanically per the mapping. Blanket renumber preferred over per-page Phase 3 split (concept-only entries can be added in a follow-up pass; current pages reference Phase 4 where they used to reference Phase 3).
• 5 FAQ files had phase-number references in body copy rewritten:
  • entitlements.md: “Phase 3” → “Phase 3 + Phase 4” (entitlement spans both now).
  • agency-coordination.md: Phase 3, 4, 5, 8 renumbered to 3+4, 5, 6, 9 with adjusted descriptions for the new Phase 3 (pre-app) vs Phase 4 (PP) distinction.
  • value-engineering.md: Phase 3, 4, 5 sections renumbered to Phases 3–4, 5, 6.
  • code-comprehensive-plan-research.md: “Phase 3” → “Phases 3–4”.
  • overall-project-management.md: “9-phase process” → “10-phase process”.
• master-planned-communities.md intentionally left alone — its “Phase 1 / Phase 3-6” references are about master-plan project phasing, not Bailey’s process phases. Different meaning.
• “9-phase” / “nine phases” string sweep across ~15 additional files (FaqArticle.astro default related-links, services/index.astro callout, dev-iq/index.astro summary, land-planning/index.astro body, feasibility-studies pages, rs4-nampa.astro, eagle-cap-compliance.astro, staying-current-with-ai.astro, all FAQ related-links arrays, homepage insight card, search.astro shortcut card, seo-plan/items.json).
• Memory updates:
  • project_bailey_scope.md: phases 2/6/9 → 2/7/10; delivered 1,3,4,5,7,8 → 1,3,4,5,6,8,9; added numbering-history paragraph + link to [[project_legals_easements_ownership]].
  • MEMORY.md index line updated.

Decisions made during execution

• Q6 (Phase 3 split per service page): blanket renumber. Service-page Phase 3 entries were renumbered to Phase 4 wholesale. Adding proper Phase 3 (concept-only) entries to each of the 16+ affected service pages is editorial work and was deferred to a follow-up pass.
• Q7 (devlog historical notes): leave devlogs as immutable historical record. Three old devlog entries reference the old phase numbering. No edits — devlog is an audit trail per CLAUDE.md.
• totalTime schema value kept at P3Y (defensible upper bound for Idaho multi-agency reality vs the textbook’s 18–30 month national average).

Why

Shane + Kelli meeting 2026-05-15. Their notes flagged two real problems on the existing page:

1. “CDS” was used for two different things on the same page — Phase 4 was labeled “Conceptual Design Services (CDS)” but the bullets described engineering construction drawings, and “Construction Drawings (CDs)” appeared as a different abbreviation two phases later.
2. Phase 3 (“Entitlements”) collapsed two distinct planning-board events — the feedback loop (concept + pre-app) and the public-hearing approval (preliminary plat → PZ → council) were bundled into one phase, hiding a meaningful conceptual distinction.

A fact-check against Johnson, Residential Land Development Practices (ASCE 3rd ed., 2008) confirmed both issues. The textbook treats Conceptual Design Planning (Ch. 8), Residential Subdivision Design (Ch. 9), and Project Approval Strategy (Ch. 11) as distinct chapters — Shane and Kelli’s split brings Bailey’s page back into alignment with that canonical structure.

Planning artifacts and the fact-check live in .tmp/0008_26_05_15_our_process/ (PLAN.md, FINDINGS.md, PATH_A_DIFF.md).

Files affected

Created:

• .tmp/0008_26_05_15_our_process/PLAN.md
• .tmp/0008_26_05_15_our_process/FINDINGS.md
• .tmp/0008_26_05_15_our_process/PATH_A_DIFF.md
• This devlog entry
• Memory: project_legals_easements_ownership.md (created earlier in session)

Modified (~60 files):

• src/data/site.ts (source of truth)
• src/content/config.ts (Zod schema)
• src/components/ProcessCallout.astro, src/components/FaqArticle.astro
• src/pages/dev-iq/our-process.astro (full phases array rewrite + hero)
• src/pages/index.astro, src/pages/search.astro
• src/pages/services/index.astro, src/pages/services/land-planning/index.astro, src/pages/services/civil-engineering/feasibility-studies.astro
• src/pages/dev-iq/index.astro, src/pages/dev-iq/faqs/feasibility-studies.astro
• src/pages/dev-iq/land-use-intelligence/rs4-nampa.astro, src/pages/dev-iq/land-use-intelligence/eagle-cap-compliance.astro, src/pages/dev-iq/ai-iq/staying-current-with-ai.astro
• 23 services sub-pages under /services/civil-engineering/, /services/commercial-industrial-site-design/, /services/land-planning/, /services/master-planned-communities/, /services/multifamily-site-design/
• 6 project markdown files in src/content/projects/
• 8 FAQ markdown files in src/content/faqs/ (related-link sweep + 5 with body copy)
• src/content/seo-plan/items.json (one HowTo item title)
• ~/.claude/.../memory/project_bailey_scope.md, ~/.claude/.../memory/MEMORY.md

Deleted: none.

Open follow-ups

1. Per-page Phase 3 expansion on service pages — the 16 service pages whose old Phase 3 entries got blanket-renumbered to Phase 4 (PP) could benefit from a new Phase 3 (concept) entry describing the pre-app work. Defer until next services-page review pass.
2. Verify the build is clean before deploy.
3. AI visibility re-test — per the feedback_visibility_retest_cadence memory, wait ~3 weeks post-deploy before re-running the 10 visibility queries; crawlers need that long to surface the new schema.