spec: INTENT-4 — absent-key = empty list, context-only session scoping, cold-start re-emission#113
Draft
JarbasAl wants to merge 1 commit into
Draft
spec: INTENT-4 — absent-key = empty list, context-only session scoping, cold-start re-emission#113JarbasAl wants to merge 1 commit into
JarbasAl wants to merge 1 commit into
Conversation
…context-only session scoping, cold-start recovery - Absent list-valued keys equal empty lists; all-four-keys shape requirement dropped (§5.2, §6.1). - Unknown payload fields ignored and preserved, never malformed (§5.3, §6.3) — the carrier for companion-spec fields. - Manifest is observability-only for registration processing; read-only consultation by other specs permitted (§2). - Deregistration session scoping reads exclusively from context.session.session_id; payload session_id removed (§8.4, §11). - Enable/disable of unregistered intents is a no-op; reload-state survival out of scope (§8.5). - Cold-start recovery: skills SHOULD re-emit registrations on the deployment readiness announcement; idempotent per §8.1 (§10). - describe responses keyed on method, ordering RECOMMENDED (§10.2). - Orchestrator passivity qualified by the §3.2 reserved-name exclusion; citations corrected; timeless out-of-scope wording. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Internal-purity refinement of OVOS-INTENT-4.
Changes
requires_context/excludes_context) ride on registration payloads.session_idfor deregistration — includingovos.skill.deregister— is read exclusively fromcontext.session.session_id, never fromMessage.data; the payload-levelsession_idfield is removed. One rule for every message in the spec.enabledfield is authoritative).method; consumers MUST key on it, withkeyword-then-templateordering RECOMMENDED rather than a MUST enabling positional access.ovos.intent.register.template,.deregister,.enable,.disable,ovos.intent.list) — none are dispatch topics, so none take the reserved colon shape (MSG-1 §2.1.1).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