Question 1

What does per-location landing page pre-publish QC actually deliver, and how does the 4-skill bundle decompose?

Accepted Answer

An orchestration layer that sits above the operator headless-CMS + crawler + structured-data-validation + page-speed + accessibility + visual-regression + SEO + consent-management + AI-content + policy-as-code + WORM-storage stack and refuses to publish any per-location landing page that would fail Schema.org / Google Search Central structured-data requirements, ADA Title III + WCAG 2.2 AA accessibility, Core Web Vitals + Page Experience signals, FTC + Lanham + per-vertical advertising rules, or privacy + cookie-consent + AADC + DSA + EU AI Act Article 50 marking. The skill is a four-skill bundle on the page-generator agent. Skill 1 — Draft: produce the per-location landing page content through the operator-chosen AI content tool (Anthropic Claude, OpenAI GPT, Microsoft Copilot, Google Gemini, Jasper, Copy.ai, Writesonic, Persado, Phrasee — operator chooses) under operator-approved deployment posture, write to the operator headless CMS (Sanity, Contentful, Strapi, Storyblok, Prismic, Hygraph, Sitecore, Adobe Experience Manager, WordPress, Drupal — operator chooses) with per-location signal (operator-defined location-specific hours, service area, current promotions, current inventory or service-availability, staff and amenity attributes, language/translation per operator-approved per-market translation memory). Draft composes operator-validated facts; it does not invent claims. Skill 2 — Validate: run the page through the validation pipeline — Schema.org Validator + Google Rich Results Test + Schema Markup Validator + Bing Markup Validator for structured-data correctness; WAVE + axe + Pa11y + Stark + Microsoft Accessibility Insights + Siteimprove + Deque + Level Access + Tenon.io for ADA Title III + WCAG 2.2 AA accessibility; Lighthouse + PageSpeed Insights + WebPageTest + GTmetrix + Pingdom + SpeedCurve + Calibre + Chrome User Experience Report CrUX for Core Web Vitals (Largest Contentful Paint, Interaction to Next Paint replacing First Input Delay as of March 2024, Cumulative Layout Shift) + Google Page Experience signals; Screaming Frog + Sitebulb + DeepCrawl + Botify + OnCrawl + JetOctopus + ContentKing + Lumar for crawl + SEO technical issues; SEMrush + Ahrefs + Moz + Lumar for SEO-side checks. Validate emits a per-page per-check report with pass/fail status and rule-citation evidence. Skill 3 — Gate: refuse to publish on failure of the operator-counsel-approved compliance gate. Gate evaluates Schema.org Google Search Central rich-result eligibility; ADA Title III + 2010 ADA Standards-aligned web accessibility + state Unruh Civil Rights Act + New York Human Rights Law; Core Web Vitals + Page Experience signals; FTC Section 5 + Endorsement Guides 2024 + FTC Fake Review Rule 16 CFR Part 465 effective October 2024 + Made-in-USA Labeling Rule 16 CFR Part 323 + Green Guides + ROSCA + Click-to-Cancel + state automatic renewal when subscription destination + per-vertical advertising rules (ABA Model Rule 7.1 + per-state attorney advertising for legal; HIPAA + state medical-board for healthcare; FDA OPDP for DTC pharma; DEA for controlled substances; per--regulator; DISCUS + per-state liquor-board for alcohol; FDA CTP for tobacco; state insurance-commissioner; state real-estate-commission); ePrivacy cookie-consent banner when EU users reachable + CCPA cross-context-behavioral-advertising opt-out propagation; COPPA + California AADC (effective July 2024) + Connecticut SB 3 + Maryland AADC + DSA Article 28 child protection when minor audiences reachable; DSA Article 26 online-advertising transparency requirements when applicable; EU AI Act Article 50 generative-content marking when AI-generated content is used. Skill 4 — Publish: emit the approved page to production through the operator deployment pipeline (Vercel + Netlify + Cloudflare Pages + AWS Amplify + Azure Static Web Apps + operator CI/CD — operator chooses) with per-publish attestation written to the WORM audit trail (per-page per-check status + rule-citation evidence + counsel-policy-version + page-version hash). The headless CMS, crawler, structured-data, page-speed, accessibility, visual-regression, SEO, consent, AI-content vendors below ship strong primitives. The orchestration above them — operator-counsel-approved per-vertical advertising rule enforcement + ADA Title III + WCAG 2.2 AA enforcement + Core Web Vitals + Page Experience + Schema.org rich-result + FTC representation + cookie-consent + COPPA + AADC + DSA + EU AI Act Article 50 enforcement + audit trail — is operator-side architecture.

