Repository navigation
loop-lane: decide whether a capability tier binds haiku now that it resolves to Haiku 5.5 #6856
Description
Problem
The loop-lane convention (docs/conventions/loop-lane/README.md, Alias binding) says haiku is admissible in no lane because the model it resolves to has a smaller context window and an older knowledge cutoff than the lanes need. On the Anthropic API the haiku alias now resolves to Claude Haiku 5.5, which has the same context window and knowledge cutoff as the other current models; on Claude Platform on AWS, Amazon Bedrock, Google Cloud's Agent Platform and Microsoft Foundry it still resolves to Haiku 4.5.
#4348 corrects the stated reason but keeps the exclusion. Whether a tier (or a new one) should bind haiku where it resolves to Haiku 5.5 is a policy decision that needs a separate call.
Evidence
- https://code.claude.com/docs/en/model-config#model-aliases (alias resolution per provider), read 2026-10-10
- https://platform.claude.com/docs/en/about-claude/models/overview#latest-models-comparison (context window and cutoff), read 2026-10-10
- https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/prompting-claude-haiku-5-5#prevent-early-stopping-in-long-agent-prompts (early stopping at low effort in long agent prompts), read 2026-10-10
Done when
A decision is recorded in the loop-lane convention and its CHANGELOG: either a tier binds haiku (with the provider caveat), or the exclusion stays with a reason that holds on every provider.
Refs: #4348
Activity
github-actions commentedon Oct 10, 2026
Thanks for the report. Automated triage handed this issue to a maintainer.
Automated triage. A maintainer reviews it.
kyle-sexton commentedon Oct 13, 2026
Decision recorded. The owner approved applying independently verified recommendations on 2026-10-12.
Asked for a recorded decision on whether a loop-lane tier binds haiku now that the alias resolves to Haiku 5.5 on the Anthropic API. Main now records that haiku stays admissible nowhere, on four new grounds with a recheck trigger tied to #6901.
Verification notes:
Verified by an independent fresh-context check (confirmed, risk low): origin/main docs/conventions/loop-lane/README.md:580-602 (haiku admissible nowhere, four grounds incl. provider alias, as of 2026-10-10, recheck on #6901); origin/main docs/conventions/loop-lane/CHANGELOG.md:62-71 ([10.3.0] entry); PR #7100 MERGED 2026-10-11; #6856 Done-when satisfied (exclusion kept with a reason that holds on every provider)
Closing: Shipped: loop-lane 10.3.0 records the decision (haiku stays excluded on four provider-independent grounds) in the convention and its CHANGELOG, which is this issue's Done-when.