Skip to content

Drop unbounded speed claims from Neo capability grid - #21582

Open
workprentice[bot] wants to merge 1 commit into
masterfrom
workprentice/neo-in-seconds-claim
Open

workprentice[bot] wants to merge 1 commit into
masterfrom
workprentice/neo-in-seconds-claim

Conversation

@workprentice

@workprentice workprentice Bot commented Sep 13, 2026

Copy link
Copy Markdown
Contributor

Fixes #21581

Drops two unbounded, unverifiable speed claims from the Neo capability grid on the product page: "Instantly surface..." and "...explains in seconds." Both promise a specific timeline for an open-ended operation across an arbitrary cloud estate or deployment, which we can't actually guarantee. This is the same defect class #21569 fixed at line 39 ("in minutes") on this same page; these two were left over from that sweep.

Before:

Instantly surface your least-used, most expensive resources and get actionable recommendations to reduce cloud spend.

Ask why a deployment failed or what's misconfigured. Neo investigates and explains in seconds.

After:

Surface your least-used, most expensive resources and get actionable recommendations to reduce cloud spend.

Ask why a deployment failed or what's misconfigured. Neo investigates and explains what went wrong.

Scope note: I re-audited the whole file for every speed/immediacy/timeline pattern (second, minute, hour, day, instant, immediate, real-time, within, fast, quick, rapid) before making this change. Line 39's "in minutes" claim is already fixed by the separate, already-mergeable PR #21569 and is intentionally not touched here to avoid duplicating or conflicting with that review. Line 35's "industry's first AI agent" is a superlative/priority claim, not a timeline promise, and tracks Pulumi's approved positioning, so it's out of scope for this fix. No other instances remain on the page.

This is a plain-text content change to two YAML front-matter scalars rendered via {{ .description | markdownify }} in template-three-column.html; no template or rendering logic is touched.


🧠 This PR was created by workprentice.

Replaces 'Instantly surface...' and '...explains in seconds' with
plain descriptions of the capability. Fixes #21581.
@github-actions github-actions Bot added review:triaging Claude Triage is currently classifying the PR domain:website PR touches marketing, pricing, legal, or competitive landing pages review:in-progress Claude review is currently running and removed review:triaging Claude Triage is currently classifying the PR labels Sep 13, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Reviewer's guide v1 — not for the author

Tip

This is the reviewer's guide. Work through the ⚠️ checklist below, then approve — approving asserts only that the ⚠️ items looked right to you. Machine-verified this run: links, shortcodes, page metadata, and every claim marked verified (receipts on the evidence page). Code samples are read, not compiled.

PR author: your to-do list is the other review comment, "Author action guide" — nothing on this card is yours.

Note

What this PR changes:

  • Cost optimization card: drops "Instantly" from the front of the description.
  • Debug & diagnose card: replaces "explains in seconds" with "explains what went wrong".

The wrongness that would matter here is a capability blurb promising performance the product can't guarantee, or a rewrite that quietly changes what Neo does. Claim verification ran over the page's capability statements and a frontmatter sweep ran on the body and meta_desc.

Review confidence:

Dimension Level Notes
mechanics HIGH
facts HIGH Both edits narrow existing copy; no new capability is asserted.

⚠️ Check these before approving

No findings to check — but the editorial stances below still need a human eye.

Editorial stances introduced by this PR

Superlative, ranking, or comparative language the diff adds. No verdict — a page's own framing isn't fact-checkable — but confirm each is a stance the docs should take, and that no agent-written rewrite introduced it unasked.

None — the extractor found no positioning or comparison language in this PR's added lines.

✅ What you can rubber-stamp

  • Facts: 3 factual claims checked — 3 verified clean.
  • Mechanics: frontmatter sweep ran; no internal links added.
  • Style: 0 advisory suggestion(s) left with the author; never blocking.

💡 Pre-existing issues in touched files: 0 — details on the evidence page.

📎 Full evidence: verification trail, investigation log, review history.

Review v1 · updated 2026-09-13T00:11:16Z · head commit 48dd696


For the reviewer: the ⚠️ items above are the minutes that matter — the receipts for everything machine-verified are on the evidence page. The author's open items live on their own card (the comment headed "Author action guide"); while any are open, a Waiting on the author list above tracks them, and merge stays blocked until they're answered. If something here seems off, comment on the PR — @claude <your point> #update-review re-adjudicates with your input.

@github-actions

Copy link
Copy Markdown
Contributor

Author action guide v1 — nothing blocks merge

Note

Nothing here blocks merge — no open items need an answer from you. A human reviewer still approves the merge.

This PR softens two capability blurbs on the Neo product page by dropping the unbounded speed words ("Instantly", "in seconds"); the review checked the page's factual claims, frontmatter, and prose style and found nothing to fix.

🚨 Fix or disagree

Nothing to fix — this section is empty.

❓ Questions for you

No open questions for you.

📎 Full evidence: verification trail, investigation log, review history.

Review v1 · updated 2026-09-13T00:11:16Z · head commit 48dd696


How to answer

Every 🚨 and ❓ item above needs one of these before merge:

  1. Fix it — push the change. If your push lines up with the flagged lines, this card shows a 🔄 banner within a minute and then refreshes itself. No banner? Comment:

    @claude I pushed a fix for F1 #update-review
    
  2. Disagree with it — say which item and why; the review re-checks with your input:

    @claude F2: <your reasoning — e.g. where the figure comes from> #update-review
    

    Either way your answer counts: the review marks the item resolved, or keeps it with a 🛡️ note for your human reviewer to weigh — it stops blocking merge in both cases.

  3. Accept it as-is — you own the PR; a one-line reason is a valid answer, and your reviewer sees it beside the finding:

    @claude F2: accepting as-is — <your reason> #update-review
    

    To accept every open item at once: @claude accepting all open items — <reason> #update-review.

The #update-review hashtag matters — it routes your reply to this review, and (besides pushing a fix) it is the only reply that unblocks merge. A bare @claude gets you ad-hoc help and leaves this card — and the merge block — untouched.

Please don't edit, hide, or delete this comment — it is the review's record. Full mechanics: CONTRIBUTING.md §AI-assisted contributions.

@github-actions github-actions Bot added review:no-blockers Claude review completed cleanly; outstanding is empty and removed review:in-progress Claude review is currently running labels Sep 13, 2026
@pulumi-bot

Copy link
Copy Markdown
Collaborator

Your site preview for commit 48dd696 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-21582-48dd696e.s3-website.us-west-2.amazonaws.com

Changed pages:

@workprentice
workprentice Bot enabled auto-merge (squash) September 13, 2026 00:18
@CamSoper
CamSoper requested a review from cnunciato September 14, 2026 22:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

domain:website PR touches marketing, pricing, legal, or competitive landing pages review:no-blockers Claude review completed cleanly; outstanding is empty

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unbounded "in seconds" / "Instantly" speed claims in the Neo capability grid

2 participants