Review evidence — pulumi/docs #21603

Verification trail

#1 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:28

The AWS API Gateway component applies infrastructure as code techniques to declarative API definitions, including built-in Lambda integration.

evidence: The pulumi-aws-apigateway README states: "The Pulumi AWS API Gateway library provides a Pulumi component that easily creates AWS API Gateway REST APIs," links to a serverless-application (Lambda) template as its "Get Started" entry…; source: gh api repos/pulumi/pulumi-aws-apigateway/contents/README.md

source: gh api repos/pulumi/pulumi-aws-apigateway/contents/README.md

pass1

#2 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:50

An API Gateway stage's default name is `stage` if you leave the stage name unspecified.

evidence: Source code confirms: aws-apigateway/apigateway/api.ts contains `const stageName = args.stageName || "stage";`, meaning if stageName is left unspecified it defaults to the literal string "stage".; source: gh search code stageName --repo pulumi/pulumi-aws-apigateway (aws-apigateway/apigateway/api.ts)

source: gh search code stageName --repo pulumi/pulumi-aws-apigateway (aws-apigateway/apigateway/api.ts)

pass1

#3 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:56

The AWS API Gateway component supports multiple ways to define APIs: handling requests with Lambda, serving static files from S3, integrating with other AWS…

evidence: The pulumi-aws-apigateway README describes the component as exposing "the Crosswalk for AWS functionality documented in the Pulumi AWS API Gateway guide" (i.e., this very doc page family is the canonical reference). The doc page itself…; source: gh api repos/pulumi/pulumi-aws-apigateway/contents/README.md; content/docs/iac/guides/clouds/aws/api-gateway.md

source: gh api repos/pulumi/pulumi-aws-apigateway/contents/README.md; content/docs/iac/guides/clouds/aws/api-gateway.md

pass1

#4 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:58

The AWS API Gateway component supports defining an entire endpoint with OpenAPI.

evidence: The pulumi-aws-apigateway RestAPI resource schema exposes a `swaggerString` property, documented as: "Either `swaggerString` or `routes` must be specified" — used to supply an entire OpenAPI/Swagger specification to initialize the API…; source: gh search code swaggerString repo:pulumi/pulumi-aws-apigateway (schema.yaml, restAPI.ts, RestAPIArgs.java)

source: gh search code swaggerString repo:pulumi/pulumi-aws-apigateway (schema.yaml, restAPI.ts, RestAPIArgs.java)

pass1

#7 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:154

Amazon API Gateway integrations connect an API Gateway endpoint to backend services that execute code in response to requests.

framing: The source details multiple integration types (AWS, AWS_PROXY, HTTP, HTTP_PROXY, MOCK); the claim is a general summary statement entailed by these specifics.; evidence: The page describes integration types (AWS, AWS_PROXY/Lambda, HTTP, HTTP_PROXY, MOCK) that connect API Gateway methods to backend services such as Lambda functions and HTTP endpoints that execute code/return results in response to…; source: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-integration-types.html

source: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-integration-types.html

pass2

#8 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:160

The `aws` integration route type allows an API to expose an AWS service action, such as invoking AWS Lambda functions, Amazon DynamoDB, Amazon Simple…

evidence: AWS docs state: "AWS: This type of integration lets an API expose AWS service actions. In AWS integration, you must configure both the integration request and integration response and set up necessary data mappings from the method…; source: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-integration-types.html

source: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-integration-types.html

pass3

#9 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:160

The `aws` integration route type requires you to configure the data mappings between the HTTP and underlying AWS service requests and responses.

evidence: AWS docs confirm the AWS (non-proxy) integration type requires configuring data mappings: for the Lambda custom/AWS service integration, "you must set up necessary data mappings from the method request to the integration request, and…; source: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-integration-types.html

source: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-integration-types.html

pass3

#10 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:163

The `aws_proxy` integration route type integrates a route with a Lambda function invocation (Lambda proxy integration), passing the HTTP request, including…

evidence: AWS docs confirm: "In Lambda proxy integration, the input to the Lambda function can be expressed as any combination of request headers, path variables, query string parameters, body, and API configuration data" and "API Gateway…; source: https://docs.aws.amazon.com/apigateway/latest/developerguide/getting-started-with-lambda-integration.html

source: https://docs.aws.amazon.com/apigateway/latest/developerguide/getting-started-with-lambda-integration.html

