GUI-1: GUI display subsystem specification

[JarbasAl]

OVOS-GUI-1 — GUI Display Subsystem specification

Adds a formal, implementation-agnostic specification for the OVOS GUI display
subsystem, in the same style as the existing specs (MSG-1, SESSION-1/2, INTENT-*).

ovos-gui-1.md (OVOS-GUI-1, Draft) covers:

• Model — applications declare what to display (semantic templates), not how;
  the GUI service is a pure state-and-dispatch hub.
• Closed template vocabulary — a curated set of SYSTEM_* templates (consistency
  across a varying display surface), full catalogue of all 22 templates with normative
  session-data keys/types; raw-passthrough (SYSTEM_html/SYSTEM_url) marked discouraged.
• Wire protocol — gui.value.set / gui.page.show (page_names, index, __from,
  __idle), reserved-key stripping, namespace lifecycle (builds on MSG-1).
• Addressing — session_id only; shared/multi-room screens share a session_id;
  no separate location dimension (builds on SESSION-1/2).
• Adapter contract — entry-point discovery, additive multi-modal fan-out, capability
  • graceful-degradation table, exception-safe / non-blocking / no-shared-state.
• Interaction — media transport + confirm/select responses carrying the
  originating session_id.
• Conformance — MUST/SHOULD for producers, the GUI service, and adapters.

Also wires OVOS-GUI-1 into README.md (index), CHANGELOG.md, and GLOSSARY.md.
Normative text is implementation-agnostic; code/toolkit names appear only in the
non-normative example.

[coderabbitai]

Warning

Review limit reached

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

More reviews will be available in 35 minutes and 18 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 285dbad1-c4dd-4bad-a108-e15c4788f887

📥 Commits

Reviewing files that changed from the base of the PR and between b97d563 and 94a4f4f.

📒 Files selected for processing (3)

• CHANGELOG.md
• GLOSSARY.md
• gui-1.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/gui-spec

---

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.}