Skip to content

spec: INTENT-2 — implementation-neutral language-fallback wording#120

Open
JarbasAl wants to merge 1 commit into
devfrom
spec/intent-2
Open

spec: INTENT-2 — implementation-neutral language-fallback wording#120
JarbasAl wants to merge 1 commit into
devfrom
spec/intent-2

Conversation

@JarbasAl

@JarbasAl JarbasAl commented Jul 4, 2026

Copy link
Copy Markdown
Member

Internal-purity refinement of OVOS-INTENT-2.

Changes

  • §2.2 language fallback: the suggestion previously named a concrete library (langcodes), its tag_distance() function, and a numeric threshold — a code-referencing justification in a normative document. It now reads: a loader MAY fall back to the nearest available language, as measured by any language-tag distance metric that treats close regional variants as usable matches. The normative posture is unchanged (SHOULD prefer exact match; any fallback is an implementation choice, because cross-region substitution can produce wording a user would not expect).

CHANGELOG entry appended under the spec's current class. Version field unchanged: per VERSIONING.md it is a V1/V2 compatibility class, and this refinement does not change class.

🤖 Generated with Claude Code

…allback

The §2.2 language-fallback suggestion no longer names a specific
library or its numeric distance threshold; a loader MAY fall back to
the nearest available language as measured by any language-tag
distance metric that treats close regional variants as usable
matches. The fallback remains an implementation choice, not a
requirement.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 4, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@JarbasAl, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 24b3338f-c0e0-41a4-8ae7-79337c502f39

📥 Commits

Reviewing files that changed from the base of the PR and between 9003dcd and d59a920.

📒 Files selected for processing (2)
  • CHANGELOG.md
  • intent-2.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch spec/intent-2

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@JarbasAl
JarbasAl marked this pull request as ready for review July 16, 2026 07:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant