KofTwentyTwo/Jarvis
2
0 Fork 0
Code Issues 111 Pull Requests 16 Actions Packages Projects Releases 4 Wiki Activity

v1.1 OQ-T4: runtime origin-tagging on events for single-writer assertion #81

New Issue
Open
opened 2026-05-12 19:30:19 +00:00 by KofTwentyTwo · 0 comments
KofTwentyTwo commented 2026-05-12 19:30:19 +00:00 (Migrated from github.com)
Copy link
Copy source

Summary

Add runtime origin tags to OrchestratorEvent and HUD-state emissions to prove single-writer invariants at runtime, not just via grep gates + behavioral tests. Currently the HUD-08 `HudStateCoordinator` single-writer guarantee is enforced by `scripts/check-single-writer-hudstate.sh` (compile-time) and unit tests (behavioral) — there's no runtime assertion catching a future regression in CI-released code.

Evidence

  • Migration plan §10: `.planning/architecture/JARVIS-API-MIGRATION-PLAN.md:736` — "OQ-T4 (state-ownership runtime assertion) — origin tagging on events to prove single-writer at runtime; v1.0 ships grep + behavioral, v1.1 adds runtime origin tags."

Gap classification

"design-mapped but not built" — open question explicitly deferred to v1.1.

Recommended action

File against v1.1. Pattern: each event carries an `origin: Origin` field (typed enum); coordinator asserts origin matches the expected writer at emission time. Cheap; surfaces the bug class proactively.

Cross-references

  • Migration plan §10 v1.1
  • HUD-08 invariant (REQUIREMENTS.md)
## Summary Add runtime origin tags to OrchestratorEvent and HUD-state emissions to prove single-writer invariants at runtime, not just via grep gates + behavioral tests. Currently the HUD-08 \`HudStateCoordinator\` single-writer guarantee is enforced by \`scripts/check-single-writer-hudstate.sh\` (compile-time) and unit tests (behavioral) — there's no runtime assertion catching a future regression in CI-released code. ## Evidence - Migration plan §10: \`.planning/architecture/JARVIS-API-MIGRATION-PLAN.md:736\` — \"OQ-T4 (state-ownership runtime assertion) — origin tagging on events to prove single-writer at runtime; v1.0 ships grep + behavioral, v1.1 adds runtime origin tags.\" ## Gap classification \"design-mapped but not built\" — open question explicitly deferred to v1.1. ## Recommended action File against v1.1. Pattern: each event carries an \`origin: Origin\` field (typed enum); coordinator asserts origin matches the expected writer at emission time. Cheap; surfaces the bug class proactively. ## Cross-references - Migration plan §10 v1.1 - HUD-08 invariant (REQUIREMENTS.md)
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
area:agent
area:build
area:bus
area:devtool
area:hud
area:logging
area:mcp
area:memory
area:vision
area:voice
audit-finding
bug
Something isn't working
 carry-forward
comment-cleanup
Comment / docstring cleanup per .planning/code-commenting-guide.md
 dependencies
Dependency updates
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 epic
good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 javascript
Pull requests that update javascript code
 migration
question
Further information is requested
 severity:critical
severity:high
severity:low
severity:medium
wontfix
This will not be worked on
No labels area:agent area:bus enhancement severity:low
Milestone
No items
No Milestone v1.1 — Backlog (Orpheus, WhisperKit, Voice Log, presence, advanced)
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/Jarvis#81