What to do next on this site

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

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

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

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

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

GOAL (on pinest-tech.atxaisites.com)
Build the definitive Artificial Intelligence cornerstone guide — on the site pinest-tech.atxaisites.com.

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

GOAL (on pinest-tech.atxaisites.com)
Add an interactive tool and an email capture for Artificial Intelligence — on the site pinest-tech.atxaisites.com.

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

GOAL (on pinest-tech.atxaisites.com)
Publish: The latest frontier AI model tier and what it unlocks — on the site pinest-tech.atxaisites.com.

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

GOAL (on pinest-tech.atxaisites.com)
Publish: Agentic workflows a small business can deploy this month — on the site pinest-tech.atxaisites.com.

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

GOAL (on pinest-tech.atxaisites.com)
Anchor page in the atxaisites Austin AI cluster — on the site pinest-tech.atxaisites.com.

WHY IT MATTERS
Give Pinest Tech a clear role in the atxaisites.com constellation — link it from the cluster index and sibling demo sites with descriptive anchors ('agent build studio demo'). Cluster sites live or die on internal routing; an unlinked demo subdomain collects zero of the cluster's traffic. (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: pinest-tech.atxaisites.com (live at https://pinest-tech.atxaisites.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/pinest-tech.atxaisites.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for pinest-tech.atxaisites.com and no other site — make all changes on pinest-tech.atxaisites.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on pinest-tech.atxaisites.com)
Austin AI scene calendar and builder roundups — on the site pinest-tech.atxaisites.com.

WHY IT MATTERS
Maintain a monthly page of real Austin AI events — Capital Factory sessions, AI meetups, hackathons — with dates verified from organizers' public pages. Local-scene calendars earn recurring visits and links from event organizers themselves, and they root a demo-brand site in a real community. (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: pinest-tech.atxaisites.com (live at https://pinest-tech.atxaisites.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/pinest-tech.atxaisites.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for pinest-tech.atxaisites.com and no other site — make all changes on pinest-tech.atxaisites.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on pinest-tech.atxaisites.com)
Publish one worked agent-build teardown — on the site pinest-tech.atxaisites.com.

WHY IT MATTERS
Document a single real automation from the WholeTech network end-to-end — problem, agent design, cron wiring, outcome — as Pinest Tech's flagship case page, institutional byline per content rules. One honest teardown outranks ten capability-brochure pages for 'how to build an AI agent' queries. (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: pinest-tech.atxaisites.com (live at https://pinest-tech.atxaisites.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/pinest-tech.atxaisites.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for pinest-tech.atxaisites.com and no other site — make all changes on pinest-tech.atxaisites.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on pinest-tech.atxaisites.com)
Publish: Answer-engine optimization — getting cited by AI search — on the site pinest-tech.atxaisites.com.

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

GOAL (on pinest-tech.atxaisites.com)
Route consulting leads to atxengine.com pipeline — on the site pinest-tech.atxaisites.com.

WHY IT MATTERS
Add an engagement-inquiry form feeding the same funnel as atxengine.com, submissions written as Gmail DRAFTS for review — never auto-sent. Pinest Tech's job in the portfolio is surface area: another door into the one real studio offer, not a separate business to invent. (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: pinest-tech.atxaisites.com (live at https://pinest-tech.atxaisites.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/pinest-tech.atxaisites.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for pinest-tech.atxaisites.com and no other site — make all changes on pinest-tech.atxaisites.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on pinest-tech.atxaisites.com)
Publish: Practical AI guardrails and what to avoid — on the site pinest-tech.atxaisites.com.

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

GOAL (on pinest-tech.atxaisites.com)
Newsletter capture aimed at Austin builders — on the site pinest-tech.atxaisites.com.

