You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#11 states the Director's v1 context precisely: "frontmost application name,
idle duration, time of day, recent Behavior identifiers, and the active
Character's Personality Prompt." Four of those five have no producer.
#2 delivers the owning application name per window, which is not the same as
tracking which application is frontmost and noticing when that changes. Nothing
measures idle duration. Clock is named as a trait in docs/SPEC.md's adapter list
and in its "fakes, not mocks" rule, but does not exist.
Three user stories depend on this and on nothing else: 33 (react to me opening a
different application), 34 (settle down or sleep when I have been idle), 35
(behaviour shifts with the time of day).
Scope
The Free sensing tier, which docs/SPEC.md defines as needing no permissions at
all:
The frontmost application's name, and a signal when it changes.
Idle duration: how long since the last user input.
A Clock trait and its system implementation, so nothing else reads the wall
clock directly.
Explicitly not here: window titles, screen capture, clipboard, input contents.
Those are the Ambient and On-Demand tiers, which ADR-0005
puts behind consent and docs/SPEC.md puts out of scope for v1.
Acceptance criteria
The frontmost application name is readable with no permission prompt on a
machine where nothing has been granted.
Switching application produces a change signal rather than only a new value on
the next poll.
Idle duration grows while input stops and returns to zero on the next input.
No caller reads the wall clock directly; time arrives through Clock.
Nothing here requests Screen Recording or Accessibility.
Tests
Hand-written fakes for all three, per docs/SPEC.md's "fakes, not mocks". Tests
assert on what the Director context ends up containing, not on calls made to the
fakes, and never sleep — elapsed time arrives from the fake Clock.
The permission-free claim is verified the way #2 verified its own: by which APIs
are called, since a development machine that has already granted consent cannot
demonstrate the clean-machine case.
Activity