[FEATURE] Qualify secure entropy initialization and failure for Alpha 1 #782

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

Problem and motivation

An entropy API requires an actual qualified source and secure initialization, not deterministic fixture bytes.

Proposed behavior and scope

Implement the Alpha 1 scope in kernel, runtime libraries and the selected entropy provider. 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

  • Name the entropy provider, source assumptions, initialization and generator/reseeding policy.
  • Security-sensitive requests never succeed with deterministic test data or an uninitialized generator.
  • Define missing/degraded-source behavior, concurrency and exhaustion/refusal semantics.
  • Run positive and unavailable-source tests through actual runtime consumers and document delegated entropy authority.

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 An entropy API requires an actual qualified source and secure initialization, not deterministic fixture bytes. ## Proposed behavior and scope Implement the Alpha 1 scope in kernel, runtime libraries and the selected entropy provider. 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 - [ ] Name the entropy provider, source assumptions, initialization and generator/reseeding policy. - [ ] Security-sensitive requests never succeed with deterministic test data or an uninitialized generator. - [ ] Define missing/degraded-source behavior, concurrency and exhaustion/refusal semantics. - [ ] Run positive and unavailable-source tests through actual runtime consumers and document delegated entropy authority. ## 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/integration#782
No description provided.