Add: Platform Engineering in the Agentic Era

[workprentice]

What this adds

A new blog post, "Platform Engineering in the Agentic Era: When Agents Provision" (byline: Joe Duffy), at /blog/platform-engineering-agentic-era/.

The existing platform-engineering coverage on pulumi.com and elsewhere (including our own /what-is/ pillars, the April "Agent Sprawl" post, and Red Hat's May post on developer portals) has already made the observation that AI agents are becoming platform consumers. This post assumes that point is made and goes one level deeper: once an agent isn't just reading the platform for context but calling it to provision infrastructure, what does the platform actually have to provide? It works through identity and credential scope, where policy evaluates in an agent's loop, what replaces code review when no human is watching, blast-radius controls for concurrent agent activity, and what an audit trail needs to contain when no human approved the change.

It cites Gartner's public forecasts (40% of enterprise apps carrying a task-specific agent by end of 2026; over 40% of agentic AI projects canceled by end of 2027), a named expert quote from Luca Galante (Weave Intelligence, via platformengineering.org's 2026 predictions post), and DORA's 2025 research on AI-assisted development. No proprietary or internal data is used anywhere in the piece.

Structure and schema

• Answer-first opening, question-phrased H2s with an ### -level non-question subheading under each one carrying any table/list, per the FAQ-collector convention (faq-entity.html sweeps every ##/### heading ending in ?, so tables and lists always sit under a non-question heading).
• faq_schema: true, no howto_schema (this isn't a step-by-step tutorial).
• Verified the rendered FAQPage JSON-LD with an isolated Hugo harness (real layouts/partials/schema/ + shortcodes + team data, minimal template): 14 questions extracted, each with a clean acceptedAnswer.text (40-90 words, no leaked #/backtick/pipe characters), no @id collisions.
• No feature_image is set, matching the precedent set by the most recent Joe Duffy post (ai-agents-on-kubernetes) in this same voice/series, which also ships without one and falls back cleanly to the default OG image.

Internal linking

• Adds a one-line reciprocal link from /what-is/what-is-platform-engineering/'s existing "How is AI changing platform engineering?" section into this new post (the rest of that page's refresh is tracked separately).
• Links to /what-is/what-is-an-internal-developer-platform/, /what-is/what-is-agentic-infrastructure/, /blog/agent-sprawl-iac-platform-is-the-answer/ (cited explicitly as prior art), /blog/ai-agents-on-kubernetes/, /blog/backstage-vs-pulumi-idp-why-infrastructure-first-platform-engineering-matters/, and /blog/golden-paths-infrastructure-components-and-templates/. Product links (/product/secrets-management/, /docs/insights/policy/, /docs/iac/guides/building-extending/components/build-a-component.md, /docs/iac/concepts/automation-api.md) are used sparingly so the post argues on its own merits rather than reading as a pitch.

Checks run locally

• node scripts/lint/lint-markdown.js — 0 errors on both changed files.
• Pre-commit hook (husky/lint-staged) ran clean.
• Isolated Hugo schema harness — see above.

---

🧠 This PR was created by workprentice.

[github-actions]

Social Media Review

content/blog/platform-engineering-agentic-era/index.md

X — PASS

LinkedIn — PASS

Bluesky — PASS

---

Suggestions (advisory)

These are stylistic notes — they don't block the post.

X

• No detail here is Pulumi-specific — the Gartner stat and "assumes a person calls your APIs" framing could open a post from any platform-engineering vendor; ground it in something only this article's angle can say

LinkedIn

• Second paragraph spells out the article's own framework ("identity, policy, review, and audit") — reads as a table of contents, not a hook; drop the four-item list and tease one thread instead
• "the operational questions a platform team actually has to answer" stays abstract — ground it with one named scenario from the piece
• Nothing here ties to Pulumi specifically — swap the company and the post reads the same; add a Pulumi-specific detail or reference

Bluesky

• Setup makes a generic industry claim ("platform engineering advice hasn't caught up") with no Pulumi-specific angle — swap in any vendor and the post still works

---

Updated for commit 7b0c8c8bb79b005d524c0339e58fe671fbdbad48 (short: 7b0c8c8) at 2026-08-18 13:31 UTC.

[github-actions]

🧹 Optional style suggestions from the pre-merge review — apply or dismiss; none of them block.

---

Generated by Claude Code

[github-actions]

Pre-merge Review — Last updated 2026-08-18T13:29:29Z

Tip

Summary: This PR adds a new blog post, "Platform Engineering in the Agentic Era," on what an internal developer platform has to provide once an AI agent writes to it rather than only reads from it (identity scope, policy gates, blast radius, audit trails, golden paths), plus a one-line cross-link from /what-is/what-is-platform-engineering/ into the new post. The fix push at 7b0c8c8b clears the last remaining note: the L100 paragraph no longer ends two consecutive sentences on the "templating language" contrast — the tail is gone from the first sentence, so the contrast now lands once, in the second sentence, where it carries the cited kagent post's own argument. The shortened first sentence is still supported by the same source (content/blog/ai-agents-on-kubernetes/index.md:211 lists loops, functions, types, and unit tests as what a real language brings), so the claim stays verified rather than needing a new source. A whole-file sweep confirms "templating language" now occurs once. Every bucket is empty; nothing blocks merge.

Review confidence:

Dimension	Level	Notes
mechanics	HIGH	All internal doc links re-checked against the repo, including the two CTA-card targets. blog/cta-card usage validated against the shortcode's own parameter contract.
facts	HIGH	Headline statistics verified against primary sources; the Galante pullquote confirmed verbatim; the kagent cross-reference re-checked against its source sentence after this run's rewording.
coherence	HIGH
editorial balance	HIGH	6 substantive Pulumi mentions across 10 H2 sections, all load-bearing. Unchanged by 7b0c8c8b.
code correctness	MEDIUM	The single TypeScript snippet is illustrative and elided (a constructor body of comments), so it isn't compilable as written — intentional for the point it makes.

Investigation log

• Cross-sibling reads: not run (not in a templated section)
• External claim verification: 25 of 40 claims verified (2 unverifiable, 0 contradicted, 0 framing-drift) · 4 specialists (numerical, cross-reference, capability, framing); 0 cross-specialist corroborations · routed: 0 inline, 13 Pass 1, 2 Pass 2 (verified 2, contradicted 0, unverifiable 0), 25 Pass 3 (verified 12, contradicted 0, unverifiable 13).
• Cited-claim spot-checks: 3 of 3 cited claims fetched and compared (the kagent post re-read from the repo again this run, since the reworded sentence is the one it sources)
• Frontmatter sweep: ran on body + meta_desc + social.{bluesky, linkedin, twitter} (untouched by this push; re-swept to confirm the reworded phrase didn't need a matching frontmatter edit)
• Temporal-trigger sweep: ran (no recency words remain unbounded)
• Code execution: not run (no static/programs/ change)
• Code-examples checks: ran (3 specialists: structural, existence, body-code-coverage); 0 findings
• Editorial-balance pass: ran (10 H2 sections, 0 flags fired) — re-run unchanged; the push removed six words of prose and touched no heading, mention, or FAQ entry
• Scope of this run: re-review of ff7b2a1c...7b0c8c8b (1 new commit, a single-line change to content/blog/platform-engineering-agentic-era/index.md) and re-verification of the one ⚠️ item from the previous review. Claim extraction was not re-run from scratch — the push edits one previously-flagged line — but the two L100 claims were re-read against the kagent source sentence, and the extracted/verified counts are unchanged at 40/25 because the reworded sentence is the same claim, shortened.
• Duplicate-phrase sweep: ran on the phrase the prior finding quoted — "templating language" now occurs once in the file (was twice, in consecutive sentence-final positions)
• Link-integrity re-check: ran (the edited line's only link, /blog/ai-agents-on-kubernetes/, resolves to content/blog/ai-agents-on-kubernetes/index.md; both touched files re-swept for any absolute link ending in .md, 0 found)

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

✏️ 2 one-click style suggestions are posted inline — apply them from the Files changed tab, individually or with Add suggestion to batch.

🔍 Verification trail

40 claims extracted · 25 verified · 2 unverifiable · 0 contradicted · 0 framing-drift (re-verified against 7b0c8c8b)

• L3 in content/blog/platform-engineering-agentic-era/index.md "date: 2026-08-18" → ➖ not-a-claim (evidence: This is a front-matter date field (publication date metadata) for a blog post, not a falsifiable factual assertion.; source: content/blog/platform-engineering-agentic-era/index.md)
• L21 in content/blog/platform-engineering-agentic-era/index.md "Gartner expects 40% of enterprise applications to carry a task-specific AI agent by the end of 2026." (also L31, L168) → ✅ verified (evidence: Gartner's official newsroom press release states: "Forty percent of enterprise applications will be integrated with task-specific AI agents by the end of 2026, up from less than 5% today, according to Gartner Inc."; source: https://www.gartner.com/en/newsroom/press-releases/2025-08-26-gartner-predicts-40-percent-of-enterprise-apps-will-feature-task-specific-ai-agents-by-2026-up-from-less-than-5-percent-in-2025)
• L25 in content/blog/platform-engineering-agentic-era/index.md "Most platform engineering writing about AI agents stops at the observation that agents will use your internal developer platform too." → ➖ not-a-claim (evidence: This is a subjective editorial framing statement characterizing the general state of "platform engineering writing" on a topic, not a falsifiable factual claim with a specific cited source. It's the author's own positioning/opinion…; source: content/blog/platform-engineering-agentic-era/index.md)
• L27 in content/blog/platform-engineering-agentic-era/index.md "The post discusses the operational questions a platform team must answer once an agent starts provisioning infrastructure through the platform: identity, policy, review, and audit." → ➖ not-a-claim (evidence: This is a description of the blog post's own content/argument structure, not a falsifiable external claim requiring verification. Still self-referential after 7b0c8c8b, which didn't touch the frontmatter.; source: content/blog/platform-engineering-agentic-era/index.md)
• L27 in content/blog/platform-engineering-agentic-era/index.md "social.linkedin copy does not repeat a phrase across its two paragraphs" → ✅ verified (evidence: Fixed in ff7b2a1c and unchanged by 7b0c8c8b. The second paragraph's closing beat is "…when the thing asking can already have acted by the time you notice"; a sweep of the whole file for "watching the diff scroll by" returns a single hit (L25, the first paragraph). No other cross-paragraph phrase repeat in the LinkedIn copy.; source: frontmatter re-sweep of social.linkedin against 7b0c8c8b)
• L31 in content/blog/platform-engineering-agentic-era/index.md "Gartner projects that 40% of enterprise apps will carry a task-specific AI agent by the end of 2026." → ✅ verified (evidence: Gartner's official press release states: "Gartner predicts 40% of enterprise applications will be integrated with task-specific AI agents by the end of 2026," up from less than 5% today.; source: https://www.gartner.com/en/newsroom/press-releases/2025-08-26-gartner-predicts-40-percent-of-enterprise-apps-will-feature-task-specific-ai-agents-by-2026-up-from-less-than-5-percent-in-2025)
• L38 in content/blog/platform-engineering-agentic-era/index.md "Red Hat made the point that developer portals matter more in the age of AI agents." → ✅ verified (evidence: The linked page returns HTTP 200 and is titled "Why developer portals matter more in the age of AI agents", which matches the claim's assertion exactly. The unverifiable "in May" date qualifier was dropped in ae9299b6, so the remaining claim is fully supported by the fetched title.; source: https://www.redhat.com/en/blog/why-developer-portals-matter-more-age-ai-agents)
• L38 in content/blog/platform-engineering-agentic-era/index.md "This blog post is the first in Pulumi's writing to stay specific to the case where an AI agent writes to a platform, rather than only reads from it." → 🤷 unverifiable (evidence: This is a self-referential "first in Pulumi's writing" claim about the entire corpus of Pulumi's blog content. Searches show many Pulumi posts (e.g. agentic infrastructure era, Neo, agent skills) discuss agents both reading from and…; source: WebSearch ran query "Pulumi blog AI agent writes to platform vs reads"; top results didn't address the claim's "first" framing; intuition: Superlative "first in Pulumi's writing" claims about an entire content corpus are inherently unfalsifiable via search…) — see 📋 Triaged verifier findings: the post does not actually make this claim.
• L38 in content/blog/platform-engineering-agentic-era/index.md "The Pulumi page 'What Is Platform Engineering?' treats agents as a platform consumer alongside human developers." → ✅ verified (evidence: The "What is Platform Engineering?" page has a section "How is AI changing platform engineering?" with a bullet titled "AI agents as a new class of platform consumer": "Human developers are no longer the only callers of the platform's…; source: gh api repos/pulumi/docs/contents/content/what-is/what-is-platform-engineering.md (read_file with pattern "agent"))
• L42 in content/blog/platform-engineering-agentic-era/index.md "An agent that reads your platform's documentation to answer a question and an agent that calls your platform's API to provision a database are different…" → ➖ not-a-claim (evidence: This is a subjective positioning/opinion statement by the blog author about two categories of AI agents, not a falsifiable factual assertion citing any external source.; source: content/blog/platform-engineering-agentic-era/index.md (author's own framing))
• L46 in content/blog/platform-engineering-agentic-era/index.md "| | Agent reads the platform | Agent writes to the platform |" → ➖ not-a-claim (evidence: This is a table row/header fragment from the blog post's own conceptual comparison table, not a falsifiable third-party claim.; source: content/blog/platform-engineering-agentic-era/index.md)
• L51 in content/blog/platform-engineering-agentic-era/index.md "Red Hat's developer-portal piece is an example of where 'agent reads the platform' content shows up." → ➖ not-a-claim (evidence: This is a table cell in the blog post's own comparison table ("Where it shows up in this writing | Red Hat's developer-portal piece, our own what-is pages | This post"), summarizing citations already made in the same post's prose.; source: content/blog/platform-engineering-agentic-era/index.md)
• L53 in content/blog/platform-engineering-agentic-era/index.md "Pulumi's agent-sprawl blog post named seven things an agent needs from a platform: a trustworthy context lake, pre-cleared integrations, governed actions…" → ✅ verified (framing: Source's terse list ("Context, integrations, governed actions, deterministic policy, audit, review, approval") is elaborated with descriptive adjectives in…; evidence: The Pulumi blog post "Agent Sprawl Is Here. Your IaC Platform Is the Answer." explicitly enumerates "Step back from the seven pillars and look at what they have in common... Context, integrations, governed actions, deterministic policy…; source: https://www.pulumi.com/blog/agent-sprawl-iac-platform-is-the-answer/)
• L61-63 in content/blog/platform-engineering-agentic-era/index.md "A credential scoped to one provisioning run and revoked afterward bounds the damage of a compromised or confused agent in a way a long-lived key never will." → ➖ not-a-claim (evidence: This is an opinion/design-argument statement (a general security reasoning claim about scoped vs. long-lived credentials) made by the blog post author about security best practices, not a falsifiable factual assertion about a specific…; source: content/blog/platform-engineering-agentic-era/index.md)
• L63 in content/blog/platform-engineering-agentic-era/index.md "An agent cleared to provision in a sandbox account should not hold the same credential in production." → ➖ not-a-claim (evidence: This is a prescriptive best-practice statement authored by the blog post itself, not a falsifiable third-party claim.; source: content/blog/platform-engineering-agentic-era/index.md L63)
• L64 in content/blog/platform-engineering-agentic-era/index.md "Pulumi ESC provides dynamic, short-lived credentials pulled at the moment of use and never written to disk, regardless of whether the caller is a human, a CI…" → ✅ verified (framing: Source: "Dynamic, short-lived credentials via OIDC... Automatically revoke access when leases expire" (general capability). Claim narrows this to a specific…; evidence: The /product/secrets-management/ page states: "Secure by default: Dynamic, short-lived credentials via OIDC. No plaintext secrets, anywhere, ever." and "Dynamic credentials: Generate just-in-time, short-lived credentials via OIDC.…; source: gh api repos/pulumi/docs/contents/content/product/secrets-management.md (decoded YAML front matter))
• L66-68 in content/blog/platform-engineering-agentic-era/index.md "Luca Galante, Managing Director & Senior Analyst at Weave Intelligence, stated that AI agents will graduate from experimental tools to first-class platform citizens…" → ✅ verified (evidence: Re-fetched the linked article directly. Under the heading "Prediction 1: Agentic infrastructure becomes standard architecture" the article opens: "AI agents will graduate from experimental tools to first-class platform citizens. By 2026, mature platforms will treat agents like any other user persona, complete with RBAC permissions, resource quotas, and governance policies." — verbatim match for both sentences of the pullquote. The byline reads "Luca Galante, Managing Director & Senior Analyst, Weave Intelligence", matching the attribution string character-for-character. Published 2025-12-12.; source: https://platformengineering.org/blog/10-platform-engineering-predictions-for-2026)
• L70 in content/blog/platform-engineering-agentic-era/index.md "Luca Galante's 2026 predictions were published on platformengineering.org." → ✅ verified (evidence: The cited URL (platformengineering.org/blog/10-platform-engineering-predictions-for-2026) returns HTTP 200 and is titled "10 Platform engineering predictions for 2026", confirming the predictions article was published on…; source: https://platformengineering.org/blog/10-platform-engineering-predictions-for-2026)
• L81 in content/blog/platform-engineering-agentic-era/index.md "pulumi preview shows the actual diff of what will change, including resources added or destroyed." → ✅ verified (evidence: The auto-generated CLI reference (from pulumi/pulumi source) states: "This command displays a preview of the updates to an existing stack whose state is represented by an existing state file... These allocations are then compared against…; source: repo:content/docs/iac/cli/commands/pulumi_preview.md)
• L82 in content/blog/platform-engineering-agentic-era/index.md "Policy as code, as described in Pulumi's policy documentation, is evaluated automatically at a pre-deploy gate and blocks the apply if it fails." → ✅ verified (framing: Source describes "Preventative" as one of two enforcement modes (the other being non-blocking "Audit"); the claim's blanket statement matches the…; evidence: The Pulumi Policies doc (content/docs/insights/policy/_index.md) states: "Preventative: Validates Pulumi stack resources during pulumi preview and pulumi up, blocking deployments when violations are detected. Prevents non-compliant…; source: gh api repos/pulumi/docs/contents/content/docs/insights/policy/_index.md)
• L83 in content/blog/platform-engineering-agentic-era/index.md "Continuous policy and inventory scanning, as documented by Pulumi, operates across the whole estate to catch drift or resources that slipped through other…" → ✅ verified (framing: Claim's "continuous policy and inventory scanning across the whole estate" is a paraphrase of the doc's description of org-wide, account+stack-level governed…; evidence: The Policy Findings doc confirms continuous, organization-wide compliance tracking: "Resource compliance score: The percentage of your governed resources that are fully compliant with all applicable policies. Governed resources include…; source: repo:content/docs/insights/policy/policy-findings.md)
• L83 in content/blog/platform-engineering-agentic-era/index.md "internal link /docs/insights/policy/policy-findings/ resolves to a published page" → ✅ verified (evidence: Fixed in ae9299b6; the .md suffix is gone and content/docs/insights/policy/policy-findings.md is present in the repo, so the rendered href resolves.; source: link-integrity re-check against the site's docs URL scheme)
• L85 in content/blog/platform-engineering-agentic-era/index.md "A pre-deploy gate is the one that matters most for an unattended agent, because it's the only stage that can stop a bad change before it becomes a bad change…" → ➖ not-a-claim (evidence: This is the blog author's own editorial/positioning argument about why pre-deploy gates matter for agentic workflows, not a falsifiable factual claim citing an external source or product spec.; source: content/blog/platform-engineering-agentic-era/index.md)
• L93 in content/blog/platform-engineering-agentic-era/index.md "| | Agent writes code | Agent calls an API or tool |" → ➖ not-a-claim (evidence: This is a table row fragment from the blog post's own comparison table contrasting conceptual approaches, which is the author's own framing/opinion rather than a falsifiable…; source: content/blog/platform-engineering-agentic-era/index.md)
• L95 in content/blog/platform-engineering-agentic-era/index.md "An agent can call a service you've built on Pulumi's Automation API to spin up a pre-defined environment." → ✅ verified (evidence: Reworded in ae9299b6 from "an Automation API endpoint" to "a service you've built on Automation API", which matches the docs' own framing: "a programmatic interface for running Pulumi programs without the Pulumi CLI... a strongly typed SDK, so you can drive the Pulumi engine from within your own application." The prior framing-drift verdict no longer applies.; source: content/docs/iac/concepts/automation-api.md)
• L95 in content/blog/platform-engineering-agentic-era/index.md "internal link /docs/iac/concepts/automation-api/ resolves to a published page" → ✅ verified (evidence: Fixed in ae9299b6; content/docs/iac/concepts/automation-api.md is present in the repo, so the rendered href resolves.; source: link-integrity re-check against the site's docs URL scheme)
• L97 in content/blog/platform-engineering-agentic-era/index.md "| Best for | Novel or exploratory changes, refactors, anything not covered by an existing template | Repeatable, high-volume requests: a new dev environment…" → ➖ not-a-claim (evidence: This is a table cell from the blog post's own comparative framework (agentic vs. template-based workflows), reflecting the author's own opinionated categorization rather than a falsifiable external fact.; source: content/blog/platform-engineering-agentic-era/index.md L97)
• L100 in content/blog/platform-engineering-agentic-era/index.md "Pulumi's blog post about running agent workloads on Kubernetes argued that once you have a package, composing it into your environment, wiring its secrets, gating its rollout with policy, and testing it before it ships is software engineering that a general-purpose language is built for." → ✅ verified (evidence: Unchanged by 7b0c8c8b, which edited only the sentence before it. The cited post says at content/blog/ai-agents-on-kubernetes/index.md:211: "Distributing a reusable, versioned package is a job Helm is built for. Composing that package into your specific cluster, wiring its secrets, gating its rollout with policy, and testing the whole thing before it ships is software engineering, and it benefits from a real language: loops, functions, types, unit tests, and the same CI/CD your application code already runs through." The wording tracks that sentence clause-for-clause, including the Helm-chart framing the same paragraph supplies ("which remain genuinely good tools for packaging and distributing charts").; source: repo:content/blog/ai-agents-on-kubernetes/index.md:211)
• L100 in content/blog/platform-engineering-agentic-era/index.md "Real programming languages carry loops, functions, types, and test frameworks, which means an agent's output can be tested the same way a human's pull request would be." → ✅ verified (evidence: Shortened in 7b0c8c8b — the trailing "that a templating language doesn't" is gone, so the sentence now asserts only the feature list and the testability that follows from it. Both halves are stated directly by the cited source: "…it benefits from a real language: loops, functions, types, unit tests, and the same CI/CD your application code already runs through." The dropped clause was the weaker part of the claim (a comparative the source makes elsewhere in the same sentence rather than as a general statement about templating languages), so the shortened form is more closely sourced than before, not less, and the previous run's framing note about the claim generalizing the source's contrast no longer applies.; source: repo:content/blog/ai-agents-on-kubernetes/index.md:211)
• L111 in content/blog/platform-engineering-agentic-era/index.md "* Cost estimate — a projected cost delta, so an agent's request to 'add capacity' doesn't turn into a five-figure surprise before anyone reads the invoice." → ➖ not-a-claim (evidence: This is a rhetorical illustration within the author's own argument about platform engineering guardrails, not a falsifiable factual assertion attributed to a third party or external source.; source: content/blog/platform-engineering-agentic-era/index.md (self-authored content))
• L136 in content/blog/platform-engineering-agentic-era/index.md "* Before-and-after state — enough to restore the prior state directly, rather than requiring someone to reason out what 'before' looked like." → ➖ not-a-claim (evidence: This is a bullet point expressing the blog author's own opinion/framework about what constitutes good rollback design, not a falsifiable third-party factual claim.; source: content/blog/platform-engineering-agentic-era/index.md (author's own argument))
• L144 in content/blog/platform-engineering-agentic-era/index.md "A Pulumi component is callable from any language the platform supports and can bake org defaults into the resource it creates, rather than relying on the caller to get them right." → ✅ verified (evidence: Reworded in ae9299b6 from "enforce policy internally" to "bake org defaults into the resource it creates". The doc supports both halves of the new wording directly: "Package it as a Pulumi plugin package so it can be consumed from any Pulumi-supported language via a generated SDK," and components "encapsulate best practices." The prior framing-drift verdict no longer applies.; source: repo:content/docs/iac/guides/building-extending/components/build-a-component.md)
• L144 in content/blog/platform-engineering-agentic-era/index.md "internal link /docs/iac/guides/building-extending/components/build-a-component/ resolves to a published page" → ✅ verified (evidence: Fixed in ae9299b6; content/docs/iac/guides/building-extending/components/build-a-component.md is present in the repo, so the rendered href resolves.; source: link-integrity re-check against the site's docs URL scheme)
• L158 in content/blog/platform-engineering-agentic-era/index.md "Pulumi covered the tradeoffs between service catalogs and infrastructure-first platforms in the post 'Backstage vs. Pulumi.'" → ✅ verified (evidence: The post at content/blog/backstage-vs-pulumi-idp-why-infrastructure-first-platform-engineering-matters/index.md (matching the cited slug) explicitly frames the comparison as "Portal-first vs infrastructure-first platform engineering,"…; source: repo:content/blog/backstage-vs-pulumi-idp-why-infrastructure-first-platform-engineering-matters/index.md)
• L158 in content/blog/platform-engineering-agentic-era/index.md "Pulumi covered the shape of golden paths in the post 'Golden Paths: Infrastructure, Components, and Templates.'" → ✅ verified (evidence: The post at /blog/golden-paths-infrastructure-components-and-templates/ is titled "Golden Paths in IDPs: A Complete Guide to Reusable Infrastructure with Pulumi Components and Templates" and states: "In this guide, you'll learn how to…; source: https://www.pulumi.com/blog/golden-paths-infrastructure-components-and-templates/)
• L158 in content/blog/platform-engineering-agentic-era/index.md "The value of a component like this isn't that it's clever, it's that it's the same component whether a human calls it from the CLI or an agent calls it from…" → ➖ not-a-claim (evidence: The sentence is the blog author's own editorial argument about component parity/guardrails, followed by an internal cross-link description.; source: content/blog/platform-engineering-agentic-era/index.md:158)
• L168 in content/blog/platform-engineering-agentic-era/index.md "Gartner expects 40% of enterprise applications to carry a task-specific AI agent by the end of 2026, up from under 5% in 2025." → ✅ verified (evidence: Gartner's official press release states: "Forty percent of enterprise applications will be integrated with task-specific AI agents by the end of 2026, up from less than 5% today."; source: https://www.gartner.com/en/newsroom/press-releases/2025-08-26-gartner-predicts-40-percent-of-enterprise-apps-will-feature-task-specific-ai-agents-by-2026-up-from-less-than-5-percent-in-2025)
• L174 in content/blog/platform-engineering-agentic-era/index.md "### Should platform teams be worried about agentic AI project failure rates?" → ➖ not-a-claim (evidence: This is a section heading phrased as a rhetorical question within the blog post itself, not a falsifiable factual assertion attributed to a third party.; source: content/blog/platform-engineering-agentic-era/index.md)
• L176 in content/blog/platform-engineering-agentic-era/index.md "Gartner projects that over 40% of agentic AI projects will be canceled by the end of 2027 due to escalating costs, unclear business value, or inadequate risk…" → ✅ verified (evidence: Gartner's official press release states: "Over 40% of agentic AI projects will be canceled by the end of 2027, due to escalating costs, unclear business value or inadequate risk controls, according to Gartner, Inc."; source: https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-predicts-over-40-percent-of-agentic-ai-projects-will-be-canceled-by-end-of-2027)
• L184 in content/blog/platform-engineering-agentic-era/index.md "A service catalog does not enforce identity scope, policy evaluation, or audit trails on the infrastructure changes that come out of using a template." → ➖ not-a-claim (evidence: This is the blog author's own analytical/comparative argument in an FAQ section explaining how Pulumi differs from service catalogs like Backstage — it's not attributed to or citing an external authoritative source, and is a general…; source: repo:content/blog/platform-engineering-agentic-era/index.md (line 184 context))
• L188 in content/blog/platform-engineering-agentic-era/index.md "DORA's 2025 research on AI-assisted software development found that AI's primary effect is to amplify an organization's existing strengths and weaknesses…" → ✅ verified (evidence: The official DORA 2025 report page states: "The State of AI-assisted Software Development report reveals AI's primary role is as an amplifier, magnifying an organization's existing strengths and weaknesses." This directly matches the…; source: https://dora.dev/dora-report-2025/)
• L192 in content/blog/platform-engineering-agentic-era/index.md "internal link /docs/get-started/ resolves to a published page" → ✅ verified (evidence: Added in ff7b2a1c (the closing blog/cta-card href). content/docs/get-started/_index.md is present in the repo, so the section landing page renders at that path.; source: link-integrity check against the site's docs URL scheme)
• L193 in content/blog/platform-engineering-agentic-era/index.md "internal link /docs/insights/policy/get-started/ resolves to a published page" → ✅ verified (evidence: Added in ff7b2a1c (the CTA card's body link). content/docs/insights/policy/get-started.md is present in the repo.; source: link-integrity check against the site's docs URL scheme)
• L88 in content/what-is/what-is-platform-engineering.md "* AI agents as a new class of platform consumer: Human developers are no longer the only callers of the platform's APIs. Coding agents, deployment…" → 🤷 unverifiable (evidence: The cited URL /blog/platform-engineering-agentic-era/ could not be located via search; the closest matching Pulumi blog post is /blog/the-agentic-infrastructure-era/. However, the general thesis is corroborated by Pulumi's broader…; source: WebSearch ran query "pulumi.com/blog/platform-engineering-agentic-era"; top results didn't return that exact URL; intuition: Cited source_hint URL slug does not appear to match any live Pulumi blog post found in search; possible…) — see 📋 Triaged verifier findings: the link target is the post this PR adds.

📊 Editorial balance

Section depth, mention distribution, recommendation steering

• Section depth: 10 H2 sections (mean 8.7 lines, median 9.0, std 3.3). No section-depth outliers (≥3× median). Unchanged by 7b0c8c8b, which shortened one sentence within an existing section.
• Vendor / entity mentions: unchanged by this push (the removed words name no entity). Literal "Pulumi" occurrences: 6 — Pulumi ESC (L64), Pulumi's Automation API (L95), "a Pulumi component" (L144), the Backstage-vs-Pulumi cross-link (L158), and the closing CTA-card button label (L192); plus pulumi preview (L81) as a lowercase command. Others: Gartner: 3 · Backstage: 2 · Red Hat: 2 · DORA: 1 · Weave Intelligence / platformengineering.org: 1 each · Kubernetes: 1. Every Pulumi mention names a specific capability the surrounding sentence depends on; none is a name-drop. Competitor mentions are brief and comparative rather than dismissive; no threshold trip.
• FAQ steering: 6 FAQ entries; 2 name Pulumi-adjacent capability generically (policy as code, components), 1 compares against Backstage/service catalogs, 3 answer vendor-neutrally. No FAQ entry closes with a product CTA — the CTA card sits after the post's final "Where this goes next" section, not inside the FAQ block, so it doesn't trip the steering check.

🚨 Outstanding in this PR

No outstanding findings. The last remaining note is fixed in 7b0c8c8b — see ✅ Resolved since last review.

⚠️ Low-confidence

No low-confidence findings.

Style suggestions

Optional polish from pattern-based linting — never blocking, not counted above. Take the ones that read better and ignore the rest. ✏️ marks one you can apply from the Files changed tab — use Add suggestion to batch on each, then Commit suggestions to take several in a single commit.

content/blog/platform-engineering-agentic-era/index.md

• line 74: [style] weasel word — 'usually' is a weasel word!
• line 116: [style] difficulty qualifier — Avoid difficulty qualifier 'easy' -- it judges difficulty for the reader (STYLE-GUIDE.md §Inclusive Language). ✏️

content/what-is/what-is-platform-engineering.md

• line 88: [style] weasel word — 'significantly' is a weasel word! ✏️

📋 Triaged verifier findings

I double-checked these and realized they weren't real findings — click to expand

• [L38] content/blog/platform-engineering-agentic-era/index.md — "This blog post is the first in Pulumi's writing to stay specific to the case where an AI agent writes to a platform, rather than only reads from it." — Mis-sourced: the post never makes a "first in Pulumi's writing" claim. The published sentence is "This post is about that gap, and it stays specific to the case where the caller writes" — a statement of scope, not a priority claim. The verification step checked a stronger reading than the text asserts.

• [L88] content/what-is/what-is-platform-engineering.md — "…see Platform Engineering in the Agentic Era" — Mis-sourced: the link target couldn't be found live because it's the post this same PR adds. The slug in the new post's directory (content/blog/platform-engineering-agentic-era/) matches the href exactly, so the link resolves once this merges.

💡 Pre-existing issues in touched files (optional)

No pre-existing issues in touched files.

✅ Resolved since last review

• [L100] content/blog/platform-engineering-agentic-era/index.md — the rewritten paragraph ended two consecutive sentences on the same contrast: "…test frameworks that a templating language doesn't" followed by "…a general-purpose language is built for that in a way a templating language isn't." Fixed in 7b0c8c8b, exactly as suggested: the tail is dropped from the first sentence, which now ends on the testability point it was actually making, and the contrast lands once — in the second sentence, where it carries the cited post's own argument. A whole-file sweep for "templating language" returns a single hit. The shortened sentence stays ✅ verified against the same source; the clause that went away was the looser half of the claim, so the remaining assertion is more closely sourced than before.

• [L100] content/blog/platform-engineering-agentic-era/index.md — "that's the same argument we made about running agent workloads on Kubernetes: code that an agent produces is only as trustworthy as the tooling that can check it, and a general-purpose language gives that tooling more to work with than a fixed schema does" — that formulation isn't in the cited post, which credits it with an argument it doesn't state. Fixed in ff7b2a1c. The new wording tracks the source sentence at content/blog/ai-agents-on-kubernetes/index.md:211 clause-for-clause ("Composing that package into your specific cluster, wiring its secrets, gating its rollout with policy, and testing the whole thing before it ships is software engineering, and it benefits from a real language"), and the "whether a Helm chart or a golden-path component" framing matches that paragraph's explicit "this isn't a knock on Helm or Kustomize" stance. The claim moves from 🤷 unverifiable to ✅ verified — this was the last remaining over-strong paraphrase in the post.

• [L27] content/blog/platform-engineering-agentic-era/index.md — the tightened social.linkedin copy used "watching the diff scroll by" in both paragraphs, spending the closing beat on a line the reader had just seen. Fixed in ff7b2a1c: the second paragraph now closes "…when the thing asking can already have acted by the time you notice", which keeps the paragraph's job (naming identity, policy, review, and audit) and ends on the stake rather than a repeat. A sweep of the whole file for the phrase returns one hit.

• [L83] (previously L81) content/blog/platform-engineering-agentic-era/index.md — the link target /docs/insights/policy/policy-findings.md keeps its .md extension, which Hugo does not strip from an absolute in-content link. Fixed in ae9299b6: now /docs/insights/policy/policy-findings/, and content/docs/insights/policy/policy-findings.md is present in the repo.

• [L95] (previously L93) content/blog/platform-engineering-agentic-era/index.md — /docs/iac/concepts/automation-api.md should be /docs/iac/concepts/automation-api/. Fixed in ae9299b6.

• [L144] (previously L142) content/blog/platform-engineering-agentic-era/index.md — /docs/iac/guides/building-extending/components/build-a-component.md should be /docs/iac/guides/building-extending/components/build-a-component/. Fixed in ae9299b6. A sweep of both touched files for any remaining absolute link ending in .md found none.

• [L66-68] (previously L64-66) content/blog/platform-engineering-agentic-era/index.md — the Luca Galante pullquote could not be located in the 2026 predictions article the post links immediately afterward, or in any other source. concede: author is right — I re-fetched the article and both sentences of the pullquote appear verbatim under "Prediction 1: Agentic infrastructure becomes standard architecture," with the byline matching the attribution string exactly. My first-review fetch did not reach the prediction bodies. No change needed; the pullquote is correctly attributed and correctly rendered as a quote.

• [L38] (previously L36) content/blog/platform-engineering-agentic-era/index.md — "Red Hat made the same point about developer portals in May." — the page renders its publication date client-side, so the month couldn't be confirmed. Fixed in ae9299b6: the month qualifier is dropped, and what remains ("Red Hat made the same point about developer portals") is supported by the linked page's title.

• [L95] (previously L93) content/blog/platform-engineering-agentic-era/index.md — "an Automation API endpoint to spin up a pre-defined environment" — reads as though Pulumi exposes a REST endpoint an agent can hit. Fixed in ae9299b6: now "a service you've built on Automation API", which matches the docs' SDK framing.

• [L144] (previously L142) content/blog/platform-engineering-agentic-era/index.md — "it can enforce policy internally rather than relying on the caller to get it right" — suggests a policy mechanism inside the component that the docs don't describe. Fixed in ae9299b6: now "it can bake org defaults into the resource it creates, rather than relying on the caller to get them right", which matches both the docs and the snippet below it.

📜 Review history

• 2026-08-18T12:36:47Z — First review: 3 internal doc links carry a .md extension and 404 as rendered, the Luca Galante pullquote couldn't be located in its linked source, and two framing fixes (Automation API described as an "endpoint," components described as enforcing policy internally); headline Gartner and DORA statistics verified. (323b8e9)
• 2026-08-18T12:59:58Z — Re-reviewed after fix push (1 new commit, ae9299b). All 4 outstanding findings cleared: 3 .md links fixed and re-verified against the repo, and the Galante pullquote conceded to @workprentice[bot]'s dispute. On the dispute: the author asserted the quote is verbatim in the linked article and that my first-review fetch may have been truncated. This is a verifiable claim, so I re-fetched https://platformengineering.org/blog/10-platform-engineering-predictions-for-2026 rather than deferring — the section "Prediction 1: Agentic infrastructure becomes standard architecture" opens with exactly the two sentences in the pullquote, and the byline matches the attribution string character-for-character. The author's diagnosis of the first-review failure was correct. Also resolved from ⚠️ Low-confidence: the "in May" Red Hat qualifier, the Automation API framing, and the component policy-enforcement framing. One new ⚠️ Low-confidence item introduced by the push: the tightened LinkedIn copy repeats "watching the diff scroll by" in both paragraphs. The L100 attribution to Pulumi's own Kubernetes post is unchanged and still open as ⚠️. Outstanding: 0. (ae9299b)
• 2026-08-18T13:19:40Z — Re-reviewed after fix push (1 new commit, ff7b2a1). Both ⚠️ items cleared. On L100: @workprentice[bot] recast the cross-reference rather than softening it, which is the stronger fix — I re-read the cited post from the repo and content/blog/ai-agents-on-kubernetes/index.md:211 reads "Composing that package into your specific cluster, wiring its secrets, gating its rollout with policy, and testing the whole thing before it ships is software engineering, and it benefits from a real language," so the new sentence is a clause-for-clause paraphrase rather than a synthesis, and the "whether a Helm chart or a golden-path component" hedge matches that same paragraph's explicit "this isn't a knock on Helm or Kustomize." That claim moves 🤷 → ✅. On L27: the phrase repeat is gone; a whole-file sweep for "watching the diff scroll by" returns one hit. On the CTA shortcode: validated against layouts/shortcodes/blog/cta-card.html — named-parameter closed form (the template reads .Inner, so an unclosed shortcode would be a build error), title/label/href are all in the documented set, and both link targets exist in the repo (content/docs/get-started/_index.md, content/docs/insights/policy/get-started.md). The AGENTS.md reading is right: blog/cta-card is reserved for destinations with no card of their own plus generic get-started asks, and this is both. One correction to the mention's framing, for the record rather than as a finding — the diff shows the card as a pure addition (+4/-0 at the end of the file), not a conversion of an existing hand-written CTA; there was no prior closing CTA in the post. The cited precedent is also slightly off (pulumi-kubernetes-operator-2-0 doesn't use the shortcode), but six other posts do, including converting-full-terraform-programs-to-pulumi with the same title/label/href triple. On Pulumi-mention balance: confirmed, and the recount is in 📊 Editorial balance above — 6 literal mentions plus one pulumi preview, each naming a capability its sentence depends on, and the new CTA lands after the closing section rather than inside the FAQ block, so the steering check stays clean. One new ⚠️ Low-confidence item, cosmetic only: the rewritten L100 paragraph now ends two consecutive sentences on the "templating language" contrast. Outstanding: 0 → nothing blocks merge. (ff7b2a1)
• 2026-08-18T13:29:29Z — Re-reviewed after fix push (1 new commit, 7b0c8c8). The one remaining ⚠️ item is cleared. @workprentice[bot] took the suggested rewrite verbatim: the diff is a single line, dropping "that a templating language doesn't" from the first sentence of the L100 paragraph. A whole-file sweep confirms "templating language" now appears once, in the second sentence, so the contrast lands where the citation's own argument puts it. I re-read content/blog/ai-agents-on-kubernetes/index.md:211 again because the edited sentence is the one that sources to it, and the shortened claim is if anything better supported than the longer one — the source states the feature list directly ("it benefits from a real language: loops, functions, types, unit tests"), while the dropped clause was a comparative the source makes only in passing within that same sentence, not as a general statement about templating languages. That trail entry keeps its ✅ and loses the framing note it carried about generalizing the source's contrast. Nothing else in the file moved: no heading, entity mention, FAQ entry, link, or frontmatter key is touched, so the editorial-balance and link-integrity re-runs come back unchanged. All four buckets are now empty; nothing blocks merge. (7b0c8c8)

---

• Refresh this review — comment @claude #update-review. Say what you fixed, or which finding you dispute and why; both work in the same mention.
• Ask for anything else — comment @claude with no hashtag (questions, one-off fixes). Leaves this review untouched.

Important

Please don't hide, resolve, or delete this comment! It breaks things!

📖 How pre-merge review works — the full lifecycle, short-circuits, and escape hatches.

[pulumi-bot]

Your site preview for commit 7b0c8c8 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-20949-7b0c8c8b.s3-website.us-west-2.amazonaws.com

Changed pages:

• /blog/platform-engineering-agentic-era/
• /what-is/what-is-platform-engineering/

[workprentice]

@claude #update-review

Fixed at ae9299b65c (was 323b8e979b):

• Dead .md links (3, outstanding): fixed all three — /docs/insights/policy/policy-findings/, /docs/iac/concepts/automation-api/, /docs/iac/guides/building-extending/components/build-a-component/.
• Framing drift on Automation API / components: reworded both per the suggestion — Automation API is now described as something you build a service on rather than an "endpoint," and the component line no longer claims it "enforces policy internally."
• Red Hat "in May" date qualifier: dropped; the sentence no longer asserts a date I can't independently re-confirm at review time.
• Social copy (Bluesky FAIL): applied your suggested two-paragraph repair.
• LinkedIn table-of-contents nit: tightened so it teases the article's questions instead of listing all five.
• Also cleaned up a few weasel words/wordier phrasing (usually, obviously, just, largely) flagged in the inline suggestions.

Disputing the Galante pullquote finding: I fetched https://platformengineering.org/blog/10-platform-engineering-predictions-for-2026 directly this session (not just at draft time) and the quote is verbatim in "Prediction 1: Agentic infrastructure becomes standard architecture": "AI agents will graduate from experimental tools to first-class platform citizens. By 2026, mature platforms will treat agents like any other user persona, complete with RBAC permissions, resource quotas, and governance policies." Byline on the page confirms "Luca Galante — Managing Director & Senior Analyst, Weave Intelligence." If your fetch of that page was truncated or blocked, that would explain the mismatch; happy to paste the surrounding paragraph if useful for re-verification.

[CamSoper]

@workprentice clean review, and the Galante concession was a good dispute to hold. Two ⚠️ left — please take both.

1. L100 — this one is worth more than the review gives it. I read content/blog/ai-agents-on-kubernetes/index.md at head. The sentence here says "code that an agent produces is only as trustworthy as the tooling that can check it, and a general-purpose language gives that tooling more to work with than a fixed schema does", framed as "that's the same argument we made." That post doesn't make that argument, and on the specific fixed-schema contrast it points the other way: L243 says kagent's CRDs "exist specifically to make those concepts declarative, so a policy engine, a reviewer, or another automation can reason about them the same way it reasons about a Deployment or a Service" — i.e. the fixed schema is the thing that gives tooling something to work with. What that post actually argues (L207-211) is narrower: a general-purpose language beats templated YAML for composing, testing, and gating a package once you have it, explicitly "not a knock on Helm or Kustomize."

   So don't just soften the attribution — the claim as written would read as careless to anyone who follows the link. Either recast it to the composing/testing/gating argument the post does make, or drop the cross-reference and let the sentence stand as this post's own point.

2. L27 — take the reviewer's rewrite of the second social.linkedin paragraph. "Watching the diff scroll by" landing in both paragraphs reads as an editing artifact, and it spends the closing beat on a line the reader just saw.

Push both together and request the review refresh yourself the usual way — the hashtag form, prefixed with the mention it needs to fire.

---

Generated by Claude Code

[github-actions]

🧹 Optional style suggestions from the pre-merge review — apply or dismiss; none of them block.

---

Generated by Claude Code

[github-actions]

🤖 Review updated on @workprentice[bot]'s request.

[workprentice]

Pushed ff7b2a1c53, addressing both outstanding items plus the CTA questions:

1. L100 — recast the cross-reference rather than just softening it. It now points to the argument the kagent post actually makes (L207-211: a general-purpose language wins for composing, testing, and gating a package once you have it, not a knock on Helm/Kustomize) instead of the fixed-schema framing that post argues against.
2. L27 — reworded the second social.linkedin paragraph's closing beat so it no longer repeats "watching the diff scroll by" from the first paragraph.
3. CTA shortcode — converted the hand-written closing CTA to blog/cta-card (title/label/href to /docs/get-started/, body keeps the policy-as-code link), matching AGENTS.md's reservation of that shortcode for docs/product/signup and generic get-started asks — same pattern already in production on the pulumi-kubernetes-operator-2-0 post.
4. Pulumi-mention balance — checked: 9 mentions across the post, all substantive (Pulumi ESC, pulumi preview, Pulumi component, Automation API, the Backstage-vs-Pulumi cross-link, and the closing CTA), none name-dropped for its own sake. Reads balanced to me, but noted for whatever the balance pass flags.

@claude #update-review

[github-actions]

🧹 Optional style suggestions from the pre-merge review — apply or dismiss; none of them block.

---

Generated by Claude Code

[github-actions]

🤖 Review updated on @workprentice[bot]'s request.

[CamSoper]

Two things.

Correction to the review, for the record. The 13:19:40Z entry says "The cited precedent is also slightly off (pulumi-kubernetes-operator-2-0 doesn't use the shortcode)." It does. Checked against origin/master:

$ git show origin/master:content/blog/pulumi-kubernetes-operator-2-0/index.md | grep -n 'cta-card'
382:{{< blog/cta-card title="Run Pulumi inside your cluster" >}}
384:{{< /blog/cta-card >}}

@workprentice's citation was accurate. Worth correcting since it's in the permanent review history, and since the surrounding note reads as though the author cited a precedent that doesn't exist. (The related note that the card is a pure addition rather than a conversion is a merge-base artifact: 828ea878 added a hand-written CTA and ff7b2a1c converted it to the shortcode, so across the two-commit span the net diff is +4/-0 even though the conversion did happen. Not worth a change either way.)

@workprentice — one ⚠️ left, and it's worth taking. The L100 rewrite is correct on substance but now ends two consecutive sentences on the same "templating language" contrast. Take the reviewer's version: drop the tail from the first sentence and let the contrast land once, in the second sentence where it's carrying the citation's own argument. Nothing else is outstanding after that.

---

Generated by Claude Code

[workprentice]

Thanks for the correction on the precedent, and taking the last one. Pushed 7b0c8c8bb7: dropped the "that a templating language doesn't" tail from the first sentence so the templating-language contrast lands once, in the second sentence, where it carries the kagent post's own argument.

@claude #update-review

[github-actions]

🧹 Optional style suggestions from the pre-merge review — apply or dismiss; none of them block.

---

Generated by Claude Code

[github-actions]

[style] difficulty qualifier — drops difficulty judgment, same meaning

Suggested change

	Concurrency is the failure mode that doesn't show up until an agent workflow scales past a demo: one agent provisioning one environment is easy to reason about, and fifty agents proposing changes to overlapping infrastructure at the same time is a distributed-systems problem a platform has to solve before it happens, not after.
	Concurrency is the failure mode that doesn't show up until an agent workflow scales past a demo: one agent provisioning one environment is straightforward to reason about, and fifty agents proposing changes to overlapping infrastructure at the same time is a distributed-systems problem a platform has to solve before it happens, not after.

[github-actions]

[style] weasel word — removes unquantified intensifier

Suggested change

* **AI agents as a new class of platform consumer**: Human developers are no longer the only callers of the platform's APIs. Coding agents, deployment agents, and on-call agents increasingly provision, debug, and remediate infrastructure directly. That makes a clean, programmatic, well-documented platform interface significantly more valuable, with strong authentication, authorization, and audit trails on it as table stakes. For the operational questions this raises, identity and credential scope, where policy evaluates, and what replaces code review when no human is watching, see [Platform Engineering in the Agentic Era](/blog/platform-engineering-agentic-era/).

* **AI agents as a new class of platform consumer**: Human developers are no longer the only callers of the platform's APIs. Coding agents, deployment agents, and on-call agents increasingly provision, debug, and remediate infrastructure directly. That makes a clean, programmatic, well-documented platform interface more valuable, with strong authentication, authorization, and audit trails on it as table stakes. For the operational questions this raises, identity and credential scope, where policy evaluates, and what replaces code review when no human is watching, see [Platform Engineering in the Agentic Era](/blog/platform-engineering-agentic-era/).

[github-actions]

🤖 Review updated on @workprentice[bot]'s request.

[workprentice]

Review refreshed against 7b0c8c8bb7: Outstanding 0, Low-confidence 0, Pre-existing 0, Resolved 10. CI is green. Standing by for merge.

[CamSoper]

@workprentice Excellent, thank you. Tagging in @cnunciato for approval and merging.