WHY IT MATTERS
Embed wholetech.com/newsletter/widget.js with a scene-specific hook: 'Austin AI events and one real agent build, monthly'. A local-niche list is small but dense with potential clients and collaborators — worth far more per subscriber than a generic AI-news signup. Feature one subscriber project occasionally, with permission. (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: pinest-tech.atxaisites.com (live at https://pinest-tech.atxaisites.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/pinest-tech.atxaisites.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for pinest-tech.atxaisites.com and no other site — make all changes on pinest-tech.atxaisites.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on pinest-tech.atxaisites.com)
Pine-and-circuit motif: needles as trace routing — on the site pinest-tech.atxaisites.com.

WHY IT MATTERS
Own the name visually: evergreen-green palette on warm dark ground, pine-needle clusters drawn as PCB trace fans, a tree-line horizon rendered in circuit silkscreen linework, wood-grain texture behind code panels. It separates Pinest from every blue-gradient AI template instantly. Carry the motif into favicon and OG images. (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: pinest-tech.atxaisites.com (live at https://pinest-tech.atxaisites.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/pinest-tech.atxaisites.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for pinest-tech.atxaisites.com and no other site — make all changes on pinest-tech.atxaisites.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on pinest-tech.atxaisites.com)
Disclosed AdSense on AI explainer library — on the site pinest-tech.atxaisites.com.

WHY IT MATTERS
Run pub-7759195213529699 only on evergreen explainers (what agents-first means, agent-vs-chatbot, small-biz automation basics), keeping demo and inquiry pages clean. Explainer queries are the site's realistic search traffic; monetize the readers, not the prospects. Cap density at two units per page so the explainers keep the studio's polished feel. (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: pinest-tech.atxaisites.com (live at https://pinest-tech.atxaisites.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/pinest-tech.atxaisites.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for pinest-tech.atxaisites.com and no other site — make all changes on pinest-tech.atxaisites.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

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

GOAL (on pinest-tech.atxaisites.com)
Build /sources/ out to at least 10 authoritative links — on the site pinest-tech.atxaisites.com.

WHY IT MATTERS
Only 4 sources detected. A deep, current /sources/ page is a ranking and trust signal; pad it from the curated and popular catalogs.

HOW TO APPROACH IT
1. Open the source and confirm it is authoritative and genuinely relevant to Artificial Intelligence.
2. Add it to /sources/ with a one-line annotation explaining why it matters, placed in the right group, with no duplicates.

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 link works, is annotated and well-placed, and is a reference a real Artificial Intelligence expert would trust.
- 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: pinest-tech.atxaisites.com (live at https://pinest-tech.atxaisites.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/pinest-tech.atxaisites.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for pinest-tech.atxaisites.com and no other site — make all changes on pinest-tech.atxaisites.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on pinest-tech.atxaisites.com)
Add an FAQ answering the top questions in Artificial Intelligence — on the site pinest-tech.atxaisites.com.

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

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

GOAL (on pinest-tech.atxaisites.com)
FAQ schema answering Austin AI-services questions — on the site pinest-tech.atxaisites.com.

WHY IT MATTERS
FAQPage JSON-LD for 'who builds AI agents in Austin', 'what does a small-business agent automation cost range look like' (honest ranges only), 'what is agents-first'. Run af-deploy.py to 90+ so assistants fielding Austin AI-vendor questions have a citable local source. (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: pinest-tech.atxaisites.com (live at https://pinest-tech.atxaisites.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/pinest-tech.atxaisites.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for pinest-tech.atxaisites.com and no other site — make all changes on pinest-tech.atxaisites.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on pinest-tech.atxaisites.com)
Growth-rings diagram for the agent-maturity model — on the site pinest-tech.atxaisites.com.

WHY IT MATTERS
Present the build methodology as tree growth rings — core script, scheduled automation, monitored agent, self-correcting system — as one annotated ring diagram used consistently across pages. A single ownable diagram gives the demo brand an idea people remember and screenshot. (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: pinest-tech.atxaisites.com (live at https://pinest-tech.atxaisites.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/pinest-tech.atxaisites.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for pinest-tech.atxaisites.com and no other site — make all changes on pinest-tech.atxaisites.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on pinest-tech.atxaisites.com)
Live demo widget powered by existing network data — on the site pinest-tech.atxaisites.com.

WHY IT MATTERS
Embed a small working demonstration — e.g., a live feed rendering wholetech.com/api/stats.json into plain-English status lines — labeled 'an agent maintains this'. A running artifact on the homepage proves capability in five seconds, which no amount of service copy achieves. (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: pinest-tech.atxaisites.com (live at https://pinest-tech.atxaisites.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/pinest-tech.atxaisites.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for pinest-tech.atxaisites.com and no other site — make all changes on pinest-tech.atxaisites.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

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

GOAL (on pinest-tech.atxaisites.com)
Add a /live/ news feed for Artificial Intelligence — on the site pinest-tech.atxaisites.com.

WHY IT MATTERS
An auto-publishing, attributed Google-News feed keeps the site fresh daily and reuses the existing GA + AdSense.

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

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

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

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

GOAL (on pinest-tech.atxaisites.com)
Refresh the /videos/ playlist with current, embeddable uploads — on the site pinest-tech.atxaisites.com.

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

HOW TO APPROACH IT
1. Find 6-10 authoritative, genuinely useful Artificial Intelligence 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: pinest-tech.atxaisites.com (live at https://pinest-tech.atxaisites.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/pinest-tech.atxaisites.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for pinest-tech.atxaisites.com and no other site — make all changes on pinest-tech.atxaisites.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on pinest-tech.atxaisites.com)
Add the network affiliate + AdSense setup — on the site pinest-tech.atxaisites.com.

WHY IT MATTERS
Inject the shared Skimlinks script and the AdSense unit so existing traffic earns; one-time setup.

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.