Question 2

Where does single-vendor accessibility or single-vendor SEO crawler stop compounding for multi-location operators publishing at scale?

Accepted Answer

Single-vendor accessibility is solved. axe ships strong open-source accessibility evaluation. WAVE ships strong browser-based audits. Pa11y ships strong command-line scanning. Siteimprove + Deque + Level Access + Tenon.io ship strong enterprise accessibility platforms. Screaming Frog + Sitebulb + DeepCrawl + Botify + OnCrawl + JetOctopus + ContentKing + Lumar ship strong SEO crawlers. Lighthouse + PageSpeed Insights + WebPageTest + GTmetrix ship strong page-speed. Google Rich Results Test + Schema.org Validator ship strong structured-data validation. The compound case the page-generator agent has to handle is the one where a 50-1,500 location operator publishes thousands of per-location landing pages where each page (a) must carry per-location Schema.org structured data (LocalBusiness + Organization + per-vertical Product/Service/FAQ/HowTo/Article schemas) that meets Google Search Central rich-result requirements for the eligible result types — Google’s structured-data requirements distinguish required vs recommended properties and rich-result eligibility for each result type; missing required properties forfeit the rich result, (b) must pass ADA Title III + WCAG 2.2 AA accessibility — the post-Robles v Domino (9th Cir 2019) legal environment treats websites with nexus to physical place of public accommodation as covered by ADA Title III, and DOJ’s April 2024 web accessibility rule for state and local government Title II entities (Federal Register publication May 2024) signals federal direction on web accessibility standards more broadly; state-level enforcement under California Unruh Civil Rights Act and New York Human Rights Law has driven a wave of demand letters and litigation; alt-text + color-contrast + keyboard navigation + form-label association + ARIA correctness must hold on every page, (c) must hit Core Web Vitals + Page Experience thresholds — Largest Contentful Paint (under 2.5s good), Interaction to Next Paint (under 200ms good, replaced First Input Delay as a Core Web Vital in March 2024), Cumulative Layout Shift (under 0.1 good) + mobile-friendliness + HTTPS + safe-browsing + intrusive-interstitial guidelines, (d) must satisfy FTC Section 5 + Lanham + state UDAP + FTC Endorsement Guides 2024 + FTC Fake Review Rule 16 CFR Part 465 + FTC Made-in-USA Labeling Rule 16 CFR Part 323 (all-or-virtually-all standard) + Green Guides + ROSCA + Click-to-Cancel + state automatic renewal when subscription destination, (e) must respect per-vertical advertising rules where vertical applies (ABA Model Rule 7.1 + per-state attorney; HIPAA + state medical-board for healthcare; FDA OPDP for pharma; DEA for controlled substances; per--regulator; DISCUS + per-state liquor-board; FDA CTP for tobacco; state insurance-commissioner; state real-estate-commission), (f) must wire ePrivacy cookie-consent + CCPA cross-context-behavioral-advertising opt-out + GDPR Article 22 when solely automated decisionmaking + Article 35 DPIA + state-comprehensive-privacy + COPPA + California AADC + Connecticut SB 3 + Maryland AADC + DSA Article 28 child protection when minors reachable + DSA Article 26 online-advertising transparency, (g) must apply EU AI Act Article 50 generative-content marking when AI-generated content is on the page. Without an orchestration layer above the CMS + crawler + structured-data + page-speed + accessibility + visual-regression + SEO + consent + AI-content vendors, per-vertical advertising rules get applied inconsistently per page, Schema.org rich-result eligibility drifts (required properties missing, leading to rich-result loss), accessibility fails get pushed to production despite axe + WAVE flagging them, Core Web Vitals fail without halting publish, FTC Made-in-USA + Endorsement Guides + Fake Review enforcement gets missed per page, cookie consent breaks, COPPA + AADC + DSA Article 28 enforcement gaps surface, EU AI Act Article 50 marking gets omitted on AI-generated content, and the audit trail of "which page, validated against which checks under which counsel-policy-version, against which page-version hash, with which gate decision" fragments across consoles. The orchestration above the vendors is what holds the cross-vendor + cross-vertical + cross-jurisdiction + cross-standard invariants.

