docs: surface OVOS Architecture repo + claim OVOS-MSG-1 conformance#220
docs: surface OVOS Architecture repo + claim OVOS-MSG-1 conformance#220JarbasAl wants to merge 2 commits into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Automated check summary ready. 📊I've aggregated the results of the automated checks for this PR below. 📋 Repo HealthScanning for any signs of 'copy-paste' obesity. 🍕 ✅ All required files present. Latest Version: ✅ 🔒 Security (pip-audit)Security check! Are we safe from vulnerabilities? 🛡️ ✅ No known vulnerabilities found (52 packages scanned). 📊 CoverageI've been crunching the numbers! Here's how the test coverage changed. 📈 ✅ 91.0% total coverage (threshold: 65.0%) Files below 80% coverage (1 file)
Full report: download the ⚖️ License CheckNavigating the maze of open-source compliance. 🧩 ✅ No license violations found. Policy: Apache 2.0 (universal donor). StrongCopyleft / NetworkCopyleft / WeakCopyleft / Other / Error categories fail. MPL allowed. 🏷️ Release PreviewI've checked the 'Bug Fixes' list for accuracy. 🐛 Current:
✅ PR title follows conventional commit format. 🚀 Release Channel Compatibility Predicted next version:
🔍 LintEverything looks good so far! ✅ ❌ ruff: issues found — see job log 🔨 Build TestsI've inspected the foundation of your PR. 🕵️♂️ ✅ All versions pass
Standard Automated Signature v2.0 🏷️ |
PR #220 waits on the architecture-side specs that formalise the session carrier and the intent-context sub-object. Forward-link to those drafts from concepts.md and session.md so readers know where the layer-2 shape is being normatively pinned. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- README: top-level conformance callout citing OVOS-MSG-1 and the architecture repo; Related section lists architecture and ovos-spec-tools alongside ovos-pydantic-models. - docs/concepts.md: opening note pointing at OVOS-MSG-1 as the normative source for the envelope, routing keys, session carrier and derivations. - docs/session.md: link the two normative session fields (session_id, lang) to OVOS-MSG-1 §4 and frame the rest as layer-2 extensions per the spec. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
PR #220 waits on the architecture-side specs that formalise the session carrier and the intent-context sub-object. Forward-link to those drafts from concepts.md and session.md so readers know where the layer-2 shape is being normatively pinned. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3fa5f3c to
bc3fe74
Compare
Follow-up to #218. Now that the architecture repo is published and
ovos_bus_client.Messagere-exports the spec-tools reference implementation of OVOS-MSG-1, this package can claim conformance — and should make the spec discoverable.Changes
ovos-spec-toolsas the reference implementation.session_id,lang) to OVOS-MSG-1 §4 and frames the rest of theSessionclass (pipeline, site_id, IntentContextManager, persona, preferences) as layer-2 extensions per the spec.No code changes. 553 tests still pass.
🤖 Generated with Claude Code