What Changed, Newest First

His screenshot showed the browser tab reading "About David Whann, Jr."; the page title is now "About Us | Homeowner Insights", keeping the site-wide suffix. One line in site-data, rebuilt, QA clean, pushed, and verified live on the domain. Deploy note for the routine: wrangler 4.140.0 aimed at a wrong account id until `CLOUDFLARE_ACCOUNT_ID=d9c7f4f1f0b5427fc4fbe64a5e66abfc` was set; pin that env var in every `wrangler pages deploy` from now on.

His report, filed to the roadmap's search-visibility item. The live sitemap (26 URLs, www canonical) and the robots.txt pointer were verified serving beforehand. Recommended next on his question about other platforms: Bing Webmaster Tools via its import-from-GSC path (covers Bing, Yahoo, DuckDuckGo, and AI assistants); the foreign-market consoles (Yandex, Baidu, Naver) ruled out for a Florida-only firm; Google Business Profile flagged as the bigger local-visibility win but gated on the HI-4 mailing-address decision.

His design verbatim: three italic subheaders group the form into The Engagement (What do you need? and Deadline side-by-side at top), Contact Information (First Name and Last Name replacing the single full-name field, then Your Role beside a new optional Company (If Applicable) field, then Email beside Phone), and Your Property (Association or Property Name full-width, Address beside City, Property Type beside Number of Units). The What do you need? dropdown becomes his six options, splitting both study types into New, From Scratch and Update From Prior Report variants plus Consulting Services and Help Me Choose. The Deadline example moved from help text below the box to a placeholder inside it ("Example: Desired Completion by December 1st"). The Worker's field whitelist gained the three new names, reordered so the email reads in the form's order, and was redeployed; a test submission delivered ok:true. The contact form is untouched. Browser-verified on desktop and mobile (subheaders collapse cleanly to one column). Also established: `wrangler pages deploy` from the CLI now handles the redeploy to David's Pages project, replacing the browser zip upload. 27 pages, QA clean; verified live on the domain.

His words: "I don't want to move forward with the registrar transfer at this time." The domain's registration stays at Hostinger (paid through 2027-05-14, auto-renew on) while DNS and hosting live on his Cloudflare account; the item is recorded as declined, not pending, in the go-live decision record and the infra reference, to be revisited only on his word. The go-live record also gained a resolutions block (forms armed and verified, analytics enabled, transfer declined), and the stale-reference sweep caught the pre-launch leftovers: the company-overview domain row (was "string and registrar to confirm") and four ROADMAP items (GitHub/Cloudflare connect, HI-3 domain, HI-15 go-live, form worker) now record their completion dates, plus HI-13's resolution-by-removal. On David's word ("walk me through the domain verification now"), the domain was added to his Resend account and verified the same evening. Division of labor per the DNS-change gate: the Resend side (add domain, read off the records, click verify, watch it turn green) ran in his logged-in Chrome; the four Cloudflare records were David's own clicks from a written walkthrough (DKIM TXT at resend._domainkey, CNAMEs rsend/send to forge.rmta.net set to DNS Only, and a new v=DMARC1 p=none TXT at _dmarc, none existing before). All four verified character-perfect on public DNS before the verify click; Resend flipped to Verified in about 15 minutes. Resend's Enable Receiving toggle deliberately stays OFF and no MX records were touched: inbound mail remains Google Workspace's. Auto-configure (which would have granted Resend standing access to his Cloudflare account) was declined in favor of manual records. FROM_ADDRESS updated in wrangler.toml, the worker redeployed, and a live test submission returned ok:true from the new sender. Also this session: Cloudflare Web Analytics enabled by David one-click on the Pages project and verified end-to-end (beacon auto-injected on the live pages, test visit accepted with a 204). Remaining optional infra: the ~$10 registrar transfer, and git-connecting his Pages project.

David test-submitted the proposal form on the live site and saw the something-went-wrong fallback while the email still arrived; investigation showed his submission fell in the broken-key window (the message was accurate then), and a fresh real-browser submission of the live contact form succeeded cleanly (fields reset, success path). What his report DID surface: both form pages still carried a static "Draft form. Delivery is wired and waiting on the intake endpoint..." note. Both notes are removed at his direction (the renderer now prints a note only when one is set), with the endpoints verified intact. The something-went-wrong fallback message stays: it is the correct behavior for genuine failures and includes his email and phone as the backup path. 27 pages, QA clean.

