What to do next on this site

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

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

GOAL (on cargosolar.com)
Build the definitive Alternative Homes cornerstone guide — on the site cargosolar.com.

WHY IT MATTERS
Create the single most useful, authoritative page on Alternative Homes 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 Alternative Homes — 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 Alternative Homes 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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

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

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

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

GOAL (on cargosolar.com)
Add an interactive tool and an email capture for Alternative Homes — on the site cargosolar.com.

WHY IT MATTERS
Build one genuinely useful interactive element for Alternative Homes (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 Alternative Homes — 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 Alternative Homes 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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on cargosolar.com)
Container-home solar sizing guide with real math — on the site cargosolar.com.

WHY IT MATTERS
Publish a sizing guide that walks the actual watt-hour math for 20-foot and 40-foot container homes: typical loads, panel counts, controller sizing, and battery-bank capacity, with worked examples. Off-grid forums link calculation pages that show their arithmetic, and this exact query space has weak, ad-stuffed competition. (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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on cargosolar.com)
Publish: The 2026 cost-per-square-foot for tiny / container / ADU builds — on the site cargosolar.com.

WHY IT MATTERS
Trending angle in Alternative Homes. 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 Alternative Homes 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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on cargosolar.com)
Publish: Financing an alternative dwelling when banks balk — on the site cargosolar.com.

WHY IT MATTERS
Trending angle in Alternative Homes. 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 Alternative Homes 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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on cargosolar.com)
Verified /videos/ page of container solar builds — on the site cargosolar.com.

WHY IT MATTERS
Build a /videos/ page of container-home solar installation walkthroughs and time-lapse builds, embedding only videos that pass check-embed.mjs so nothing renders as a dead player. Real build footage is the content this audience binges, and a curated, working gallery earns return visits and video-rich search results. (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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on cargosolar.com)
Publish: Permitting and zoning wins that opened up this year — on the site cargosolar.com.

WHY IT MATTERS
Trending angle in Alternative Homes. 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 Alternative Homes 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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on cargosolar.com)
Texas off-grid permitting notes by county — on the site cargosolar.com.

WHY IT MATTERS
Compile county-by-county notes on solar permitting and inspection requirements for alternative dwellings in Texas, sourced strictly from official county and utility pages with links to each. Permitting confusion is the top blocker container-home builders discuss, and a maintained sourced reference becomes the page forums point newcomers to. (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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on cargosolar.com)
Publish: Off-grid power kits that paid back fastest — on the site cargosolar.com.

WHY IT MATTERS
Trending angle in Alternative Homes. 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 Alternative Homes 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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on cargosolar.com)
Amazon parts lists per system size — on the site cargosolar.com.

WHY IT MATTERS
For each worked sizing example, publish a disclosed parts list — panels, MPPT charge controllers, LiFePO4 batteries, wiring — with Amazon Associates links on tag colinfirthfan-20. Readers arriving from the sizing guide are at purchase intent, and matched-to-the-math parts lists convert far better than generic gear roundups. (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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on cargosolar.com)
Installer-quote form with draft-only notifications — on the site cargosolar.com.

WHY IT MATTERS
Add a request-an-installer-quote form capturing location and system size that writes a Gmail DRAFT notification for review, never auto-sending. Off-grid solar leads are valuable to regional installers, and once volume appears they can be referred through a disclosed arrangement, turning guide traffic into real recurring revenue. (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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on cargosolar.com)
AdSense across guide and permitting pages — on the site cargosolar.com.

WHY IT MATTERS
Run shared AdSense pub-7759195213529699 on the sizing guide, permitting notes, and FAQ pages where readers spend long research sessions. Keep parts-list pages affiliate-only so the two revenue streams never crowd one page, and keep ad density modest so the technical content stays the obvious star. (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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on cargosolar.com)
Wiring-schematic art direction throughout — on the site cargosolar.com.

WHY IT MATTERS
Style the site like an electrical install manual: schematic linework for section dividers, corrugated-steel texture panels, safety-yellow accent color, and spec-plate labels on data callouts. Every diagram drawn in proper one-line schematic style signals technical competence to an audience that judges sites by their wiring diagrams. (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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

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

GOAL (on cargosolar.com)
Calculator styled as charge-controller display — on the site cargosolar.com.

WHY IT MATTERS
Design the load calculator interface to mimic an MPPT charge controller's LCD readout — segmented digits, amber-on-dark display, labeled terminals for inputs. Builders already stare at these screens daily, so the familiar instrument styling makes the tool feel native to the trade rather than a generic web form. (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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on cargosolar.com)
Add an FAQ answering the top questions in Alternative Homes — on the site cargosolar.com.

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

HOW TO APPROACH IT
1. Audit the flagship Alternative Homes 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 Alternative Homes.
- 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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on cargosolar.com)
Interactive daily-load kWh calculator — on the site cargosolar.com.

WHY IT MATTERS
Build a client-side calculator where users toggle appliances, enter run-hours, and get daily kWh, recommended panel wattage, and battery capacity using the same formulas as the written guide. An interactive tool earns bookmarks and repeat sessions, and its result screen links straight to the matching Amazon parts list. (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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on cargosolar.com)
FAQ schema for battery-bank sizing questions — on the site cargosolar.com.

WHY IT MATTERS
Add FAQ schema answering the recurring questions — how many panels for a 40-foot container, what battery bank runs a mini-split overnight, AGM versus LiFePO4 — with answers drawn from the published math. Ship both sitemaps and ping IndexNow so answer engines pick up the calculated, 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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

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

WHY IT MATTERS
Confirm the cron is publishing fresh, attributed Alternative Homes items and pinging IndexNow each run.

HOW TO APPROACH IT
1. Confirm or set up the auto-publishing /live/ or /news/ feed for Alternative Homes: 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 Alternative Homes 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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

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

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

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

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

GOAL (on cargosolar.com)
Verify affiliate links and ad placement resolve correctly — on the site cargosolar.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: cargosolar.com (live at https://cargosolar.com/), a Alternative Homes site in the WholeTech network, served from /var/www/cargosolar.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for cargosolar.com and no other site — make all changes on cargosolar.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

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

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

HOW TO APPROACH IT
1. Find 6-10 authoritative, genuinely useful Alternative Homes 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.