spec: stop-1.md — recency-targeted stop (no escalation on silence), RECOMMENDED timeouts, shared_pipeline_id defined

[JarbasAl]

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

Changes

• Recency-targeted stop, never escalation-by-silence (§4.1 step 5, §4.2, §5.1): a generic stop with no positive pong responder falls back to the most recently activated active_handlers entry and MUST NOT escalate to global_stop. A pong can be absent for reasons unrelated to stoppability (busy handler thread, satellite round-trip beyond the ping window); escalating a missed sub-second reply to a session-wide wipe destroys converse state, response modes, and unrelated skills' activity. Recency-targeted stop degrades gracefully — at worst the dispatch is a no-op. global_stop now has exactly two triggers: explicit global-stop vocabulary and empty active_handlers.
• Timeouts are RECOMMENDED defaults (§4.1): ping-pong window RECOMMENDED default 0.5 s, SHOULD NOT exceed 1 s (stop is the most latency-sensitive user path); the hardcoded window value is removed from the step-5 rationale so the rule does not go stale with tuning.
• <shared_pipeline_id> defined precisely (§5.2): the pipeline_id of the stop plugin instance whose match produced the Match — the identity the global_stop dispatch addresses and PIPELINE-1 §7.1 stamps; "shared" across multiple §3.1 session.pipeline entries resolving to that instance, which MUST deduplicate to exactly one ovos.stop broadcast per global stop event per session (dedup stays MUST).
• blacklisted_intents operationalised (§6.3): the plugin MUST NOT return a Match whose <Match.skill_id>:<Match.intent_name> appears in the list; a stop utterance resolving to global_stop is governed by the global_stop entry.
• Cross-protocol note that the pong boolean's field name (can_handle) is protocol-local (CONVERSE uses result, COMMON-QUERY can_answer).

Principle

MUST/MUST NOT mark correctness invariants (dedup-to-one-ovos.stop, no escalation on silence, blacklist honouring); timing values are RECOMMENDED defaults. Silence is evidence of latency, not of absence of activity — destructive escalation must require positive intent (explicit vocabulary), never a timeout.

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

🤖 Generated with Claude Code

[coderabbitai]

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: f02107cd-e5ce-4177-97ac-7f6c92d60007

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/stop-1

---

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