pass3

#11 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:177

AWS API Gateway supports several mechanisms for controlling and managing access to APIs, including authentication and authorization with resource policies…

evidence: AWS documentation confirms API Gateway supports resource policies, IAM roles/policies, Cognito user pools, and Lambda authorizers as access control mechanisms: "Amazon API Gateway lets you use various mechanisms to control and manage…; source: https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-control-access-to-api.html

source: https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-control-access-to-api.html

pass3

#12 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:177

AWS API Gateway access can also be configured via cross-origin resource sharing (CORS), client-side SSL certificates, AWS WAF, and limiting access to…

evidence: AWS's own API Gateway docs state: "Cross-origin resource sharing (CORS) lets you control how your REST API responds to cross-domain resource requests... Client-side SSL certificates can be used to verify that HTTP requests to your…; source: https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-control-access-to-api.html

source: https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-control-access-to-api.html

pass3

#13 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:179

The API Gateway component's `RestAPI` resource supports three methods of controlling access to APIs.

evidence: The pulumi-aws-apigateway source (restAPI.ts) defines `export type Authorizer = CognitoAuthorizer | LambdaAuthorizer;` (Cognito and Lambda authorizer types) plus `apiKeyRequired?: boolean` on `RestAPIRoute` (supporting API…; source: gh api repos/pulumi/pulumi-aws-apigateway/git/blobs/f3e2abbd8d0190ca6f060710b8604b287bc63ac4 (aws-apigateway/restAPI.ts)

source: gh api repos/pulumi/pulumi-aws-apigateway/git/blobs/f3e2abbd8d0190ca6f060710b8604b287bc63ac4 (aws-apigateway/restAPI.ts)

pass1

#14 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:185

Usage plans let you provide API keys to customers, and then track and limit usage of your APIs.

evidence: AWS docs state: "you can use API Gateway usage plans to make them available as product offerings for your customers. You can configure usage plans and API keys to allow customers to access selected APIs, and begin throttling requests to…; source: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-usage-plans.html

source: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-usage-plans.html

pass3

#15 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:187

For access-control capabilities not directly supported by the API Gateway component's `RestAPI` resource, those capabilities remain accessible through the…

evidence: The doc text itself states: "Details on each are below. For those not directly supported, these capabilities remain accessible through the [Pulumi AWS package](/registry/packages/aws/)...". This reflects the standard Pulumi architecture…; source: repo:pulumi/pulumi-aws-apigateway (component metadata) and content/docs/iac/guides/clouds/aws/api-gateway.md L187

source: repo:pulumi/pulumi-aws-apigateway (component metadata) and content/docs/iac/guides/clouds/aws/api-gateway.md L187

pass1

#16 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:191

Cognito Authorizers allow you to use Amazon Cognito User Pools as an authorizer for API Gateway.

evidence: AWS docs state: "As an alternative to using IAM roles and policies or Lambda authorizers (formerly known as custom authorizers), you can use an Amazon Cognito user pool to control who can access your API in Amazon API Gateway,"…; source: https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-integrate-with-cognito.html

source: https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-integrate-with-cognito.html

pass3

#17 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:191

With a Cognito user pool, users can sign into a web or mobile app through Amazon Cognito directly, social identity providers like Google and Facebook, or…

framing: Claim faithfully summarizes Cognito's three sign-in paths (direct via Cognito, social IdPs, SAML/OIDC IdPs) as documented by AWS.; evidence: AWS Cognito documentation confirms this: "Your app users can either sign in directly through a user pool, or they can federate through a third-party identity provider (IdP)" and "The user pool manages the overhead of handling the tokens…; source: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-identity-federation.html

source: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-identity-federation.html

pass3

#18 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:197

When deployed, the Cognito authorizer configuration in the example requires that a user authenticate, get an identity or access token, and call the API with…

evidence: The doc text states "When deployed, this configuration will require that a user authenticate, get an identity or access token, and call your API with that token" directly following an example using a Cognito User Pool authorizer, which…; source: content/docs/iac/guides/clouds/aws/api-gateway.md (lines 189-197), corroborated by linked AWS doc docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-integrate-with-cognito.html

source: content/docs/iac/guides/clouds/aws/api-gateway.md (lines 189-197), corroborated by linked AWS doc docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-integrate-with-cognito.html

pass1

#19 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:201

Lambda Authorizers are AWS Lambda Functions that control access to an API by using information in the request itself, including headers, paths, query…

framing: Source describes the two authorizer types (REQUEST using headers/query params/paths, TOKEN using bearer tokens) separately; claim synthesizes both into one…; evidence: The AWS doc states: "A REQUEST authorizer receives the caller's identity in a combination of headers, query string parameters, stageVariables, and $context variables" and "A TOKEN authorizer receives the caller's identity in a bearer…; source: https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-use-lambda-authorizer.html

source: https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-use-lambda-authorizer.html

pass2

#20 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:203

API Gateway supports `request` or `token` type Lambda authorizers.

evidence: AWS documentation confirms Lambda authorizers come in REQUEST and TOKEN types: "For a Lambda authorizer (formerly known as a custom authorizer) of the TOKEN type..." and "For a Lambda authorizer of the REQUEST type, API Gateway passes…; source: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-lambda-authorizer-input.html

source: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-lambda-authorizer-input.html

pass3

#21 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:203

You can define a Lambda Authorizer for an event-handler route or a static route.

evidence: The pulumi-aws-apigateway repo README states verbatim: "Lambda Authorizers... are AWS Lambda functions that provide control access to an API. You can define a Lambda Authorizer for an Event Handler Route or a Static Route." This matches…; source: gh search code "authorizer" --repo pulumi/pulumi-aws-apigateway -> aws-apigateway/apigateway/README.md

source: gh search code "authorizer" --repo pulumi/pulumi-aws-apigateway -> aws-apigateway/apigateway/README.md

pass1

#22 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:234

API Gateway can perform basic validations against the parameters of a request, the request payload, or both, and when a validation fails, a 400 error is…

evidence: AWS docs state: "You can configure API Gateway to perform basic validation of an API request before proceeding with the integration request. When the validation fails, API Gateway immediately fails the request, returns a 400 error…; source: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-method-request-validation.html

source: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-method-request-validation.html

pass3

#23 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:234

When an API Gateway request validation fails, a 400 error is returned immediately, without invoking the backend integration.

evidence: AWS's official API Gateway documentation states: "When the validation fails, API Gateway immediately fails the request, returns a 400 error response to the caller, and publishes the validation results in CloudWatch Logs. This reduces…; source: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-method-request-validation.html

source: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-method-request-validation.html

pass3

#24 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:263

To validate that a particular parameter is present in each request, you use the `requiredParameters` route property, which is an array defining each required…

evidence: The pulumi-aws-apigateway schema.yaml defines `requiredParameters` on the `Route` type as `type: array` with items `$ref: '#/types/aws-apigateway:index:RequiredParameter'`, described as: "Required Parameters to validate. If the request…; source: gh api repos/pulumi/pulumi-aws-apigateway/contents/schema.yaml (decoded content, `aws-apigateway:index:Route.requiredParameters` and `aws-apigateway:index:RequiredParameter` type)

source: gh api repos/pulumi/pulumi-aws-apigateway/contents/schema.yaml (decoded content, `aws-apigateway:index:Route.requiredParameters` and `aws-apigateway:index:RequiredParameter` type)

pass1

#25 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:265

The example under the 'Assigning validators to APIs and methods' section declares a `/search` route with `requiredParameters` set to `name: "q"` and `in…

evidence: The referenced example program (static/programs/awsx-apigateway-validation-types-typescript/index.ts) defines a `/search` route with `requestValidator: apigateway.RequestValidator.ALL` and `requiredParameters: [{ name: "q", in: "query"…; source: repo:static/programs/awsx-apigateway-validation-types-typescript/index.ts and repo:content/docs/iac/guides/clouds/aws/api-gateway.md

source: repo:static/programs/awsx-apigateway-validation-types-typescript/index.ts and repo:content/docs/iac/guides/clouds/aws/api-gateway.md

pass1

#26 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:272

Request body validation is not yet supported by the AWS API Gateway component, per the open GitHub issue pulumi/pulumi-aws-apigateway#36.

evidence: Issue pulumi/pulumi-aws-apigateway#36 "[API Gateway] Support Request Body Validation" is state: OPEN, confirming request body validation is not yet supported by the AWS API Gateway component.; source: gh issue view 36 -R pulumi/pulumi-aws-apigateway

source: gh issue view 36 -R pulumi/pulumi-aws-apigateway

pass1

#27 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:277

Usage plans and API keys allow customers to use an API at agreed-upon request rates and quotas.

evidence: AWS docs state: "You can configure usage plans and API keys to allow customers to access selected APIs, and begin throttling requests to those APIs based on defined limits and quotas," and elsewhere describe usage plans as allowing…; source: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-usage-plans.html

source: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-usage-plans.html

pass3

#28 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:311

API Gateway automatically provisions and assigns a domain name, a URL that contains the stage, and SSL support.

evidence: The live Pulumi docs page for this exact guide states: "API Gateway will auto-generate a domain name with built-in HTTPS support. The stage name will also be part of this URL." This matches the claim that API Gateway automatically…; source: https://www.pulumi.com/docs/iac/guides/clouds/aws/api-gateway/

source: https://www.pulumi.com/docs/iac/guides/clouds/aws/api-gateway/

pass3

#31 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:321

The ACM certificate in the example is created in the `us-east-1` region because this is a CloudFront requirement, and it is validated with a…

evidence: The referenced example program (static/programs/awsx-apigateway-custom-domain-typescript/index.ts) creates `certificate` with `new aws.acm.Certificate(..., { provider: usEast1 })` where `usEast1` is `new aws.Provider("us-east-1", {…; source: repo:static/programs/awsx-apigateway-custom-domain-typescript/index.ts

source: repo:static/programs/awsx-apigateway-custom-domain-typescript/index.ts

pass1

#32 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:321

In the example, the ACM certificate is created in the `us-east-1` region because that is a CloudFront requirement.

evidence: AWS's own CloudFront documentation confirms: "To use a certificate in AWS Certificate Manager (ACM) to require HTTPS between viewers and CloudFront, make sure you request (or import) the certificate in the US East (N. Virginia) Region…; source: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/cnames-and-https-requirements.html

source: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/cnames-and-https-requirements.html

pass3

#33 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:321

ACM also supports importing certificates issued by third-party certificate authorities.

evidence: AWS's ACM docs state: "You might do this because you already have a certificate from a third-party certificate authority (CA), or because you have application-specific requirements that are not met by ACM issued certificates."; source: https://docs.aws.amazon.com/acm/latest/userguide/import-certificate.html

source: https://docs.aws.amazon.com/acm/latest/userguide/import-certificate.html

pass3

#34 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:330

Amazon API Gateway supports the OpenAPI specification, formerly known as "Swagger", for defining APIs.

evidence: Swagger.io confirms: "The OpenAPI specification, formerly known as the Swagger Specification is the world's standard for describing RESTful APIs." AWS documentation and announcements confirm API Gateway supports importing/exporting APIs…; source: https://swagger.io/open-api/ and https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-import-api.html

source: https://swagger.io/open-api/ and https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-import-api.html

pass3

#35 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:337

To use an OpenAPI specification to initialize an API Gateway instance via the component, you supply an entire OpenAPI specification as a JSON string in the…

evidence: The pulumi-aws-apigateway schema defines `swaggerString` as a string-typed input on RestAPI: "Either `swaggerString` or `routes` must be specified" (schema.yaml, and mirrored in generated SDKs for TS/Python/Go/.NET/Java), confirming it…; source: gh search code --owner pulumi swaggerString repo:pulumi/pulumi-aws-apigateway (schema.yaml, restAPI.ts, rest_api.py)

source: gh search code --owner pulumi swaggerString repo:pulumi/pulumi-aws-apigateway (schema.yaml, restAPI.ts, rest_api.py)

pass1

#36 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:357

You can define a single API route, a "raw data" route, with OpenAPI using the `data` property.

evidence: The pulumi-aws-apigateway SDK's RouteArgs interface (sdk/nodejs/types/input.ts) defines a `data?: any;` field documented as "A raw Swagger object to include verbatim in the integration for this path" — confirming a route can be defined…; source: gh api repos/pulumi/pulumi-aws-apigateway/contents/sdk/nodejs/types/input.ts (RouteArgs.data field)

source: gh api repos/pulumi/pulumi-aws-apigateway/contents/sdk/nodejs/types/input.ts (RouteArgs.data field)

pass1

#37 ✅ Verified

content/docs/iac/guides/clouds/aws/api-gateway.md:361

The `data` property is the `x-amazon-apigateway-integration` object.

evidence: The pulumi-aws-apigateway README states: "A Raw Data Route is a fallback route for when raw swagger control is desired. The `data` field should be an object that will be then included in the final swagger specification. For more…; source: pulumi/pulumi-aws-apigateway:aws-apigateway/apigateway/README.md

source: pulumi/pulumi-aws-apigateway:aws-apigateway/apigateway/README.md

pass1

#5 ➖ Not a claim

content/docs/iac/guides/clouds/aws/api-gateway.md:154

The Lambda and S3 route examples described earlier in the AWS API Gateway component documentation use API Gateway integrations internally, even though this…

evidence: The claim is a direct paraphrase of the doc's own existing text in the same file: "The previous Lambda and S3 examples use API Gateway integrations internally, even if it's not evident in the streamlined interface the component exposes."…; source: repo:content/docs/iac/guides/clouds/aws/api-gateway.md L154

source: repo:content/docs/iac/guides/clouds/aws/api-gateway.md L154

pass1

#29 ➖ Not a claim

content/docs/iac/guides/clouds/aws/api-gateway.md:311

API Gateway automatically provisions and assigns a domain name, a URL containing the stage, and SSL support, and generates URLs such as…

evidence: The cited "URL" is not a real reachable endpoint but an illustrative example API Gateway hostname (a placeholder-style identifier `no90ji5v23`) used to demonstrate the auto-generated URL format—consistent with AWS's own documentation…; source: https://no90ji5v23.execute-api.us-west-2.amazonaws.com/stage/

source: https://no90ji5v23.execute-api.us-west-2.amazonaws.com/stage/

pass2

#30 🤷 Unverifiable

content/docs/iac/guides/clouds/aws/api-gateway.md:318

You can configure a custom domain name for an API Gateway instance and customize the base path of the URL to be something other than `/stage`.

evidence: The cited URL is AWS CloudFront's marketing homepage, which is about CloudFront's CDN product generally and does not mention API Gateway custom domain names, base path mapping, or the `/stage` URL prefix at all. This source cannot…; source: https://aws.amazon.com/cloudfront/; intuition: Cited source (CloudFront marketing page) appears mismatched to the claim topic (API Gateway custom domain/base path)…

source: https://aws.amazon.com/cloudfront/

pass2

#6 🌀 Framing drift

content/docs/iac/guides/clouds/aws/api-gateway.md:154

API Gateway integrations give full control over how HTTP requests are handled and responses are served by an API Gateway route.

framing: source distinguishes proxy integrations (streamlined, no manual request/response config) from custom integrations (full control, "must configure both the…; evidence: The source describes multiple integration types (AWS, AWS_PROXY, HTTP, HTTP_PROXY, MOCK) with varying levels of control — proxy integrations are explicitly "streamlined" and do NOT require configuring integration request/response, while…; source: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-integration-types.html

source: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-integration-types.html

pass2

Findings

ID	Bucket	File:lines	Status	Disposition
F2	⚠️ Reviewer check	content/docs/iac/guides/clouds/aws/api-gateway.md:154	open	—

Editorial stances

The extractor found no positioning or comparison language in this PR's added lines.

Investigation log

cross-sibling-reads: 0 of 9 siblings
external-claim-verification: 33 of 37 claims verified (1 unverifiable, 0 contradicted, 1 framing-drift) · 4 specialists (numerical, cross-reference, capability, framing); 0 cross-specialist corroborations · routed: 0 inline, 16 Pass 1, 5 Pass 2 (verified 2, contradicted 1, unverifiable 2), 16 Pass 3 (verified 16, contradicted 0, unverifiable 0).
cited-claim-spot-checks: 5 of 5 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: not run (no fenced code blocks in content files)
editorial-balance-pass: not run (not under content/blog/)

Triaged

{
  "file": "content/docs/iac/guides/clouds/aws/api-gateway.md",
  "from_bucket": "author-answer",
  "id": "F1",
  "kind": "mis-sourced",
  "note": "the check followed the CloudFront product page linked later in the same sentence, which says nothing about API Gateway custom domains; the claim is standard API Gateway behavior and the page already cites AWS's \"Set up Custom Domain Name for an API in API Gateway\" a few lines below. The sentence is also unchanged by this PR \u2014 only the CDN product name was reworded."
}

History

2026-09-14T19:34:45Z 0244eb6
initial review (pending publication)