[FEATURE] Define parent-death and orphan cleanup for Alpha 1 #61

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

Problem and motivation

Parent or supervisor loss must leave surviving children and terminal records with an explicit authorized owner.

Proposed behavior and scope

Implement the Alpha 1 scope in procd, launchd, posixd and kernel. 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 child survival, ownership/adoption, exit notification and reaping when a parent exits or its supervisor disappears.
  • Preserve generation identity and delegated authority; adoption cannot grant broader process control.
  • Test nested descendants, concurrent child exit, blocked waiters and repeated parent loss without leaking records, mappings or capabilities.

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 Parent or supervisor loss must leave surviving children and terminal records with an explicit authorized owner. ## Proposed behavior and scope Implement the Alpha 1 scope in procd, launchd, posixd and kernel. 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 child survival, ownership/adoption, exit notification and reaping when a parent exits or its supervisor disappears. - [ ] Preserve generation identity and delegated authority; adoption cannot grant broader process control. - [ ] Test nested descendants, concurrent child exit, blocked waiters and repeated parent loss without leaking records, mappings or capabilities. ## 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:53 +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/procd#61
No description provided.