FALLBACK-1: fallback pipeline plugin specification#39
Conversation
|
Warning Review limit reached
More reviews will be available in 37 minutes and 19 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the 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 credits. 🚦 How do rate 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 see our Fair Usage Limits Policy for further information. ✨ 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 |
JarbasAl
changed the title
|
Merge-readiness: resolved. Merges resolved across two commits (c158adf + db0bace):
Added FALLBACK-1, COMMON-QUERY-1, BRIDGE-1 in-review rows to README spec table. No other semantic flags. Cross-references in Note on #55: |
…isten field Consolidates the PIPELINE-1 companion edits previously bundled into the union-slots (#56), FALLBACK-1 (#39), COMMON-QUERY-1 (#40) and AUDIO-1 (#38) feature PRs into a single one-file change to ovos-pipeline-1.md. - §6.1/§6.2 — orchestrator backstop for required_slots (INTENT-3 §5.3): the orchestrator treats a Match as declined if any required slot is absent. Second line of defense behind engine-side enforcement. - §7.3 — reserve intent_names "fallback" (FALLBACK-1 §6.3) and "common_query" (COMMON-QUERY-1 §3). COMMON-QUERY-1 asserted the reservation but never registered the row; this closes that gap. - §9.6 — add the OPTIONAL listen field to ovos.utterance.speak; the output-side behaviour is owned by AUDIO-1. All additions are backwards-compatible. PIPELINE-1 is already V2 (its namespaced topics replace the pre-spec names); these refinements do not change the class, so the Version stays 2. Adds the missing PIPELINE-1 CHANGELOG section. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
JarbasAl
changed the title
1 participant
Companion issue: #48
Summary
Defines the fallback pipeline plugin — the final stage(s) in the utterance lifecycle that handle utterances no earlier stage claimed, by querying registered fallback skills in priority order and dispatching to the first willing one.
The defining property of a fallback skill is that it evaluates the utterance with its own logic rather than relying on registered intents. Regular skills declare coverage through INTENT-4; fallback skills receive the raw utterance at query time and decide for themselves — analogous to CONVERSE-1's per-skill poll.
What the spec covers
ovos.fallback.register/.deregister) with priority hint; session-scoped per INTENT-4 §11session.fallback_handlers(ordered preference list, same composition model as transformers)session.blacklisted_skills<skill_id>.fallback.ping/<skill_id>.fallback.pong); request carriesutterances+langso skill can parse the utterance itself<skill_id>:fallback(reserved intent name, PIPELINE-1 §7.3)fallback_high/medium/low) preserved via per-instance priority rangesCompanion edits (same PR)
ovos-pipeline-1.md§7.3 — reserve intent_namefallbackovos-session-1.md§3 — registerfallback_handlersfield