Skip to content

spec: INTENT-3 — dual-method registrations, method-keyed replacement, precise required-slot semantics#121

Draft
JarbasAl wants to merge 1 commit into
devfrom
spec/intent-3
Draft

spec: INTENT-3 — dual-method registrations, method-keyed replacement, precise required-slot semantics#121
JarbasAl wants to merge 1 commit into
devfrom
spec/intent-3

Conversation

@JarbasAl

@JarbasAl JarbasAl commented Jul 4, 2026

Copy link
Copy Markdown
Member

Internal-purity refinement of OVOS-INTENT-3, aligning the intent model with the OVOS-INTENT-4 wire contract.

Changes

  • Dual-method intents (§2): an intent is defined by one or both of the two methods. Each individual registration still uses exactly one method — the shapes are never mixed within one registration — and an intent MAY carry one registration per method, as two training-data representations of the same handler (INTENT-4 §3.2). This removes the contradiction where INTENT-3 said "exactly one method" while INTENT-4 keys registration and replacement by method.
  • Method-keyed replacement (§6.1): replacement is keyed on the (skill id, intent name, language, method) quadruple; registering one method leaves the other method's registration for the same triple untouched.
  • Required-slot failure (§5.3): stated precisely — when a required slot is absent from the match result, the engine MUST treat the intent as unmatched for that utterance; it MAY internally consider other templates of the same intent before concluding the intent is unmatched.
  • Wording hygiene: "slots map" normalized to "slot map" throughout; the slot-typing deferral restated as out of scope alongside the normalization it depends on (matching the INTENT-1 companion change); the "this one — the last —" dependency-order aside dropped.

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

🤖 Generated with Claude Code

…-keyed replacement, required-slot semantics

- An intent is defined by one or both methods; each individual
  registration uses exactly one, one registration per method
  (aligned with OVOS-INTENT-4 §3.2) (§2).
- Replacement keyed on (skill id, intent name, language, method);
  the other method's registration is untouched (§6.1).
- Required-slot failure: the engine MUST treat the intent as
  unmatched for that utterance; it MAY consider other templates of
  the same intent first (§5.3).
- Slot map wording normalized; typing deferral restated as a
  timeless out-of-scope statement.

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

coderabbitai Bot commented Jul 4, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c02831cc-afda-4967-b787-b89cbffd2539

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch spec/intent-3

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.

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