Skip to Content

← All archived runs

Run: fix-ai-provider-claims

run.md

Run: fix-ai-provider-claims

  • branch: claude/fix-ai-provider-claims
  • pr: #821

02_define/output/spec.md

Spec: Correct the docs' AI provider and model claims

  • slug: fix-ai-provider-claims
  • personas: admin
  • touches: apps/docs/app/technical/packages/services/page.mdx, apps/docs/app/technical/architecture/technology-stack/page.mdx, apps/docs/app/technical/architecture/system-diagram/page.mdx, apps/docs/app/business/service-journey/requirements/page.mdx, apps/docs/app/business/initiatives/build-the-bridge/page.mdx
  • complexity: trivial

Problem

The service-journey requirements page claimed the BRD agent runs on "Claude Haiku via the OpenRouter API". It doesn't — every agent routes through Vercel's AI Gateway (AI SDK v6), with anthropic/claude-haiku-4.5 as the default agent model and anthropic/claude-sonnet-5 for deep extraction (packages/services/src/ai/core/agent.ts). Two docs pages disagreed with each other and one was flatly wrong, which undermines the docs' credibility as the project's source of truth.

Proposed change

State the full provider/model truth once, on the services package page (the page documenting packages/services/src/ai, where the model constants live): a models table listing DEFAULT_AGENT_MODEL (anthropic/claude-haiku-4.5) and DEEP_EXTRACTION_MODEL (anthropic/claude-sonnet-5), both routed through Vercel's AI Gateway. Every other page that carried a provider or model claim — the requirements page (OpenRouter claim + mermaid label), the build-the-bridge initiative page, the technology-stack page (table row + AI note), and the system diagram — now states only the gateway/provider and links to that single models table, so a future model bump has one edit point.

Acceptance criteria

  • No mention of OpenRouter remains in apps/docs.
  • The requirements page, build-the-bridge initiative page, and technical pages agree, with the model detail stated in exactly one place (the services package page's models table).
  • The stated models match packages/services/src/ai/core/agent.ts at merge time (anthropic/claude-haiku-4.5 default agent model, anthropic/claude-sonnet-5 deep extraction).

Out of scope

  • Changing the actual models or gateway config.
  • The AI billing runbook (ai-platform-enablement/ai-gateway-billing-unlock writes that).

Open questions

  • none

03_build/output/notes.md

Build notes: fix-ai-provider-claims

  • commits: docs: correct AI provider/model claims — AI Gateway truth stated once, referenced elsewhere

What changed

  • apps/docs/app/technical/packages/services/page.mdx: the closing line of the AI section became a ### Models subsection — the docs' single statement of the models. It names Vercel's AI Gateway (AI SDK v6) and tables the two constants from packages/services/src/ai/core/agent.ts: DEFAULT_AGENT_MODEL = anthropic/claude-haiku-4.5, DEEP_EXTRACTION_MODEL = anthropic/claude-sonnet-5. The #models anchor is what every other page links to.
  • apps/docs/app/business/service-journey/requirements/page.mdx: removed the false "Claude Haiku via the OpenRouter API" claim — now says the agent runs through Vercel's AI Gateway and links to the models table. The mermaid participant label dropped its stale "(Claude Haiku)" suffix.
  • apps/docs/app/business/initiatives/build-the-bridge/page.mdx: the BRD Agent bullet's "(Claude Haiku 4.5)" parenthetical now links to the models table instead of naming a model.
  • apps/docs/app/technical/architecture/technology-stack/page.mdx: the stack table's AI row and the AI note no longer name claude-haiku-4.5; the note links to the models table.
  • apps/docs/app/technical/architecture/system-diagram/page.mdx: the external-service node label "Anthropic / Claude via AI SDK" corrected to "Vercel AI Gateway / Anthropic Claude" (the gateway is the external endpoint); node id unchanged so all edges still resolve.

Acceptance criteria status

  • No mention of OpenRouter remains in apps/docs — case-insensitive grep over all of apps/docs returns zero matches.
  • The requirements page, build-the-bridge initiative page, and technical pages agree, with the model detail stated in exactly one place — grep for Haiku/Sonnet/claude- model strings over apps/docs/app hits only the services package page's models table; all other pages link to /technical/packages/services#models.
  • The stated models match packages/services/src/ai/core/agent.ts — the table mirrors DEFAULT_AGENT_MODEL = "anthropic/claude-haiku-4.5" and DEEP_EXTRACTION_MODEL = "anthropic/claude-sonnet-5" verbatim.

Notes for Verify

  • Docs-only diff (five page.mdx files, prose + one mermaid label) — no code, no tests apply.
  • Check the /technical/packages/services#models anchor resolves in the docs preview: Nextra derives it from the new ### Models heading.
  • apps/docs/app/technical/demo-environment/page.mdx was deliberately not touched — it carries no model claim (its "streaming-LLM" line names no provider/model), and another PR is editing that page.
  • The mermaid edits (participant label, node label) should render unchanged structurally — only label text changed; the system-diagram node id Anthropic is intentionally kept so edge references still resolve.