spec: bridge-1.md — gate invariant (re-apply policy every inbound Message); managed-mode distinct sessions

[JarbasAl]

Refines OVOS-BRIDGE-1 to Version 3.

• §4.1 gate invariant: a bridge injecting policy fields (any blacklisted_* array, restricted pipeline) MUST re-apply them to every inbound Message from the governed participant. Connect-time-only policy is non-conformant under client authority (SESSION-2 §2.5) — a client may omit injected fields on any later Message, silently voiding the policy. The bridge is a gate, not a handshake.
• §4.2.4: a managed-mode bridge (§3.4.2) fronting concurrent independent clients MUST assign each a distinct session_id — in managed mode session attachment is the bridge's obligation. Relaying-mode satellites keep the SHOULD.
• §4.2.5: TTS-as-a-service relocated adjacent to the hub-side-audio topology it complements; hub-side audio bus surface cited to OVOS-AUDIO-1 instead of a future-spec promise.
• Timelessness: hardened-minimum topic set cites PIPELINE-1 §9 without enumerating ("currently ...") its topics; repository gap-catalogue pointers removed from normative text.
• Topic and session rules verified against MSG-1 §2.1.1 (all bridge topics dotted, no colons) and SESSION-1/2.
• CHANGELOG entry + Version bump to 3.

🤖 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: 8b33914a-7250-41c0-9626-a49db4333005

📥 Commits

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

📒 Files selected for processing (2)

• CHANGELOG.md
• bridge-1.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch spec/bridge-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.}