Track Amazon Nova 2 Bedrock models

[a5c-ai]

Model update to track

Provider: Amazon Bedrock / Amazon Nova
API family: AWS Bedrock Converse/InvokeModel APIs.

Exact model IDs/versions to verify:

• Amazon Nova 2 Pro / Nova 2 Lite / Nova 2 Omni where currently available.
• Existing previous process artifacts mention Amazon Nova 2 Pro, but no open model-version-update issue matched Amazon Nova 2.

Sources:

• https://docs.aws.amazon.com/bedrock/latest/userguide/models-supported.html
• https://docs.aws.amazon.com/nova/latest/userguide/what-is-nova.html
• https://aws.amazon.com/bedrock/pricing/

Context/capability notes:

• Record exact Bedrock model IDs, regions, input modalities, output modalities, context windows, video/image support, and tool-use/converse support.

Pricing:

• Use AWS Bedrock pricing and region-specific SKU notes for Nova 2 models.

Cross-provider availability:

• Bedrock is the primary provider. Do not add Azure/Vertex availability unless separately documented.

Graph changes needed:

• Add Amazon/Nova model families/versions and link them to provider:bedrock provider-version records.
• Add evidence claims for supported model list, Nova docs, and pricing pages.

Transport-adapter proxy support:

• Confirm transport-adapter proxy supports Bedrock Converse/InvokeModel and Nova-specific multimodal request schema before marking supported.

Exact IDs/details found in AWS docs/search snapshots on 2026-07-16:

• us.amazon.nova-2-lite-v1:0 appears in AWS Nova 2 console guidance as the US CRIS endpoint example.
• amazon.nova-2-sonic-v1:0 appears in the Amazon Nova 2 developer guide PDF sample metadata.
• AWS docs list Nova 2 Lite and Nova 2 Sonic as new Nova 2 models; AWS Nova 2 overview states up to 1M-token context and advanced reasoning capabilities for Nova 2 models.
• AWS Nova documentation says Nova 2.0 includes Nova 2.0 Omni, Nova 2.0 Lite and Pro, Nova Sonic 2.0, built-in tools including web grounding and code interpreter, structured output support, and improved document/video understanding.

If adding Nova 2 Pro/Omni records, use the exact Bedrock model IDs from AWS Supported Foundation Models or Nova 2 model cards; do not rely on third-party IDs except as secondary evidence.

[a5c-ai]

This appears to have been fixed: Already covered in existing Atlas graph work. origin/staging contains commit 0c9027d / PR #371 for Amazon Nova 2 Lite and Sonic, commit def1a44 / PR #558 for Amazon Nova 2 Pro Preview, and commit 533e2c4 adding Amazon Nova 2 Omni in the batch graph update. Current graph records include packages/atlas/graph/compute/model-families/amazon-nova-2.yaml, packages/atlas/graph/compute/models/amazon-nova-2-lite.yaml, amazon-nova-2-sonic.yaml, amazon-nova-2-omni.yaml, and amazon-nova-2-pro-preview-issue-535.yaml, all linked to provider:aws-bedrock with Bedrock Converse/Invoke or bidirectional streaming transport metadata where applicable. Related closed issues: #362, #535/#1093, and #904. Closing.

[a5c-ai]

Triage Summary

• One-line: Update Atlas Amazon Nova 2 Bedrock coverage by verifying current AWS sources and patching only missing/stale graph evidence, especially Omni and any newly public Pro details.

Critical Evaluation

• The issue is valid, but it is not a wholly missing model-family issue.
• Existing work already covers Nova 2 Lite/Sonic, Nova 2 Pro Preview, and a basic Nova 2 Omni record.
• The remaining work is evidence/freshness cleanup: do not duplicate existing graph records.

Root Cause Analysis

Affected Atlas graph areas:

