spec: fallback.md — bounded polls with RECOMMENDED ceiling, malformed-pong decline, broadcast-poll equivalence

[JarbasAl]

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

Changes

• Bounded polls, tunable ceiling (§6.1): the plugin MUST bound each per-skill wait — an unbounded wait stalls the whole utterance behind one unresponsive skill — while the ceiling itself is a RECOMMENDED default of 0.5 s (matching the analogous OVOS-CONVERSE-1 §4.2 and OVOS-STOP-1 §4.1 polls), deployer-adjustable.
• Absent/malformed pong = can_handle: false (§6.1): silence, a missing or non-boolean can_handle, or a mismatched skill_id all decline and skip — uniform with the companion protocols' silence rules.
• Broadcast-poll optimisation (§6.1): a single broadcast to the effective pool is permitted as an observably equivalent alternative to the sequential cycle — selection stays keyed on pool order, never response-arrival order, so outcomes are identical while waits overlap.
• Priority bands stay RECOMMENDED (§3.3): the three confidence tiers are a convention; different band conventions map by band membership, not numeric rescale. Catch-all last-entry ordering stated as SHOULD.
• Topic rule: registration events and ping/pong are dotted non-dispatch topics; the only colon topic is the genuine dispatch <skill_id>:fallback.
• §6.3 utterance = first element of the candidate list (PIPELINE-1 §4.1); cross-protocol note that the poll boolean's name (can_handle) is protocol-local; citations corrected (blacklisted_skills → PIPELINE-1 §5.3, session registry → SESSION-1 §2.2, ovos.intent.unmatched → PIPELINE-1 §9.3; SESSION-1 canonical title).

Principle

MUST/MUST NOT mark correctness/interop invariants (bounded waits, pool-order selection, decline-on-malformed); numbers (ceilings, priority bands) are RECOMMENDED defaults. Colon <x>:<y> is reserved for the orchestrator dispatch shape (MSG-1 §2.1.1); polls and registrations are dotted.

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: 839bb81b-4f3a-435a-b2fe-43e0c16cadcb

📥 Commits

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

📒 Files selected for processing (2)

• CHANGELOG.md
• fallback.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch spec/fallback

---

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.}