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

[JarbasAl]

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

[coderabbitai]

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: 6092e2da-6572-411b-8b17-18770ab83b12

📥 Commits

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

📒 Files selected for processing (2)

• CHANGELOG.md
• common-query.md

✨ 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

• X
• Mastodon
• Reddit
• LinkedIn

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