• packages/atlas/graph/compute/models/amazon-nova-2-lite.yaml
• packages/atlas/graph/compute/models/amazon-nova-2-sonic.yaml
• packages/atlas/graph/compute/models/amazon-nova-2-omni.yaml
• packages/atlas/graph/compute/models/amazon-nova-2-pro-preview-issue-535.yaml
• packages/atlas/graph/compute/model-families/amazon-nova-2.yaml
• packages/atlas/graph/compute/model-families/amazon-nova-2-issue-535.yaml
• packages/atlas/graph/compute/providers/bedrock.yaml and aws-bedrock-issue-535.yaml
• packages/atlas/graph/compute/model-transport-protocols/bedrock-converse.yaml, bedrock-invoke.yaml, and issue-scoped sidecars
• packages/atlas/graph/catalog-meta/evidence-sources/*amazon-nova-2*
• packages/atlas/graph/catalog-meta/claims/*amazon-nova-2*

Code evidence:

• Lite and Sonic have provider model IDs plus evidence/claim records from issue Track Amazon Nova 2 Lite and Nova 2 Sonic #362.
• Pro Preview is tracked from issue Track Amazon Nova 2 Pro model version #535, but providerModelIds is intentionally empty and pricing is unresolved because reviewed public AWS sources did not expose those values at the time.
• Omni exists in amazon-nova-2-omni.yaml, but it still has contextWindowTokens: 0 and notes saying exact Bedrock runtime model ID, context window, token limits, and pricing need confirmation.
• No catalog-meta evidence/claim records were found for amazon-nova-2-omni.

Affected Components

• Packages: @a5c-ai/atlas
• Effort: effort:medium

Recommended Approach

Do not re-add duplicate Nova 2 Lite/Sonic/Pro records. First verify current official AWS Bedrock/Nova docs and pricing, then patch only missing or stale Atlas data:

• Update amazon-nova-2-omni.yaml with exact official provider model IDs, context/token limits, pricing notes, regions, and lifecycle only where AWS docs support them.
• Add Omni evidence-source and model-version claim records under packages/atlas/graph/catalog-meta/.
• Re-check Nova 2 Pro: if official AWS docs now expose exact public Bedrock IDs/pricing, update the Pro Preview records and claims; otherwise preserve the explicit unresolved-public-docs limitation.
• Confirm provider/protocol links for Bedrock Converse, InvokeModel, and any multimodal/bidirectional streaming surfaces before marking support.
• Preserve issue-scoped provenance and avoid duplicate model-family:amazon-nova-2 or model:* IDs.

Verification:

• npm run verify:metadata
• npm run build --workspace=@a5c-ai/atlas
• npm run validate:edges if the edge changes touch provider/protocol relationships
• git diff --check

Reproduction

Run:

rg -n "amazon-nova-2-omni|Nova 2 Omni|nova-2-omni" packages/atlas/graph/compute packages/atlas/graph/catalog-meta
rg -n "providerModelIds|pricing|contextWindowTokens|evidence:amazon-nova-2" packages/atlas/graph/catalog-meta packages/atlas/graph/compute/models/amazon-nova-2-*

Compare Lite/Sonic/Pro evidence coverage with Omni. Omni currently has graph presence but incomplete evidence-backed details.

Related Issues/PRs

• Track Amazon Nova 2 Lite and Nova 2 Sonic #362 / PR Track Amazon Nova 2 Lite and Sonic #371: Nova 2 Lite and Sonic tracking, merged.
• Track Amazon Nova 2 Pro model version #535 / PR Track Amazon Nova 2 Pro preview in Atlas graph #558: Nova 2 Pro Preview tracking, merged with public-doc limitations.
• Track Amazon Nova 2 Omni model version #904: Nova 2 Omni basic record, closed, but still appears incomplete for evidence-backed details.
• Track Amazon Nova 2 Pro #1093: duplicate of Track Amazon Nova 2 Pro model version #535.

Priority

priority:medium - Atlas catalog freshness matters for downstream model/provider discovery, but this is not a runtime crash and partial coverage already exists.

Risk Analysis

• Risk Level: risk:medium
• Duplicate/conflicting graph records
  • Mitigation: preflight exact target paths and IDs with rg; patch existing YAML/sidecars instead of adding duplicate IDs.
• Unverified AWS model IDs/pricing
  • Mitigation: use official AWS Bedrock supported-model, Nova, and pricing pages as primary evidence; encode unresolved limitations explicitly instead of guessing.
• Incorrect transport support
  • Mitigation: compare existing Bedrock Converse, InvokeModel, and bidirectional-stream records; add support edges only where the transport shape is actually covered.

/plan ready for development

[a5c-ai]

Correction: the later triage handoff supersedes the earlier fixed-status note.

After checking the graph records more closely, this issue should remain open and ready for development because the existing Nova 2 coverage is incomplete for the rollup scope, especially Omni evidence/claim details and any newly public Pro ID/pricing data.