The test submission returned ok:true and delivered to David's inbox via his Worker and Resend, and the honeypot check passed (fake success to the bot, nothing sent). Getting there took three rounds of secret-entry debugging, all diagnosed from worker logs and Resend error fingerprints: wrangler's hidden prompt on Windows stores a single character from a paste (Resend's edge answers a malformed one-character token with a bare 400), and a second attempt stored a stale clipboard's revoked key (proper 401 "API key is invalid"); the working method, now in the form-handler README, is piping the key from a scratch file. The first key, which appeared on-screen during a mis-paste, was rotated out. With this, everything on the launch stack works: live domain, indexable pages, working forms with attachments and spam protection. Remaining nice-to-haves: Resend domain verification (emails currently from onboarding@resend.dev), analytics activation, the optional registrar transfer.

David created the Resend account and key himself, then ran the wrangler login/secret/deploy sequence in his terminal (one Windows execution-policy hiccup solved with npx.cmd; the two deploy warnings were benign defaults). The worker `hi-form-handler` runs on HIS Cloudflare account (verified via wrangler whoami) at hi-form-handler.dark-resonance-c8cc.workers.dev with the Resend key stored as an encrypted secret, TO_ADDRESS david@homeownerinsightsllc.com, and both live origins allowed (CORS verified for apex and www). `site.formEndpoint` now carries that URL, ending two and a half months of draft-mode forms; an end-to-end test submission follows. Mail sends from Resend's shared onboarding@resend.dev sender until the domain is verified in Resend (the documented later upgrade). 27 pages, QA clean.

His instruction verbatim: "Remove the search engine blocks so the website can go fully live." The noindex meta is gone from every page, robots.txt flips from Disallow-all to Allow-all with a Sitemap pointer, and the real `sitemap.xml` (26 public pages on the www canonical) replaces `sitemap-preview.xml`. qa.mjs's draft guard is inverted: it now FAILS the build if a noindex ever reappears on the live site. The go-live decision record is filed at `Facts/decisions/2026-09-24-go-live.md` and HI-15 is checked off, closing the question list's launch item after two and a half months. Pushed to the repo and redeployed to David's Cloudflare account, then verified on the live domain. The site that began as a draft prototype on 2026-07-10 is public at homeownerinsightsllc.com. Top remaining post-launch item, flagged in the decision record: the intake forms still need their Resend endpoint armed before they deliver email. 27 pages, QA clean.

His ruling after the domain went live ("this website is active and no longer a draft form"): the footer's "Draft website system for review. Nothing on this prototype is approved for publication." line is removed site-wide, leaving the legal name alone; like the banner, it renders only when `site.footerDraftNote` is set. He also completed the www custom-domain attach (Cloudflare verifying). Verified live earlier today: the apex domain serves the new site from his account, banner-free, with noindex still on. The remaining go-live gates are now ONLY the invisible ones: noindex, blocking robots.txt, and the preview sitemap, awaiting his formal word. 27 pages, QA clean; pushed and redeployed to his account.

He completed the custom-domain attach himself, putting homeownerinsightsllc.com on his Pages project, and instructed removing the "Draft for David's review" banner as part of the cutover. The bar now renders only when `site.draftBanner` is set and the field is emptied (restore = refill it), verified gone from all 27 pages. Deliberately NOT removed, pending his word: the noindex/robots/sitemap go-live gates (search engines stay blocked; HI-15's formal switch), and the footer's visible "Draft website system for review" legal line, flagged to him as the remaining draft-marked text a visitor can see. Pushed to DJ's auto-deploying preview AND redeployed as a fresh direct-upload to David's own project, since the domain serves that snapshot.

On his explicit authorization, working in his logged-in Chrome: verified the Cloudflare account at his link is his own (David@homeownerinsightsllc.com); created the Pages project `homeowner-insights` and direct-uploaded the current 27-page build (first upload hit the Windows-zip backslash bug, homepage-only; rebuilt with bsdtar and redeployed; all routes then verified 200 at homeowner-insights.pages.dev with draft gates intact); added the zone `homeownerinsightsllc.com` (Free plan) with Hostinger's records imported 1:1, preserving his Google Workspace email MX/TXT and revealing the domain currently serves an old Wix page; and switched the nameservers at Hostinger from Wix's to lara/watson.ns.cloudflare.com (Hostinger confirmed). No money spent; the registrar transfer was NOT initiated (would charge a renewal year; connect-first is the required prerequisite anyway, and the transfer can follow on his word). The final step, attaching homeownerinsightsllc.com and www as custom domains on the Pages project, was stopped by the session's DNS-change permission gate and handed to David as two clicks, with the consequence spelled out: attaching replaces the Wix records, so the real domain would show the draft-gated site until his go-live word strips the gates. Infra facts recorded in `Facts/reference-index/published-pages.md`, including that the direct-upload copy is a snapshot that does not auto-update on push. DJ's git-connected hi-site-preview deployment continues unchanged as the canonical auto-deploying preview.

His instruction: the four linked PDF samples are not a Homeowner Insights, LLC product (they carried the national practice's branding, the HI-13 flag since 2026-07-10), so they came off /resources/samples/ and moved intact to `Archive/2026-09-24-retired-sample-pdfs/`; HI-13 is checked off as resolved-by-removal. The How to Read a Sample section came off with them, taking the [VERIFY] band that was the LAST inline review flag on the site: the built site now renders zero inline flags anywhere. In their place, his note verbatim ("We are working on a sample for your review online, although you can reach out if you'd like specific demonstrations of our product and dynamic *what if* file.", the italics via a new opt-in `rich` option on split sections) with a "Contact Us to Request a Demo/Sample" button below it (new opt-in split `cta`). Two pieces of Claude wording flagged for his review: the hero lede's second sentence ("Reach out for a demonstration and see the deliverable up close.") and the meta description, both of which had promised downloadable samples. The old PDF URLs 404. 27 pages, QA clean.

Site Content now reads "without both permission and attribution." The Terms page carries no open flags. 27 pages, QA clean.

The inline [ATTORNEY REVIEW] flag came off at his direction, so inline attorney-review flags now survive only on the samples page, the last one site-wide. All five term sections revised verbatim: the education section retitled to name accounting, legal, and engineering and rebuilt around consult-your-legal-counsel; the engagement section retitled "Engagements Only Start With a Signed Proposal" with his resource-first framing; Site Content now requests permittance and attribution instead of the quote-briefly line; Accuracy hardens to verify-before-any-action; and Governing Law and Changes recast around Florida-only service and annual legislative sessions (his version drops the explicit these-terms-are-governed-by-Florida-law clause and the material-changes-date line, his call as reviewer). The closing CTA becomes "Have A Question These Terms Do Not Answer? / Send it over. Get a clear response." One verbatim quirk flagged to David: "permittance" (nonstandard; usually "permission"). 27 pages, QA clean.

His lede verbatim (the attorney clause becomes "should be consulted for any legal questions or clarifications"), the hero button becomes "Back to Homepage" via the same per-page primaryCta override as Privacy, and the "Draft language prepared for attorney review before launch." intro line came off. Unlike Privacy, he has not stated a manual review of the Terms language, so the inline [ATTORNEY REVIEW] flag stays on the page pending his word. Held unpushed pending his push instruction. 27 pages, QA clean.

The lede now opens "Clear explanation of the information this website collects..." verbatim, and the hero's button reads "Back to Homepage" linking to "/", built as an opt-in per-page `primaryCta` override so every other page keeps the site-wide Request a Proposal button (homepage verified unchanged). 27 pages, QA clean.

The marketing-emails sentence now reads "from which you can unsubscribe if you no longer wish to be included on the mailing list." The Privacy page carries no open flags; analytics activation (dashboard token or one-click Pages enablement) remains the one outstanding step. 27 pages, QA clean.

His direction throughout. The draft-language intro and the inline [ATTORNEY REVIEW] flag came off on his explicit statement that he manually reviewed the language (inline attorney flags now remain only on the Terms page and the samples page). Information You Share With Us takes title case and his four paragraphs: proposal-preparation-only use, business-documentation correspondence, the new engagement-documentation paragraph (vendor research calls, report history, cost history), and the new marketing-emails paragraph with unsubscribe (a planned mailing list, filed as a fact). What We Do Not Do becomes his three-bullet list (the prose renderer gained opt-in bullet support), adding the Reserve-Study-results confidentiality bullet naming the authorized recipients. Cookies and Analytics rewritten (Claude's copy for his review) around Cloudflare Web Analytics: cookieless visitor counts and referral sources, with no draft/preview reference; the site-wide draft gates (banner, footer line, noindex) are untouched and stay until go-live. The beacon itself is wired token-gated (`site.cloudflareAnalyticsToken`, empty renders nothing): activation awaits either the token from the Cloudflare dashboard or one-click Web Analytics enablement on the Pages project, flagged to David as the one outstanding step. One verbatim quirk flagged: "of which you will be able to unsubscribe from" (doubled preposition). Browser-verified. 27 pages, QA clean.

His reasoning, recorded as the working principle: that caption identifies who is in the photo (David) for all readers to see, unlike the illustration captions (city scenes, funding curve) that only described what sighted visitors could already see and so moved to alt text. Photo captions that identify people or convey information stay visible; decorative-illustration descriptions live in alt text only. No site change.

The hero's numbered question now reads "How much do you need to collect to pay for those projects?" verbatim. And matching the city-scene treatment from 2026-09-09, the visible caption under the hero funding curve ("Illustrative funding curve: steady contributions meeting each project as it arrives across a 30 year plan.") no longer renders; its wording now leads the SVG's aria-label so screen readers and search engines keep the full description. The conference-photo caption further down the page is a different figure and stays, untouched per his hero-specific instruction. 27 pages, QA clean.

"All inspection work will be scheduled in November as soon as possible." The band carries no open flags. 27 pages, QA clean.

David's message verbatim on every page, directly under the menu: his firstborn (a girl!) arrives in early October, no communication for the first half of that month while he prioritizes family, inspection work scheduling into November, with the warm still-interested invitation to submit a contact or proposal request. Built as an optional `site.noticeBand` field (delete the field to retire the band when the moment passes) rendering in a sand band with a Harbor accent line, browser-verified under the header on all 26 rendered pages. Two facts filed in `Facts/about-hi/company-overview.md`: the services launch target of November 1st, 2026 (his stated intent; the website go-live word and launch gates remain separate), and the October availability pause. One verbatim quirk flagged to David: "all inspection work will be scheduled in November as possible" (possibly "as soon as possible"). 27 pages, QA clean.

The site-wide band on every statute-touching page (17 of 27) now reads "Any statute references on this website were last reviewed on September 12th, 2026. Laws change, and no information on this website is intended as a legal opinion. Please verify current legislative requirements with your association attorney." replacing the July 10 / current-to-HB 913 wording. The date stays data-driven (one field in `site.statuteReview`; the unused HB 913 note field removed), and the September 12th date is David's asserted review date, reflecting his rewrite of the statute-touching copy across the September sessions. The attorney-review launch-gate item is unchanged. 27 pages, QA clean.

His replacement wording closes the flag left by the HB 913 retirement: the sentence now reads "which you can find more on within our SIRS service page", with "SIRS service page" linked to /services/structural-integrity-reserve-studies/. The article's date fields bumped, so the page reads "Last Updated on September 12th, 2026". No open flags remain anywhere from today's session. 27 pages, QA clean.

His reasoning recorded in the archive README: he may bring it back later, but the freshly rewritten SIRS services page adequately explains what the section's only article covered. "HB 913 in Plain English" moved intact to `Archive/2026-09-12-retired-lessons/` (no image; restore path documented), and the Structural Integrity Reserve Studies topic came out of `LESSON_TOPICS`. With this retirement, inline attorney-review statute flags survive only on the samples page. One knock-on handled and flagged: the Avoiding Underfunding intro (his copy) linked to the article; the hyperlink was removed with his sentence left verbatim, so it still reads "(see the HB913 article for more on that)" and now references a lesson that no longer exists, awaiting his call on a rewording. The retired URL falls to the branded 404. The library is three articles in two sections (General Reserve Principles; Reserve Studies); the site is 27 pages. QA clean.

"The information shown is our understanding" drops its stray "a". The SIRS page carries no open flags. 28 pages, QA clean.

His copy verbatim. The section: retitled "Additional Flexibility From the 2025 Law", the professional-hygiene clause dropped, the closing paragraph replaced with his not-legal-advice reminder, and the aside becomes "Founded Experience Before and After The Legislation" with his prior-firm SIRS-process story (an unnamed reference he authored himself; filed in `Facts/about-hi/company-overview.md`, and the sibling never-name rule unchanged). The FAQ: the two-story question replaced by his 2023-SIRS-not-followed answer, a new update-another-provider's-SIRS answer with the "1 Lump Sum" example, the milestone-redundancy answer rebuilt around SIRS-after-milestone sequencing, and three additions: the mixed two/three-story all-buildings answer, the DBPR reporting answer stating the Board must file within 45 days with the site's second external link (the Florida DBPR SIRS-reporting page, verified live, opening in a new tab), and the compliance answer rebuilt as first-step-not-only-step. The old compliance question effectively moved to slot six in his new words. One verbatim quirk flagged to David: "The information shown is a our understanding" (stray "a"). Statute-adjacent claims (the 45-day filing window, all-buildings inclusion) ship as his statements under the page's statute band and attorney referrals. 28 pages, QA clean.

The card now reads "the SIRS will need to be completed again at least once every 10 years." The What Changed section carries no open flags. 28 pages, QA clean.

His copy verbatim across the intro and all four cards: the intro drops the confirm-with-attorney line in favor of "summarized to be as clear as possible" (the page's lede, table note, and Check with Counsel aside still carry the attorney referrals); the cadence card's closer becomes his "will need completed again once at least every 10 years"; the waiver card trims to one sentence, dropping "structural" from "SIRS items" and the show-of-hands line; "Baseline Funding Plan" is retitled "Minimum Funding Requirement" with the association-must-follow framing and "$0"; and the threshold card splits its intent into a second sentence. One phrasing note flagged to David: "will need completed again once at least every 10 years" reads regionally ("will need to be completed" / "at least once every") if he wants it smoothed. 28 pages, QA clean.

The questions-answered SIRS cell drops its "all": "What funding should we collect so (predictable) structural projects can be completed?" 28 pages, QA clean.

His restructure: the side-by-side table now carries the "A key distinction" eyebrow, the "A SIRS Is Not a Milestone Inspection" title, and his new intro line, while the separate prose section below it (with its Plain Version aside) is removed as merged. Every table cell revised to his copy: the questions-answered row now pairs safety-and-remediation against funding-for-predictable-projects, who-performs-it lists "A Licensed Engineer, Architect, or credentialed Reserve Specialist" for the SIRS (dropping the David-has-performed-SIRS-personally line from the table; the credential remains in the Also New aside and on About), the statute row names Condominiums and Cooperatives, timing becomes his Initial/Thereafter phrasing with "Initial Immediately If Not Yet Completed" for the SIRS, and the deliverable row gains repair-recommendation and milestone-incorporation language. The note under the table becomes his current-understanding version with the annual-legislative-session caveat and the attorney line retained. Removing the section shifts the page's alternating band colors below it (the FAQ moves from the dark band to white), a mechanical consequence of the merge. 28 pages, QA clean.

The Waterproofing description's parentheses repaired to "pool resurfacing (if part of the structure), etc.", Related Items reads "attached to the exterior", and the Waterproofing & Exterior Painting and Windows & Exterior Doors cards take "&" per his choice, matching the Fireproofing & Fire Protection Systems style. The SIRS page carries no open flags. 28 pages, QA clean.

His copy verbatim: the lede now carries his we-aren't-attorneys disclosure and legislative-session caveat; the "Who must" eyebrow becomes "Who", the statute paragraph gains his legal-opinion-on-necessity closing, the second paragraph becomes the low-rise-to-beachfront-towers range, and the photo placeholder came out of the section; the checklist becomes "What's included / What a SIRS Covers" with his intro, and every component now carries his practitioner description (Roof membranes, Structure with visual-inspection limits and milestone-inspection feed-in, Fireproofing & Fire Protection Systems with DLM-era examples, Plumbing allowances, Electrical infrared inspections, Waterproofing projects, Windows and Exterior Doors with the unit-owner-responsibility carve-out, and Connected Items renamed Related Items with the $25,000 threshold and examples); the closing note becomes his each-association-is-unique line, dropping the attorney-confirm sentence (the Check with Counsel aside and statute band remain). Three verbatim quirks flagged to David: the Waterproofing description's broken parentheses ("pool resurfacing if a part of the structure), etc.)"), "they're attached the exterior" in Related Items (likely "attached to"), and the Waterproofing/Windows card titles keeping their existing "and" since only the descriptions were instructed (his heading wrote "Waterproofing & Exterior Painting"). 28 pages, QA clean.

The lede reads "a funding plan presentation owners will support" (stray "an" removed), and the approach paragraph opens "Consulting engagements are tailored to your specific question or need." The page carries no open flags. 28 pages, QA clean.

His copy verbatim: the H1 becomes "Specialized Services Created For Your Needs", the lede recast around reviewing an existing report and preparing a funding plan presentation, the first card retitled "Reserve Study Reviews" with a shortened description, the Board Education card ends on "founded understanding", the Funding Plan Help card speaks of a Reserve Study's initial recommendations, the approach section becomes "Valuable Insights, Regardless of Scope" with his transparency framing and positive-value-every-client closer across both paragraphs, and the CTA's "Contact David" button becomes "Contact Us". Two verbatim quirks flagged to David: "a funding plan presentation an owners will support" in the lede (stray "an"), and "specifically designed to your specific question" (the doubled specific plus "designed to" reading unusually; possibly "tailored to your specific question"). 28 pages, QA clean.

"Certain Collier County communities may still be working through repairs" gains its "be". The Naples page carries no open flags. 28 pages, QA clean.

His copy verbatim: the lede recast around storm frequency, property values, and property-type variance with "six-to-seven figures"; the estimates paragraph softened (drops the seven-figure-project and compounding-errors lines); the club paragraph tightens to "densest country club markets" with "meticulously created"; and the SIRS paragraph generalizes Hurricane Ian to "past hurricanes" and drops the three-stories qualifier from the requirements sentence (the FAQ still carries it). All three FAQ items replaced: the new "How do you estimate replacement costs?" answer publishes his four-step hierarchy (past cost history, then local vendor research, then comparable projects, then estimation tools as a rare last resort), filed with attribution in `Facts/services/reserve-studies.md` as reusable methodology; the country-club answer now routes scope confirmation to the proposal process; and the milestone-vs-SIRS answer opens "Likely, yes." and keeps the attorney line. One verbatim quirk flagged to David: "may still working through repairs" (likely "may still be working"). 28 pages, QA clean.

"Typically coincides with a rise in costs of living" gains its "with", and the roof answer reads "not the ones described in an older report". The Fort Myers page carries no open flags. 28 pages, QA clean.

His copy verbatim: the insurance-pressure paragraph shifts to founded assessments and a "current Reserve Study"; the seasonal paragraph widens to the surrounding region and closes on an easy-to-follow report rather than the executive-summary line; the post-Ian roof answer now records "the history of each component" against current conditions; the seasonal-owners answer becomes his review-first process with virtual-meeting availability for boards whose members live in many different states; and the insurance answer restructures as "Directly, no. ... Indirectly, yes." with the cost-of-living escalation path. Verbatim quirks flagged to David: "typically coincides a rise" (likely "coincides with a rise") and the roof answer's "based on current conditions, not the one described" (possibly "the ones"). 28 pages, QA clean.

Unlike the retired cities, Destin's full entry (copy, FAQ, dune scene, map coordinates) stays intact in cities.mjs and florida-map.mjs; only its slug left `publishSlugs`, joining Miami, Fort Lauderdale, and Jacksonville in the held set, so restoring it is a one-line change. Its page, card, and map marker no longer render, the URL falls to the branded 404, and the Service Areas meta description, which named Destin, now names St. Augustine. No nearby arrays referenced Destin, so no re-mesh was needed. The site is 28 pages with 7 published city pages (Sarasota, Naples, Fort Myers, Melbourne, Orlando, St. Augustine, Tampa). README counts updated; Destin remains a Major market in the Facts since it is held, not retired. QA clean.

The entry moved verbatim (with its "sail" scene background) to `Archive/2026-09-12-retired-city-pages/` with a README and restore path, its marker came off the interactive Florida map, and its slug left `citySlugs` and `publishSlugs`. The nearby meshes re-wired: Melbourne and Naples now point at Tampa in its place, and the held Fort Lauderdale and Miami entries point at Melbourne. The retired URL falls to the branded 404. The site is 29 pages with 8 published city pages (Sarasota, Naples, Fort Myers, Melbourne, Orlando, St. Augustine, Destin, Tampa); Miami, Fort Lauderdale, Jacksonville stay built but held. Facts and README counts updated. QA clean.

"The capability to account for owners' needs" takes the plural possessive. The Sarasota page carries no open flags. 30 pages, QA clean.

His copy verbatim: the lede shifts to "many 55+ communities" and confidence-at-the-meeting framing; the barrier-islands paragraph now closes on high-cost downtown components (elevators, major mechanical, parking garage structures, interior renovations); the retirement paragraph drops the special-assessment definition and adds the "what if" testing capability (the Excel tool already named on /services/, now on a city page); the SIRS paragraph gains "condominium and cooperative" and "above that mark"; and all three FAQ answers rebuilt (the special-assessment answer around a viable financial plan, the coastal-inland answer opening "Yes. Our process (following the Reserve Study Standards)...", and the SIRS answer introducing the two-reserve-schedules reality, dropping its attorney-confirm closer, the same call he made on St. Augustine). One verbatim quirk flagged to David: "account for owner's needs" (likely the plural "owners' needs"). 30 pages, QA clean.

"With many of its buildings now decades old" gains its "of", and the SIRS answer now recommends "consulting with your association's attorney to determine exact needs", restoring the counsel referral alongside his not-legal-counsel hedge. The Melbourne page carries no open flags. 30 pages, QA clean.

His copy verbatim: the H1 becomes "Reserve Studies Throughout the Space Coast", the lede drops its salt-air clause, the barrier-island paragraph widens to "from Cocoa Beach down through Indian River Shores", the mainland paragraph pairs new-community first studies with older developments' sustainability, and the third paragraph (sent as his fifth bullet with replacement text only, same pattern as St. Augustine) recast around the SIRS requirement affecting the whole region. The FAQ: the first-study answer becomes his best-time-is-now version, the salt-exposure question is replaced by a new insurance-implications Q&A (roof-age replacement demands and premium hikes, the first place insurance carrier behavior appears on a city page), and the SIRS question becomes the partial-three-story-buildings scenario with his all-buildings-included understanding, hedged as not-legal-counsel. Two verbatim quirks flagged to David: "with many its buildings" (likely "many of its"), and the Q3 recommendation to consult "with your association" (reads circular; possibly "your association's legal counsel"). 30 pages, QA clean.

"More common throughout this region" drops the stray "in", the SIRS answer settles on "The engagement covers ... and produces", and the home-market paragraph now reads "oceanfront and gulf-front St. Petersburg condominium towers" per his chosen phrasing. The Tampa page carries no open flags. 30 pages, QA clean.

His copy verbatim: the lede recast around Tampa Bay's waterfront towers and suburban associations; the home-market paragraph now names the three surrounding counties (Hillsborough, Pasco, Pinellas), St. Petersburg towers, and Wesley Chapel with the Gulf-coast-experience closer, replacing the specialist-answers-the-phone line; the SIRS paragraph reframed against Lakeland and Orlando with "parking garage structures" and softened statute phrasing; the suburban paragraph now opens on traditional Reserve Studies remaining common; the SIRS FAQ answer credits "our founder (David)" with extensive Florida SIRS work; and the suburban-HOA answer rebuilt around the asset list with outcome projections. Verbatim quirks flagged to David: "more common in throughout this region" (stray word), "The engagement will cover ... and produces" (tense mismatch, likely "produce"), and "oceanfront St. Petersburg" (St. Pete fronts the Gulf and the bay; "oceanfront" is loose if he wants strict geography). 30 pages, QA clean.

"Even though it's inland" gains its apostrophe, the SIRS answer's "condominium or cooperative building" gets its "or", and "We recommend confirming" replaces "recommend to confirm". (The services card's "condominium and cooperative buildings" is the site-wide template phrasing naming both categories and correctly keeps its "and".) The Orlando page carries no open flags. 30 pages, QA clean.

His copy verbatim throughout: the H1 gains "& Properties", the lede recast around the inland-but-severe climate, all three local-context paragraphs revised (project intervals over national assumptions; gated entrances replacing stormwater infrastructure in the scale paragraph; the SIRS note closing on "we're here to help!" instead of the straight-answer line), and all three FAQ items retitled and reanswered (the SIRS answer routing confirmation to "your association's legal counsel", the climate answer shortened, the short-term-guest answer softened to "It can."). Verbatim quirks flagged to David: "Even though its inland" in the lede (likely "it's"), "a condominium and cooperative building" in the SIRS answer (likely "or"), and "We recommend to confirm" (likely "recommend confirming"). Browser-tab title unchanged and within QA's length cap. 30 pages, QA clean.

The turnover answer now reads "for both a Turnover Study and a first Reserve Study". His rulings on the two flags, recorded: Turnover Studies are NOT a Homeowner Insights, LLC product offering (the FAQ mention is educational; fact filed with a never-sell rule in `Facts/services/reserve-studies.md`), and the attorney-confirm line stays out of the St. Augustine FAQ as-is. The page carries no open flags. 30 pages, QA clean.

All three local-context paragraphs and all three FAQ items his, verbatim: the historic-to-new framing paragraph, the age-spectrum paragraph pairing new-development first studies with historic-property realities, and the region paragraph with its tailored-report closing (his message labeled the last one and the turnover answer as "change from" with only one quoted text each; both read plainly as replacements for the corresponding live copy and were applied as such). The turnover question generalizes off Nocatee ("Our HOA just went through turnover. Now what?") and its answer introduces the Turnover Study alongside the first Reserve Study, the first time that service term appears on the site; the coastal-inland answer softens to "For some items, meaningfully different"; and the SIRS answer swaps the attorney-confirm closer for a reach-out-to-us invitation. Two notes flagged to David: "for a both a Turnover Study" in the turnover answer looks like a stray word (likely "for both a"), and with his new copy the confirm-with-your-attorney line no longer appears anywhere on the page's FAQ or body, though the page keeps its statute-review band. 30 pages, QA clean.

"SIRS vs Milestone Inspection: What Florida Boards Actually Need" came off the Lessons library and moved intact to `Archive/2026-09-09-retired-lessons/` (README with restore path; the article had no image asset, and no cross-references pointed at it). The Structural Integrity Reserve Studies section now holds HB 913 in Plain English alone, and the library settles at four articles. Notable consequence recorded in the archive README: this article carried inline attorney-review flags, so inline statute flags now live only in the HB 913 article and on the samples page. The retired URL falls to the branded 404. Site total drops to 30 pages, QA clean.

The rentals answer now reads "such as a rooftop cooling tower or an interior pool dehumidifier, are designed for more constant usage" (his replacement wording), the climate answer's "specifically within your property" gains its "in", and the body paragraph's "Gulf-front" lowercased to "gulf-front" to match the lede (his chosen direction; other cities' pages keep their own casing, untouched per his Destin-scoped instruction). The Destin page carries no open flags. 31 pages, QA clean.

The contrast bug was a side effect of yesterday's drivers-section removal: the Questions section slid into each city page's navy band, where the base FAQ rule kept painting answers in the light-surface muted ink. A dark-surface override now colors answers in the established `--dark-muted` light grey (#A9BFCB, the same body-text grey every other dark section uses) while questions stay Paper white, matching the site's dark-band hierarchy; applied site-wide, verified by computed style in the browser. Destin: his lede and first two local-context paragraphs verbatim (short-term-rental usage framing, the freeze/humidity climate paragraph), and all three FAQ questions and answers replaced with his (Emerald Coast asset exposure; short-term rentals with the cooling-tower/dehumidifier vs elevator/flooring distinction; the insurance-and-vendor-communication answer with his DLM elevator example). The third local-context paragraph he sent as a change was character-identical to what was live, so nothing moved there (flagged back). Verbatim quirks flagged and shipped: "would are designed" in the rentals answer, "specifically with your property" (possibly "within"), and lowercase "gulf-front" in the lede against "Gulf-front" elsewhere on the page. 31 pages, QA clean.

Three template changes applied to all nine published city pages at once. The visible caption under each city's line-art scene ("{City} building stock in the Homeowner Insights, LLC line art style.") no longer renders; its content lives only in the SVG's aria-label, which was already the richer description and now ends "drawn in the Homeowner Insights, LLC line art style." so screen readers and search engines keep the full text (and the label now honors the ", LLC" name rule, which the old "Homeowner Insights style" tail predated). The local-context section's eyebrow became "Local context for reserve planning" per his wording. And the "Planning drivers" section ("What Drives Reserve Planning in {City}") came off every page as redundant to the local-context prose; the `drivers` data stays in cities.mjs as the vetted trait record behind each entry's copy and scene backgrounds, and the unused drivers renderer remains in build.mjs for possible reuse. Verified across all nine built city pages: zero figcaptions, zero drivers sections, old eyebrow gone, new eyebrow present. 31 pages, QA clean.

The sentence now reads "We have experience with and offer services from the Panhandle to the Keys." with his chosen "with and offer" language. The Service Areas page carries no open flags. 31 pages, QA clean.

His copy verbatim on the Service Areas page's "Not on the List? Still Covered" section: the body now leads "We have experience with offer services from the Panhandle to the Keys." and closes on detailed reports, interactive tools, and top-notch customer care; the Based in Riverview aside now names the Tampa Bay, Bradenton, and Sarasota regions within easy reach while serving the whole state. One verbatim quirk flagged to David: "experience with offer services" reads like a missing word (perhaps "with and offer" or "offering"). 31 pages, QA clean.

His confirmation, verbatim in intent: all changes and new graphics are appropriate and approved. That ratifies every judgment call flagged across today's three pushes: the "Major Markets Across the State" section title and eyebrow, the redrafted Service Areas meta description, the de-linked Cocoa Beach mention in the SIRS vs milestone article, the St. Augustine lighthouse signature, and the two Spark accents (Orlando's sun, Melbourne's contrail dot). Nothing from the restructure remains open.

His caption verbatim: "This is a stylized map for orientation, not to scale. The marked cities are markets with dedicated pages, although we serve all of Florida!" And on his note that the city card graphics read too alike, the parametric scene renderer gained a `background` option, a subdued signature drawn behind each skyline from that city's vetted drivers: Destin gets beach dunes with sea oats, Fort Myers calm clouds (its storm-season driver, stated quietly), Melbourne a rising launch contrail for the Space Coast, Naples a sun settling on the Gulf horizon beside its golf flag, Orlando a bright rayed sun for its heat-and-UV driver, Sarasota a barrier-island strip with one distant palm, St. Augustine a generic coastal lighthouse (its real Anastasia Island landmark, drawn generically; flagged for David's comfort), Tampa a distant bay bridge, and West Palm Beach a sailboat on the Intracoastal horizon. Held cities get a background assigned when published (noted in the schema comment). All muted Harbor/hairline strokes so the building line art still leads; the Spark orange appears only as Orlando's sun and Melbourne's contrail dot. Every card browser-verified against a rendered contact sheet: unique signature present, nothing outside the canvas, no collisions with the golf flag or crane. 31 pages, QA clean.

David's restructure, all in one instruction. The Service Areas page's two card sections merged into one "Major Markets Across the State" section listing every published city alphabetically with the fuller card text, and the interactive Florida map now draws every marker in the same white (Paper) dot at the same size the Primary cities carried (the Shoal secondary style and the `map-marker-primary` class are gone). The Bradenton, Cocoa Beach, and Pompano Beach pages were removed and archived verbatim at `Archive/2026-09-08-retired-city-pages/` (entries, map coordinates, restore path); their URLs fall to the branded 404, and the ten `nearby` arrays that referenced them were re-meshed. Orlando, fully built since 2026-07-10 but held as a contested metro under decision 7 of the 2026-07-17 review, is now published on his word, superseding that hold for Orlando only (Miami, Fort Lauderdale, Jacksonville stay held); decision record filed at `Facts/decisions/2026-09-08-service-area-restructure.md`. Facts updated to match: `target-cities.md` restructured to a single Major markets table with a retired-pages section, `company-overview.md`'s target-markets list merged, and the keyword plan's priority order annotated as dated research. Two mechanical consequences flagged to David: the SIRS vs milestone article's Cocoa Beach link was removed (sentence text unchanged, its Last Updated date left alone), and the Service Areas meta description, which named Bradenton, was redrafted to name published cities. Section title "Major Markets Across the State" and eyebrow are Claude's wording for his review. Browser-verified: 9 uniform white markers, 9 cards, Orlando page complete with three published nearby links. 31 pages, QA clean.

His copy verbatim: the lede under "Serving Communities Throughout Florida" now reads "Homeowner Insights, LLC works statewide, from our home base in Riverview. The following are some major markets, although we're here to help if your community is located anywhere in Florida." replacing the markets-where-we-focus phrasing. 33 pages, QA clean. Held unpushed pending David's word (his message carried no push instruction, and more Service Areas direction is expected).

The broken sentence now reads "aesthetics (interiors) and amenities (levels of use and care by residents)." with "is" restored at its head; the Conclusion sentence became "A Reserve Study helps the association determine funding needs for future projects"; and "There will still be time" gained its "be". The article is clean of flags. 33 pages, QA clean.

His copy verbatim (curly quotes normalized) across six sections: the budgeting-whirlwind opening with four italicized questions, a what-is-a-Reserve-Study section naming the CAI Reserve Study Standards, the three-part component test with his italicized commentary under each numbered line and a nine-item Florida project list, the two underlined Answers (Proactive Planning with his elevator lead-time example, Project Prioritization with his three-tier safety/damage/disruption ordering), the reactive-cost section, and a Conclusion defining "current" as within three years. Two link mechanics handled for him: his pasted absolute hoi-site-preview.pages.dev links were converted to root-relative internal links (they would have broken at the real domain), and the CAI Standards PDF at caionline.org is the site's FIRST external link, so `emphasize` learned https links, rendered with target=_blank rel=noopener so a reader keeps their place; internal links stay same-tab and route-checked. The article date bumped to 2026-09-05. Four verbatim quirks flagged for his call: the visibly broken "aesthetics (interiors) and amenities (." sentence, "A Reserve Study is that it lets" (words missing), "There will still time" (missing "be"), and "This often related" (missing "is"). His DLM elevator-compliance example (January 1, 2024) ships as his industry fact under the statute band. 33 pages, QA clean.

Drawn to David's spec for "Using a Reserve Study to Prepare for Major Projects", replacing the construction-crane photo (archived): a report page on the left with genuinely blurred text bars (an SVG blur filter, not fake gray lines), the brand lens over the page clarifying a line-art elevator inside the glass (clipped to the lens circle, handle bottom-right per the established style), and a dashed projection cone opening to a right-hand panel carrying his four checked items verbatim, the 24-year age note, the 2028 modernization, the 12-month lead time with March 2027 bidding, and the no-special-assessment funding confirmation, wrapped across thirteen lines that all sit inside the panel. His example dates (2027, 2028) are illustrative story content, not commitments. The article's date bumped, so the page reads Last Updated on August 30th, 2026. 33 pages, QA clean.

On David's word: his coastal-definition sentence now carries a parenthetical acknowledging that local enforcement authorities may still require the earlier 25-year milestone inspection where conditions such as salt water proximity justify it (the nuance from the SB 154 research), and "where funding gaps hide" came out of the meta description. QA caught the trimmed description at 117 characters, so it was extended with "for a coastal property" to clear the floor without reintroducing the removed phrase. Every open item on this article is now resolved. 33 pages, QA clean.

"A 2023 revision removed the variation" and "dated or generic numbers". Left standing by his silence, still open: the SB 154 local-option nuance and the stale meta description. 33 pages, QA clean.

His copy verbatim (curly quotes normalized), replacing every section's text within the five-section outline he set earlier today. Notable content decisions, all his: the intro drops the inline statute-review line (the page band remains); his coastal-definition paragraph edits Claude's draft and simplifies the SB 154 story to "removed the variation so the 30-year mandate was statewide", dropping the local-25-year-option nuance (flagged back to him, since local enforcement agencies can still require 25 years); the FAQ reorders manufacturer-life first, italicizes the questions instead of bolding them, and rewrites all three answers, including a strong new two-paragraph financial-planning-tools-only answer on the safety question with the invasive-inspection referral path; and the old credentials closing (CAI framework, RS #369, 500+ studies) is replaced by his italicized educational-disclosure paragraph. His rewrite also retired this article's remaining inline [ATTORNEY REVIEW]/[VERIFY] brackets; site-wide, inline attorney flags now live only in the HB 913 and SIRS-vs-milestone articles plus the samples page. Two verbatim quirks flagged: "A 2023 removed the variation" (missing a word like "revision") and "dated or generic figures numbers" (doubled word). Still open: the meta description's stale "where funding gaps hide". 33 pages, QA clean.

The article now runs exactly his five sections: "Salt Air and Component Life: The Introduction" (retitled, text untouched per his instruction), the new "What qualifies as a coastal property in Florida?", "What Salt Air Does to a Building" (held as-is for his future edits), "What a Coastal Reserve Study Should Include", and "Frequently Asked Questions (Coastal Edition)" with the same three Q&As but each question now a standalone bold line. Four sections removed at his word (observed condition vs manufacturer averages, where funding gaps hide, the cost of waiting, and the SIRS backdrop), taking the Melbourne and SIRS-service-page internal links with them. The new section is Claude's copy pending his review, built on live research that confirmed his three-mile recollection: s. 553.899, F.S. originally required milestone inspections at 25 years for buildings within 3 miles of the coastline (as defined in s. 376.031), and SB 154 (2023) converted that to a local-enforcement-agency option justified by conditions like salt proximity; the section states there is no universal industry definition, uses ~3 miles as the practical screening line, frames exposure as a spectrum, and carries an [ATTORNEY REVIEW] flag on the statute characterization. Kept and flagged to David: the untitled closing paragraph (credentials plus the not-legal-advice line) since it is the article's standing footer rather than a listed section, and the meta description still mentions "where funding gaps hide" though that section is gone. 33 pages, QA clean.

The ocean surface dropped and the sand rose, so the beach now crests visibly above the waterline (sand top y 525 vs water y 541) and slopes down to meet it at the shoreline; the chaise lounges flipped, backrests now on the right so they face the water, and they sit up on the raised sand; and the palm moved from the shoreline to the sand between the lounges and the perimeter fencing (trunk at x 498, crown spanning 461 to 560, clear of the fence lens), scaled down to fit the spot. The arrows' Spark origin stays at the shoreline meeting point. One composition note recorded: the third arrow's route passes in front of the palm's lower crown, drawn over it in normal infographic layering. All geometry re-verified inside the viewBox with transforms applied. 33 pages, QA clean.

His review of the first draft, all four applied: the ocean is now a distinct Harbor-washed zone meeting a pale sand tint at a visible shoreline; the palm was redrawn realistic (segmented curved trunk, six ribbed drooping fronds, coconuts) and two chaise lounges sit on the sand facing the water; all three magnifying-glass handles now match the rooftop one at bottom-right; the water squiggle came out of the fencing so it reads as plain perimeter fencing along the building's left side, extended to meet the wall; and the arrows' conjoined Spark point moved to ground level exactly where the ocean meets the sand. Verified with transforms applied this time: every shape inside the viewBox, all handles pointing down-right, the origin at the shoreline. 33 pages, QA clean.

David's copy verbatim: the title became "Coastal Reserve Studies in Florida: How the Salt Environment Affects Component Lives" on the H1 and the Lessons card (the browser-tab title runs shorter for QA's length cap, same pattern as Avoiding Underfunding), and the lede shifted from distance-to-salt-water to exposure framing. The image is a new brand-token line drawing to his spec at `static/blog-images/salt-air-component-life.svg`: beach with waves and a palm on the left, a high-rise on the right, three Harbor magnifying glasses (the brand's lens motif) over a rooftop HVAC unit, a mid-building window, and ground-level pool fencing, and three arrows fanning from a single Spark point on the beach to each lens. During verification two of the three arrowheads were found pointing backward and all three were recomputed to land just off their lens rings. The beachfront photo joined the replaced-assets archive. The date bumped, so the page reads "Last Updated on August 30th, 2026". 33 pages, QA clean.

David's second curation round of the day: Overdue on Your SIRS (which carried three of the site's inline attorney-review flags; they retire with it), the golf and country club article, and the worship facilities article all moved to `Archive/2026-08-30-retired-lessons/` (README updated with both rounds and his reasoning). With its two articles gone, the Property-Specific Articles section came off the index entirely, his stated preference being "specific topics that apply to most properties". The library is now five articles in three sections: General Reserve Principles (Avoiding Underfunding), Reserve Studies (major projects, salt air), and SIRS (HB 913, SIRS vs milestone). Site total: 33 pages. No cross-references pointed at the retired three; retired URLs fall to the branded 404. Of the twelve attorney-review [VERIFY] marks inventoried on 2026-08-24, today's retirals leave far fewer standing, all in the remaining statute articles and the samples page. QA clean.

David's call, made knowing General Reserve Principles drops to a single article ("that's okay", his words, recorded in the archive README). "Common Reserve Planning Mistakes Florida Boards Make" and "How Maintenance Schedules and Reserve Planning Work Together in Florida" moved with their images to `Archive/2026-08-30-retired-lessons/` per archive-never-delete, their slugs came out of `LESSON_TOPICS`, and no cross-references pointed at them (verified before removal). The Lessons library is now eight articles across four sections; the site is 36 pages, and retired URLs fall to the branded 404. QA clean.

All four on his instruction: "Substantial Cost Increases" (was Costs), "the membership's financial capabilities" (apostrophe), "Assessments should be adjusted" (was the doubled "Assessment adjustments should be adjusted"), and "HB913 article" in the intro now links to `/resources/lessons/hb-913-plain-english/`. On the chart, his cut-off report was right: "The Path Abandoned" overran the right edge of the viewBox. Both labels now run parallel to their lines as he specified, "The Path Chosen" above its line slanting upward (rotated -28 degrees at the curve midpoint) and "The Path Abandoned" below its line slanting downward (+19 degrees), and every text element was measured in SVG user units to sit fully inside the canvas. 38 pages, QA clean.

The first full article rewrite of the Lessons era, his copy verbatim throughout (curly quotes normalized to the site's straight quotes). New title "Avoiding Underfunding: Recent Context and a Path Forward" on the H1 and the index card; the browser-tab title runs shorter ("Avoiding Underfunding: A Path Forward") because QA correctly failed the full form at 77 characters, and the meta description was redrafted to match the new content (both flagged as not-his-words). The article now runs six sections in his structure: reserve funding intro, his underfunding-vs-underfunded distinction, the 2020s causes as a bulleted list (COVID-19 supply chains, hurricanes Ian/Idalia/Helene/Milton, insurance premium jumps, cost escalation), three bold warning-sign indicators, course correction, and a SIRS funding section opening on his italicized not-a-legal-opinion disclaimer. To carry the formatting, article bodies now use the same inline marks as FAQ answers (the emphasize pipeline; verified no existing article contained literal marks). The date bumped to 2026-08-30, so this page is the first to exercise the Last Updated mechanism ("Last Updated on August 30th, 2026", verified). The image: a new brand-token SVG chart at `static/blog-images/avoiding-underfunding.svg`, drawn per his brief, a Deepwater history line splitting at a Spark "Today" point into a rising Harbor "The Path Chosen" and a sinking dashed "The Path Abandoned", with axis labels; the construction-team photo moved to `Archive/2026-08-30-replaced-article-assets/`. Notable content consequences of his rewrite, all his call: the three inline [ATTORNEY REVIEW] brackets are gone (his own disclaimer paragraph now carries the legal distance; the statute-review band stays), the RS #369 body mention and Sarasota link are gone, and the old percent-funded/funding-goals material is condensed since the FAQ now covers it. Flagged verbatim quirks: "Costs Increases" in the COVID bullet, "the memberships financial capabilities" (missing apostrophe), and "Assessment adjustments should be adjusted". 38 pages, QA clean.

David's direction: articles are living documents, so every Lessons article page now opens with "Last Updated on July 10th, 2026" instead of the name-credential-date byline. The line is DERIVED from each post's `dateIso` by a new formatter in `build.mjs` (ordinal day included), so revising an article and bumping its date fields refreshes the visible line automatically, exactly the maintenance model he described. Nothing machine-readable was lost: the BlogPosting structured data still credits "David Whann, Jr." as author and carries `datePublished`/`dateModified`, verified on all ten article pages. The site README's add-an-article notes now say to bump the date fields when revising. Worth noting: this removes the last visible RS #369 from the lessons; the credential remains on the About page and in the deliverable checklist. 38 pages, QA clean.

David's copy verbatim: the title's "the" capitalized to proper Title Case, and the summary rewritten from the how-the-gap-forms framing to his shortfall-avoidance one ("We review how to avoid those shortfalls through founded and steady planning."). Both live in the post module, so the index card and the article page hero updated together. 38 pages, QA clean.

David's reasoning recorded with the change: articles will be updated over time, so a stamped date on the index card misleads, and the current date shows in the byline once the reader opens the article (verified still rendering there). Each of the ten cards is now title, summary, and a "Learn More" link to the same URL. 38 pages, QA clean.

David's direction throughout. The index hero became "Clear, Direct Education For Your Benefit" with his updated-for-context lede, and the back button recased to "Back to Resources". The ten remaining articles now sit under his four topic headings, in his order: General Reserve Principles (three), Reserve Studies (two), Structural Integrity Reserve Studies (three), and Property-Specific Articles (two), driven by a new `LESSON_TOPICS` map in `build.mjs`; a post added without a topic assignment lands in a visible "More Lessons" section rather than silently vanishing, and the site README's add-an-article instructions were updated to match. Three articles were retired at his word, two as too generic (Asset Lifecycles, Financial Confidence) and the $25,000 threshold piece as duplicative of HB 913 in Plain English; per the archive-never-delete rule they moved intact, modules and images, to `Archive/2026-08-24-retired-lessons/` with a README recording his reasons and the restore path. The threshold FIGURE stays live in the FAQ's SIRS answer; only the article about it retired. The site is now 38 pages (10 articles). No inbound links pointed at the retired URLs (verified before removal), and QA's route check passed clean.

David's copy verbatim. The eyebrow became "Frequently Asked Questions", the H1 "Your Reserve Study Questions, Answered", and the lede now frames the page as educational and informative with an invitation to suggest additions via contact. The hero's ghost secondary button, which duplicated the site-wide Request a Proposal primary beside it, was relabeled "Contact Us" and pointed at `/contact/`, pairing naturally with the new lede's invitation. The hero now carries one proposal button and one contact button. 41 pages, QA clean.

His full pass over the nine-question section (Q3 and Q4 explicitly unchanged). The rewrites add real practitioner texture throughout: inspections mostly complete within one to two days; the site-visit description now includes counts; useful life is explicitly property-specific (environment, geography, use levels); the emergency-repairs advice now names four advisors (accountant, community manager, legal counsel, Reserve Study provider) instead of routing everything to the attorney; the amenities answer gained his five-to-ten-camera "logical upgrade" worked example in a second paragraph; the future-studies answer, freshly de-flagged, strengthened from "Commonly yes" to "Yes!" with named examples (milestone inspections, infrared electrical testing, plumbing scoping); and the replacement-timing question was retitled to name the Reserve Study and rebuilt as three paragraphs around his 15-year HVAC at remaining-life-zero example. One mechanical note: a double space in the camera paragraph was collapsed, and his "->" arrow in "One short example of variable timing ->" ships as written (a hyphen-arrow, not a banned dash). 41 pages, QA clean.

His words, filed verbatim in `Facts/services/reserve-studies.md`: "yes Reserve Studies are professional services that can qualify as a reserve expense and thus be included in a Reserve Study's component list/funding plan." As the credentialed Reserve Specialist he is the authority on his own methodology, so the bracket came out of the FAQ answer and the claim is publishable. Inventory taken while clearing it: the twelve [VERIFY] marks still rendering in the built site are all of a different kind, statute characterizations across five lessons articles that wait on the association-attorney reviewer (launch gate item 5) plus the samples page's note about the sample documents carrying the prior practice's branding (HI-13 territory). None of those are David's to clear by himself. 41 pages, QA clean. **Held unpushed pending David's word** (his message carried no push instruction).

He replaced the Claude-drafted position-three answer with his own, naming the reserve-component-specific access list (irrigation enclosures, rooftop spaces, mechanical rooms, amenity buildings, pool equipment enclosures) and the numbered point-of-contact-plus-access framing. He ratified keeping "Will the study tell us exactly when to replace things?" in place (adjustment context to come) and confirmed bolding "Additional & Helpful For Us" was the right call. Every FAQ answer on the page is now either his wording or his ratification. Still standing: the [VERIFY] bracket in the future-studies answer. 41 pages, QA clean.

His direction, resent complete after a truncated first paste. Promoted into Fundamentals with new responses: "Do lenders and insurers look at Reserve Studies?" (his three paragraphs naming Fannie Mae and Freddie Mac, the sales-process shift, and the insurer risk lens) and "What do you need from us to prepare a proposal?" (three bold headings with nine bullets, replacing the old single-paragraph answer; the prior-study, governing-documents, and nuanced-responsibilities intake detail is all his). Going Deeper now runs his exact eight-question order with two of his retitles ("Can reserve funds pay for brand new amenities?", "Can the cost of future Reserve Studies be built into our reserve funding plan?"). Removed: "What is a cost threshold?" and "What happens if we fund below the recommendation?". Three judgment calls flagged to David: (1) position three, "What does a Reserve Study provider need during the site visit?", had no supplied response, so a short access-and-point-of-contact draft was written for it, Claude's words awaiting his review; (2) "Will the study tell us exactly when to replace things?" was neither sequenced nor removed by his instructions, so it sits last in Going Deeper; (3) the middle heading "Additional & Helpful For Us" carried no BOLD instruction where its two siblings did, and was bolded anyway for visual consistency. Still standing: the [VERIFY] bracket inside the future-studies answer, unanswered twice now. Fundamentals holds fourteen questions, Going Deeper nine. 41 pages, QA clean.

David's copy verbatim, after a truncated first paste was flagged back and resent (the resend also added an NFPA fire alarm bullet). Gone: "Does a Reserve Study make us compliant with Florida law?" and "How do we get started?" (the get-started role is covered by the Request a Proposal buttons now on the cost and turnaround answers). Added in their place: "What does a Reserve Study provider need to complete the Reserve Study?" with two bold headings, Bare Minimum (governing documents; current-year financials; the most recent NFPA annual fire alarm inspection report if applicable) and Beneficial For High-Quality Report (project history, planned projects, vendor list), closing with the Excel-based intake form and post-inspection follow-up line. Two process facts surface here for the first time: the Excel-based document-request form (a sibling to the "what if" tool already named on `/services/`) and the NFPA report as a standard intake item. The Fundamentals section stays at thirteen questions. 41 pages, QA clean.

David's copy verbatim, question unchanged. The answer now speaks as Homeowner Insights, LLC (goal: four to six weeks from inspection completion, longer stated on the proposal), adds his deadline-adjustment commitment, gains a Request a Proposal button, and, the substantive news, states for the first time that **the inspection is scheduled on receipt of a deposit of 50% of the engagement's fee**, so the clock depends on the client. That number completes the "deposit invoice" step he added to Request a Proposal on 2026-08-24 but never quantified; filed in `Facts/about-hi/pricing.md` with attribution as publishable. One verification note: a leftover-phrase check false-alarmed on "before anything is scheduled", which turned out to belong to the untouched "How long does a site visit take?" answer in the Going Deeper section. 41 pages, QA clean.

A colon now follows "anticipated in 2027", and the stray "(Level 1)" came off the SIRS heading, which now reads plainly "Structural Integrity Reserve Study: $4,000 to $10,000+". The pricing fact file's note about the heading style was updated to match. 41 pages, QA clean.

David's pass on the FAQ's pricing pair. "What do we actually receive?" was removed outright (its content long since superseded by the Reserve Studies deliverable checklist). The cost answer was rebuilt to his structure: the 2027 "normal range" framing, **Full Reserve Study (Level 1): $2,000 to $6,000** and **Structural Integrity Reserve Study (Level 1): $4,000 to $10,000+** as bold lines, his SIRS caveat that the range covers SIRS plus a traditional Reserve Study of non-SIRS items, and the biggest news, update-study percentages published for the first time: With Site Visit typically 60% to 80% of the original Full study cost, No Site Visit 25% to 35%, with his inflation caveat. That closes the last HI-7 residual, open since 2026-07-17. The fact rippled through the whole brain in one sweep: `Facts/about-hi/pricing.md` rewritten as the 2026-08-24 guidance with a history section and a new never-quote-percentages-off-a-current-fee rule; `Facts/faqs/client-faq.md`, `Facts/services/sirs-structural-integrity.md`, and `services-overview.md` updated off the old $3,500; the sales script's [INSERT: update-study pricing] placeholder finally cleared with a spoken-register version of the percentages; the hub setup-guide example refreshed; and the homepage quick-answer's $3,500 raised to $4,000 so the site does not state two SIRS floors at once (the one edit beyond David's letter, flagged to him). Verified in the built output: zero $3,500 anywhere in dist. The FAQ page's [VERIFY]-style stale count in the site README was also loosened to stop naming a question count. Two of David's wording quirks shipped verbatim and flagged: the intro's missing period after "anticipated in 2027", and "(Level 1)" appearing on the SIRS heading. 41 pages, QA clean.

David's copy verbatim. "What does the RS designation mean?" became "Who is best qualified to complete a Reserve Study?", a candid buyer's guide under three bold headings, Background, Credentials, and Experience, opening with his own disclaimer ("take it with a grain of salt") and closing with the ask-who-is-actually-on-site advice and "Homeowner Insights, LLC" linked to `/about/`. Notable content facts, all his: the answer now names the competing PRA credential alongside the RS, openly calls the company new while resting the case on David's decade and 500+ studies (both approved stats), and drops the explicit "RS #369" from this page; the number still lives on the About page, article bylines, and the deliverable checklist. 41 pages, QA clean.

"although there a few caveats" is now "although there are a few caveats". 41 pages, QA clean.

David's copy verbatim, question unchanged. The answer now opens with the CAI three-year best practice he endorses, then three bulleted caveats: property size and complexity affecting frequency, Florida's 10-year SIRS requirement with a consult-your-accountant-and-counsel line for the follow-the-funding-plan wrinkles, and his post-storm update recommendation ("reality has its own plans!"). One likely typo shipped verbatim and flagged: "although there a few caveats to note" is missing "are". Statute content stays under the page's review band and the attorney-review gate. 41 pages, QA clean.

David's copy verbatim, after a garbled first paste was flagged back and he resent the clean version. The question became "What is a Structural Integrity Reserve Study (SIRS)?", the answer keeps the three-stories-and-taller framing, adds his visual-inspection-only comparison to a traditional Reserve Study, and lists the eight covered items as bullets, including "Other Structural Elements (As Applicable Above the $25,000 SIRS Threshold)", the first place the site states that dollar figure outside the lessons library. The closing paragraph links "Structural Integrity Reserve Study (SIRS)" to the service page and carries his strengthened legal-distance line: not attorneys, not a legal opinion, confer with your property's legal counsel. That is stronger than the old "confirm specifics with your association attorney" and consistent with the attorney-review launch gate. FAQ answers gained a `{ bullets }` block rendering as an unordered list alongside the existing numbered one. 41 pages, QA clean.

The colon came off "Full Funding" so the three goal headings match, *Percent Funded* is now italicized at both Q6 occurrences for consistency with questions four and five, and he confirmed the statutory-funding goal stays out. 41 pages, QA clean.

The question became "What are the funding options our association/property can choose from?" and the answer walks Full, Threshold, and Baseline Funding under bold headings, each with his risk framing: Full as lowest-risk, Threshold as the middle ground with a dollar or Percent Funded floor, and Baseline as the high-risk bare minimum. Two substantive notes for the record. First, the old answer's fourth goal, statutory funding, is gone by his design: the list is now "three main options". Second, the Baseline paragraph carries a pointed industry observation, that Florida's "Fully Fund" statutory language typically maps to what the industry calls Baseline Funding, "an unfortunate disconnect between our industry vs. the state in terminology". That is a statute-adjacent characterization; the FAQ page already carries the statute last-reviewed band and the attorney-review gate covers it before launch. Shipped verbatim, including "Full Funding:" keeping its colon where the other two headings have none, flagged to David. Also flagged: Percent Funded appears twice in this answer unitalicized, where questions four and five italicize it, his call whether to match. 41 pages, QA clean.

His copy verbatim. David caught a wording issue in his earlier question-two text himself: "must be material to the association" became "must be financially significant to the association to be included", plainer for a board reader. Question five became "What is the \"Fully Funded Balance\"?" with a four-paragraph answer: the definition in terms of accumulated deterioration, the halfway-through-its-life clubhouse roof example, the honest yardstick-but-theoretical framing against *Percent Funded*, and the same Lessons pointer question four carries. Both key terms italicized at every occurrence (five across the answer) and "Lessons" linked to `/resources/lessons/`, matching the treatment he set on question four. 41 pages, QA clean.

He ratified the bold Level 1 to 4 subheadings ("Good decision... leave as you've inserted it") and confirmed the question-four typo fix: "look at the your association's" is now "look at your association's". The italics around it are untouched. Same pattern as the 2026-08-10 FAQ flags: his copy shipped verbatim, the issues were named, he decided. 41 pages, QA clean.

His copy verbatim on `/resources/faq/`. Question one's answer doubled into two paragraphs naming real components; question two became "How do you determine what items should be funded within a Reserve Study?" with CAI's three-part test as a numbered list plus his two caveat paragraphs on visual-only inspections and the reserve threshold; question three became "What are the different types of Reserve Study engagements?" walking all four Levels of Service; question four became "What is \"Percent Funded\" and what does it mean?" with *Percent Funded* and *Fully Funded Balance* italicized at every occurrence (five total) and "Lessons" linking to `/resources/lessons/`. The FAQ machinery grew to carry this: answers may now be arrays of paragraphs with `{ list }` blocks rendering as ordered lists, and the inline marks gained *italic* and internal `[text](/path/)` links alongside the existing bold and underline (bold runs first so the existing bold-underline combo on the Reserve Studies page is untouched, verified in the built output). The FAQPage structured data flattens arrays, numbers the list items, and strips all marks, so search engines get clean prose; QA's route check covers the new inline link. Two presentation calls flagged to David: the four "Level N" lines render bold to read as subheadings, and one likely typo shipped verbatim in question four, "a way for us to look at the your association's". 41 pages, QA clean.

The one card on `/resources/` still carrying pre-rename wording ("Plain-English articles... planning practice from the specialist", flagged when the section was restructured earlier today) now reads, verbatim from David: "Direct articles intended to educate Florida Boards, Managers, and Owners on various reserve-related topics!" The "Read the Articles" button he left alone stays. 41 pages, QA clean.

The lessons rename surfaced that the site had no `404.html`, so Cloudflare Pages was serving the homepage with a success status for every unknown URL, a soft-404 problem once the site goes live. David asked for a draft. The new page is the 41st: standard chrome, eyebrow "Page Not Found", H1 "We Could Not Find That Page", a two-sentence lede, a "Back to the Homepage" hero button, and a "Looking For Something Specific?" button row to Services, Who We Serve, Resources, and Contact. The copy is Claude's draft, awaiting David's word before it ships. Mechanics: `pageFile` learned that a route ending in `.html` writes as that file, since Cloudflare only honors a top-level `404.html`; the page carries `notFound: true` and is excluded from `sitemap-preview.xml`; QA picked it up automatically (41 pages, 0 warnings, after lengthening the meta description QA flagged on the first build). Verified locally: correct title, all five links resolve, the Florida aside and draft banner render, no overflow. **Held unpushed for David's review per his standing instruction.**

David's pass on `/resources/`, his copy verbatim. New H1 ("Educational and Informational Tools Designed To Enhance Your Knowledge") and lede. The single "Available Now and Coming Soon" cards section split in two: **Available Now** (Frequently Asked Questions (FAQ) at 01 with rewritten text naming what the FAQ actually covers, Sample Reports at 02 with his honest each-report-is-altered framing, Short Lessons at 03) and **In the Future** (Budget Season Checklist at 01, SIRS Guide (2027) at 02, both with his new descriptions and the "Coming soon." prefixes dropped since the section title now carries that meaning). The renumbering came free: card numbers are per-section automatics, so two sections restart at 01 by themselves. The larger change is the rename: David dislikes the blog framing ("spamming of posts... for added perceived presence") and wants focused lessons, so the article library moved from `/resources/blog/` to **`/resources/lessons/`**, all 13 article URLs with it. Index title is now "Reserve Study Lessons", eyebrow "Lessons", breadcrumbs and the "All Lessons" back-link updated, footer link relabeled. Article content untouched pending his direction; internal module names (`blog.mjs`, `blogIndexPage`) deliberately keep the old wording so the rename stays a content decision, not a refactor. No redirects needed: the site is pre-launch and noindexed, so no external links or search entries point at the old URLs. Verified in the browser: both sections with correct numbering, 13 articles all under `/resources/lessons/`, an article page loading at its new URL, and zero `/blog` hrefs anywhere. Build wipes dist, so the old directory is simply gone. 40 pages, QA clean (its broken-route check is what proves no stale blog links survived).

David's copy verbatim. Step one became "Property Details Reviewed" (was "David Reviews Your Details"), and step three's text now walks the actual sequence, "Once approval occurs, a deposit invoice will be provided, the inspection will be scheduled, and the process begins", replacing the site-visit-booked line and its single-point-of-contact close. Worth noting for the record: this is the first copy on the site to mention a **deposit invoice**, a real process fact about how engagements start that nothing in `Facts/` had captured; it traces to David directly. Step two untouched. 40 pages, QA clean.

The Request a Proposal form now carries exactly the fields David listed, in his order: Association or Property Name, Address, City, Property Type (11-option dropdown), Number of Units (whole-number field, min 1, step 1), What do you need? (4 options), Deadline (optional, with his example as visible help text rather than a vanishing placeholder), Your Full Name, Your Role (8 options), Email Address, Phone Number (now required), Anything else we should know?, and an attach-files button. Required dropdowns open on a disabled "Select One" placeholder so `required` actually blocks submission instead of silently passing the first real option. The attachment feature is the substantive build: a styled button labeled with David's exact wording drives a hidden file input; rules are up to 5 files, PDF / Word / Excel only, 15 MB combined (the size ceiling is an email-deliverability necessity, not in David's spec, and is flagged to him). Enforcement happens three times: the accept attribute, `site.js` with visible error messages per failure mode, and the Worker, which rejects rather than silently drops, then base64-encodes valid files into Resend's `attachments` field so they arrive as ordinary email attachments. The Worker's field allowlist was updated for the new names, which also caught that the contact form's `association-name` and `contact-city` fields (added 2026-08-24 earlier) were missing from it and would never have reached the email. The delivery stays in draft mode until the endpoint is armed per `form-handler/README.md`, which gained an Attachments section including the note that Formspree's free tier (fallback Option B) cannot forward uploads. Verified in the browser with synthetic files: valid picks listed with sizes, a PNG rejected, six files rejected, a 16 MB file rejected, each with the right message, and FormData confirmed carrying the chosen file for submission. One specificity fix along the way (`.form-field input` beat `.file-input-hidden` on width, same clash as the seal earlier today). 40 pages, QA clean.

David's full pass on `/about/`, copy verbatim. New H1 ("A Florida-Focused Firm Founded Upon Experience") and lede. The founder card finally carries his real photo: the approved headshot found on his machine (`2026 - DW Headshot - DIY Compressed.jpg`, already web-compressed at 281KB) with his RS designation seal overlaid bottom-right, the seal downscaled from a 249KB 2076px scan to a 34KB 368px square and clipped to a circle in CSS with a white ring, since the source is a white-ground JPG. The card is retitled "Your Primary Contact, Our Founder", the name became "David Whann Jr., MBA, RS, EBP", the credential "CAI Reserve Specialist #369", a mailto link was added, and the description paragraph came out in favor of The Story below. The Story was rewritten to his three paragraphs (new title "Ten Years, Over 500 Reserve Studies/SIRS, One Commitment"), and its photo placeholder and redundant Credentials aside were removed; `renderSplit` learned to render aside-less at full width. Why Florida Only got both new paragraphs, including David's deliberate, unnamed transparency line about being part of another national Reserve Study provider (filed with a do-not-extend note), and the Standards Commitment link relabeled. **The Affiliation section is gone: David states the company is not a current CAI Business Partner and may not be through 2027, which closes HI-12** and retires its [VERIFY] flag; a restore pointer stays in the source. The closing CTA became "Interested in Moving Forward?". **Launch-gate item 4 (the headshot) is now DONE** in the site README, and HI-5 advanced. Verified in the browser: photo and seal load, seal circular at 26% of photo width pinned in the corner, story full-width with three paragraphs, no [PHOTO] slot, no Business Partner text, no [VERIFY] flag. Two renderer bugs caught during verification: the seal initially never loaded because `loading="lazy"` kept it unfetched below the fold (attribute removed), and the `.portrait > img` rule outranked `.portrait-seal` on specificity, blowing the seal up to full width (selector strengthened). 40 pages, QA clean.

David's pass on `/contact/`, his copy verbatim. The H1 tightened to "Talk with the Specialist" and the lede was rewritten around what gets answered (a report, a scheduled project, reserve requirements, fit) and by whom, "a credentialed Reserve Specialist", replacing the "no queue, no intake team" framing. The hero's duplicate ghost "Request a Proposal" button was removed by dropping the page's `secondaryCta`, leaving only the Harbor primary. The site-wide hero aside is retitled from "Florida Is the Entire Focus!" to **"Florida is Our Only Focus!"**, one edit in `site.heroAside` that propagates to all 38 pages carrying the card (verified: 38 with the new title, 0 with the old; the only other copies live in the v1 archive and dated logs, untouched per guardrails). In How to Reach Us, the Email note became David's warmer first-person invitation naming what to send (a prior Reserve Study, budgets, governing documents, maps), the Base note now claims the whole state ("from Pensacola to Key West!"), and the Service Area card was removed, its job now done by the Base note; the nav and footer Service Areas links remain. The Send a Message form gained two optional short-text fields, "Your Association or Property Name" (`association-name`) and "City" (`contact-city`), between Email Address and the question box, and its three existing labels recased to "Your Full Name", "Email Address", "Your Question". The new fields are optional deliberately: a casual question should not require an association name. The proposal form is untouched. One mechanical note: a double space in David's email copy was collapsed; the "send questions ... along with your questions" repetition in that sentence was kept verbatim and flagged to him. 40 pages, QA clean.

David's copy verbatim across the whole split section on `/who-we-serve/`. The heading dropped "the Same Two Questions" for "the Same Goals", and the first paragraph now numbers the two questions inline (1, 2) and names the Community Associations Institute's Reserve Study Standards explicitly as the basis for each report rather than referring to "the same standards framework" abstractly. The second paragraph is the bigger shift in positioning: the old copy said what changes is the level of translation for different readers, which framed the firm as an interpreter; David's version says "where we differ is the desire, effort, and execution", and names a volunteer Treasurer, a Community Association Manager, and a church's Board of Trustees as the readers. The portfolio aside changed from describing a framework that already exists to an offer to build one ("We can design a consistent report framework and output specifically for your Florida communities"), and its link label softened from "Talk Through Your Portfolio" to "Let's Discuss Your Portfolio". The link still points at `/contact/`. 40 pages, QA clean.

He reviewed the card subtext written for him on 2026-08-10 and kept five as-is, revising three. Maintenance Teams softened "The people who know the property best" to "Those who often know the property best" and made the promise concrete rather than figurative: notes on repairs and replacements are "directly reviewed and incorporated within the component details section of each report" instead of going "straight into the component picture". Management swapped the budget calendar for "the board, the owners, and the budget", putting owners in the list. And More! dropped its closing invitation entirely, leaving just the list of roles. The five he left alone are now his by ratification rather than mine by default, which closes the read he was asked for on that section. 40 pages, QA clean.

The Who We Serve grid went from twelve tiles to ten, all copy David's. Renamed to his preferred client-facing labels: "Homeowner Associations (HOA)", "Co-Ops (Cooperatives)", "Country Clubs" (not "Golf and Club Communities"), "Office Buildings and Commercial Properties", "Schools and Universities" spelled out, and "Churches and Other Worship Facilities". Three tiles came out (55 and Over Communities, Vacation and Resort Condos, Marinas and Waterfront Assets) and one went in: Mobile Home Communities, with a new `mobileHome` glyph drawn for it, a wide body under a shallow roof pitch so it reads as a manufactured home rather than the site-built house already used for HOAs. Verified in the browser: ten tiles in order, the three removals gone from the page, the new glyph valid and inside its viewBox. **The quiet win is in the note under the grid.** David's rewrite names municipalities in the experience list, which is precisely the residual that had kept `HI-11` open since 2026-07-17 ("municipalities remain unlisted; say the word if they belong"). That is the word, so HI-11 is now marked answered in full and the fact is filed in `Facts/about-hi/company-overview.md` under a new dated section, along with mobile home communities, the naming preferences, and a note that the three dropped tiles are a presentation decision rather than a statement that the work is not done. Worth recording how carefully he framed it: the note says "our experience spans beyond what is just listed", which reads as career experience rather than a Homeowner Insights, LLC service claim, and marinas stay named in the note even though the marina tile came out. 40 pages, QA clean.

David's pass on `/who-we-serve/`. New H1 ("Built to Serve Those Who Lead Their Communities!") and lede, both his words. The bigger change is structural: the seats section moved BELOW the property-type grid, so the page now establishes what we work on before who we work with. The grid was retitled "Providing Our Services to All Property Types" with a warmer, explicitly non-exhaustive intro. The seats section, retitled "The Seats Within Those Property Types", had cards that listed property types and therefore duplicated the grid directly beneath it; those six are replaced by eight roles David named: Board of Directors, Property Owners, Developers, Finance Committees, Maintenance Teams, Management, Worship Facility Representatives, and And More! Each card's subtext was written fresh for this brief rather than supplied, so it is the one part of this pass that is not David's wording and is worth his read. Eight new glyphs were drawn to carry them, exported as `roleArt` in `src/illustrations.mjs` in the same 64x64 line-art language as the property-type glyphs (Deepwater strokes, one Harbor accent each) so the two icon sets read as one family now that both appear on the page: three figures at a table, a house with a keyhole, a plan sheet, a page with a bar chart, a gear, a clipboard with a check, an arched hall, and a plus. Cards render them through a new `icon` field and a `.card-art-role` rule that keeps them icon-sized at 64px instead of the 220px building art. Verified: all eight render, no malformed geometry, every glyph inside its viewBox, a 4x2 grid at 1280px collapsing to one per row at 375px with no horizontal overflow. 40 pages, QA clean.

The two things raised with him rather than corrected silently are now corrected on his instruction: the stray "the" is out of question five ("but you should more directly consider..."), and question two ends in a question mark, so all five now do. The bold-underline on "your" survives the edit, and the FAQPage structured data picked up the corrected question text. This is the standing rule working as intended: his copy shipped verbatim, the problems were named, and he decided. 40 pages, QA clean.

The three generic questions on `/services/reserve-studies/` are gone, replaced by five David wrote: cost, update cadence, taking over another firm's study, whether the funding levels are mandatory, and why choose Homeowner Insights, LLC. Three supporting changes. (1) FAQ sections take `wide: true`, dropping the 860px reading cap so the cards span the full 1120px container the way the levels and deliverable above them now do; the 14-question `/resources/faq/` page was checked afterwards and is untouched at 860px. (2) Answers can carry two inline marks, `**bold**` and `__underline__`, escaped first so they are the only markup an answer can produce; David asked for "your" bold and underlined in the last line of question five, which renders as `<strong><u>your</u></strong>`. The FAQPage structured data strips the marks rather than rendering them, so search engines get clean text. (3) Two pricing facts were filed in `Facts/about-hi/pricing.md`: the $2,000 to $6,000 range David quotes matches the approved guidance already there, but the **two business day proposal turnaround** is new and was recorded with attribution, since it is a service commitment nothing in the brain had. Two things flagged back to David rather than silently fixed, per the standing rule that his copy ships verbatim: question two has no question mark, and question five reads "but the you should more directly consider". Also noted: this replacement removed the SIRS-cadence FAQ answer he had earlier decided to leave alone, since it lived in one of the three questions being replaced. 40 pages, QA clean.

David asked for the same top-to-bottom reading he chose for the level cards. Checklists were a fixed two-up grid capped at 980px, and the same component renders the SIRS statutory list on another page, so rather than change the shared rule this adds an opt-in `columns` on the checklist section (the pattern the card grids already use) and a `.checklist-1` rule that goes single column and drops the 980px cap. Measured at 1280px: five rows, one item each, 1120px wide, exactly matching the level cards above; at 768px the same, at 713px. The SIRS checklist was checked afterwards and is untouched, still two-up at 476px per column inside its 980px cap. 40 pages, QA clean.

David answered the flag raised earlier the same day: "I am confirming that the majority of Reserve Studies I've completed are in Florida, although I do not know the exact figure." Because he is the primary source on his own record, that is now a filed fact in `Facts/about-hi/company-overview.md` under a new dated section, along with the note that it resolves rather than contradicts `florida-market-research.md`, which records the 500+ as nationwide: the studies span his whole career and most of them happened in Florida. Both entries are true. In the same breath he decided the qualifier should not appear on the site: "for consistency, let's remove the language ... to be consistent throughout the website." So `(with the majority completed in Florida)` came out of the deliverable item on `/services/reserve-studies/` and the citable stat is back to a plain "500+ Reserve Studies over the past 10 years" everywhere. The fact file records both halves, the fact and the instruction not to publish it, so a future session does not helpfully add the qualifier back. Swept the brain for other copies of the phrasing: none outside the fact file and the dated changelog and hub records. This was new information rather than an answer to a numbered `QUESTIONS-FOR-DAVID.md` item, so nothing was checked off; noted in `Log/work-log.md` instead. 40 pages, QA clean.

David's pass on the deliverable checklist, his copy verbatim. He asked for it on "the Services page", but the quoted strings only exist in the checklist on `/services/reserve-studies/`, which is where the edit was made. Five items now instead of six: "Condition Assessment from Observation" was removed outright, and the rest were retitled and rewritten. The inventory item now promises context rather than quantities (photos, location, maintenance recommendations, what is excluded and why); the funding plan item names the actual range, Baseline to Fully Funding, and the supplemental Excel scenario tools; the post-delivery item became "Continued, Intentional Support" and now offers Board presentations, not just answering questions. **Needs David's confirmation:** the new life-and-cost item claims "over 500 Reserve Studies completed (with the majority completed in Florida) over the past 10 years." The 500+ and 10-year halves are the approved citable stat in `Facts/about-hi/company-overview.md`, but the Florida-majority half is new and is in tension with `Facts/about-hi/florida-market-research.md`, which records the 500+ as **nationwide**. It shipped because David is the primary source for his own record, and it was flagged back to him to confirm so the answer can be filed. 40 pages, QA clean.

David did not like the 2x2 block the four level cards formed, so the section moved to a single column and the levels read straight down, Level 1 to Level 4. Needed a new `.card-grid-1` rule, declared after the 980px breakpoint block so it holds at every width rather than snapping back to two columns on tablets. Verified at 1280px and 768px: four rows, one card each, full container width, no horizontal overflow.

Second pass on `/services/reserve-studies/`, David's copy verbatim. The comparison table gained a fourth column (Full, Update - With Site Visit, Update - No Site Visit, New Construction) and every cell was rewritten; "Condition assessment" became plural and now answers Yes/Yes/No/No instead of prose. The SIRS cadence note under the table was removed, since SIRS has its own page. Replacing the old "Communities That Are Not Built Yet" split section: a new **"The Reserve Study Process"** section carrying the nine-step preparation procedure from the CAI Reserve Study Standards, redrawn from the snapshot David supplied. Built as a new `diagram` section type plus `reserveProcessSvg()` in `src/illustrations.mjs`, drawn as the same left-to-right, right-to-left, left-to-right snake as the source, with the reading order held in a small cell map so grid position and step number can differ on the middle row. The source art is dark boxes on white; because this section lands on the page's Deepwater band, the boxes are styled through CSS custom properties so they invert to the brand's dark-glass spec with Paper type there and would render as Deepwater boxes on any light section. Spark carries the chevrons only, never type, on either ground. Verified in the browser: nine boxes, sixteen chevron strokes, no chevron overlapping a box, the widest label 162 units inside a 186-unit usable box width, and the figure scrolling inside its own container at 375px with no page-level horizontal scroll, the same rule the comparison tables follow. The page description was also corrected from "three" to "The four Reserve Study levels for Florida communities". 40 pages, QA clean.

David's pass on `/services/reserve-studies/`, his copy in verbatim throughout. The H1 became "A Reserve Study Your Board, Management, and Owners Can Understand!" and the lede was rewritten to name associations, communities, and properties and to frame the two questions as what is predictably coming and how much should be collected. The Florida hero aside was dropped here for the same reason as on `/services/`, so two of the 40 pages now opt out and 38 keep it. The levels section is the substantive change: "Three Study Levels for Existing Communities" became "Four Levels of Service For Reserve Studies", the framing intro line was removed, all three existing cards got new titles and new body copy, and a fourth card was added for preliminary studies on communities not yet constructed. Two supporting changes made this possible: cards now accept an optional `number` so the eyebrow can read "Level 1" instead of the automatic "01" (it still renders uppercase Harbor mono, unchanged styling), and the section is set to two columns, because four cards in the default three-up grid would leave a single orphan on the second row. Measured at 1280px: a clean 2x2, 550px per card, rows equal height, no horizontal overflow. 40 pages, QA clean. **Not pushed:** held per David's 2026-08-09 standing instruction that nothing deploys without his explicit word.

David's second pass on the copy he wrote earlier the same day, in verbatim. The audience line widened from "other property decision makers" to "Association Boards, Property Managers, and Unit Owners, and/or other property representatives", the promise sharpened from "highest-quality reports and service in the Florida Reserve Study industry" to "highest-quality, yet clearest reports directly to those needing reserve planning guidance in Florida", and the list of differentiators gained a new item: a supplemental Excel-based "what if" file for testing. Structurally, David's text carried a blank line before "How?", so it is now two entries in the section's `text` array rather than one, which renders as two paragraphs; the section is three paragraphs total. The straight quotes around "what if" pass through `escapeHtml` as `&quot;` and render as ordinary quotes, verified in the browser. "straight forward" remains as David writes it, flagged to him once already and deliberately not corrected. 40 pages, QA clean.

David supplied the replacement copy for the split section on `/services/` directly, so it is in verbatim. The first paragraph reframes the CAI Reserve Study Standards as the shared foundation every provider should follow and cite openly, rather than as a Homeowner Insights, LLC credential claim. The second is the founding-story paragraph in David's own voice ("Now here's where we come in"), naming the three things the reports do differently: clear explanations of calculations and findings, Executive Summaries that can be shared directly at meetings, and funding plan options presented as board choices rather than one verdict. The aside answer became "We can help with that. Just provide your property's name and address...", and its "Request a Recommendation" link moved from `/request-a-proposal/` to `/contact/`, which suits an ask that is a conversation rather than a scoped fee request. Two mechanical notes: a double space in "founded on the desire" was collapsed to one (HTML collapses it either way, so nothing renders differently), and "straight forward" is left exactly as David wrote it and flagged back to him rather than silently corrected to "straightforward", per the standing rule that his own copy ships verbatim. Not changed: the H2 still reads "Every Engagement Follows the Same Framework". A rewrite to "Every Engagement Starts With the Same Foundation" appeared in an earlier message David then withdrew, and it was not in the direction he actually gave, so it was left alone and raised with him. 40 pages, QA clean.

David's third pass on `/services/`. The section head became "Choose The Option That Would Best Serve Your Property To Learn More!", and two of the three buttons went singular: "Reserve Study" and "Structural Integrity Reserve Study" (labels only; the hrefs and the destination pages keep their plural routes, so nothing else on the site had to move). The bigger change is the removal of the "Side by side" section and its four-engagement comparison table: it compares Reserve Study engagements only, so on an overview page that also offers SIRS and consulting it did not speak to all three services. The equivalent table on `/services/reserve-studies/` stays exactly as it was, verified after the build (4 columns, 4 rows, untouched), because that page is where the comparison actually belongs. A consequence worth recording: `/services/` is now down to two body sections, so it no longer picks up a mid-page Deepwater band. That is consistent with the brand sheet's marketing page rhythm rather than a violation of it, since the rule places a band every fourth section and a two-section page never reaches one; the page still opens on the full-bleed Deepwater hero and closes on the Midnight CTA panel and footer. 40 pages, QA clean.

David reviewed the compact cards from earlier today and did not like them visually, so the card framing is gone entirely: the three service names are now simply three buttons, each linking to its own page. A new `type: "buttons"` section renderer does this (a section head plus a `.button-row` of `.button-primary` links), and the `variant: "compact"` card code and its CSS were deleted rather than left sitting unused, since nothing else on the site used them; the old version is in git history if it is ever wanted back. Measured: at 1280px all three sit on one row (174px, 322px, 198px wide, 51px tall) with Harbor `#005F61` grounds and Paper text; at 768px they wrap two-then-one; at 375px they go full width and stack, with `white-space: nowrap` released at that breakpoint so a long name like "Structural Integrity Reserve Studies" wraps inside its button instead of overflowing. No horizontal page scroll at any width. 40 pages, QA clean.

David's second pass on `/services/`. Three changes, all his call. (1) The site-wide "Florida Is the Entire Focus!" hero aside was redundant on this page, where the H1 already reads "Reserve Planning Services for Florida Communities." Rather than delete the shared object and strip it from all 40 pages, `renderHero` now honours `heroAside: false` per page and drops the whole second hero column when there is no figure or aside, so the copy takes full width instead of sitting beside an empty gutter. Verified: 39 pages still carry the aside, only `/services/` does not. (2) The section head became "Choose The Option That Would Best Serve Your Property." (3) The three service cards lost their descriptive paragraphs and their "Explore ..." text links; each is now the title plus a "Learn More" button, since the card's only job is to route the reader to the service page that carries the detail. Implemented as a new `variant: "compact"` on the cards section, not a rewrite of the shared card, so the other 111 cards on the site are byte-identical. Compact cards render as full-width stacked rows rather than three columns: the titles are long ("Structural Integrity Reserve Studies") and a third-width column would wrap them to four lines beside the button, which is the opposite of the shorter box David asked for. Measured at 1280px: every card 83px tall, title on one line, button vertically centred 21px off the right edge, no overlap. At 375px the button drops full-width below the title with no horizontal overflow. Buttons use Harbor (`#005F61`), not Spark, so the light-ground rule holds. 40 pages, QA clean.

Pushing the lede change surfaced a GitHub notice that the repository had moved from `damianvonfrankjr-coder/hoi-brain` to `djvonfrank/hoi-brain`. The push still worked because GitHub redirects renamed repos, but redirects stop working the moment the old owner name is reclaimed by anyone, so nothing should rely on them. David asked for it fixed. Changed: the local `origin` remote (verified with `git ls-remote`, which resolved to the same commit), CLAUDE.md section 8 (with AGENTS.md regenerated), `GITHUB_BASE` in `Hub/build-hub.mjs` (this also cleared a stale TODO claiming the repo was not connected yet, which stopped being true on 2026-07-31), and the clickable repo links in `Drafts/DJ/SETUP-GITHUB-CLOUDFLARE.md` and both versions of the David meeting guide. Deliberately left alone: dated historical records in `Log/`, `Archive/`, and the older DJ planning drafts, which correctly record the name as it was at the time, and the sibling brain's separate repo reference. Cloudflare Pages follows the rename on GitHub's side, so both deployments keep building; the site preview was reverified green after the push.

David rewrote the subheader on `/services/` himself: the old line ("Whether your association needs its first study, a statutory SIRS, or a second opinion on a plan you already have, the work follows the same standard: clear scope, disclosed methodology, plain English.") described the firm's process; the new line ("Whether your property needs its first Reserve Study (or SIRS), an update to a pre-existing Reserve Study, or a second opinion on your current plan, we're here to help you today!") speaks to the reader's situation and names the three real entry points, including the study-update case the old line left out. One-line change in `Website/homeowner-insights/src/site-data.mjs`; site rebuilt, 40 pages, QA clean. Separately: Node.js was not installed on David's Windows machine, so the brain's build and QA scripts could not run locally at all. Installed Node 24.19.0 LTS via `winget install OpenJS.NodeJS.LTS --scope user`; it lands as a winget portable package and its shim directory is on the user PATH, so `node` works in any new shell (existing shells need a restart to pick it up).

When the Pages projects were git-connected earlier today, `published-pages.md`, the setup checklist, and the changelog were all updated, but CLAUDE.md section 8 was missed: it still described deployments as manual wrangler uploads and said push-to-deploy "comes when the Pages projects are git-connected." Section 5's ship row had the same "once GitHub is connected" hedge. David's Claude Code session flagged the contradiction between the commit message and the constitution while onboarding him, which is exactly the stale-reference sweep the guardrails ask for, working from the other side. Both passages now state the current reality: both projects are git-connected, every push to `main` rebuilds and redeploys, the site's QA runs inside the build so a violation fails the deploy, and wrangler remains a fallback rather than the normal path. AGENTS.md regenerated. Also corrected in the same pass: the first-run setup prompt in both meeting guides assumed a Mac, and David is on Windows, so it now says "this computer" and accounts for the repo already being cloned.

DJ asked for the two sites to work the way the GreenRoom projects do. Cloudflare turned out to allow adding a Git connection to an existing direct-upload project, so this was done WITHOUT changing either pages.dev URL, which matters because David already has both links. `hoi-site-preview` builds with `node build.mjs && node qa.mjs` from root directory `Website/homeowner-insights` publishing `dist`; `hoi-brain` builds with `node Hub/build-hub.mjs` from the repo root publishing `Hub`. Both track branch `main` with automatic deployments enabled. A useful consequence: the site's QA script runs inside the Cloudflare build, so a rule violation (a banned dash, a sibling-brand name, a broken internal route, a retired palette hex) now fails the deployment rather than publishing a bad page. Manual `npx wrangler pages deploy` still works as a fallback but is no longer the normal path: commit and push instead.

DJ asked for David to be able to edit the hosted sites, and handed over the invite page. Invited `davidwhannjr@gmail.com` to DJ's Cloudflare account with the **Workers Platform Admin** role rather than Administrator or Super Administrator: it grants full create, read, update, and delete across the Workers and Pages platform, which is exactly what editing and deploying `hoi-site-preview` and `hoi-brain` requires, while deliberately excluding billing, account settings, and membership management. Status is Pending until David accepts from his email. The meeting guide's Part 2 previously advised deferring Cloudflare; both the HTML and markdown versions were updated to reflect that the invite is sent and to explain what the role does and does not allow. Revoke or change at Manage Account, Members, the row menu.

DJ asked for the old site to live alongside the new one, in the same repository, so that he, David, or an AI can lift things from it without opening the old workspace. Archived to `Archive/2026-07-30-v1-website/`: the complete v1 build system in `source/` (build and QA scripts, `src/` with the site data, 15 cities, 13 post modules, illustrations and the retired `studio.mjs`, the Dark Waters `styles.css` and `site.js`, the `static-studio/` overlay, and the form-handler Worker) plus `rendered-pages/`, all 40 pages exactly as they render live at hi-site-preview.pages.dev, in their original route folders. Deliberately excluded: the blog images, four sample PDFs, and the CAI photo, all verified byte-identical to the copies already in the v2 site's static folder, which kept about 19 MB of duplicate binaries out of the repo (the archive README says how to restore them for a full rebuild). A routing row was added to CLAUDE.md so the AI reaches for the archive on its own when asked to compare or lift from the old site, with the standing rule that the retired palette, fonts, and mark never come back across. Total added: 1.4 MB.

DJ reviewed the live preview on his phone and called it: too much light blue everywhere, almost no variation, and the brand navy barely present outside the footer. He was right. Paper, white, and Mist sit within a few percent of each other, so every surface on a page was effectively the same value and Deepwater only ever appeared as text. Fixed with colour only, no structural or layout changes: (1) every page hero is now a full-bleed Deepwater to Midnight band with a Spark eyebrow, Paper headline, and the existing figure and aside cards floating on it as white panels; (2) the section rhythm changed from Paper/white/Mist/white to Paper/white/DARK/white, so every page carries a Deepwater band with dark-glass surfaces, Shoal numerals, and one Spark wash; (3) asides became Deepwater cards instead of near-invisible tinted boxes; (4) comparison table head rows became Deepwater with Shoal row labels; (5) a 44px Spark rule now opens every section head and a 3px Spark edge sits under the trust strip, carrying the accent through the long light stretches; (6) process steps gained a Harbor top edge and the statute band a Harbor rule. Spark still never carries type on a light ground, and the dark bands use the brand sheet's documented dark glass, so nothing here breaks the system: the rhythm is now written into brand-sheet.md's Contexts section as the marketing page rule. Site rebuilt (40 pages, QA clean) and redeployed to hoi-site-preview.pages.dev.

DJ asked for everything to be meeting-ready by morning. Done overnight: (1) the brain pushed to the new private repo `damianvonfrankjr-coder/hoi-brain` (full phased history); (2) `GITHUB_BASE` stamped into the hub build so the asset directory's GitHub links resolve, hub rebuilt and redeployed; (3) CLAUDE.md §8 updated to the real infrastructure and AGENTS.md regenerated; (4) the meeting run-of-show written at `Drafts/DJ/2026-07-31-david-meeting-guide.md` (accounts, Claude Code connection with a four-prompt acceptance test, four live demos, a five-idea crash course, and David's printable cheat sheet), with `SETUP-GITHUB-CLOUDFLARE.md` updated to show what's done vs. remaining. One item needs DJ's phone and could not be done by the AI: sending David's collaborator invite (GitHub sudo-mode 2FA); it is step one of the guide's pre-flight, with the direct URL.

DJ asked for both builds to go live so he and David can review them. Wrangler was authorized on DJ's Cloudflare account (OAuth, approved by DJ in browser), then two new Pages projects were created and deployed by direct upload: the site at https://hoi-site-preview.pages.dev (project hoi-site-preview, 40 pages, draft gates verified live: blocking robots.txt, noindex, visible banner) and the hub at https://hoi-brain.pages.dev (project hoi-brain, unlisted, noindex). SITE_ORIGIN in Hub/build-hub.mjs now points at the live site, so the hub's Product grid links resolve. These are manual-upload deployments: after any change, rebuild and rerun the wrangler deploy command recorded in Facts/reference-index/published-pages.md; push-to-deploy arrives with the GitHub connection (Drafts/DJ/SETUP-GITHUB-CLOUDFLARE.md). The v1 previews remain live and untouched.

DJ asked for the copied-over hub to shed the old Dark Waters look and wear the new brand. What was built: (1) `_shared/brain.css` plus the tools stylesheets rewritten on the v1.0 tokens (Paper ground, Deepwater ink, Harbor primary, Shoal on dark, mono eyebrows), with the three Google Fonts loaded in the chrome; (2) new byte-identical chrome on all ten chromed pages with the horizontal-dark lockup, a Brand System nav link, and the retired sibling-brand page removed; (3) the home page gained a build-regenerated "What Changed Today" table and "The Product" grid stamped from a single SITE_ORIGIN constant (localhost preview until deploy); (4) Brand OS rebuilt from brand-sheet.md v1.0 (mark, measured palette, type, copy rules, Funding Curve, PROPOSED banner for HI-16); (5) Skills & Add-Ons restructured into Installed / Running / Queued-with-triggers; the Prompt Gallery gained the pinned First 5 strip and lost its two-brand plumbing; (6) the 22 generator tools reseeded via `hi-defaults.js` on the bumped `fbt.brandkit.v2` key with new palette, tagline, and v1.0 logo data URLs; (7) `build-hub.mjs` now syncs the logo suite from Brand/ on every build, parses the new changelog format, regenerates the marker blocks, and QAs for chrome identity, dashes, sibling names, and retired-palette hexes. `node Hub/build-hub.mjs` exits 0.

DJ asked for the Homeowner Insights brain to be rebuilt on the layout proven on the GreenRoom build, single-brand, with the ground-up new brand from Claude Design. What was built: (1) this workspace, scaffolded fresh with the routing-table CLAUDE.md, generated AGENTS.md, David-facing README, reset ROADMAP, and the carried-forward QUESTIONS-FOR-DAVID (HI-1 through HI-15, plus new HI-16 brand approval and HI-17 collateral export); (2) every Homeowner Insights fact, rule, tone, audience, channel style, template, skill, and review-queue draft migrated from the v1 brain with paths updated to the plain-English folder scheme and sibling-company operational content removed (the sibling has its own brain now); (3) Brand System v1.0 installed under Brand/homeowner-insights/ (brand-sheet.md and ui-pattern-library.md promoted as the token and component sources of truth, stable-named logo working set, full kit tree brand-system-v1.0/); (4) the website generator carried over minus the retired Studio variant and reskinned light-first on the new tokens, all 40 pages and every QA rule intact; (5) the hub rebuilt on the new brand with the 22-tool suite reseeded and the full Brand System document added as its own page. The v1 brain at ~/Downloads/Homeowner Insights Brain is untouched and its previews stay live. What's blocking: David's review of the new brand (HI-16), then GitHub + Cloudflare connection (checklist in Drafts/DJ/SETUP-GITHUB-CLOUDFLARE.md).