What to do next on this site

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

GOAL (on changeaustin.com)
Lock down sensitive data — nothing private is publicly reachable — on the site changeaustin.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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site changeaustin.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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Make the homepage genuinely distinctive — kill any generic-template feel — on the site changeaustin.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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Verify HTTPS, security headers & a safe Agents-First surface — on the site changeaustin.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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Add an interactive tool and an email capture for Civic & Government — on the site changeaustin.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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Build the definitive Civic & Government cornerstone guide — on the site changeaustin.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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Publish: The local ballot measures and deadlines coming up — on the site changeaustin.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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Publish: How to actually get a city response — the channels that work — on the site changeaustin.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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Ten district pages tracking local issues — on the site changeaustin.com.

WHY IT MATTERS
Build a page per council district tracking its live issues — rezonings, road projects, parks bonds — each item cited to city documents or published coverage. District-plus-issue searches are underserved, and district pages give every Austin neighborhood association a specific, relevant page to link rather than a generic homepage. (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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Weekly plain-English council agenda preview — on the site changeaustin.com.

WHY IT MATTERS
Every week, summarize the posted Austin City Council agenda in plain English with links to the official backup documents, published before the Thursday meeting. Residents search agenda items when local news mentions them, and a consistent, early, linked preview becomes the page neighborhood groups circulate. (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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Ballot-measure explainers each election cycle — on the site changeaustin.com.

WHY IT MATTERS
Before each election, publish neutral explainers for every Austin ballot proposition: what it does, who supports and opposes it per published statements, and what it costs per city fiscal notes. Cross-link austinmayor.com and austinhangout.com so the network's civic cluster reinforces itself during peak search weeks. (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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Publish: Open-data sources residents can use — on the site changeaustin.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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
AdSense on explainers, not issue trackers — on the site changeaustin.com.

WHY IT MATTERS
Run shared AdSense pub-7759195213529699 on evergreen explainers — how council works, how to testify, bond basics — while keeping district issue trackers ad-free. The explainer pages carry long research dwell times that earn, and the clean trackers preserve the neutrality that makes civic sites linkable. (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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Publish: Neighborhood organizing playbooks — on the site changeaustin.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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Civic digest newsletter with sponsor slot — on the site changeaustin.com.

WHY IT MATTERS
Install the wholetech.com/newsletter/widget.js signup and send a weekly digest of council actions and district updates. Once subscriptions are real, offer one labeled local sponsor slot per issue to an Austin bookstore or nonprofit. All signup notifications arrive as Gmail DRAFTS, 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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Austin civics bookshelf via Amazon tag — on the site changeaustin.com.

WHY IT MATTERS
Curate a disclosed shelf of books on Austin history, Texas municipal government, and urban policy through Amazon Associates tag colinfirthfan-20, placed on the explainer pages. Readers digging into how their city works are exactly the audience that buys civic history, and the label keeps trust intact. (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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Deepen the main Civic & Government guide with current data and examples — on the site changeaustin.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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Zoning-map color-block art direction — on the site changeaustin.com.

WHY IT MATTERS
Art-direct with Austin's planning visual language: zoning-map color blocks as section backgrounds, street-grid linework dividers, and public-notice poster typography for headlines. Anyone who has read a rezoning sign on an Austin curb will recognize the vocabulary instantly, which is exactly the civic literacy the site teaches. (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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Add an FAQ answering the top questions in Civic & Government — on the site changeaustin.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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Agenda items styled as official notices — on the site changeaustin.com.

WHY IT MATTERS
Render each tracked agenda item as a compact official-notice card — case-number header, posting-date stamp, and status line — mirroring the city's own notice format. The document-styled cards make screenshots self-explanatory when shared to neighborhood Facebook groups and Nextdoor threads, which is where Austin civic traffic lives. (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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
FAQ schema on participating in council — on the site changeaustin.com.

WHY IT MATTERS
Add FAQ schema answering how to sign up to speak at Austin City Council, when agendas post, and how to contact each district office, sourced from the city clerk's official pages. Ship both sitemaps and ping IndexNow so answer engines quote the procedural answers directly. (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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Sortable issue-tracker worksheet with status — on the site changeaustin.com.

WHY IT MATTERS
Build the master issue list as an alldomains-model worksheet: sticky-number sortable table with district, issue, status, next-council-date, and source columns, rows expanding to detail cards. Chips for district and topic let a resident filter to their block in seconds — the tool local reporters will cite. (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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Apply a WT-Skins kit to lift the design and Agents-First score — on the site changeaustin.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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Keep the live / news feed updated on cadence (2×/day) — on the site changeaustin.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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Submit updated URLs via IndexNow and refresh the sitemap — on the site changeaustin.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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Add Article + FAQ structured data — on the site changeaustin.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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Strengthen internal links between the core, /sources/ and this worksheet — on the site changeaustin.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: changeaustin.com (live at https://changeaustin.com/), a Civic & Government site in the WholeTech network, served from /var/www/changeaustin.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for changeaustin.com and no other site — make all changes on changeaustin.com. Act like a senior editor and web engineer who knows the Civic & Government niche cold.

GOAL (on changeaustin.com)
Refresh the /videos/ playlist with current, embeddable uploads — on the site changeaustin.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.

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

GOAL (on changeaustin.com)
Verify affiliate links and ad placement resolve correctly — on the site changeaustin.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.