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

M-5: Vision events — framePending/frameSent/frameExpired (F-007/F-010) #122

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

Goal

Vision events: framePending(captureId), frameSent(turnId, captureId), frameExpired(captureId). F-007 / F-010 amendment. Captures correlate via FrameCaptureID. ManualClock advances cause frameExpired after 5s deterministic.

Scope

  • 3 events with FrameCaptureID correlation
  • frameExpired after 5s default TTL, settable via clock
  • ManualClock-driven deterministic expiry in tests

Files

  • packages/JarvisAPI/Sources/JarvisAPI/Surfaces/Vision+Adapter.swift

Acceptance

  • 3 events emitted with correlated FrameCaptureID
  • frameExpired fires 5s after framePending
  • ManualClock advance(by: .seconds(5)) triggers expiry deterministically

Test

S-VIS-003 (5s frameExpired via ManualClock G-002).

Parent epic

#9

Source

.planning/architecture/JARVIS-API-MIGRATION-PLAN.md §2.6 (M-5.2)
.planning/architecture/JARVIS-API-DESIGN-v0.2.md F-007, F-010

## Goal Vision events: framePending(captureId), frameSent(turnId, captureId), frameExpired(captureId). F-007 / F-010 amendment. Captures correlate via FrameCaptureID. ManualClock advances cause frameExpired after 5s deterministic. ## Scope - 3 events with `FrameCaptureID` correlation - `frameExpired` after 5s default TTL, settable via clock - ManualClock-driven deterministic expiry in tests ## Files - `packages/JarvisAPI/Sources/JarvisAPI/Surfaces/Vision+Adapter.swift` ## Acceptance - [ ] 3 events emitted with correlated FrameCaptureID - [ ] `frameExpired` fires 5s after `framePending` - [ ] ManualClock `advance(by: .seconds(5))` triggers expiry deterministically ## Test `S-VIS-003` (5s frameExpired via ManualClock G-002). ## Parent epic #9 ## Source `.planning/architecture/JARVIS-API-MIGRATION-PLAN.md` §2.6 (M-5.2) `.planning/architecture/JARVIS-API-DESIGN-v0.2.md` F-007, F-010
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:vision enhancement migration
Milestone
No items
No Milestone v0.8 — API M-4..M-7 (Memory / Vision / Voice / Turn surfaces)
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#122