Skip to content

spec: GLOSSARY.md — topic-shape, stop-targeting, and shared_pipeline_id entries#127

Open
JarbasAl wants to merge 1 commit into
devfrom
spec/glossary-terms
Open

spec: GLOSSARY.md — topic-shape, stop-targeting, and shared_pipeline_id entries#127
JarbasAl wants to merge 1 commit into
devfrom
spec/glossary-terms

Conversation

@JarbasAl

@JarbasAl JarbasAl commented Jul 4, 2026

Copy link
Copy Markdown
Member

Adds four glossary entries introduced by the spec refactors:

  • Dispatch-shaped topic — the colon form <skill_id>:<intent_name> (MSG-1 §2.1.1).
  • Dotted addressed topic — a :-free dotted topic that names a recipient in a segment (e.g. <skill_id>.common_query.request); addressed, not a dispatch.
  • Recency-targeted stop — STOP-1 §4.1 fallback to the most recently activated handler instead of escalation.
  • <shared_pipeline_id> — STOP-1 §5.2's identity for the stop plugin instance addressed by global_stop.

The glossary carries no stale SESSION-1 title; entries are terse and defer to the authoritative spec sections. Non-normative — no CHANGELOG entry.

🤖 Generated with Claude Code

@coderabbitai

coderabbitai Bot commented Jul 4, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@JarbasAl, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 53 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: 226025f2-277b-43fa-8702-2dbac3b48c92

📥 Commits

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

📒 Files selected for processing (1)
  • GLOSSARY.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch spec/glossary-terms

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

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

@JarbasAl
JarbasAl marked this pull request as ready for review July 16, 2026 07:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant