[FEATURE] Own bootstrap namespace acquisition lifetimes #12

Open
opened 2026-10-18 22:12:19 +02:00 by erikinkinen · 7 comments
Owner

Problem and motivation

Bootstrap and executable discovery need namespace access before compatibility realms are available. Give those clients an explicit acquisition lifetime using their existing namespace grants.

Proposed behavior and scope

Add opt-in authenticated reply-budget metadata to Kernel CLAIM, define the matching LibIPC and namespace lease contracts, and migrate Vfsd, LibVfs, Loaderd, Rootd and Integration together. Keep path traversal inside Vfsd and preserve each client's existing operations. Remove superseded namespace acquisition APIs after all callers migrate.

Authority, security and reliability

Authenticate operations through original native caller and receiver lifetimes. Keys and generations locate owned state; they confer no authority. Add no grants. Check complete replies against native budgets and reserve readiness and retirement capacity before admission. Retain owners across errors, and require positive provider disposal before reporting retirement. Native bookkeeping alone cannot establish that result.

Acceptance criteria

  • Define the budget-attested CLAIM format, namespace wire contracts, typed client ownership and exact result correlation.
  • Implement counted producer storage with reserved readiness, cancellation and retirement progress.
  • Preserve existing grants, operation ceilings and bootstrap ordering across all seven repositories.
  • Migrate every namespace acquisition caller and remove the superseded APIs.
  • Cover success, refusal, lost results, cancellation, identity replacement, stale requests, exhaustion and provider retirement with independent controls.
  • Update component documentation and the technical manual, and exercise the original bootstrap and executable-discovery workloads.

Alternatives and tradeoffs

A receiver-wide reply minimum would restrict smaller operations; per-request native metadata avoids that. Using Posixd here introduces a bootstrap dependency cycle. Exporting the existing general scope factory would require broader grants. A namespace-specific frontend can reuse the counted acquisition machinery while keeping the current client boundaries.

Tracking and rollout

Coordinate Kernel, LibVfs, Vfsd, Loaderd, Rootd and Integration. Define the contracts first, then migrate producer and consumers as one cohort. Track phase completion in Integration #65.

## Problem and motivation Bootstrap and executable discovery need namespace access before compatibility realms are available. Give those clients an explicit acquisition lifetime using their existing namespace grants. ## Proposed behavior and scope Add opt-in authenticated reply-budget metadata to Kernel CLAIM, define the matching LibIPC and namespace lease contracts, and migrate Vfsd, LibVfs, Loaderd, Rootd and Integration together. Keep path traversal inside Vfsd and preserve each client's existing operations. Remove superseded namespace acquisition APIs after all callers migrate. ## Authority, security and reliability Authenticate operations through original native caller and receiver lifetimes. Keys and generations locate owned state; they confer no authority. Add no grants. Check complete replies against native budgets and reserve readiness and retirement capacity before admission. Retain owners across errors, and require positive provider disposal before reporting retirement. Native bookkeeping alone cannot establish that result. ## Acceptance criteria - [x] Define the budget-attested CLAIM format, namespace wire contracts, typed client ownership and exact result correlation. - [x] Implement counted producer storage with reserved readiness, cancellation and retirement progress. - [ ] Preserve existing grants, operation ceilings and bootstrap ordering across all seven repositories. - [ ] Migrate every namespace acquisition caller and remove the superseded APIs. - [ ] Cover success, refusal, lost results, cancellation, identity replacement, stale requests, exhaustion and provider retirement with independent controls. - [ ] Update component documentation and the technical manual, and exercise the original bootstrap and executable-discovery workloads. ## Alternatives and tradeoffs A receiver-wide reply minimum would restrict smaller operations; per-request native metadata avoids that. Using Posixd here introduces a bootstrap dependency cycle. Exporting the existing general scope factory would require broader grants. A namespace-specific frontend can reuse the counted acquisition machinery while keeping the current client boundaries. ## Tracking and rollout Coordinate [Kernel](https://git.erikinkinen.fi/erix/kernel/pulls/3), [LibVfs](https://git.erikinkinen.fi/erix/lib-vfs/issues/1), [Vfsd](https://git.erikinkinen.fi/erix/vfsd/issues/1), [Loaderd](https://git.erikinkinen.fi/erix/loaderd/issues/1), [Rootd](https://git.erikinkinen.fi/erix/rootd/issues/1) and [Integration](https://git.erikinkinen.fi/erix/integration/pulls/12). Define the contracts first, then migrate producer and consumers as one cohort. Track phase completion in [Integration #65](https://git.erikinkinen.fi/erix/integration/issues/65).
Author
Owner

