Review evidence

Verification trail

No claims match the current filter.

Findings

Editorial stances

Superlative, ranking, or comparative language the diff adds. No verdict — a page's own framing isn't fact-checkable — listed so a reviewer can confirm each is a stance the docs should take.

• content/docs/ai/agents/permissions.md L44 To start a task, a teammate needs `agent_task:create` and access to the agent. For an agent with an assigned role, the teammate must hold that role directly… positioning · found by regex

Investigation log

cross-sibling-reads

0 of 8 siblings

external-claim-verification

175 of 333 claims verified (138 unverifiable, 1 contradicted) · 4 specialists (numerical, cross-reference, capability, framing); 0 cross-specialist corroborations · routed: 0 inline, 280 Pass 1, 7 Pass 2 (verified 1, contradicted 0, unverifiable 6), 46 Pass 3 (verified 19, contradicted 1, unverifiable 26).

cited-claim-spot-checks

7 of 7 cited claims fetched and compared

frontmatter-sweep

ran on body + meta_desc

temporal-trigger-sweep

ran (recency words present in diff; spot-check in-review)

code-execution

not run (no `static/programs/` change)

code-examples-checks

ran (3 specialists: structural, existence, body-code-coverage); 0 findings

editorial-balance-pass

not run (not under content/blog/)

Triaged

• {
    "file": "content/docs/ai/agents/_index.md",
    "from_bucket": "outstanding",
    "id": "F2",
    "kind": "spurious",
    "note": "The closing \"Use Pulumi Agents\" section is a standard next-steps hub, and repeating the tasks link there doesn't cost the reader anything."
  }

• {
    "file": "content/docs/ai/agents/integrations.md",
    "from_bucket": "outstanding",
    "id": "F3",
    "kind": "spurious",
    "note": "The steps are in the right order: select integrations in the agent's configuration, then edit that selection to add integrations connected later. Nothing is missing."
  }

• {
    "file": "content/docs/ai/agents/permissions.md",
    "from_bucket": "outstanding",
    "id": "F5",
    "kind": "spurious",
    "note": "This sentence comes after the role requirements it qualifies, so no prerequisite is out of order."
  }

• {
    "file": "content/docs/ai/agents/reference.md",
    "from_bucket": "outstanding",
    "id": "F6",
    "kind": "spurious",
    "note": "A preview reference page with a single section is deliberate. The H2 isn't orphaned."
  }

• {
    "file": "content/docs/ai/agents/integrations/aws.md",
    "from_bucket": "author-answer",
    "id": "F10",
    "kind": "spurious",
    "note": "IAM treats `s3:GetBucketVersioning` as its own bucket-level action, separate from object reads (`s3:GetObject`) and from `s3:PutBucketVersioning`, so the sentence is correct as written."
  }

• {
    "file": "content/docs/ai/agents/integrations/datadog.md",
    "from_bucket": "author-answer",
    "id": "F11",
    "kind": "spurious",
    "note": "This is a citation, not a claim: the link is live and points at Datadog's key-requirements section."
  }

• {
    "file": "content/docs/ai/_index.md",
    "from_bucket": "reviewer-check",
    "id": "F23",
    "kind": "spurious",
    "note": "This is a high-level summary of what the new agents pages document in detail. The weak support doesn't change anything for the reader."
  }

• {
    "file": "content/docs/ai/agents/custom.md",
    "from_bucket": "reviewer-check",
    "id": "F25",
    "kind": "spurious",
    "note": "Saying an agent needs VCS push and PR permissions in order to push and open PRs is true by definition."
  }

• {
    "file": "content/docs/ai/agents/integrations/google-cloud.md",
    "from_bucket": "reviewer-check",
    "id": "F27",
    "kind": "spurious",
    "note": "A connection having name and notes fields matches the AWS and Azure sibling pages, and a wrong label wouldn't block a reader."
  }

• {
    "file": "content/docs/ai/neo/integrations/mcp/_index.md",
    "from_bucket": "reviewer-check",
    "id": "F29",
    "kind": "spurious",
    "note": "The Supabase steps match Supabase's Access Tokens UI, and the claim was verified."
  }

History

1. 2026-10-22T22:24:15Z 7fbea27

   initial review (pending publication)

2. 2026-10-23T18:03:43Z 6de586eee6

   Re-verified 6de586e: F1 Honeycomb wording and F16 Atlassian steps fixed in 958d731; other questions still open

3. 2026-10-23T18:18:33Z 6de586eee6

   Maintainer confirmed all open ❓ product-behavior claims via the PR author (feature owner/SME); conceded.