Question 3

How does Skill 2 Validate handle Schema.org rich-result requirements vs ADA + WCAG accessibility vs Core Web Vitals separately?

Accepted Answer

Validate runs structured-data, accessibility, and page-speed checks in parallel against operator-counsel-and-engineering-team-approved thresholds and emits a per-check report. Structured-data validation runs against Google Rich Results Test (which checks eligibility for Google’s rich result types), Schema.org Validator (which checks Schema.org vocabulary correctness without Google-specific eligibility), Schema Markup Validator (combines both), and Bing Markup Validator (for Bing-specific structured-data). Different result types require different properties — Product rich result requires Schema.org Product with offers + name + image + price + priceCurrency + availability + per-Google-Search-Central rich-result documentation; LocalBusiness requires Schema.org LocalBusiness with @type subtypes + name + address + telephone + url + openingHours; Article requires Schema.org Article with headline + image + author + datePublished; FAQ requires Schema.org FAQPage with mainEntity Question + acceptedAnswer; HowTo requires Schema.org HowTo with step + image; BreadcrumbList requires Schema.org BreadcrumbList with itemListElement. Required vs recommended distinctions matter — missing required properties forfeit the rich result. Accessibility validation runs against axe (open-source DOM-rule-based) + WAVE (visual + DOM analysis) + Pa11y (command-line) + Stark (color-contrast + design-time) + Microsoft Accessibility Insights (browser-based) + Siteimprove or Deque or Level Access or Tenon.io (enterprise platforms with manual + automated audits) against WCAG 2.2 AA success criteria — 1.1.1 non-text content alt-text, 1.4.3 contrast minimum, 2.1.1 keyboard, 2.4.7 focus visible, 3.3.1 error identification, 4.1.2 name/role/value, 4.1.3 status messages. Automated accessibility tools detect approximately 30-40 percent of WCAG issues per industry consensus; manual evaluation catches remaining issues including keyboard-only navigation flow, screen-reader experience, and color-contrast at runtime. Operator-counsel-and-accessibility-team-approved policy requires automated + manual evaluation per WCAG 2.2 AA for production publication; Gate refuses pages that fail automated checks at operator-counsel-set severity threshold; manual evaluation is the operator accessibility team’s responsibility. Page-speed validation runs against Lighthouse + PageSpeed Insights + WebPageTest + GTmetrix + Pingdom + SpeedCurve + Calibre for synthetic measurement plus Chrome User Experience Report (CrUX) for field-data measurement against Core Web Vitals thresholds (Largest Contentful Paint under 2.5 seconds good, Interaction to Next Paint under 200 milliseconds good replacing First Input Delay as a Core Web Vital in March 2024, Cumulative Layout Shift under 0.1 good). Synthetic measurement and field data can diverge; operator-engineering-team-approved policy specifies which signal drives Gate decisions for which page class. Per-check pass/fail with rule-citation evidence writes to the per-page Validate report. Validate does not autonomously override failures; operator counsel + accessibility team + engineering team approve override paths when documented manual evaluation supersedes an automated check.

Question 4

