Drop unverifiable "in minutes" claim from the /product/superintelligence-infrastructure/ closing heading
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown
- Domain
- documentation
Research direction
Edit content/product/superintelligence-infrastructure.md around line 147, in the learn: block that renders the closing CTA heading. Compare the rendered heading with the page's supporting proof points, remove the unverifiable time claim, and verify the heading now reads "Build superintelligence infrastructure".
Written by the indexing model from the issue text.
Description
Where
content/product/superintelligence-infrastructure.md line 147, the learn: block that renders as the closing CTA heading (<h2> in <section id="learn">) on https://www.pulumi.com/product/superintelligence-infrastructure/.
What's live today
Build superintelligence infrastructure in minutes
Why this needs a fix
"Superintelligence infrastructure" is an open-ended outcome with no defined scope, so pairing it with a bounded time claim ("in minutes") is not verifiable and reads as marketing hyperbole rather than a claim we could stand behind if asked.
The page's own cited proof points undercut the claim directly. The stats band on the same page (lines 24-25) reports Snowflake's deployment cycles going from 1.5 weeks to under 24 hours, not minutes. The Supabase case study on the same page (line 75) cites a week for regional infrastructure readiness. The page's own overview (line 13) scopes "superintelligence infrastructure" as spanning "pre-training on 100,000+ GPUs to serving billions of inference requests" - work that takes far longer than minutes by any customer evidence the page itself presents.
That mismatch between a closing headline and the body's own supporting data is exactly the kind of inconsistency an AI answer engine or a skeptical reader picks up on, and it undercuts the credibility of the surrounding, better-supported claims.
Proposed fix
Drop the time claim and let the heading stand on the outcome alone:
Build superintelligence infrastructure
An alternative would be to move the time-bound claim down to the first item under the heading ("Get started with Pulumi Cloud in minutes"), since that's the actual bounded action being described. We'd lean against that option here because the item directly below the heading is already titled "Get started with Pulumi Cloud", so repeating it in the heading would make the H2 and the H5 beneath it nearly identical.
Opening a PR against this issue now.
- Dominant language
- HTML
- Stars
- 178
- Forks
- 271
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 546
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pulumi/docs
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
area/www-content Bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
area/www-content Bug
Difficulty 1/5 Under an hour Newbie friendliness 94/100
-
area/docs-content Bug kind/bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
area/automation area/infrastructure awaiting-upstream
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100