Skip to content

INTENT-3: required_slots and union slot sets for template intents#67

Merged
JarbasAl merged 1 commit into
devfrom
spec/intent3-required-slots
Jun 26, 2026
Merged

INTENT-3: required_slots and union slot sets for template intents#67
JarbasAl merged 1 commit into
devfrom
spec/intent3-required-slots

Conversation

@JarbasAl

Copy link
Copy Markdown
Member

Extracts the OVOS-INTENT-3 half of the union-slots / required_slots work into its own one-file PR (per 1 file, 1 PR).

Changes (ovos-intent-3.md)

  • §5.1 — a template intent's templates MAY declare different slot sets; the engine extracts only the slots of the best-matching template (OVOS-INTENT-1 §5.5).
  • §5.3 (new)required_slots: an optional list of slot names the engine MUST extract for a match to be valid. A required slot must be declared by at least one template, otherwise the definition is malformed. Former §5.3 (Example) → §5.4, §5.4 (.blacklist) → §5.5; references updated.
  • §7.1 — a handler MAY rely on required_slots being populated; all other slots remain optional and must be defended against.

Companion one-file PRs: INTENT-1 (union slots §5.5), INTENT-4 (required_slots payload + §6.2/§6.3), PIPELINE-1 (orchestrator backstop §6.2).

@coderabbitai

coderabbitai Bot commented Jun 22, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

More reviews will be available in 39 minutes. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 23ec8ec6-a20d-47a4-a83a-a48d2a22f7fb

📥 Commits

Reviewing files that changed from the base of the PR and between 54c6a0e and fb5c140.

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

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 force-pushed the spec/intent3-required-slots branch from 0c92982 to fb5c140 Compare June 23, 2026 05:16
@JarbasAl JarbasAl marked this pull request as ready for review June 26, 2026 20:54
@JarbasAl JarbasAl merged commit 08cdc00 into dev Jun 26, 2026
1 check passed
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