What to do next on this site

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Lock down sensitive data — nothing private is publicly reachable — on the site changebastrop.com.

WHY IT MATTERS
Make sure a logged-out visitor or bot cannot reach anything sensitive on this site: /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404, never 200. Then scan the served HTML, JS, and JSON for leaked keys, tokens, internal emails, or personal data and remove them.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Make the homepage genuinely distinctive — kill any generic-template feel — on the site changebastrop.com.

WHY IT MATTERS
Give the homepage a clear point of view, a memorable hero, and real utility above the fold. A distinctive, intentional design lifts trust, time-on-page, and the Agents-First score out of generic-template territory.

HOW TO APPROACH IT
1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in Civic & Government — then build exactly that.
2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway.
3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics.
4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The page is genuinely the strongest Civic & Government resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Build the definitive Civic & Government cornerstone guide — on the site changebastrop.com.

WHY IT MATTERS
Create the single most useful, authoritative page on Civic & Government anywhere — the resource the whole site points to. Deep, current, expertly structured, and link-worthy. This anchors the site's authority and is the page most likely to earn rankings and citations.

HOW TO APPROACH IT
1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in Civic & Government — then build exactly that.
2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway.
3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics.
4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The page is genuinely the strongest Civic & Government resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site changebastrop.com.

WHY IT MATTERS
Assume a determined automated, AI-driven attacker. Enforce HTTPS, add a sensible Content-Security-Policy plus the standard security headers, eliminate open redirects and reflected user input, validate and rate-limit any form, and ensure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data — never internal or personal information.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Verify HTTPS, security headers & a safe Agents-First surface — on the site changebastrop.com.

WHY IT MATTERS
Confirm the certificate is valid and HTTPS is forced, the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, CSP), and the Agents-First endpoints expose only public, non-sensitive information — trustworthy to humans and safe for the agents reading it.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Add an interactive tool and an email capture for Civic & Government — on the site changebastrop.com.

WHY IT MATTERS
Build one genuinely useful interactive element for Civic & Government (a calculator, checklist, finder, or quiz) plus a tasteful email capture. Tools earn repeat visits, backlinks, and a first-party audience the site actually owns.

HOW TO APPROACH IT
1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in Civic & Government — then build exactly that.
2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway.
3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics.
4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The page is genuinely the strongest Civic & Government resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Publish: The local ballot measures and deadlines coming up — on the site changebastrop.com.

WHY IT MATTERS
Trending angle in Civic & Government. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Civic & Government reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Publish: How to actually get a city response — the channels that work — on the site changebastrop.com.

WHY IT MATTERS
Trending angle in Civic & Government. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Civic & Government reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Track documented Bastrop growth arrivals — on the site changebastrop.com.

WHY IT MATTERS
Maintain a running, dated log of publicly reported industrial and infrastructure arrivals in Bastrop County — the Highline fiber buildout, aerospace and tunneling facilities, new subdivisions — each entry cited to filings or published coverage. Bastrop growth searches are surging and no one maintains a sourced chronology. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Commissioners-court and city-council coverage beat — on the site changebastrop.com.

WHY IT MATTERS
Post short, plain-English recaps of Bastrop City Council and County Commissioners Court decisions with links to agendas and minutes, in the terse austinmayor.com news template. Small-county coverage has almost no competition, so consistent recaps quickly become the search result for every contested local decision. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Cross-link the bastropfiber.com fiber guide — on the site changebastrop.com.

WHY IT MATTERS
Give the Highline $43.1M BOOT II fiber story a permanent explainer that links deep into bastropfiber.com for address-level detail, and take a reciprocal link back. The two sites cover the county's biggest household-level change from different angles, and the interlink strengthens both in Bastrop-specific search. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Publish: Open-data sources residents can use — on the site changebastrop.com.

WHY IT MATTERS
Trending angle in Civic & Government. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Civic & Government reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Labeled featured listings for local businesses — on the site changebastrop.com.

WHY IT MATTERS
Offer Bastrop businesses a clearly labeled featured card on relevant growth pages — a title company on the development tracker, a nursery on the new-resident guide — for a modest flat fee. Growth coverage attracts exactly the newcomers those businesses want, keeping the sell honest and local. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Publish: Neighborhood organizing playbooks — on the site changebastrop.com.

WHY IT MATTERS
Trending angle in Civic & Government. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Civic & Government reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
New-resident newsletter with sponsor slot — on the site changebastrop.com.

WHY IT MATTERS
Use wholetech.com/newsletter/widget.js to build a moving-to-Bastrop digest covering fiber availability, school updates, and development news. Once the list is real, sell one labeled sponsor slot per issue to a local realtor or business. Signup notifications generate Gmail DRAFTS only, never auto-sent. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Courthouse-limestone and Lost Pines art direction — on the site changebastrop.com.

WHY IT MATTERS
Art-direct with Bastrop's real palette: limestone-and-brick textures from the 1883 courthouse and Main Street storefronts, loblolly pine-green accents from the Lost Pines, and hand-painted storefront lettering for headings. The county's small-town-meets-forest identity should be visible before a single word is read. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Deepen the main Civic & Government guide with current data and examples — on the site changebastrop.com.

