OpenVoiceOS / OpenVoiceOS/architecture
Spec proposal: OVOS-COMMON-QUERY-1 — Common Query Pipeline Plugin
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 3
- Forks
- 0
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 90
Description
Proposal for OVOS-COMMON-QUERY-1, the common query pipeline plugin specification.
Problem
Voice assistants need a standardised scatter-gather mechanism for open-domain question answering: broadcast a question to registered skills, collect answers within a bounded window, select the best, and dispatch the winner to speak it. The current implementation predates any specification.
Proposal
- Question gate — binary accept/reject pre-filter before broadcast
- Scatter-gather —
ovos.common_query.questionbroadcast; timed collection with early termination andsearchingextension protocol; confidence-based selection - Pure-matcher pattern —
Match.skill_idis the winning skill, never the plugin's ownpipeline_id; dispatch is<winning_skill_id>:common_query.questionvia PIPELINE-1 §7 common_query.questionis skill-owned — skills register it via INTENT-4 normally; it is NOT a reserved intent name- Discovery —
ovos.common_query.ping/ovos.common_query.pongper PIPELINE-1 §10 pattern - Answer-type metadata — advisory COSC labels for routing/display
PR
PR #40
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with PR #40 and compare it with the referenced PIPELINE-1 §7/§10 and INTENT-4 rules; the issue provides no implementation files or tests. Done means reaching a decided, internally consistent OVOS-COMMON-QUERY-1 specification covering the listed protocols and ownership rules.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100