Add FAQPage schema + answer-first intro to AI infrastructure tools guide

[joeduffy]

What this does

Adds FAQPage structured data and an answer-first opening to /blog/ai-infrastructure-tools/, our weakest topic in AI-visibility tracking (AI Infrastructure sits at 11.36% visibility per our Profound monitoring, well behind Alternatives at 97.6% and DevOps Solutions at 96.9%) despite Pulumi's AI-native infrastructure positioning. The page already earns real citation volume, so structural improvements here compound rather than starting from zero.

Changes

1. Template: extends layouts/partials/schema/graph-builder.html and reuses the existing schema/collectors/faq-entity.html FAQ-extraction partial (already powering FAQPage schema on what-is pages) to also fire for blog posts, gated behind an opt-in faq_schema: true frontmatter flag rather than a blanket .Type "blog" check.

   The opt-in gate is deliberate: 168+ existing blog posts contain narrative ###/## headings that happen to end in ? without being real Q&A sections (checked via grep -rn '^#\{2,3\} .*?$' content/blog/). A blanket type-based gate would generate inaccurate FAQPage schema across the whole archive. The flag keeps this a reusable template mechanism, not a per-page hack: any future blog post with a genuine FAQ section picks up schema by adding one frontmatter line.

2. Content: sets faq_schema: true on /blog/ai-infrastructure-tools/, which already carries a genuine 9-question FAQ section under ## Frequently asked questions, and rewrites the opening paragraph into an answer-first format, 55 words, stating what the two AI-infrastructure markets are (infrastructure for AI vs. AI for infrastructure) before any narrative framing.

Verification

• Confirmed via grep that the existing FAQ section's H3 headings all end in ?, matching the FAQ-entity partial's parsing rule for non-/faq/ pages.
• Confirmed the FAQ answer text on the page matches what will populate the schema's acceptedAnswer.text (the partial extracts directly from .RawContent, so page and schema text are the same source and can't drift).
• Diff is minimal and additive: 2 files, 14 insertions, 4 deletions. No other blog posts are affected since none of them set faq_schema: true.
• Local Hugo build wasn't available in this environment to render and run Google's Rich Results Test end to end; recommend a live check against the deployed preview URL before merge, since the template syntax mirrors the already-shipped what-is FAQPage pattern exactly (same partial, same mainEntity shape).

---

🧠 This PR was created by workprentice on behalf of @joeduffy.

[github-actions]

Pre-merge Review — Last updated 2026-07-07T19:50:15Z

Warning

Automated fact-checking was incomplete for this review. The verification service errored on 1 of 70 claim(s); those trail entries are unconfirmed — spot-check them manually. Once the service is back, mention @claude #new-review to regenerate a complete review from scratch.

Tip

Summary: This PR is an SEO/AEO enhancement to the existing "Best AI Infrastructure Tools in 2026" blog post. It makes two changes: (1) it rewrites the opening paragraph to be answer-first — leading with the two-market definition (infrastructure for AI vs AI for infrastructure) rather than building up to it — and (2) it opts the post into FAQPage structured data via a new faq_schema: true frontmatter flag, backed by a small, well-documented extension to layouts/partials/schema/graph-builder.html that gates blog FAQ schema on the flag (avoiding false-positive structured data across the ~168 existing posts with rhetorical ? headings). The post has a genuine 10-question FAQ section with ?-terminated H3 headings, so the opt-in is correctly applied. The kind of wrongness that would matter here — a syntactically broken template guard, or an intro claim that misdescribes a named vendor — was not found: the guard is correct Hugo (or of the existing what-is case and the new blog+flag case), and the rewritten intro's vendor claims (CoreWeave as a GPU cloud, Weights & Biases as MLOps, Pulumi Neo as agentic) check out. Automated fact-checking was degraded this run (it errored on one of the article's claims), so the verification trail below is reported as recorded and not treated as fully confirmed; the single ❌ contradicted entry and every unverifiable entry sit on lines this PR does not touch. Passes run: full-article fact-check, editorial-balance, and template inspection.

Review confidence:

Dimension	Level	Notes
mechanics	MEDIUM	The FAQPage-schema template change wasn't exercised by a Hugo build this run — the docs-review preflight classified the PR as content-only and deferred the full build to build-and-deploy.yml. The guard was verified by inspection and is syntactically correct.
facts	LOW	automated fact-checking errored — claims unverified
coherence	HIGH
editorial balance	MEDIUM	The two section-depth outliers (Part 1, Part 2) reflect the guide's intentional two-part structure, and Pulumi Neo's deeper treatment is expected framing for a vendor-published comparison; this PR changes neither.

Investigation log

• Cross-sibling reads: not run (not in a templated section)
• External claim verification: 59 of 70 claims verified (10 unverifiable, 1 contradicted) · 4 specialists (numerical, cross-reference, capability, framing); 0 cross-specialist corroborations · routed: 0 inline, 38 Pass 1, 1 Pass 2 (verified 0, contradicted 0, unverifiable 1), 31 Pass 3 (verified 30, contradicted 1, unverifiable 0).
• Cited-claim spot-checks: 1 of 1 cited claims fetched and compared
• Frontmatter sweep: ran on body + meta_desc
• Temporal-trigger sweep: not run (no trigger words)
• Code execution: not run (no static/programs/ change)
• Code-examples checks: not run (no fenced code blocks in content files)
• Editorial-balance pass: ran (10 H2 sections, 2 flags fired)

🚨 Outstanding	⚠️ Low-confidence	💡 Pre-existing	✅ Resolved
0	10	1	0

🔍 Verification trail

70 claims extracted · 59 verified · 10 unverifiable · 1 contradicted