WHY IT MATTERS
Audit the flagship page; replace anything stale, add concrete numbers and a clear next step. Depth is what separates this from a thin template.

HOW TO APPROACH IT
1. Audit the flagship Civic & Government page and list exactly what is stale, thin, or vague.
2. Replace stale material with current data, add concrete real examples, tighten the structure, and add a clear next step for the reader.
3. Cross-link to /sources/ and the most related pages.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Depth and accuracy match the best competitor page in Civic & Government.
- No filler and no fabricated specifics — every number is current and sourced.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
AdSense on growth explainers and guides — on the site changebastrop.com.

WHY IT MATTERS
Place shared AdSense pub-7759195213529699 on the evergreen explainers — what is coming to Bastrop, new-resident guides, fiber background — while keeping council recaps clean. Explainer pages draw the long out-of-county research sessions that monetize, and the clean news pages protect the site's local credibility. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
FAQ schema on Bastrop growth questions — on the site changebastrop.com.

WHY IT MATTERS
Add FAQ schema answering is Bastrop growing, what companies are moving to Bastrop County, and when does fiber reach my area, with answers citing census figures, filings, and the Highline buildout timeline. Ship both sitemaps and ping IndexNow so answer engines surface the sourced responses. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Historic downtown map as navigation graphic — on the site changebastrop.com.

WHY IT MATTERS
Draw a simple illustrated map of downtown Bastrop — courthouse square, Main Street, the Colorado River crossing — and use it as a visual navigation element linking to coverage areas. A map-first interface fits a site about place and change, and residents instantly orient themselves on it. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Add an FAQ answering the top questions in Civic & Government — on the site changebastrop.com.

WHY IT MATTERS
Pull the real questions people ask in Civic & Government and answer them plainly. Mark up with FAQ schema for rich results.

HOW TO APPROACH IT
1. Audit the flagship Civic & Government page and list exactly what is stale, thin, or vague.
2. Replace stale material with current data, add concrete real examples, tighten the structure, and add a clear next step for the reader.
3. Cross-link to /sources/ and the most related pages.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Depth and accuracy match the best competitor page in Civic & Government.
- No filler and no fabricated specifics — every number is current and sourced.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Development-tracker worksheet, sortable by status — on the site changebastrop.com.

WHY IT MATTERS
Build an alldomains-style worksheet of every tracked project: sticky-number sortable table with project, type, location, status, and source-link columns, rows opening to detail cards with a dated update log. One sortable county-wide tracker becomes the reference tool realtors, reporters, and residents all bookmark. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Apply a WT-Skins kit to lift the design and Agents-First score — on the site changebastrop.com.

WHY IT MATTERS
The page looks generic without a kit. Roll the cluster's kit (snapshot the old design first) to get the AF score into the 90s.

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Keep the live / news feed updated on cadence (2×/day) — on the site changebastrop.com.

WHY IT MATTERS
Confirm the cron is publishing fresh, attributed Civic & Government items and pinging IndexNow each run.

HOW TO APPROACH IT
1. Confirm or set up the auto-publishing /live/ or /news/ feed for Civic & Government: attributed, links out, and running on a 2x/day cadence.
2. Make sure each run pings IndexNow and the items are genuinely fresh and relevant.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The feed publishes fresh, correctly-attributed Civic & Government items on schedule and is discovered quickly.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Submit updated URLs via IndexNow and refresh the sitemap — on the site changebastrop.com.

WHY IT MATTERS
Ping IndexNow for new and changed pages so they're discovered fast; confirm the sitemap lists /act/, /sources/, /videos/.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Add Article + FAQ structured data — on the site changebastrop.com.

WHY IT MATTERS
Schema.org markup earns richer results and helps answer-engines cite the page correctly.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Strengthen internal links between the core, /sources/ and this worksheet — on the site changebastrop.com.

WHY IT MATTERS
A tight internal-link web spreads authority and keeps visitors moving through the site.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Verify affiliate links and ad placement resolve correctly — on the site changebastrop.com.

WHY IT MATTERS
Spot-check Skimlinks / Amazon links and AdSense units; remove anything broken or low-value.

HOW TO APPROACH IT
1. Make the change — verify affiliate links resolve, or add the shared affiliate + AdSense setup.
2. Keep commerce low-key and well-integrated: subtle in-content links, not a bolted-on banner block.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Links resolve and can earn, and placement is tasteful and does not hurt the reading experience.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: changebastrop.com (live at https://changebastrop.com/), a Civic & Government site in the WholeTech network, served from /var/www/changebastrop.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changebastrop.com and no other site — make all changes on changebastrop.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changebastrop.com)
Refresh the /videos/ playlist with current, embeddable uploads — on the site changebastrop.com.

WHY IT MATTERS
Swap any dead or stale videos; keep only authoritative, non-clickbait Civic & Government videos. Re-verify embeds.

HOW TO APPROACH IT
1. Find 6-10 authoritative, genuinely useful Civic & Government videos that ALLOW embedding — verify each embed actually plays.
2. Curate them on /videos/ with short context, and drop anything clickbait, get-rich-quick, or low-substance.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Every embed plays, the set is authoritative and on-topic, and the page reuses the site's GA + AdSense.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.