Skip to content

docs(g6 dev): Observer IDs (deferred) note in g6_06#56

Merged
mbreiser merged 1 commit into
mainfrom
docs/observer-ids-deferred-note
May 24, 2026
Merged

docs(g6 dev): Observer IDs (deferred) note in g6_06#56
mbreiser merged 1 commit into
mainfrom
docs/observer-ids-deferred-note

Conversation

@mbreiser

Copy link
Copy Markdown
Contributor

Summary

Adds a brief subsection to g6_06-host-software.md clarifying the design intent for Observer IDs, so the open question in #50 / #55 doesn't get over-engineered.

Per @mbreiser, Observer IDs are:

  • Same registry pattern as Arena IDs (host-canonical YAML under maDisplayTools/configs/)
  • Pure pattern-creation-time metadata for provenance and logging
  • Do not reach controller or panels
  • Do not appear in the pattern header on the wire
  • Do not dispatch any runtime behavior on host, controller, or panel
  • Implementation deferred — no spec / firmware / host-runtime blocker

6 inserted lines, no other changes.

References #55.

Per @mbreiser: Observer IDs are planned pattern-creation-time metadata,
parallel to the Arena ID registry pattern. Clarifies the design intent
so Frank's open question in #50 doesn't get over-engineered.

Key points captured in g6_06 § Observer IDs (deferred):
- Same host-canonical registry pattern as Arena IDs
- Pure metadata for provenance and logging
- Do not reach controller or panels; no wire-format impact
- No runtime behavior dispatched on host, controller, or panel
- Implementation deferred; no spec / firmware / host-runtime blocker

References #55.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@mbreiser mbreiser merged commit 4a4dbcc into main May 24, 2026
@mbreiser mbreiser deleted the docs/observer-ids-deferred-note branch May 24, 2026 01:53
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