[FEATURE] Define IPC progress and cancellation under contention for Alpha 1 #130
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/kernel#130
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem and motivation
CPU fairness alone does not establish progress for competing IPC clients or control operations.
Proposed behavior and scope
Implement the Alpha 1 scope in kernel, lib-ipc and service owners. 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
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.