How does Skill 3 Gate handle FTC + Lanham + per-vertical advertising rules + EU AI Act Article 50 on AI-generated landing-page content?

Accepted Answer

Gate runs an operator-counsel-approved compliance cascade. Step 1 — FTC representation. FTC Section 5 + Lanham Act 15 USC 1125(a) + state UDAP + FTC Endorsement Guides 2024 (AI-generated review prohibitions + clearer rules on review collection, display, AI-generated content) + FTC Fake Review Rule 16 CFR Part 465 (effective October 2024 — fake reviews, AI-generated reviews, incentivized reviews without clear-and-conspicuous disclosure, insider reviews, review suppression prohibited) + FTC Made-in-USA Labeling Rule 16 CFR Part 323 (final 2022 — all-or-virtually-all standard) + FTC Green Guides + FTC Negative Option Rule + FTC ROSCA + FTC Click-to-Cancel Rule + state automatic renewal laws (California Business and Professions Code 17602 + New York General Business Law 527 + state patchwork) when subscription destination. Gate verifies the page content meets these standards before publish. Step 2 — Per-vertical advertising rules. Legal (ABA Model Rule 7.1 + ABA Model Rule 7.4 + per-state attorney advertising rules — no false or misleading communications, no improper specialization claims, per-state attorney advertising restrictions). Healthcare (HIPAA when patient-targeted content + state medical-board + dental-board + optometry/chiropractic/PT licensing-board advertising rules with state-specific outcome-claim restrictions). Pharma (FDA Office of Prescription Drug Promotion DTC rules + fair-balance + risk-disclosure obligations). Controlled substances (DEA advertising restrictions for prescribers).  (per--regulator + near-total platform prohibition for  in advertising). Alcohol (TTB Federal Alcohol Administration Act + DISCUS Code + per-state liquor-board + per-state shipping legality). Tobacco (FDA Center for Tobacco Products + 21 CFR 1140 + per-state vape-flavor bans). Insurance (state insurance-commissioner advertising rules). Real estate (state real-estate-commission advertising rules). Step 3 — Privacy. ePrivacy Directive 2002/58/EC cookie consent (banner displayed + consent collected before non-essential cookies fire when EU users reachable); CCPA Section 1798.140(ae) cross-context-behavioral-advertising opt-out propagation through operator consent-management vendor (OneTrust, TrustArc, Ketch, Securiti, BigID — operator chooses); GDPR Article 22 solely automated decisionmaking review when significant effects; Article 35 DPIA when high-risk processing; state-comprehensive-privacy patchwork per-state opt-out propagation. Step 4 — COPPA + California AADC + Connecticut SB 3 + Maryland AADC + DSA Article 28 child protection when minor audiences reachable. Step 5 — DSA Article 26 online-advertising transparency requirements when applicable to operator’s EU reach. Step 6 — EU AI Act Article 50 generative-content marking. When AI-generated content is on the page, EU AI Act Article 50 requires generative AI to mark outputs as AI-generated in a machine-readable format; the orchestration verifies operator-counsel-approved AI-generated content marking is present (C2PA Content Credentials + Adobe Content Authenticity Initiative are emerging technical implementations; the operator-counsel-approved marking method is enforced per page). Per-page per-check Gate decision + rule-citation evidence + counsel-policy-version writes to the WORM audit trail. Failed Gate routes to operator counsel + marketing team for restructure; approved overrides update the per-page exception register but never remove the audit-trail record of the original Gate decision.

Question 5

What compliance does the orchestration enforce, and how does it map to Schema.org/Google Search Central + ADA/WCAG + Core Web Vitals + FTC/per-vertical + privacy/DSA/EU AI Act?

Accepted Answer

