[FEATURE] Retain native installer publication evidence #59

Open
opened 2026-10-30 13:33:50 +01:00 by erikinkinen · 0 comments
Owner

Problem and motivation

Process construction needs native evidence that one specific installer grant reached its intended recipient. That evidence must remain usable independently of a userspace acknowledgment or the grant's later disposal.

Proposed behavior and scope

Implement observer-bound Arm, Query and Retire operations for an original installer grant. Correlate the native child and original actor generations. Publish evidence only when the actual native reply is accepted. The wire contract is in Lib-ipc #19; Procd and Loaderd consume it during staged process construction.

Authority, security and reliability

Arm requires actual caller-local grant custody. Capture the observer from native execution; witness IDs and supplied process pairs remain descriptive data. Query and retirement require the same original observer. Derived grants cannot satisfy an original grant's evidence. Retain proof-only metadata after disposal without retaining installation authority, and preserve exact identity through retries, actor death and slot reuse. Keep service authorization policy in userspace.

Acceptance criteria

  • Implement exact original-grant admission and idempotent recovery.
  • Make native reply acceptance and publication evidence one serialized transition; reject incomplete publication and roll back failed transfers.
  • Retain evidence through grant disposal and retire only the original proof's storage.
  • Settle original materializer custody without withdrawing another live recipient's grant or blocking unrelated process work.
  • Cover unauthorized actors, stale generations, derived grants, failed replies, disposal, resource failures and repeated recovery.
  • Exercise the connected process-construction path on x86-64 QEMU/OVMF, including 1, 2 and 4 CPUs.
  • Update Rustdoc, component contracts and the technical manual; record measured reply-path overhead.

Alternatives and tradeoffs

A userspace acknowledgment records a service decision rather than the native capability transfer. An exact native grant record provides a narrower correspondence boundary, at the cost of retaining counted evidence until its original observer discharges it.

Tracking and rollout

Coordinate Kernel, Lib-ipc, Procd and Loaderd. Keep incomplete consumers in WIP feature PRs and preserve existing capability ceilings. Native acceptance remains required before claiming the connected construction path complete.

## Problem and motivation Process construction needs native evidence that one specific installer grant reached its intended recipient. That evidence must remain usable independently of a userspace acknowledgment or the grant's later disposal. ## Proposed behavior and scope Implement observer-bound Arm, Query and Retire operations for an original installer grant. Correlate the native child and original actor generations. Publish evidence only when the actual native reply is accepted. The wire contract is in [Lib-ipc #19](https://git.erikinkinen.fi/erix/lib-ipc/pulls/19); Procd and Loaderd consume it during staged process construction. ## Authority, security and reliability Arm requires actual caller-local grant custody. Capture the observer from native execution; witness IDs and supplied process pairs remain descriptive data. Query and retirement require the same original observer. Derived grants cannot satisfy an original grant's evidence. Retain proof-only metadata after disposal without retaining installation authority, and preserve exact identity through retries, actor death and slot reuse. Keep service authorization policy in userspace. ## Acceptance criteria - [ ] Implement exact original-grant admission and idempotent recovery. - [ ] Make native reply acceptance and publication evidence one serialized transition; reject incomplete publication and roll back failed transfers. - [ ] Retain evidence through grant disposal and retire only the original proof's storage. - [ ] Settle original materializer custody without withdrawing another live recipient's grant or blocking unrelated process work. - [ ] Cover unauthorized actors, stale generations, derived grants, failed replies, disposal, resource failures and repeated recovery. - [ ] Exercise the connected process-construction path on x86-64 QEMU/OVMF, including 1, 2 and 4 CPUs. - [ ] Update Rustdoc, component contracts and the technical manual; record measured reply-path overhead. ## Alternatives and tradeoffs A userspace acknowledgment records a service decision rather than the native capability transfer. An exact native grant record provides a narrower correspondence boundary, at the cost of retaining counted evidence until its original observer discharges it. ## Tracking and rollout Coordinate Kernel, Lib-ipc, Procd and Loaderd. Keep incomplete consumers in WIP feature PRs and preserve existing capability ceilings. Native acceptance remains required before claiming the connected construction path complete.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 13:33:50 +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/kernel#59
No description provided.