Skip to content

spec: common-query.md — dotted .request/.response family, colon reserved for dispatch, opt-in fast-win#112

Draft
JarbasAl wants to merge 1 commit into
devfrom
spec/common-query
Draft

spec: common-query.md — dotted .request/.response family, colon reserved for dispatch, opt-in fast-win#112
JarbasAl wants to merge 1 commit into
devfrom
spec/common-query

Conversation

@JarbasAl

@JarbasAl JarbasAl commented Jul 4, 2026

Copy link
Copy Markdown
Member

Refines OVOS-COMMON-QUERY-1 for internal purity and self-consistency (per-file split of the consistency audit).

Changes

  • Topic-shape purity: the full-answer request is renamed <skill_id>:common_query<skill_id>.common_query.request. It is a plugin-emitted request, not an orchestrator dispatch, so it must not wear the colon shape MSG-1 §2.1.1 reserves for PIPELINE-1 §7 dispatch. The message family is now uniformly dotted — ovos.common_query.ping / .pong (broadcast poll + reply), <skill_id>.common_query.request / .response (addressed request + reply) — and the single remaining colon topic is the genuine dispatch <pipeline_id>:common_query.
  • Fast-win is deployment-opt-in, off by default (§8 step 3): conf is self-reported and skills share no calibrated confidence scale (Appendix B), so first-past-threshold selection turns answer selection into a nondeterministic latency race — the fastest confident skill wins, not the best. Absent opt-in the plugin SHOULD wait for all claimants within the latency ceiling.
  • Numbers stay RECOMMENDED: confidence thresholds, poll/collection windows, and the fast-win threshold are Appendix A tunables; MUSTs remain only on correctness invariants (bounded windows, (session_id, utterance) cache keying and correlation, match-timeout ≥ collection ceiling, no session mutation, skills never speak).
  • §5 early-start phrased normatively ("responses MAY already be collected", not "often are"); cross-protocol note that the poll boolean's field name (can_answer) is protocol-local; OVOS-SESSION-1 cited by canonical title.

Principle

Colon <x>:<y> is reserved for the orchestrator dispatch shape; requests, polls, and events are dotted <x>.<y>.<verb>. MUST/MUST NOT for interop invariants only; tuning values are RECOMMENDED defaults. Selection must be deterministic given the same responses — never a race.

Version stays 2: VERSIONING.md defines the field as the V0-compatibility class, which these edits do not change.

🤖 Generated with Claude Code

…olon topic, opt-in fast-win

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: 1edf00cd-30f4-47e7-bcf4-acd5e4f72dde

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/common-query

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