Five anchors. Anchor 1 — Schema.org structured data + Google Search Central + Bing structured data. Schema.org Product + LocalBusiness + Organization + Article + FAQPage + HowTo + BreadcrumbList + per-vertical subtypes (Drug + MedicalDevice + AutoBodyShop + AutoDealer + AutoPartsStore + AutoRepair + AutoRental + ProfessionalService + LegalService + HealthAndBeautyBusiness + FoodEstablishment + Restaurant + Store + HomeGoodsStore + HardwareStore + per-vertical Schema.org types). Google Search Central rich-result requirements with required vs recommended property distinctions; Bing structured-data; Schema Markup Validator; Google Rich Results Test. Anchor 2 — ADA Title III digital accessibility + WCAG 2.2 AA + Robles + state accessibility. Robles v Domino’s Pizza LLC (9th Cir 2019) confirming ADA Title III applies to digital experience with nexus to physical place of public accommodation + DOJ April 2024 Title II web accessibility rule for state and local government (signaling federal direction) + WCAG 2.2 AA standards + California Unruh Civil Rights Act (Cal Civ Code 51 with ADA-violation-as-Unruh-violation minimum $4,000 per-violation statutory damages) + New York Human Rights Law + state similar producing high-volume state-court demand letters and litigation. WCAG 2.2 AA success criteria across perceivable + operable + understandable + robust principles. Anchor 3 — Core Web Vitals + Page Experience. Largest Contentful Paint (LCP) under 2.5 seconds for good, Interaction to Next Paint (INP) under 200 milliseconds for good (INP replaced First Input Delay as a Core Web Vital in March 2024), Cumulative Layout Shift (CLS) under 0.1 for good + mobile-friendliness + HTTPS + safe-browsing + intrusive-interstitial guidelines + Google Search Central technical requirements + Chrome User Experience Report (CrUX) field data + Lighthouse synthetic measurement. Anchor 4 — FTC Section 5 + Lanham Act 15 USC 1125(a) + state UDAP + FTC Endorsement Guides 2024 + FTC Fake Review Rule 16 CFR Part 465 (effective October 2024) + FTC Made-in-USA Labeling Rule 16 CFR Part 323 + FTC Green Guides + FTC Negative Option Rule + FTC ROSCA + FTC Click-to-Cancel Rule + state automatic renewal laws + per-vertical advertising rules (legal ABA Model Rule 7.1 + per-state attorney; healthcare HIPAA + per-state medical-board; pharma FDA OPDP; controlled substances DEA;  per-state regulator; alcohol DISCUS + TTB + per-state liquor; tobacco FDA CTP; insurance state-commissioner; real estate state-commission). Anchor 5 — Privacy + DSA + EU AI Act + COPPA + AADC. CCPA Section 1798.120 + Section 1798.121 sensitive PI + Section 1798.140(ae) cross-context-behavioral-advertising opt-out + state-comprehensive-privacy patchwork. GDPR Articles 6 + 9 + 22 + 26 + Article 35 DPIA + ePrivacy Directive 2002/58/EC cookie consent (non-essential cookies require opt-in consent when EU users reachable). UK GDPR + UK PECR. COPPA 15 USC 6501 + California Age-Appropriate Design Code Act (effective July 2024) + Connecticut SB 3 + Maryland AADC + DSA Article 28 child protection. DSA Article 26 online-advertising transparency. EU AI Act (Regulation 2024/1689) Article 50 generative-AI transparency including AI-generated content marking in machine-readable format. Broader gate also enforced: HIPAA + Washington MHMDA + GLBA when relevant + state-comprehensive-privacy via policy-as-code (OPA Rego + AWS Cedar + Casbin + Cerbos + Oso). WORM audit trail (AWS S3 Object Lock + GCS retention + Azure Blob immutable + Snowflake Time Travel) with per-statute retention (FTC 7yr + state-AG variable + ADA litigation variable + GDPR 6yr + CCPA 3yr + COPPA 1yr after relationship ends + IRS 7yr) per operator counsel policy.

Question 6

What does the engagement look like across Tier 1 → Tier 2 → Tier 3, and what does the Tier 3 reporting cycle commit to?

Accepted Answer

