SESSION-1 §3.3: transfer site_id ownership to OVOS-BRIDGE-1

[JarbasAl]

Companion amendment to PR #43 (OVOS-BRIDGE-1).

Summary

• site_id's full normative definition (assignment rules, client vs. bridge authority, consumer constraints) is now owned by OVOS-BRIDGE-1 §3.4
• SESSION-1 §3.3 becomes a registry pointer only, retaining only the in-pipeline consumer rules (MUST NOT parse, MUST NOT overwrite) for components that never interact with the bridge spec directly
• Registry table updated: owner column §3.3 (this spec) → OVOS-BRIDGE-1 §3.4

Why

BRIDGE-1 is the first spec to give site_id real normative semantics: the bridge is the natural assignment point (geolocation, home-automation area names), and the client-may-report / bridge-may-override authority model is only defined there. Keeping a parallel definition in SESSION-1 would split the normative content across two specs with no clear owner.

Dependency

Merging this before PR #43 lands leaves the registry pointer dangling. Merge order: #43 first, then this.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Reorganized session specification documentation, delegating site_id field ownership and constraints to the OVOS-BRIDGE-1 specification. Updated cross-references for clarity.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 025372b0-5de1-444b-8dde-61f743becfde

📥 Commits

Reviewing files that changed from the base of the PR and between cec6c7d and 12e9049.

📒 Files selected for processing (1)

• ovos-session-1.md

---

📝 Walkthrough

Walkthrough

The session specification's site_id field transitions from internally-defined to externally-owned. The registry table is updated to cite OVOS-BRIDGE-1 §3.4 as the normative owner, and the dedicated section is replaced with a brief cross-reference while retaining orchestrator consumer constraints regarding string equality and inbound value preservation.

Changes

Documentation Ownership Delegation

Layer / File(s)	Summary
Delegate site_id ownership to OVOS-BRIDGE-1 ovos-session-1.md	Registry table entry for site_id is updated to reference OVOS-BRIDGE-1 §3.4 as the normative owner, and the dedicated subsection is replaced with a cross-reference that defers full normative behavior to the bridge specification while retaining constraints that orchestrator consumers may match only by string equality and must not overwrite inbound site_id values.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• OpenVoiceOS/architecture#22: Previous PR that initially defined or modified the site_id field semantics in the session specification, now being delegated to the bridge specification.

Poem

🐰 A field finds its home, across the spec divide,
From session's own nest to the bridge's wide side,
The table points outward, the section stands light—
One document yields what another holds tight! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the primary change: transferring site_id ownership from SESSION-1 §3.3 to OVOS-BRIDGE-1, which aligns with the main objective of the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch spec/session1-site-id-owner

---

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 and usage tips.}