• L19 in content/blog/ai-infrastructure-tools/index.md "CoreWeave is a GPU cloud company." → ✅ verified (evidence: Wikipedia confirms: "CoreWeave, Inc. is an American artificial intelligence (AI) cloud-computing company... It specializes in providing cloud-based graphics processing unit (GPU) infrastructure to AI developers and enterprises," corroborat…; source: https://en.wikipedia.org/wiki/CoreWeave)
• L19 in content/blog/ai-infrastructure-tools/index.md "Weights & Biases is an MLOps platform." → ✅ verified (evidence: Multiple authoritative sources confirm this framing, e.g. GOV.UK states: "Weights & Biases provides an MLOps platform to help organisations gain auditable and explainable end-to-end machine learning workflows for reproducibility and govern…; source: https://www.gov.uk/ai-assurance-techniques/weights-and-biases-the-ai-developer-platform)
• L19 in content/blog/ai-infrastructure-tools/index.md "Pulumi Neo is an agentic platform that generates, deploys, and governs cloud resources." → ✅ verified (evidence: The same document describes Neo as "Pulumi's agentic AI for infrastructure. The distinguishing claim is execution: Neo doesn't only suggest a Terraform snippet, it figures out the right resources, generates the code, and runs the deploymen…; source: repo:content/blog/ai-infrastructure-tools/index.md)
• L23 in content/blog/ai-infrastructure-tools/index.md "McKinsey research puts the productivity lift from generative AI in software development at 20–45%." → 🤷 unverifiable (evidence: The cited McKinsey URL could not be fetched (TimeoutError, empty body), so the specific 20–45% figure cannot be confirmed against the source. This figure is widely cited elsewhere as McKinsey's estimate for software engineering productivit…; source: https://www.mckinsey.com/capabilities/mckinsey-digital/our-insights/the-economic-potential-of-generative-ai-the-next-productivity-frontier)
• L52 in content/blog/ai-infrastructure-tools/index.md "Pulumi Neo executes changes, not only suggestions." → ✅ verified (evidence: The same blog post explicitly states: "Neo doesn't only suggest a Terraform snippet, it figures out the right resources, generates the code, and runs the deployment inside whatever guardrails you've set" and the comparison table lists "Exe…; source: repo:content/blog/ai-infrastructure-tools/index.md (lines 151, 142))
• L52 in content/blog/ai-infrastructure-tools/index.md "Pulumi Neo ships with (or has access to) policy packs for CIS, HITRUST, NIST, and PCI DSS." (also L158, L260, L312) → ✅ verified (evidence: Sibling doc content/product/insights-governance.md states "Continuously audit and block non-compliant deployments across CIS, NIST, HITRUST, and PCI DSS" and content/docs/insights/policy/policy-packs/pre-built-packs.md lists HITRUST CSF 11…; source: gh_query: gh search code --owner pulumi "HITRUST" (content/product/insights-governance.md, content/docs/insights/policy/policy-packs/pre-built-packs.md))
• L52 in content/blog/ai-infrastructure-tools/index.md "Pulumi Neo works with Terraform, CloudFormation, and resources created by hand." (also L261) → ✅ verified (evidence: The same blog post itself states: "Neo's governance applies to Pulumi-managed resources, Terraform state, CloudFormation stacks, and resources someone clicked together in the AWS console," directly supporting the claim that Neo works with…; source: repo:content/blog/ai-infrastructure-tools/index.md (L160))
• L53 in content/blog/ai-infrastructure-tools/index.md "CoreWeave's prices generally undercut the hyperscalers." → ✅ verified (evidence: Multiple independent sources confirm CoreWeave undercuts hyperscaler pricing: one source states "CoreWeave typically prices 30–60% below hyperscalers (AWS, Azure, GCP) for equivalent GPU configurations," and another notes CoreWeave's "list…; source: https://www.onesourcecloud.net/cms/coreweave-alternatives.html; https://www.thundercompute.com/blog/coreweave-gpu-pricing-review)
• L53 in content/blog/ai-infrastructure-tools/index.md "CoreWeave has a deep NVIDIA partnership." → 🤝 matches (evidence: The same blog post describes CoreWeave's strengths elsewhere as "direct NVIDIA partnership" and "teams that need dedicated GPU capacity with first access to new NVIDIA hardware," consistent with the claim that CoreWeave has a deep NVIDIA p…; source: repo:content/blog/ai-infrastructure-tools/index.md (L77: "direct NVIDIA partnership"))
• L53 in content/blog/ai-infrastructure-tools/index.md "CoreWeave is purpose-built for AI workloads." → ✅ verified (evidence: CoreWeave's own site states verbatim: "CoreWeave is purpose-built for AI workloads, with specialized infrastructure designed for performance, flexibility, and speed." Other CoreWeave pages reiterate "CoreWeave Cloud was purpose-built for A…; source: https://www.coreweave.com/ready-for-anything)
• L54 in content/blog/ai-infrastructure-tools/index.md "Modal lets a user decorate a Python function to get a GPU and pay by the second." → ✅ verified (evidence: (escalated from pass1) Multiple sources confirm this exact mechanic: "You write a function, decorate it with @app.function(gpu="H100"), and Modal handles the rest: container provisioning, GPU attachment, and billing per second of executi…; source: https://www.spheron.network/blog/spheron-vs-modal/)
• L55 in content/blog/ai-infrastructure-tools/index.md "MLflow has no vendor lock-in and runs anywhere." → 🤝 matches (evidence: The article consistently describes MLflow elsewhere as "Apache 2.0" licensed, "Open source... runs locally, on-prem, or managed" with "no lock-in" (line 109, 113), which is the well-established factual characterization of MLflow as an open…; source: repo:content/blog/ai-infrastructure-tools/index.md (lines 107-114, 237))
• L73 in content/blog/ai-infrastructure-tools/index.md "CoreWeave acquired Weights & Biases." → ✅ verified (evidence: CoreWeave publicly announced its agreement to acquire Weights & Biases in March 2025, which closed later in 2025; this is a well-documented industry event, consistent with the claim.; source: WebSearch general knowledge: CoreWeave-Weights & Biases acquisition announcement (March 2025))
• L73 in content/blog/ai-infrastructure-tools/index.md "CoreWeave signed a multi-billion-dollar capacity deal with OpenAI." → ✅ verified (evidence: CoreWeave signed an initial $11.9B deal with OpenAI in March 2025, followed by a $4B expansion in May and a $6.5B expansion in September, bringing the total to $22.4 billion: "CoreWeave has signed a $6.5 billion deal with OpenAI. The deal…; source: https://www.cnbc.com/2025/09/25/coreweave-openai-6point5-billion-deal.html)
• L73 in content/blog/ai-infrastructure-tools/index.md "CoreWeave's acquisition of Weights & Biases and NVIDIA's acquisition of Run:ai both point toward integrated platforms across the AI infrastructure stack." (also L100, L276) → ✅ verified (evidence: CoreWeave completed its acquisition of Weights & Biases in May 2025, explicitly framed as "uniting compute and developer tools to accelerate AI innovation at scale," and NVIDIA completed its acquisition of Run:ai in December 2024, a GPU or…; source: https://www.coreweave.com/news/coreweave-completes-acquisition-of-weights-biases-2; https://techcrunch.com/2024/12/30/nvidia-completes-acquisition-of-ai-infrastructure-startup-runai/)
• L78 in content/blog/ai-infrastructure-tools/index.md "CoreWeave has a smaller global footprint than AWS, GCP, and Azure." → ✅ verified (evidence: Sources confirm CoreWeave's footprint (41-44 data centers, concentrated in US/Europe) is much smaller than the hyperscalers: "CoreWeave's geographic coverage is limited to North America and Europe" with "no CoreWeave regions in Asia-Pacifi…; source: https://axecompute.com/gpu-cloud-providers-comparison-2026/ and https://www.digitalocean.com/resources/articles/comparing-aws-azure-gcp)
• L78 in content/blog/ai-infrastructure-tools/index.md "CoreWeave is not a general-purpose cloud and does not offer RDS, S3, or a managed Kafka." → ✅ verified (evidence: Source text (same file, line 78) reads: "not a general-purpose cloud, so if you need RDS, S3, and a managed Kafka in the same provider, this isn't it." This matches the claim; CoreWeave's actual Pulumi provider surface (CKS/Kubernetes, Obj…; source: repo:content/blog/ai-infrastructure-tools/index.md (L78); gh search code --owner pulumi CoreWeave (pulumi-coreweave provider resources))
• L82 in content/blog/ai-infrastructure-tools/index.md "A user can be running on an H100 on Lambda Labs in about as long as it takes to copy an SSH key." → ✅ verified (evidence: (escalated from pass1) The Pulumi blog post itself states: "Environments come pre-configured with PyTorch and TensorFlow, and you can be running on an H100 in about as long as it takes to copy your SSH key." This is a direct, near-verbatim…; source: https://www.pulumi.com/blog/ai-infrastructure-tools/)
• L82 in content/blog/ai-infrastructure-tools/index.md "Lambda Labs environments come pre-configured with PyTorch and TensorFlow." → ✅ verified (evidence: (escalated from pass1) Lambda's official Lambda Stack page confirms: "Lambda Stack includes tested AI software packages like PyTorch, TensorFlow, and Keras" and is "Preinstalled on Lambda systems for NVIDIA B200, H200, and HPC GPUs."; source: https://lambda.ai/lambda-stack-deep-learning-software)
• L87 in content/blog/ai-infrastructure-tools/index.md "Lambda Labs has a smaller scale than CoreWeave or the hyperscalers." → ✅ verified (evidence: Multiple sources confirm Lambda is meaningfully smaller than CoreWeave and hyperscalers. Per Contrary Research, "Revenue of $505M vs. CoreWeave's $5B+ means Lambda is approximately 10x smaller," and Metavert notes "CoreWeave operates at a…; source: https://research.contrary.com/company/lambda; https://www.metavert.io/compare/coreweave-vs-lambda-labs; https://sacra.com/c/coreweave/)
• L91 in content/blog/ai-infrastructure-tools/index.md "Modal handles GPU provisioning when a user decorates a Python function, with no capacity planning, no idle instances, and no Dockerfile to maintain." → ✅ verified (evidence: (escalated from pass1) Multiple sources confirm this framing of Modal: official Modal marketing states "Modal replaces YAML configs and Dockerfiles with a Python decorator @app.function(gpu="A100")" and "Scales from zero to 1,000+ GPUs i…; source: https://modal.com/resources/code-sandbox)
• L100 in content/blog/ai-infrastructure-tools/index.md "Weights & Biases integrates with essentially every ML framework and cloud." → 🤷 unverifiable (evidence: This is a vague, sweeping marketing-style claim ("essentially every ML framework and cloud") that is not precisely falsifiable and not sourced to any specific Pulumi or W&B documentation page in the repo. While W&B does have broad framewor…; source: content/blog/ai-infrastructure-tools/index.md; intuition: Hyperbolic absolute claim ("essentially every") is inherently unverifiable puffery rather than a checkable fact.)
• L100 in content/blog/ai-infrastructure-tools/index.md "Weights & Biases is the de facto standard for ML experiment tracking and model management." → ✅ verified (evidence: Multiple independent sources describe W&B in near-identical terms of market dominance: one source states W&B "has become the industry standard tool for ML experiment tracking, adopted by thousands of enterprises and research teams," an…; source: WebSearch ran query "Weights & Biases de facto standard ML experiment tracking"; intuition: Claim uses strong absolute language ("de facto standard") that is contested — several sources instead award that title…)
• L109 in content/blog/ai-infrastructure-tools/index.md "MLflow was originally built at Databricks." → ✅ verified (evidence: Databricks' own 2018 launch blog states: "At Databricks, we believe there should be a better way to manage the ML lifecycle, so we are excited to announce MLflow: an open source machine learning platform." Other sources corroborate: "Origi…; source: https://www.databricks.com/blog/2018/06/05/introducing-mlflow-an-open-source-machine-learning-platform.html)
• L109 in content/blog/ai-infrastructure-tools/index.md "MLflow is licensed under Apache 2.0." → ✅ verified (evidence: MLflow's official site and GitHub license file confirm this: "100% open source under Apache 2.0 license."; source: https://mlflow.org/)
• L109 in content/blog/ai-infrastructure-tools/index.md "MLflow has managed offerings from multiple vendors, including Databricks and the major clouds." → ✅ verified (evidence: Provider schemas confirm managed MLflow offerings: AWS SageMaker has native MlflowApp/MlflowTrackingServer resources, Databricks has built-in MLflow resources (mlflow_model, mlflow_experiment, mlflow_webhook), and Azure ML has `M…; source: gh search code --owner pulumi "MLflow" (pulumi-aws, pulumi-databricks, pulumi-azure-native, pulumi-aws-native SDKs))
• L109 in content/blog/ai-infrastructure-tools/index.md "MLflow is the leading open-source MLOps platform." → ✅ verified (evidence: Databricks' own blog states MLflow "is arguably the most widely adopted open-source MLOps framework in production environments today," and MLflow's own site/GitHub describe it as "the largest open source AI engineering platform for agents,…; source: https://www.databricks.com/blog/mlops-frameworks-complete-guide-tools-and-platforms-production-ml)
• L111 in content/blog/ai-infrastructure-tools/index.md "MLflow is licensed under Apache 2.0." → ✅ verified (evidence: MLflow's official site and GitHub repo confirm the license: "100% open source under Apache 2.0 license" and the repo's LICENSE.txt is the Apache License, Version 2.0.; source: https://mlflow.org/ and https://github.com/mlflow/mlflow/blob/master/LICENSE.txt)
• L118 in content/blog/ai-infrastructure-tools/index.md "Google Vertex AI leads on Google's models and TPUs." → 🤷 unverifiable (evidence: This is a subjective marketing/opinion-style claim about Vertex AI's positioning relative to Google's own models (Gemini/PaLM) and TPU hardware, which is trivially true in the sense that Vertex AI is Google's own platform offering first-pa…; source: N/A - subjective blog framing claim, not tied to a specific verifiable fact in pulumi repos or docs; intuition: Vague comparative/opinion claim ("leads on") typical of blog copy; plausible but not something a source definitively co…)
• L118 in content/blog/ai-infrastructure-tools/index.md "AWS SageMaker leads on AWS-native data pipelines." → 🤷 unverifiable (evidence: This is a subjective marketing/opinion claim about SageMaker's competitive positioning ("leads on AWS-native data pipelines") from a Pulumi blog post comparing AI infrastructure tools. It is not tied to a verifiable spec, version, or prici…; source: content/blog/ai-infrastructure-tools/index.md; intuition: Subjective competitive-positioning claim ("leads on") in a blog post is opinion/marketing framing rather than a falsifi…)
• L118 in content/blog/ai-infrastructure-tools/index.md "Azure ML leads on Microsoft-stack integration." → 🤷 unverifiable (evidence: This is a subjective comparative/opinion claim ("leads on Microsoft-stack integration") about Azure ML vs other AI infrastructure tools, which is inherently a value judgment rather than a checkable technical fact. Azure ML is indeed part o…; source: N/A - qualitative/subjective claim not resolvable via repo or GitHub sources; intuition: Superlative/subjective marketing-style claim ("leads on") in a blog post is typical editorial framing, not a falsifiabl…)
• L118 in content/blog/ai-infrastructure-tools/index.md "AWS SageMaker is deeply integrated with S3 and Glue, with first-class connections to Lambda for serverless inference." (also L120) → ✅ verified (evidence: (escalated from pass1) AWS docs confirm: "Serverless Inference integrates with AWS Lambda to offer you high availability, built-in fault tolerance and automatic scaling," and separately AWS Glue/SageMaker integration is well documented, e.…; source: https://docs.aws.amazon.com/sagemaker/latest/dg/serverless-endpoints.html)
• L120 in content/blog/ai-infrastructure-tools/index.md "AWS SageMaker has first-class connections to Lambda for serverless inference." → ✅ verified (evidence: This is a general, well-documented AWS capability: AWS publishes patterns and SDKs (e.g., the SageMaker + Lambda integration for invoking endpoints, and SageMaker Serverless Inference) explicitly designed for calling SageMaker models from…; source: AWS public documentation on SageMaker Serverless Inference and Lambda integration patterns (general industry knowledge, not Pulumi-specific); intuition: Claim is about a third-party AWS product feature, not something Pulumi's own repos would document — best checked agains…)
• L121 in content/blog/ai-infrastructure-tools/index.md "Google Vertex AI includes TPUs and access to Google's foundation models, and is strongest when paired with BigQuery." → ✅ verified (evidence: Google Vertex AI is publicly documented to provide TPU-backed training/serving, access to Google's foundation models (Gemini, PaLM, etc.) via Model Garden, and tight native integration with BigQuery (BigQuery ML, Vertex AI Workbench notebo…; source: repo:content/blog/ai-infrastructure-tools/index.md (surrounding text, L118, L121))
• L122 in content/blog/ai-infrastructure-tools/index.md "Azure Machine Learning has first-party MLOps integrations across GitHub Actions, Azure DevOps, and Microsoft Fabric." → ✅ verified (evidence: (escalated from pass1) Microsoft's official Azure page states: "Take advantage of built-in interoperability with Azure DevOps and GitHub Actions for seamlessly managing and automating workflows," and Microsoft's architecture guide confirms…; source: https://azure-int.microsoft.com/en-us/products/machine-learning/mlops/ and https://learn.microsoft.com/en-us/azure/architecture/ai-ml/guide/machine-learning-operations-v2)
• L124 in content/blog/ai-infrastructure-tools/index.md "Hyperscaler GPU compute typically runs 2–3x the per-hour price of specialized GPU cloud providers." → ✅ verified (evidence: Multiple independent sources confirm this ratio: GPUPerHour states "hyperscaler GPU instances typically cost 2-3x more than equivalent hardware from GPU-first providers," and ComputePrices notes "Hyperscalers offer global availability, ent…; source: https://gpuperhour.com/ and https://computeprices.com/gpu)
• L151 in content/blog/ai-infrastructure-tools/index.md "Pulumi Neo is Pulumi's agentic AI for infrastructure that figures out the right resources, generates the code, and runs the deployment inside user-defined guar…" → ✅ verified (evidence: The claim is a close paraphrase of the same blog post's own description: "Pulumi Neo is Pulumi's agentic AI for infrastructure. The distinguishing claim is execution: Neo doesn't only suggest a Terraform snippet, it figure…; source: repo:content/blog/ai-infrastructure-tools/index.md L151)
• L153 in content/blog/ai-infrastructure-tools/index.md "Pulumi Neo's license is proprietary, part of Pulumi Cloud." → ✅ verified (evidence: Pulumi's pricing page lists Pulumi Neo as a feature included/priced within Pulumi Cloud tiers (e.g. "Pulumi Neo with 5M free tokens/mo" under Individual, "$3/M tokens" for paid tiers), and docs describe it as part of Pulumi Cloud (e.g. "Pu…; source: repo:content/pricing/_index.md (lines 33, 566-573); pulumi/docs:content/blog/pulumi-neo-cli/index.md)
• L158 in content/blog/ai-infrastructure-tools/index.md "Pulumi Insights and Governance ships pre-built policy packs for CIS benchmarks, HITRUST CSF, NIST SP 800-53, and PCI DSS." → ✅ verified (evidence: content/product/insights-governance.md states: "Non-blocking compliance checks provide instant visibility into your security posture across CIS Controls, NIST SP 800-53, HITRUST CSF, and PCI DSS standards," matching the pre-built policy pa…; source: gh search code --owner pulumi "800-53" (pulumi/docs:content/product/insights-governance.md))
• L158 in content/blog/ai-infrastructure-tools/index.md "Neo can batch-remediate across stacks and accounts using natural-language prompts." → ✅ verified (framing: strengthened — claim narrows the product page's general natural-language/governance capability to the specific "batch-remediate across stacks and accounts" fra…; evidence: Pulumi's Insights & Governance product page states Neo lets you "Search and govern every resource across all your cloud, including unmanaged resources, with natural language queries" and that it "identifies policy issues and fixes them aut…; source: repo:content/product/insights-governance.md)
• L160 in content/blog/ai-infrastructure-tools/index.md "Pulumi Neo's governance applies to Pulumi-managed resources, Terraform state, CloudFormation stacks, and manually-created AWS console resources." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
• L162 in content/blog/ai-infrastructure-tools/index.md "Neo's trust levels are configurable, allowing human approval requirements to be loosened for well-defined, low-risk operations as confidence builds." → ✅ verified (framing: strengthened — claim uses term "trust levels" while Pulumi's official terminology is "Operating Modes" (Review/Balanced/Auto), but the underlying capability (c…; evidence: Pulumi's own blog post "neo-levels-up" confirms Neo has configurable autonomy: "Operating Modes let you adjust autonomy based on context: Review Mode... Balanced Mode... Auto Mode: Neo runs without stopping." This matches the claim that tr…; source: repo:content/blog/neo-levels-up/index.md)
• L164 in content/blog/ai-infrastructure-tools/index.md "The Pulumi MCP Server brings Neo into Cursor, Claude Code, Claude Desktop, Windsurf, and other MCP-compatible clients." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
• L164 in content/blog/ai-infrastructure-tools/index.md "Neo integrates into CI/CD pipelines for pre-merge policy remediation." → 🤷 unverifiable (evidence: Pulumi's Neo and Insights & Governance product pages describe MCP-based IDE integration (VS Code, Cursor, Claude Code, Windsurf) and a "review-and-merge" remediation workflow through the Pulumi Cloud UI, but neither page (nor any other doc…; source: repo:content/product/neo.md, repo:content/product/insights-governance.md; intuition: The specific phrase "CI/CD pipelines for pre-merge policy remediation" isn't substantiated anywhere else in the docs —…)
• L168 in content/blog/ai-infrastructure-tools/index.md "Werner Enterprises reduced infrastructure provisioning time from 3 days to 4 hours using Pulumi." → ✅ verified (evidence: Pulumi's own press release and Neo product page state: "Werner Enterprises reduced infrastructure provisioning time from three days to four hours while maintaining SOC 2 compliance." The blog post itself contains the identical claim verbat…; source: https://www.prnewswire.com/news-releases/introducing-pulumi-neo-the-industrys-first-ai-powered-platform-engineer-302556718.html)
• L169 in content/blog/ai-infrastructure-tools/index.md "Spear AI cut their Authority to Operate (ATO) timeline from an expected 1.5 years to roughly 3 months by using policy-as-code to evidence compliance controls f…" → ✅ verified (evidence: Pulumi's official Spear AI case study and press release both quote CEO Michael Hunter: "We've reduced our Authority to Operate (ATO) timeline from a year and a half to expecting approval in three months," attributing this to using Policy a…; source: https://www.pulumi.com/case-studies/spear-ai/)
• L175 in content/blog/ai-infrastructure-tools/index.md "Firefly discovers cloud resources you already have and generates IaC for them." → ✅ verified (evidence: Blog text itself states: "The core capability is asset codification: it discovers cloud resources you already have and generates the IaC for them" — matching the claim's framing, and consistent with Firefly's well-known public positioning…; source: repo:content/blog/ai-infrastructure-tools/index.md (L175))
• L184 in content/blog/ai-infrastructure-tools/index.md "env0's Cloud Compass adds AI to env0's IaC automation platform, focusing on analysis rather than autonomous execution." → ✅ verified (evidence: Third-party sources describe env0 Cloud Compass as an AI feature for resource visibility, drift detection/analysis, and cost insights within env0's multi-IaC platform (e.g., "Cloud Compass AI for finding unmanaged resources," "Access Cloud…; source: gh_query search code "Cloud Compass" "env0" (env0/mcp-server README, zinlab/tutorials field manual))
• L189 in content/blog/ai-infrastructure-tools/index.md "env0 Cloud Compass supports Terraform, OpenTofu, Pulumi, and Terragrunt." → ✅ verified (evidence: Multiple independent sources confirm env0's multi-IaC support including Pulumi: Pulumi's own sibling blog post states "Env0 is... an automation platform that provides workflow management, governance, and collaboration features for existing…; source: gh_query search code env0 Terragrunt OpenTofu; pulumi/docs:content/blog/infrastructure-as-code-tools/index.md)
• L193 in content/blog/ai-infrastructure-tools/index.md "Spacelift's AI work focuses on explaining deployment results and troubleshooting failures." → 🤝 matches (evidence: The blog itself states: "Spacelift's AI work is focused on the post-run experience: explaining what happened in a deployment and helping troubleshoot failures," and the summary table lists "Spacelift AI | CI/CD platform | Run explanation,…; source: repo:content/blog/ai-infrastructure-tools/index.md)
• L202 in content/blog/ai-infrastructure-tools/index.md "Upbound is the company that commercializes Crossplane." → ✅ verified (evidence: Multiple sources confirm this, e.g. AWS Marketplace: "Upbound is the company behind Crossplane, an open-source CNCF project"; Business Wire: "Upbound, the control plane company behind the popular open source project Crossplane".; source: https://aws.amazon.com/marketplace/pp/prodview-xiqrjdlaxh4do; https://www.businesswire.com/news/home/20240430929245/en/Announcing-Upbound-is-Now-Everywhere-Accelerating-Crossplane-Control-Planes-for-Enterprises)
• L202 in content/blog/ai-infrastructure-tools/index.md "Crossplane brings Kubernetes-style declarative management to cloud resources." → ✅ verified (evidence: Crossplane is an open-source Kubernetes add-on that extends the Kubernetes API to enable provisioning and management of cloud infrastructure resources using Kubernetes-style declarative (CRD-based) configuration, per Crossplane's own proje…; source: WebSearch/general knowledge of Crossplane project (crossplane.io) description as a Kubernetes-based declarative control plane for cloud resources)
• L202 in content/blog/ai-infrastructure-tools/index.md "Upbound is layering AI-native control-plane capabilities into the 2.0 generation of Crossplane/Upbound." → ✅ verified (evidence: (escalated from pass1) Upbound's own blog states: "Today we're introducing Upbound Crossplane 2.0, our AI-native distribution of Crossplane, built on the brand-new Crossplane 2.0 release," confirming Upbound is layering AI-native control-p…; source: https://blog.upbound.io/introducing-upbound-crossplane-2-0)
• L204 in content/blog/ai-infrastructure-tools/index.md "Crossplane is licensed under Apache 2.0." → ✅ verified (evidence: The official Crossplane GitHub repo states "Crossplane is under the Apache 2.0 license," confirming the claim exactly.; source: https://github.com/crossplane/crossplane)
• L204 in content/blog/ai-infrastructure-tools/index.md "Upbound's offering is proprietary." → ❌ contradicted (framing: narrowed/overclaim — claim asserts Upbound's offering broadly is "proprietary" but sources show Crossplane and UXP (Upbound's distribution) are open source; on…; evidence: Upbound's core technology is open source, not proprietary: Crossplane is a CNCF project, and Upbound's own distribution UXP is explicitly open source. As Upbound states, "UXP is different because Upbound is different... We believe open sou…; source: https://blog.upbound.io/open-source-and-upound; intuition: Calling Upbound "proprietary" is suspicious given Upbound created and open-sourced Crossplane (CNCF project) and explic…)
• L211 in content/blog/ai-infrastructure-tools/index.md "General-purpose AI coding assistants named include GitHub Copilot, Claude Code, Cursor, and Google's Gemini and Antigravity." → ✅ verified (evidence: Google Antigravity is confirmed as a real Google agentic development/coding platform: "Google Antigravity is a software development platform developed by Google... designed to orchestrate autonomous artificial intelligence agents for code…; source: https://en.wikipedia.org/wiki/Google_Antigravity)
• L211 in content/blog/ai-infrastructure-tools/index.md "These general-purpose AI coding assistants can write Terraform HCL, Pulumi programs, and CloudFormation templates." → 🤷 unverifiable (evidence: This is a general statement about third-party AI coding assistants' capabilities (writing Terraform HCL, Pulumi programs, CloudFormation templates), not a specific Pulumi product feature that can be checked against Pulumi's own docs or rep…; source: content/blog/ai-infrastructure-tools/index.md (L211); intuition: Claim is plausible and consistent with known LLM capabilities (these tools are trained on public IaC code including Ter…)
• L220 in content/blog/ai-infrastructure-tools/index.md "AWS Application Composer generates a CloudFormation template from a visual canvas, with AI suggestions for service configuration." → ✅ verified (evidence: (escalated from pass1) AWS confirms Application/Infrastructure Composer lets you drag-and-drop services onto a visual canvas to generate CloudFormation/SAM templates, with generative AI suggestions for resource configuration: "You can drag…; source: https://aws.amazon.com/about-aws/whats-new/2023/11/ide-extension-aws-application-composer/)
• L260 in content/blog/ai-infrastructure-tools/index.md "Pulumi Neo has pre-built compliance packs for CIS, HITRUST, NIST, and PCI." → 🤝 matches (evidence: The same blog post states elsewhere (L158): "Neo is integrated with Pulumi Insights and Governance, which ships pre-built policy packs for CIS benchmarks, HITRUST CSF, NIST SP 800-53, and PCI DSS." This is consistent with the claim's summa…; source: repo:content/blog/ai-infrastructure-tools/index.md (L158))
• L261 in content/blog/ai-infrastructure-tools/index.md "Pulumi Neo works against Terraform, CloudFormation, and manually created resources, enabling incremental adoption instead of migration first." → ✅ verified (evidence: The same blog post states elsewhere: "Neo's governance applies to Pulumi-managed resources, Terraform state, CloudFormation stacks, and resources someone clicked together in the AWS console. That matters because the realistic adoption path…; source: repo:content/blog/ai-infrastructure-tools/index.md (line 160, and Quick picks section line 52))
• L276 in content/blog/ai-infrastructure-tools/index.md "CoreWeave acquired Weights & Biases." → ✅ verified (evidence: CoreWeave publicly announced its agreement to acquire Weights & Biases in March 2025, a widely reported industry event; this is a general market fact not specific to Pulumi's own repos, so gh search found nothing but the claim aligns with…; source: WebSearch ran query "CoreWeave acquired Weights & Biases" (general knowledge, not found in pulumi repos))
• L276 in content/blog/ai-infrastructure-tools/index.md "NVIDIA acquired Run:ai." → ✅ verified (evidence: NVIDIA publicly announced its agreement to acquire Run:ai, a Kubernetes-based GPU orchestration platform, in April 2024, and the deal closed in 2025 — a widely reported industry fact consistent with the blog's framing of it as a consolidat…; source: repo:content/blog/ai-infrastructure-tools/index.md (claim text); general industry knowledge of NVIDIA's Run:ai acquisition announced April 2024)
• L280-282 in content/blog/ai-infrastructure-tools/index.md "Pulumi Neo is currently the most complete offering for enterprise governance plus true agentic capability, executing changes rather than just suggesting them,…" → 🤷 unverifiable (evidence: This is a subjective competitive-positioning superlative ("most complete offering") about Pulumi's own product. The underlying factual sub-claims (executes changes rather than suggesting, ships pre-built compliance frameworks like CIS/HITR…; source: repo:content/blog/ai-infrastructure-tools/index.md (lines 149-171, 280-282); intuition: Self-serving superlative about the author's own product in a "best of" comparison — expected marketing framing, not ind…)
• L292 in content/blog/ai-infrastructure-tools/index.md "Pulumi Neo can execute provisioning workflows end-to-end with governance controls intact." → 🤝 matches (evidence: The same blog post describes Neo as executing deployments "inside whatever guardrails you've set," integrated with Pulumi Insights and Governance for policy packs (CIS, HITRUST, NIST, PCI DSS), with detection and remediation running "in th…; source: repo:content/blog/ai-infrastructure-tools/index.md (L151, L158, L162))
• L306-308 in content/blog/ai-infrastructure-tools/index.md "Most general-purpose AI assistants (Copilot, Claude, Gemini, ChatGPT, Cursor) can produce Terraform HCL, Pulumi programs in TypeScript, Python, or Go, and Clou…" → ✅ verified (evidence: (escalated from pass1) The source page itself states: "Most general-purpose AI assistants (Copilot, Claude, Gemini, ChatGPT, Cursor) can produce Terraform HCL, Pulumi programs in TypeScript / Python / Go, and CloudFormation." This matches…; source: https://www.pulumi.com/blog/ai-infrastructure-tools/)
• L312 in content/blog/ai-infrastructure-tools/index.md "Pulumi Neo detects policy violations across a footprint, including resources created outside IaC, generates compliant remediation, and applies it with required…" → ✅ verified (evidence: The same blog post (and corroborating docs) confirm: "Detection and remediation run in the same loop: Neo finds a violation, generates a fix, and (subject to approvals) applies it" and "Neo's governance applies to Pulumi-managed resources,…; source: pulumi/docs:content/blog/ai-infrastructure-tools/index.md and pulumi/docs:content/product/insights-governance.md)
• L312 in content/blog/ai-infrastructure-tools/index.md "Pre-built frameworks exist for CIS, HITRUST, NIST, and PCI DSS." → ✅ verified (evidence: Pulumi docs confirm this directly: content/docs/insights/policy/policy-packs/pre-built-packs.md lists HITRUST CSF 11.5, and content/what-is/what-is-policy-as-code.md states "Pulumi publishes pre-built policy packs for CIS 8.1 (covering AWS…; source: gh_query: search code repo:pulumi/docs "HITRUST" — content/what-is/what-is-policy-as-code.md)
• L324 in content/blog/ai-infrastructure-tools/index.md "Pulumi Neo can provision and govern ML infrastructure the same way it handles other infrastructure." → ✅ verified (framing: strengthened — claim narrows Neo's general "provisions, governs, and optimizes your cloud infrastructure" (any provider/resource) to the specific case of "ML i…; evidence: Pulumi's product page describes Neo as a general-purpose agent that "provisions, governs, and optimizes your cloud infrastructure" with "visibility across AWS, Azure, Google Cloud, and hundreds of other providers, all in one place" — it is…; source: repo:content/product/neo.md)
• L324 in content/blog/ai-infrastructure-tools/index.md "CoreWeave leads at scale for GPU compute." → ✅ verified (evidence: Multiple sources confirm CoreWeave's leadership at scale for GPU compute: AIMultiple notes "CoreWeave is the largest specialist neocloud and was selected as NVIDIA's first Elite cloud services provider," and CoreWeave's own blog states it…; source: https://aimultiple.com/cloud-gpu-providers; https://www.coreweave.com/blog/a-defining-year-for-the-essential-cloud-for-ai)
• L324 in content/blog/ai-infrastructure-tools/index.md "Weights & Biases is the leading commercial platform for experiment tracking and model management." → ✅ verified (evidence: Multiple independent sources corroborate this positioning: one market report states "Weights & Biases (W&B) stands out as the market leader" in experiment tracking, and another describes W&B as having "cemented its dominance as the develop…; source: https://www.intelmarketresearch.com/ai-experiment-tracking-market-46972; https://uplatz.com/blog/the-2025-mlops-landscape-a-comparative-analysis-of-mlflow-weights-biases-and-neptune/)

📊 Editorial balance

Section depth, mention distribution, recommendation steering

• Section depth: 10 H2 sections (mean 18 lines, median 11.0, std 16.7). Outliers: Part 1: Tools for building AI infrastructure: 37 (3.4× median), Part 2: AI-powered infrastructure management tools: 57 (5.2× median).
• Vendor / entity mentions: the guide covers ~15 tools, each in its own dedicated section with balanced strengths + a "watch out for"/caveat — CoreWeave, Lambda Labs, Modal, Weights & Biases, MLflow, and the hyperscaler trio (AWS SageMaker, Google Vertex AI, Azure ML) in Part 1; Pulumi Neo, Firefly AIaC, env0 Cloud Compass, Spacelift AI, Crossplane/Upbound, general-purpose code assistants, and AWS Application Composer in Part 2. Pulumi Neo carries the deepest treatment (multiple bolded sub-headings + two case studies), which is expected asymmetry for a vendor-published comparison; notably it also carries an explicit "Tradeoff to be honest about" caveat, keeping the framing credible.
• FAQ steering: 10 FAQ entries. ~6 name Pulumi Neo as a recommended option (best-agent, gen-AI-usage, compliance/policy, Terraform/Pulumi generation, how-to-choose, ML-infra); the other 4 are conceptual/definitional with no vendor steer. Competitor tools are recommended where they fit — the ML-focused answers defer to Weights & Biases / MLflow / CoreWeave rather than force-fitting Pulumi, and the code-generation answers name Copilot/Claude/Gemini/Cursor. Steering is present but proportionate for a vendor blog.

🚨 Outstanding in this PR

No outstanding issues in this PR.

⚠️ Low-confidence

Review each and resolve as appropriate — these don't block the PR.

• [L23] content/blog/ai-infrastructure-tools/index.md — "McKinsey research puts the productivity lift from generative AI in software development at 20–45%." — verdict: unverifiable; evidence: The cited McKinsey URL could not be fetched (TimeoutError, empty body), so the specific 20–45% figure cannot be confirmed against the source. This figure is widely cited elsewhere as McKinsey's estimate for software engineering productivit…; source: https://www.mckinsey.com/capabilities/mckinsey-digital/our-insights/the-economic-potential-of-generative-ai-the-next-productivity-frontier — Cited, not a blocker. The 20–45% figure links directly to McKinsey's report; the automated fetch of that URL timed out this run, but the figure is McKinsey's widely-reported software-engineering productivity estimate and readers can follow the citation. This PR only reworded the surrounding sentence ("get this right" for "think about both") — the claim and its link are unchanged.

• [L100] content/blog/ai-infrastructure-tools/index.md — "Weights & Biases integrates with essentially every ML framework and cloud." — verdict: unverifiable; evidence: This is a vague, sweeping marketing-style claim ("essentially every ML framework and cloud") that is not precisely falsifiable and not sourced to any specific Pulumi or W&B documentation page in the repo. While W&B does have broad framewor…; source: content/blog/ai-infrastructure-tools/index.md; intuition: Hyperbolic absolute claim ("essentially every") is inherently unverifiable puffery rather than a checkable fact. — Marketing hyperbole that isn't precisely checkable; W&B does have broad framework/cloud coverage, so it's directionally true. On an untouched line (not introduced by this PR) — consider softening "essentially every" to "most" in a future content pass, but not a blocker.

• [L118] content/blog/ai-infrastructure-tools/index.md — "Google Vertex AI leads on Google's models and TPUs." — verdict: unverifiable; evidence: This is a subjective marketing/opinion-style claim about Vertex AI's positioning relative to Google's own models (Gemini/PaLM) and TPU hardware, which is trivially true in the sense that Vertex AI is Google's own platform offering first-pa…; source: N/A - subjective blog framing claim, not tied to a specific verifiable fact in pulumi repos or docs; intuition: Vague comparative/opinion claim ("leads on") typical of blog copy; plausible but not something a source definitively co… — Subjective competitive-positioning framing. Trivially true (Vertex is Google's own platform with first-party model/TPU access) but not independently verifiable as a superlative. Untouched line; editorial framing, not a blocker.

• [L118] content/blog/ai-infrastructure-tools/index.md — "AWS SageMaker leads on AWS-native data pipelines." — verdict: unverifiable; evidence: This is a subjective marketing/opinion claim about SageMaker's competitive positioning ("leads on AWS-native data pipelines") from a Pulumi blog post comparing AI infrastructure tools. It is not tied to a verifiable spec, version, or prici…; source: content/blog/ai-infrastructure-tools/index.md; intuition: Subjective competitive-positioning claim ("leads on") in a blog post is opinion/marketing framing rather than a falsifi… — Same pattern of subjective "leads on" framing. Consistent with SageMaker's tight S3/Glue integration, which is ✅ verified separately (L118/L120). Untouched line; not a blocker.

• [L118] content/blog/ai-infrastructure-tools/index.md — "Azure ML leads on Microsoft-stack integration." — verdict: unverifiable; evidence: This is a subjective comparative/opinion claim ("leads on Microsoft-stack integration") about Azure ML vs other AI infrastructure tools, which is inherently a value judgment rather than a checkable technical fact. Azure ML is indeed part o…; source: N/A - qualitative/subjective claim not resolvable via repo or GitHub sources; intuition: Superlative/subjective marketing-style claim ("leads on") in a blog post is typical editorial framing, not a falsifiabl… — Same pattern. Accurate in spirit — Azure ML's GitHub Actions / Azure DevOps / Microsoft Fabric ties are ✅ verified at L122. Untouched line; not a blocker.

• [L160] content/blog/ai-infrastructure-tools/index.md — "Pulumi Neo's governance applies to Pulumi-managed resources, Terraform state, CloudFormation stacks, and manually-created AWS console resources." — verdict: unverifiable; evidence: verification did not converge within 8 turns — Automated verification didn't converge, but the same capability is confirmed elsewhere in the trail: Neo working with Terraform, CloudFormation, and hand-created resources is ✅ verified at L52, L261, and L312. Corroborated; untouched line; not a blocker.

• [L164] content/blog/ai-infrastructure-tools/index.md — "The Pulumi MCP Server brings Neo into Cursor, Claude Code, Claude Desktop, Windsurf, and other MCP-compatible clients." — verdict: unverifiable; evidence: verification did not converge within 8 turns — Verification didn't converge. The Pulumi MCP Server + Neo IDE-client integration is consistent with Pulumi's MCP/Neo product pages. Untouched line; worth a quick confirm against the current supported-client list in a future pass, but not a blocker.

• [L164] content/blog/ai-infrastructure-tools/index.md — "Neo integrates into CI/CD pipelines for pre-merge policy remediation." — verdict: unverifiable; evidence: Pulumi's Neo and Insights & Governance product pages describe MCP-based IDE integration (VS Code, Cursor, Claude Code, Windsurf) and a "review-and-merge" remediation workflow through the Pulumi Cloud UI, but neither page (nor any other doc…; source: repo:content/product/neo.md, repo:content/product/insights-governance.md; intuition: The specific phrase "CI/CD pipelines for pre-merge policy remediation" isn't substantiated anywhere else in the docs — Author check: confirm whether Neo genuinely has a CI/CD pre-merge remediation path or whether this should be reworded. Untouched line — not a blocker for this PR since it's outside the diff.

• [L211] content/blog/ai-infrastructure-tools/index.md — "These general-purpose AI coding assistants can write Terraform HCL, Pulumi programs, and CloudFormation templates." — verdict: unverifiable; evidence: This is a general statement about third-party AI coding assistants' capabilities (writing Terraform HCL, Pulumi programs, CloudFormation templates), not a specific Pulumi product feature that can be checked against Pulumi's own docs or rep…; source: content/blog/ai-infrastructure-tools/index.md (L211); intuition: Claim is plausible and consistent with known LLM capabilities (these tools are trained on public IaC code including Ter… — General LLM-capability claim, plausible and corroborated by the FAQ version at L306–308 (✅ verified against the published post). Untouched line; not a blocker.

• [L280-282] content/blog/ai-infrastructure-tools/index.md — "Pulumi Neo is currently the most complete offering for enterprise governance plus true agentic capability, executing changes rather than just suggesting them,…" — verdict: unverifiable; evidence: This is a subjective competitive-positioning superlative ("most complete offering") about Pulumi's own product. The underlying factual sub-claims (executes changes rather than suggesting, ships pre-built compliance frameworks like CIS/HITR…; source: repo:content/blog/ai-infrastructure-tools/index.md (lines 149-171, 280-282); intuition: Self-referential superlative about the author's own product in a "best of" comparison — expected marketing framing, not ind… — Self-referential superlative about Pulumi's own product in a "best of" FAQ answer — expected vendor framing, not independently verifiable. The underlying sub-claims (executes changes, ships pre-built compliance packs) are ✅ verified elsewhere in the trail. Untouched line; not a blocker.

[github-actions]

💡 Pre-existing issues in touched files (optional)

• [L204] content/blog/ai-infrastructure-tools/index.md — "Upbound's offering is proprietary." — verdict: ❌ contradicted (source: https://blog.upbound.io/open-source-and-upound). Pre-existing: this line sits in the untouched Crossplane/Upbound section (L202–204); this PR only edits the intro paragraph and frontmatter, so it doesn't introduce the claim. The verification step read Upbound's open-source distribution (UXP / Crossplane, Apache 2.0) and flagged "proprietary" as contradicted, but the post is actually distinguishing the open-source project (Crossplane, Apache 2.0) from Upbound's commercial platform — a defensible split. If you revisit this section later, consider making the OSS-vs-commercial distinction explicit (e.g. "Upbound's commercial platform is proprietary").

✅ Resolved since last review

No items resolved since the last review.

📜 Review history

• 2026-07-05T12:50:16Z — SEO/AEO pass: answer-first intro rewrite + opt-in FAQPage schema (frontmatter flag + graph-builder.html guard). Intro vendor claims verify; template guard is correct Hugo; no blockers. One pre-existing ❌ (Upbound "proprietary") and 10 unverifiable claims all sit on untouched lines. (5a53341)
• 2026-07-07T19:50:15Z — re-verified on request (@CamSoper); no new commits to this PR's own content since the last review. The branch merged origin/master (560ec16), which brought in an unrelated template change (Extend FAQPage schema to docs comparison pages (Terraform, OpenTofu, AWS CDK, Crossplane) #20081, extending the same graph-builder.html FAQPage guard to docs-type pages and excluding dedicated FAQ pages). Confirmed this PR's own diff against current master is unchanged — same blog opt-in clause (and (eq .Type "blog") .Params.faq_schema) still present and correctly composed into the merged guard, and the content file has no changes since last review. 0 outstanding findings unchanged; no style nits this run (.vale-findings.json empty).

---

Need a re-review? Want to dispute a finding? Mention @claude and include #update-review.
(For ad-hoc questions or fixes, just @claude — no hashtag.)

[pulumi-bot]

Your site preview for commit 560ec16 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-20083-560ec161.s3-website.us-west-2.amazonaws.com

[pulumi-bot]

Lighthouse Performance Report

Commit: 560ec16 | Metric definitions

Page	Device	Score	FCP	LCP	TBT	CLS	SI
Homepage	Mobile	🔴 35	3.4s	9.7s	4254ms	0.077	4.3s
Homepage	Desktop	🟡 83	0.8s	1.1s	237ms	0.038	2.8s
Install Pulumi	Mobile	🟡 57	5.4s	7.9s	128ms	0.057	7.8s
Install Pulumi	Desktop	🟡 84	1.3s	1.7s	0ms	0.010	2.9s
AWS Get Started	Mobile	🟡 56	5.3s	8.1s	87ms	0.092	8.1s
AWS Get Started	Desktop	🟡 84	1.3s	1.7s	0ms	0.024	2.9s

[CamSoper]

@claude This branch can't merge due to a conflict. Please resolve.

[pulumi-bot]

Claude finished @CamSoper's task in 3m 37s —— View job

---

Merge conflict resolved ✅

• Gather context (fetch latest master, identify conflict)
• Merge/rebase branch onto origin/master
• Resolve conflicting hunks
• Verify build/lint where possible
• Push resolved branch

What happened

The branch's shallow clone couldn't see origin/master's history, so I ran git fetch --unshallow first, then merged origin/master into seo/faq-ai-infrastructure-tools.

The only conflict was in layouts/partials/schema/graph-builder.html. Master had landed a related-but-separate change in the meantime (docs pages also get FAQPage schema, with a dedicated-FAQ-page exclusion), while this PR added the blog opt-in flag. I combined both conditions into one gate:

{{ if and .IsPage (not $isDedicatedFaqPage) (or (eq .Type "what-is") (eq .Type "docs") (and (eq .Type "blog") .Params.faq_schema)) }}

• what-is and docs pages get FAQPage schema automatically (master's change), excluding dedicated FAQ pages.
• Blog posts only get it when faq_schema: true is set in frontmatter (this PR's change).

The merged comment block above the condition documents both rules. content/blog/ai-infrastructure-tools/index.md had no conflicting changes.

Diff vs. origin/master is now clean — just the original 2 files:

content/blog/ai-infrastructure-tools/index.md    | 5 +++--
layouts/partials/schema/graph-builder.html       | 13 +++++++++++--

Note: No Hugo binary/node_modules are available in this environment, and make ensure requires network-installing dependencies that need approval I couldn't obtain here — so I wasn't able to run a local build to render and verify the merged template. The merge is textually correct Go template syntax (verified by inspection, condition structure mirrors both parent branches), but I'd still recommend confirming the live preview renders correctly before merging, consistent with the original PR's own note about this being unverified by a local build.

[CamSoper]

@claude #update-review

[github-actions]

🤖 Review updated on @CamSoper's request.