Tier 1 AI Readiness Assessment (2-3 weeks, diagnostic): audits the operator current per-location landing page posture against the 4-skill bundle + 5-anchor compliance overlay + per-vendor headless CMS + crawler + structured-data + page-speed + accessibility + visual-regression + SEO + consent + AI-content state; deliverable is a gap-pack report identifying which pages fail Schema.org rich-result eligibility, which pages fail ADA Title III + WCAG 2.2 AA at axe/WAVE/Pa11y automated checks, which pages fail Core Web Vitals at LCP + INP + CLS thresholds, which pages lack FTC ROSCA + Click-to-Cancel disclosure when subscription destination, which per-vertical advertising rules are unenforced, which pages lack ePrivacy cookie-consent + CCPA cross-context propagation, which pages reach minors without COPPA + AADC + DSA Article 28 protection, which AI-generated content pages lack EU AI Act Article 50 marking, and a recommended remediation sequence for Tier 2. Tier 2 AI Swarm Setup Sprint (4-8 weeks): builds the 4-skill bundle on the page-generator agent, wires headless CMS + crawler + structured-data + page-speed + accessibility + visual-regression + SEO + consent + AI-content + policy-as-code + WORM-storage vendors (operator-chosen subset), configures the operator-counsel-and-accessibility-team-and-engineering-team-approved Schema.org rich-result library + ADA + WCAG 2.2 AA enforcement + Core Web Vitals thresholds + FTC representation library + per-vertical advertising ruleset + ePrivacy cookie-consent + CCPA cross-context propagation + COPPA + AADC + DSA + EU AI Act Article 50 marking flow, runs 30-day shadow + canary period before flipping to enforce-mode. Tier 3 Fractional CMO with AI Swarm (6-month minimum, 1-2 days/wk embedded): continues operating with daily Draft + Validate + Gate + Publish + weekly per-page Validate + Gate audit + monthly Schema.org + Google Search Central rich-result eligibility update review + monthly Core Web Vitals threshold review (Google updates thresholds periodically; INP became a Core Web Vital in March 2024) + monthly per-vertical advertising rule review + quarterly ADA case-law + state-Unruh + NY HRL review + quarterly compliance evidence packages. Tier 3 reporting is a 6-workstream pre-engagement-baseline reporting cycle (per-page Validate pass-rate trend + per-page Gate pass-rate trend + per-page Schema.org rich-result eligibility coverage + per-page ADA + WCAG 2.2 AA accessibility coverage + per-page Core Web Vitals + Page Experience compliance + WORM audit-trail completeness) measured against the operator’s pre-engagement baseline. Each workstream surfaces trend direction and the gap to operator-defined targets. Reporting carries explicit caveats: headless CMS + crawler + structured-data + page-speed + accessibility + visual-regression + SEO + consent + AI-content vendor SLA + Schema.org release cadence + Google Search Central rich-result eligibility updates + Bing structured-data updates + DOJ ADA Title II rule developments + ADA Title III case law + state Unruh + NY HRL case-law + WCAG version updates + Core Web Vitals threshold updates + Page Experience signal updates + Google algorithm updates + FTC Endorsement Guides + Fake Review Rule + Made-in-USA + Green Guides + ROSCA + Click-to-Cancel + state automatic renewal amendments + per-vertical regulator amendments + GDPR + ePrivacy + CCPA + state-comprehensive-privacy implementing rules + COPPA + AADC + DSA + EU AI Act Article 50 implementing acts sit outside Completions control. Attorney-client privilege preservation across operator-counsel-approved Schema.org rich-result library + ADA + WCAG policy + FTC representation library + per-vertical advertising ruleset + cookie-consent + CCPA cross-context propagation records + DSA + EU AI Act Article 50 marking records is maintained per operator counsel policy.

Question 7

Who owns the headless CMS, the Schema.org library, the accessibility policy, the per-vertical ruleset, and the audit trail?

Accepted Answer

