[FEATURE] Qualify clock domains and wall-time changes for Alpha 1 #14

Open
opened 2026-11-12 22:27:55 +01:00 by erikinkinen · 0 comments
Owner

Problem and motivation

Runtime time queries need explicit cross-core validity and wall-clock transition behavior.

Proposed behavior and scope

Implement the Alpha 1 scope in timed, RTC driver, kernel and runtime consumers. Follow the published Phase 6 requirements. Later-phase extensions remain separate.

Authority, security and reliability

Preserve explicit authority, original identity and resource custody across failure, cancellation and revocation. Apply security, reliability, then performance; names and observations must not create authority.

Acceptance criteria

  • Define monotonic and civil time contracts, source qualification and cross-core clock validity.
  • Test wall-clock adjustment, source loss and recovery without moving monotonic deadlines or accepting invalid clock domains.
  • Deadline waits and timestamp consumers fail explicitly when their required source is unavailable.
  • Exercise relevant transitions and concurrent queries on actual 1, 2 and 4-vCPU release images.

Alternatives and tradeoffs

Extend existing mechanisms where possible. Models and authored tests support the work but do not replace required original release-image evidence.

Tracking and rollout

Required by the Alpha 1 microkernel gate alongside the complete self-hosting gate. Link implementation PRs and dependencies here as they are established.

## Problem and motivation Runtime time queries need explicit cross-core validity and wall-clock transition behavior. ## Proposed behavior and scope Implement the Alpha 1 scope in timed, RTC driver, kernel and runtime consumers. Follow the [published Phase 6 requirements](https://git.erikinkinen.fi/erix/docs/src/branch/main/phases/6.md). Later-phase extensions remain separate. ## Authority, security and reliability Preserve explicit authority, original identity and resource custody across failure, cancellation and revocation. Apply security, reliability, then performance; names and observations must not create authority. ## Acceptance criteria - [ ] Define monotonic and civil time contracts, source qualification and cross-core clock validity. - [ ] Test wall-clock adjustment, source loss and recovery without moving monotonic deadlines or accepting invalid clock domains. - [ ] Deadline waits and timestamp consumers fail explicitly when their required source is unavailable. - [ ] Exercise relevant transitions and concurrent queries on actual 1, 2 and 4-vCPU release images. ## Alternatives and tradeoffs Extend existing mechanisms where possible. Models and authored tests support the work but do not replace required original release-image evidence. ## Tracking and rollout Required by the [Alpha 1 microkernel gate](https://git.erikinkinen.fi/erix/integration/issues/207) alongside the [complete self-hosting gate](https://git.erikinkinen.fi/erix/integration/issues/65). Link implementation PRs and dependencies here as they are established.
erikinkinen added this to the Alpha 1 milestone 2026-11-12 22:27:55 +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#14
No description provided.