[FEATURE] Give source event clocks a dedicated query endpoint #15

Open
opened 2026-11-15 04:27:43 +01:00 by erikinkinen · 0 comments
Owner

Problem and motivation

Native terminal events and filesystem timestamps need qualified wall observations. Give each consumer its own interface so unrelated time-service methods do not become part of its grant.

Proposed behavior and scope

Add separate, stable Ttyd and Vfsd endpoint objects supporting only NOW_WALL_V2, on both legacy and owned invocation paths. Keep existing PUBLIC clock queries and waits unchanged. Coordinate CapABI, Timed, Rootd, Ttyd and Vfsd; no new clock wire operation is needed.

Authority, security and reliability

Rootd creates each object only for an authenticated graph containing Timed and that consumer. Timed receives exact RECV and the selected consumer receives exact SEND. Vfsd’s new route replaces its PUBLIC grant. Receiver methods apply to every caller and delegated alias, without PID or role exceptions. Preserve Named publication and Launchd’s intentional general PUBLIC broker and configuration delegation.

Retire each narrow creator after its consumer’s transfer with exact absence proof; retain Launchd as the PUBLIC source’s final consumer. Partial setup and uncertain cleanup must fail closed without adopting a replacement source. Remove unused default receive aliases from Timed and Vfsd. Vfsd must verify its actual complete capability window, require exact installed roles, and reject undeclared aliases or uncertain query results without adopting or dropping them.

Acceptance criteria

  • Serve canonical qualified wall observations through each new object.
  • Reject monotonic, legacy wall, resolution, wait, RTC/private, unknown and malformed requests before clock, waiter or private-state effects, including delegated aliases.
  • Preserve existing PUBLIC wait clients, required inventories and original cleanup/retirement controls.
  • Complete paired component/native checks and document the configured-image acceptance separately.

Alternatives and tradeoffs

A sender-specific exception would not constrain delegated aliases. Reusing the broader PUBLIC object would couple the observer's authority to future methods. A dedicated receiver adds one graph-qualified endpoint per consumer but makes its method boundary explicit and stable.

Tracking and rollout

This completes the authority boundary of Rootd #22, alongside CapABI #25, Timed #11 Ttyd #11 and Vfsd #68. Publish paired feature branches and frozen CI selections, then qualify their composition. This is an existing requirement repair, not an additional release requirement.

## Problem and motivation Native terminal events and filesystem timestamps need qualified wall observations. Give each consumer its own interface so unrelated time-service methods do not become part of its grant. ## Proposed behavior and scope Add separate, stable Ttyd and Vfsd endpoint objects supporting only `NOW_WALL_V2`, on both legacy and owned invocation paths. Keep existing PUBLIC clock queries and waits unchanged. Coordinate CapABI, Timed, Rootd, Ttyd and Vfsd; no new clock wire operation is needed. ## Authority, security and reliability Rootd creates each object only for an authenticated graph containing Timed and that consumer. Timed receives exact RECV and the selected consumer receives exact SEND. Vfsd’s new route replaces its PUBLIC grant. Receiver methods apply to every caller and delegated alias, without PID or role exceptions. Preserve Named publication and Launchd’s intentional general PUBLIC broker and configuration delegation. Retire each narrow creator after its consumer’s transfer with exact absence proof; retain Launchd as the PUBLIC source’s final consumer. Partial setup and uncertain cleanup must fail closed without adopting a replacement source. Remove unused default receive aliases from Timed and Vfsd. Vfsd must verify its actual complete capability window, require exact installed roles, and reject undeclared aliases or uncertain query results without adopting or dropping them. ## Acceptance criteria - [ ] Serve canonical qualified wall observations through each new object. - [ ] Reject monotonic, legacy wall, resolution, wait, RTC/private, unknown and malformed requests before clock, waiter or private-state effects, including delegated aliases. - [ ] Preserve existing PUBLIC wait clients, required inventories and original cleanup/retirement controls. - [ ] Complete paired component/native checks and document the configured-image acceptance separately. ## Alternatives and tradeoffs A sender-specific exception would not constrain delegated aliases. Reusing the broader PUBLIC object would couple the observer's authority to future methods. A dedicated receiver adds one graph-qualified endpoint per consumer but makes its method boundary explicit and stable. ## Tracking and rollout This completes the authority boundary of [Rootd #22](https://git.erikinkinen.fi/erix/rootd/pulls/22), alongside [CapABI #25](https://git.erikinkinen.fi/erix/lib-capabi/pulls/25), [Timed #11](https://git.erikinkinen.fi/erix/timed/pulls/11) [Ttyd #11](https://git.erikinkinen.fi/erix/ttyd/pulls/11) and [Vfsd #68](https://git.erikinkinen.fi/erix/vfsd/pulls/68). Publish paired feature branches and frozen CI selections, then qualify their composition. This is an existing requirement repair, not an additional release requirement.
erikinkinen added this to the Alpha 1 milestone 2026-11-15 04:27:43 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/timed#15
No description provided.