Operator owns every artifact. The headless CMS subscription (Sanity, Contentful, Strapi, Storyblok, Prismic, Hygraph, Sitecore, Adobe Experience Manager, WordPress, Drupal — operator chooses) runs under operator billing on operator-controlled accounts. The crawler subscriptions (Screaming Frog, Sitebulb, DeepCrawl, Botify, OnCrawl, JetOctopus, ContentKing, Lumar — operator chooses) run under operator billing. The structured-data validation tools (Google Rich Results Test, Schema.org Validator, Schema Markup Validator, Bing Markup Validator) are operator-accessed. The page-speed tools (Lighthouse, PageSpeed Insights, WebPageTest, GTmetrix, Pingdom, SpeedCurve, Calibre, Chrome User Experience Report) run under operator account. The accessibility tools (WAVE, axe, Pa11y, Stark, Microsoft Accessibility Insights, Siteimprove, Deque, Level Access, Tenon.io — operator chooses) run under operator account. The visual-regression vendor (Percy, Chromatic, Applitools, LambdaTest, BrowserStack, Sauce Labs — operator chooses) runs under operator billing. The SEO vendor (SEMrush, Ahrefs, Moz, Lumar — operator chooses) runs under operator billing. The consent-management vendor (OneTrust, TrustArc, Ketch, Securiti, BigID — operator chooses) runs under operator account. The AI content tool (Anthropic Claude, OpenAI GPT, Microsoft Copilot, Google Gemini, Jasper, Copy.ai, Writesonic, Persado, Phrasee — operator chooses with operator-approved deployment posture) runs under operator account. The operator-counsel-and-accessibility-team-and-engineering-team-approved Schema.org rich-result library + ADA + WCAG 2.2 AA policy + Core Web Vitals + Page Experience threshold library + FTC representation library + per-vertical advertising ruleset + ePrivacy cookie-consent + CCPA cross-context-behavioral-advertising propagation records + COPPA + AADC + DSA Article 28 child-audience exclusion records + DSA Article 26 online-advertising transparency records + EU AI Act Article 50 generative-content marking library all live in operator counsel + accessibility-team + engineering-team repo. The Draft + Validate + Gate + Publish skill code lives in operator code repo. The WORM audit trail lives on operator-controlled cloud storage (AWS S3 Object Lock + GCS retention + Azure Blob immutable + Snowflake Time Travel) with per-statute retention enforcement. The policy-as-code policies (OPA Rego + AWS Cedar + Casbin + Cerbos + Oso) live in operator code repo, counsel-aligned. The Schema.org + Google Search Central + ADA + WCAG + Core Web Vitals + FTC + per-vertical + privacy + DSA + EU AI Act compliance evidence records are operator-counsel-maintained. Completions owns the orchestration knowledge — how to design the per-location landing page Validate + Gate against the operator’s actual page mix, how to wire Schema.org rich-result library against operator vertical mix, how to wire ADA + WCAG 2.2 AA enforcement against operator-counsel-set severity threshold, how to wire Core Web Vitals + Page Experience against operator-engineering-team-approved field-vs-synthetic policy, how to wire FTC representation enforcement across operator product/service mix, how to wire per-vertical advertising rule enforcement, how to wire ePrivacy cookie-consent banner + CCPA cross-context propagation, how to wire EU AI Act Article 50 marking on AI-generated content — and that knowledge transfers under the Tier 3 transition path (30-60 days at engagement end with full hand-off of the Schema.org rich-result library maintenance playbook, the ADA + WCAG 2.2 AA enforcement playbook, the Core Web Vitals threshold maintenance runbook, the FTC representation library maintenance playbook, the per-vertical advertising ruleset maintenance playbook, the cookie-consent + CCPA cross-context propagation playbook, the EU AI Act Article 50 marking playbook, and the compliance evidence-package generation playbook). Completions credentials revoke on engagement-end.

The real ecosystem this sits above

Headless CMS + AI content

Crawler + structured data + SEO

Page speed + accessibility

Visual regression + consent

Policy-as-code + WORM + legal research

Frequently asked