The native reply-budget witness is published in Kernel d04e3e30 and LibIPC ac0a093c. OIR3 CLAIM reports the original invocation’s capacities; OIR2 and COLLECT stay unchanged, with no new rights. The namespace codecs and typed client are being implemented next. This issue stays open for the complete producer and consumer migration.

The native reply-budget witness is published in [Kernel d04e3e30](https://git.erikinkinen.fi/erix/kernel/commit/d04e3e30e4cc70d41537db12f61095e56ae4ad62) and [LibIPC ac0a093c](https://git.erikinkinen.fi/erix/lib-ipc/commit/ac0a093c78d56e2ef04e552e31aea200f01c6d9c). OIR3 CLAIM reports the original invocation’s capacities; OIR2 and COLLECT stay unchanged, with no new rights. The namespace codecs and typed client are being implemented next. This issue stays open for the complete producer and consumer migration.
Author
Owner

CREATE parity now has a separate provider-default creation proposal. The retained namespace request does not carry creation metadata, and FAT defaults can be configured independently. The proposal keeps that policy inside each provider while preserving original acquisition and retirement custody.

CREATE parity now has a separate [provider-default creation proposal](https://git.erikinkinen.fi/erix/lib-ipc/issues/13). The retained namespace request does not carry creation metadata, and FAT defaults can be configured independently. The proposal keeps that policy inside each provider while preserving original acquisition and retirement custody.
Author
Owner

LibIPC 9e32c52 publishes the counted namespace wire format and retirement receipts. Provider-default CREATE is tracked in #13. Migration of the persistent client and counted Vfsd producer continues.

[LibIPC 9e32c52](https://git.erikinkinen.fi/erix/lib-ipc/commit/9e32c525f13c1c3a15cd36dcb8e2b6e77f091a7a) publishes the counted namespace wire format and retirement receipts. Provider-default CREATE is tracked in [#13](https://git.erikinkinen.fi/erix/lib-ipc/issues/13). Migration of the persistent client and counted Vfsd producer continues.
Author
Owner

LibVfs ccf5854 publishes the persistent counted client and its explicit cleanup model. Ramfsd d0a292c publishes the memory provider adapter. Loaderd adoption, the Vfsd producer and the remaining filesystem adapters are in progress; the complete migration stays open.

[LibVfs ccf5854](https://git.erikinkinen.fi/erix/lib-vfs/commit/ccf58540d513f57b9c31168d25e2d950ab57b752) publishes the persistent counted client and its explicit cleanup model. [Ramfsd d0a292c](https://git.erikinkinen.fi/erix/ramfsd/commit/d0a292c018b10ad222d836e6619a2452c18d824c) publishes the memory provider adapter. Loaderd adoption, the Vfsd producer and the remaining filesystem adapters are in progress; the complete migration stays open.
Author
Owner

Loaderd adoption is published at 06dd7cbb. Ordinary discovery, manifest and dependency reads use the original owned namespace lifetime; exact staged executable reads retain their existing endpoint. Rootd adoption and the matching Integration catalog, native lifecycle cases and manual updates remain open.

Loaderd adoption is published at [`06dd7cbb`](https://git.erikinkinen.fi/erix/loaderd/commit/06dd7cbbacbef36fdfb62235bcfc1a608b6d6d5a). Ordinary discovery, manifest and dependency reads use the original owned namespace lifetime; exact staged executable reads retain their existing endpoint. Rootd adoption and the matching Integration catalog, native lifecycle cases and manual updates remain open.
Author
Owner

The budget-attested CLAIM and namespace/client contracts are defined, and Vfsd now reserves counted lifetime, work and retirement storage. The first two acceptance criteria are checked. Loaderd adoption is published; Rootd, coordinated image selection and the full native lifecycle workloads still need to complete before this issue can close.

The budget-attested CLAIM and namespace/client contracts are defined, and Vfsd now reserves counted lifetime, work and retirement storage. The first two acceptance criteria are checked. [Loaderd adoption](https://git.erikinkinen.fi/erix/loaderd/pulls/2) is published; Rootd, coordinated image selection and the full native lifecycle workloads still need to complete before this issue can close.
Author
Owner

The namespace lifetime chapter and regenerated public API references are now published. They describe the counted wire contract, original-lease inspection, disposal receipts and creation defaults. Rootd adoption and complete native cancellation and retirement workloads remain in progress.

The [namespace lifetime chapter](https://git.erikinkinen.fi/erix/docs/src/commit/76daadf9f7f26766985f1409e7d73a88ecff99ba/manual/8-libraries/namespace-lifetimes.tex) and regenerated public API references are now published. They describe the counted wire contract, original-lease inspection, disposal receipts and creation defaults. Rootd adoption and complete native cancellation and retirement workloads remain in progress.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:47 +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/lib-ipc#12
No description provided.