Skip to content

spec: msg-1.md — authoritative colon-vs-dotted topic rule; producer-side strictness for unknown keys#119

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

spec: msg-1.md — authoritative colon-vs-dotted topic rule; producer-side strictness for unknown keys#119
JarbasAl wants to merge 1 commit into
devfrom
spec/msg-1

Conversation

@JarbasAl

@JarbasAl JarbasAl commented Jul 4, 2026

Copy link
Copy Markdown
Member

Refines OVOS-MSG-1 to Version 2.

  • §2.1.1 is now THE topic rule every other spec cites: : marks a dispatch-shaped topic assembled from identifiers (<skill_id>:<intent_name>), definable only by a formal spec; every other topic is dotted <x>.<y>.<verb> and MUST NOT contain :. A consumer can classify any topic with a single character test. Separator-hygiene rules restated per shape.
  • §2 unknown top-level keys: producers MUST NOT emit; consumers SHOULD treat as malformed but MAY ignore — a hard reject would let one non-conformant emitter sever valid traffic bus-wide. §7 conformance aligned.
  • §5.2: dst[0] RECOMMENDED as the reply source for array destinations (deterministic convergence); still implementation-defined, consumers MUST NOT rely on it.
  • §3.1 walkthrough marked informative.
  • CHANGELOG entry + Version bump to 2.

🤖 Generated with Claude Code

…own-key relaxation, deterministic reply source

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@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: 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: 7327f725-d583-474d-9d4b-fff1d6c65b05

📥 Commits

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

📒 Files selected for processing (2)
  • CHANGELOG.md
  • msg-1.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch spec/msg-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

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

@JarbasAl
JarbasAl marked this pull request as ready for review July 16, 2026 07:21
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