Reserve a stable receiver slot for ordinary native commands #13

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

Problem and motivation

Native commands need a stable child capability layout so complete inherited
descriptor tables can be placed independently of the parent's receipt storage.
The ordinary command ABI should reserve its receiver explicitly.

Proposed behavior and scope

Reserve child-local slot 4 for the bound receiver of ordinary native commands,
outside their delegated capability interval. Procd retains the actual created
receiver with the managed process and uses it when admitting startup data,
descriptions and terminal provisioning. Its local installer-grant coordinates
remain separate. Update LibCapabi, the producers, native consumers, fixtures
and technical manual together. Other service and realm creation policies keep
their own explicit layouts.

Authority, security and reliability

Use the receiver created with the original process and preserve its exact
identity, rights and generation. A numeric coordinate grants no authority.
Keep installer receipts and rollback owners attached through preparation,
start, exec and uncertain cleanup. Reject conflicting child capability
destinations before effects; descriptor numbers, lender identities and parent
source coordinates remain independent namespaces. Require coherent signed
suppliers, with no inferred receiver or compatibility fallback.

Acceptance criteria

  • Ordinary creation paths retain the actual receiver separately from local
    installer-grant storage, including multiple managed rows.
  • Startup, description and terminal admission use the retained receiver;
    wrong inventory, generation or destination refuses before effects.
  • Complete sparse inheritance reaches the architectural delegated boundary,
    while child receiver destinations are reserved independently of FD numbers.
  • Prepare, abort, exec and partial installation preserve original receipt,
    endpoint and cleanup custody without remapping a committed transcript.
  • Shared ABI documentation, native consumers, target-derived layouts and
    meaningful unit/integration fixtures cover the coordinated migration.

Alternatives and tradeoffs

Negotiating a receiver after preparation would require another authenticated
placement transaction. A reserved ordinary-command slot keeps the existing
intent and receipt protocols and avoids coupling child placement to parent
storage geometry.

Tracking and rollout

Implement this as a coordinated dependency of
descriptor inheritance.
Keep the phase checklist
and dependent PRs aligned with the final ABI and remaining acceptance work.

## Problem and motivation Native commands need a stable child capability layout so complete inherited descriptor tables can be placed independently of the parent's receipt storage. The ordinary command ABI should reserve its receiver explicitly. ## Proposed behavior and scope Reserve child-local slot 4 for the bound receiver of ordinary native commands, outside their delegated capability interval. Procd retains the actual created receiver with the managed process and uses it when admitting startup data, descriptions and terminal provisioning. Its local installer-grant coordinates remain separate. Update LibCapabi, the producers, native consumers, fixtures and technical manual together. Other service and realm creation policies keep their own explicit layouts. ## Authority, security and reliability Use the receiver created with the original process and preserve its exact identity, rights and generation. A numeric coordinate grants no authority. Keep installer receipts and rollback owners attached through preparation, start, exec and uncertain cleanup. Reject conflicting child capability destinations before effects; descriptor numbers, lender identities and parent source coordinates remain independent namespaces. Require coherent signed suppliers, with no inferred receiver or compatibility fallback. ## Acceptance criteria - [ ] Ordinary creation paths retain the actual receiver separately from local installer-grant storage, including multiple managed rows. - [ ] Startup, description and terminal admission use the retained receiver; wrong inventory, generation or destination refuses before effects. - [ ] Complete sparse inheritance reaches the architectural delegated boundary, while child receiver destinations are reserved independently of FD numbers. - [ ] Prepare, abort, exec and partial installation preserve original receipt, endpoint and cleanup custody without remapping a committed transcript. - [ ] Shared ABI documentation, native consumers, target-derived layouts and meaningful unit/integration fixtures cover the coordinated migration. ## Alternatives and tradeoffs Negotiating a receiver after preparation would require another authenticated placement transaction. A reserved ordinary-command slot keeps the existing intent and receipt protocols and avoids coupling child placement to parent storage geometry. ## Tracking and rollout Implement this as a coordinated dependency of [descriptor inheritance](https://git.erikinkinen.fi/erix/exsh/issues/27). Keep the [phase checklist](https://git.erikinkinen.fi/erix/integration/issues/65) and dependent PRs aligned with the final ABI and remaining acceptance work.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:10 +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#13
No description provided.