[FEATURE] Audit authority, code quality and documentation in lib-ipc #1

Open
opened 2026-09-12 07:57:50 +02:00 by erikinkinen · 2 comments
Owner

Problem and motivation

Audit lib-ipc throughout Phase 6. Define IPC wire formats, transfer receipts and service operation contracts, including the nested x86_64 syscall shim.

Review each changed boundary at the final published revision. Prioritize security, reliability, then performance.

Proposed behavior and scope

Lost-provision-reply retirement refinement — 24 September 2026 (implementation pending): RETIRE alone permits an all-zero startup digest to explicitly describe an unknown startup after a lost or malformed Provision response. The actual original Launchd caller, complete original child/generation and retained realm binding remain mandatory; the zero sentinel omits only digest correlation and never selects a replacement or confers authority. A supplied nonzero digest must still match exactly. START never permits this sentinel. Known pre-provision staged custody keeps its existing authenticated staged-abort route. Final retirement acknowledgment still requires actual exact-instance disposal and all locally owned transport/authority obligations, rather than native absence alone.

Private start admission refinement — 24 September 2026 (implementation pending): add Launchd START_REALM operation 0x6D4 with an exact 40-byte authority-free request: request/op at offsets 0/4, original realm/generation at 8/16, and explicit request/result byte budgets at 24/32. The actual pending native caller must still own that retained realm. Validate packet arithmetic and both minimum 96-byte budgets before effects. Preserve all existing BEGIN/PREPARE/READ/ABORT selectors and the ordinary process-start gate.

Extend descriptive realm state with Starting (6) and PrivateReady (7), retaining values 0–5. Reuse the existing 40-byte admission response; a successful START acknowledgment requires PrivateReady. The service retains the original response obligation while its immediate private caller and configuration-server owners progress. READ may describe Starting; a lost public response or cancellation retains exact cleanup. PrivateReady proves the observed native-child Ready and confirmed independent controller challenge plus retirement of Launchd-owned transport handles. It does not claim that server COMPLETE observes Posixd's later caller RELEASE, nor does it seal, publish or grant client access.

Private provisioning transport refinement — 24 September 2026 (implementation pending): the guarded preparation request remains non-starting. Add separate typed Procd operations for Provision (0x433), private Start (0x434) and exact Retire (0x435), all admitted only from the original Launchd generation on its held private receiver. Provision carries a 48-byte request with exact child and realm identity plus explicit request/result byte budgets, and exactly one moved Generic SEND configuration receipt. Procd derives the actual child capability extent from its retained creation geometry, installs configuration at child slot 5, and computes page-rounded startup/workspace mappings beyond the recorded executable extent. Its successful 224-byte response returns the canonical 208-byte startup record after a 16-byte correlation/result/state prefix; failure carries no startup bytes. Start and Retire each carry 64 bytes with the original child/realm and canonical startup digest, preventing cross-stage substitution. These bytes constrain actual held routes and never confer authority.

Procd has no existing own-process identity in its startup payload. Reuse native caller attribution through a separate 64-byte configuration ContextProbe/Ack before RBS1 construction. The probe carries correlation, realm/child and original Launchd identity, with zero controller fields; Launchd obtains the Procd pair from actual CLAIM, retains that original pair and echoes it in the correlated acknowledgment. Procd retains the accepted invocation through retirement before committing the resulting context. This adds no kernel identity query, process endpoint or permission to trust an arbitrary first challenge. Posixd still requires its supplied controller to match the challenge's actual native caller.

Launchd explicitly reserves four capability columns per admitted realm in its authenticated deployment geometry. It creates the configuration receiver before exporting SEND, binds an ancestor revoker to its own native lifetime, keeps a separate nested revoker for early retirement, and removes all bypass source aliases. Original executable-scope storage may be reused for temporary construction only after its absence is acknowledged. Procd retains the received configuration sender in an already empty role-owned scratch column, accounts for every mapped frame and setup alias, consumes the actual GRANT through operation 58 only after provisioning, and records uncertain start disposition before the native start effect. No grant-derived MINT capability or ordinary-start fallback is added.

Private Start completes only after native start and the independent control challenge have completed their owned caller cleanup; readiness uses Launchd's separate actual-child CLAIM and full startup digest. Invocation handles and application owners remain retained on cancellation, malformed response, lost reply, supervisor loss and partial disposal. Retire selects running termination after any possibly committed start and waits for exact terminal observation/destruction before acknowledging final retirement. Frame allocation and each handshake must preserve explicit ownership and bounded progress; ordinary staging and all existing refusal/cleanup witnesses remain required. Provision, Start, readiness, seal, publication and client I/O remain distinct acceptance steps.

Private mediator execution design — 24 September 2026 (implementation pending): the next native witness executes the actual Posixd binary using the existing serialized process mapping path. Private address-space-root routing remains separate work; source review found no dependency that requires it before this witness.

The shared contract will add a distinct counted RBS1 startup image: exact version/byte extent; original realm and generation; native child, Launchd supervisor and Procd controller identity pairs; ordered endpoint and writable-workspace records; explicit capability-window and request/result/receipt storage budgets. The initial schema admits exactly a control RECV endpoint and a configuration SEND endpoint, with no root object, Process route or factory. Reject unknown roles, surplus records, duplicate slots, reserved bits, arithmetic overflow and overlapping storage. Counts describe the supported bootstrap roles, while deployment inputs set storage budgets. Startup bytes are child-read-only/NX; Procd verifies installed inventory and separate private RW/NX workspace before execution. The consumer checks actual local capability types/rights. The complete canonical bytes are SHA-256 correlated in readiness and the independent control challenge; parsing and digests grant no authority.

Provisioning finishes by consuming the existing GRANT-only installer through native child-lifetime binding (operation 58), without adding MINT or another installer. Record uncertain binding/start effects before replying. Native start independently requires an empty installer census. Adopt generation-bound native running termination through a new Process operation 61: original child/generation and kill reason, zero reserved fields, no extra route or rights. The generation comparison and terminal transition share native lifecycle serialization; stale requests must never select a replacement. Its acknowledgment is distinct from terminal observation, invocation retirement and native destruction.

Posixd will register only its declared control receiver and use immediate owned operations to submit readiness through its declared configuration SEND while continuing bounded control progress. Launchd authenticates readiness from actual CLAIM origin. Procd independently challenges its retained control endpoint; COLLECT payloads do not attest a server identity. Both exchanges carry exact original identities and startup digest, admit no capabilities at this bootstrap stage, and retain every accepted native handle even on unusual immediate status. Configuration, sealing and client publication remain later separate gates.

Required evidence includes strict codecs and actual inventory denial; committed-effect/lost-reply ownership; wrong/stale caller and generation denial; running-child retirement; supervisor loss; and a maintained VM executing Posixd with native readiness and challenge. Existing unstarted staging regressions remain required. Subsequent acceptance still requires two mediators, two clients each, mediated byte I/O, cross-realm refusal and full retirement, followed by the external toolchain rebuild and both complete guest OS build generations.

Detailed scope and contracts

Original PTY readiness checkpoint — 2 October 2026

Original cancellation, acknowledged draining, definite result-capacity refusal and uncertain publication remain distinct; unknown custody forbids replay and requires terminal teardown.

TTYd registers original private input/output receivers before either bootstrap or dynamic session creation exports SEND aliases. Actual occupancy, capacity and closure drive readiness; unchanged waits issue no repeated status RPC or native custody probe.

The signed image requires explicit TTY waiter capacity, admits pristine compiler geometry, checks alignment/native extent and places exact trailing waiter rows above core state and below the terminal stack.

This checkpoint adds no whole-feature acceptance: Launchd delegated-view forwarding, original descriptor subscriptions, complete POSIX consumers, signal/deadline composition and end-to-end native readiness workloads remain unfinished. Both complete EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.

Counted public clock deadlines — 2 October 2026

One earliest native timer uses only Timed's existing Time SEND binding; no Time capability is delegated to clients.

Original caller cancellation, source failure, definite result-capacity refusal and uncertain timer/result custody remain distinct.

Image packaging requires explicit waiter capacity, validates pristine compiler geometry and checked native extent, expands the signed arena and shifts its terminal stack. Zero capacity deliberately refuses deferred admissions; padding never adds rows.

Its required TIMED_DEADLINES_OK marker follows all assertions. The dedicated scenario retains a 90-second external diagnostic budget; the existing time profile also requires the workload and actual APIC wake backend. Hosted adapters cannot fabricate guest success.

Original descriptor/provider subscriptions, mediator/client consumers, signal masks and complete poll/select workloads remain unfinished. Overall phase checklist acceptance is unchanged. Both complete EriX guest generations and rebuilding external Rust/LLVM inside EriX remain required and unperformed.

Authorized native deadlines — 2 October 2026

ARM_DEADLINE (0x59) derives the actual current running process, generation and CSpace, validates the original dedicated Time SEND binding and syscall window, admits a calibrated clock and real interrupt source, and reserves storage before returning an original timer selector. No extra service grant, copied capability, retained user pointer, relative overflow or arbitrary duration/count ceiling is introduced.

Binding loss retains one final original wake; terminal cleanup ends all custody, and serials never wrap/reset.

Runtime and owned-invocation images include the real APIC backend; unsupported profiles refuse timer admission. Elapsed decisions use calibrated monotonic nanoseconds, never interrupt counts.

It requires actual native blocking, increased hardware acknowledgment, a newer epoch, elapsed status and GP/direction canaries, then cancels the original timer. The required deadline marker follows every native/user assertion.

This prerequisite adds no phase acceptance. Timed still needs counted original public deadline waiters/cancellation; descriptor/provider subscriptions, mediator/client consumers, signals and complete poll/select workloads remain unfinished. A service must cover every real event source before replacing cooperative yielding with atomic waiting. Both complete EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.

Explicit legacy receiver watches — 2 October 2026

WATCH_RECEIVER (0x57) authenticates the actual current running generation, CSpace, syscall window and original generic endpoint RECV binding. Registration receives no data, retains no capability, creates no owned-request intake and grants no implicit clock or provider route. Repeated registration of the same binding is idempotent; serials never wrap, including across quiescent storage resets.

Backpressure does not claim CALL acceptance or move capabilities.

Ten new native unit controls cover original versus foreign watchers, observe/arm arrival, identical registration, SEND denial, absence of implicit owned intake, alias and binding retirement, same-slot replacement, transfer rendezvous, allocation refusal, exact register shapes and process teardown. Its required legacy-watch marker follows all native and user assertions.

This prerequisite adds no phase acceptance. Authorized monotonic deadlines, counted original waiters, descriptor/provider subscriptions, mediator/client consumers, signals and complete poll/select workloads remain unfinished. A service must cover every real event source before replacing cooperative yielding with atomic waiting. Both complete EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.

Original native activity and atomic wait — 2 October 2026

Epoch exhaustion refuses sleep without wrap. Accepted COMPLETE ends serving observation custody, so the former server cannot observe later caller collection or retirement.

Ten new native-object and scheduling controls are authored, alongside extended literal and hosted-refusal controls. The original real-CPL3 scenario now makes the server capture its actual epoch and sleep; cancellation of its original delivery wakes it, and user instructions require a strictly newer returned epoch before acknowledgment. The scenario requires the activity-wake marker only after the complete original workload.

This is prerequisite implementation, with no new checklist acceptance. Explicit legacy receiver watches, authorized finite deadlines, original descriptor subscriptions, mediator/provider consumers, signal handling and full poll/select workloads remain unfinished. Mixed legacy/native loops must not yet replace their yielding with native-only waiting. Both complete EriX guest generations and external Rust/LLVM rebuilding remain required and unperformed.

VFS requires frozen Write for regular-file resize and live admitted file/directory custody for sync. Known refusals preserve original admission; uncertainty keeps cleanup-only custody, with no retry or pathname reopen.

No request or adapter adds a device, mount, credentials, new native rights or capability transfer.

They cover literal framing, unchanged output on refusal, full correlation, access direction, actual aliases and zero growth, storage/format refusal, clean recovery ownership, lost barriers/replies, retained cleanup and short reply capacity.

Existing ext logical-range conversions and sparse-gap traversal still need the size-boundary audit; compatibility truncate/ftruncate/fsync/fdatasync consumers, complete cancellation controls and new live workloads remain unfinished. Current phase completion remains 19.20% weighted, 7.61% whole acceptance: 27/460 parents and 486/949 children.

Both full guest EriX generations and external Rust/LLVM rebuilding remain required and unperformed.

Staged construction without root capabilities — 15 September 2026

Add kernel-control operation 54, CREATE_STAGED_PROCESS_WITHOUT_ROOT_CAPS, and checked StagedProcessWithoutRootCapsV1 scalar framing. Successful creation returns a live Created process and nonzero generation whose CSpace contains exactly its requested primary endpoint, with no CNode, VSpace or TCB capabilities. Native CSpace/TCB/VSpace objects and the process's VSpace lifetime reference still exist. No child code executes during construction. The endpoint initially retains its ordinary full endpoint rights; operation 53 independently narrows it before bootstrap execution.

Keep the existing creation operation 32 and its producer behavior unchanged. The new selector is independently recognized: an older kernel refuses it, and callers must not fall back to old ignored flags or a child self-report. Admit it only on the existing Process endpoint family, without adding a capability type, endpoint factory or ChildPopulate creation authority.

Use the existing fixed request envelope. arg0 contains the caller-local install-grant destination in its low 32 bits; its upper half is zero. arg1 low/high halves contain child-local primary endpoint and caller-local endpoint-master destinations. arg2 low/high halves contain the child window base and optional caller-local VSpace destination. arg3 contains the 32-bit window length, with a zero upper half. Flag bit 0 means that the VSpace receipt is requested; all other flag bits are zero. When the bit is clear, arg2's upper half must be zero. This explicit presence bit distinguishes an omitted receipt from a real receipt in slot zero. All slot fields retain their full unsigned width; slot zero and otherwise vacant former root positions are ordinary requested slots, subject to native bounds, actual caller-window visibility and occupancy. The checked codec validates framing, not native capacity or authority. The native constructor requires a valid child window containing the primary endpoint.

The caller receives only its actual unique stage-bound install grant, endpoint master and optional MAP-only VSpace receipt. The grant is bound to the returned process/generation and exact child window. Existing capability ceilings, actual object identity and explicit disposal rules remain in force. Temporary native setup bindings must be gone before constructing the final primary endpoint and publishing the grant; otherwise former root positions would remain an unnecessary destination restriction. The TCB's independently held VSpace reference must keep backing alive even without any child or parent VSpace capability.

On failure, destroy the partial child and dispose only successfully created parent receipts. Preserve pre-existing or overlapping destinations and the original failure; uncertain cleanup fail-stops. Never treat a requested slot as evidence that its capability was created. The new contract supplies an initial inventory, not a permanent prohibition on later explicitly authorized installations or a sealed realm. The returned grant remains a real pre-start population authority that its owner must account for and retire.

Required checks include full-width codec/reserved-field cases, omitted versus slot-zero VSpace receipts, zero/former-root/last-slot endpoint destinations, invalid or inaccessible windows, occupied/overlapping outputs, exact parent and child inventories, no residual native objects, mapping/startup backing retention, attenuation through the actual grant and abort/terminal cleanup. Actual CPL3 creation/refusal/disposal must complement host tests. Procd adoption must select this operation only for the mediator role and preserve all ordinary start gates until authenticated grant return, minimum typed startup, retained native/nested guards, readiness, configuration/seal and fair retirement are independently implemented. No runnable realm or guest build is established by this constructor alone.

Native staged endpoint attenuation — 15 September 2026

Add kernel-control operation 53, ATTENUATE_STAGED_ENDPOINT_WITH_GRANT, with a checked ProcessBoundEndpointAttenuationV1 request. This is a new recognized operation; an older kernel must refuse it, and producers must never fall back to an unchecked or post-execution self-report. No syscall number or service endpoint permission is added.

Use the existing fixed KernelControlRequestV1 layout: arg0 low/high halves are the caller's actual install-grant slot and child endpoint destination; arg1 is the exact 32-bit rights mask, with its upper half zero; arg2 low/high halves are expected process and staging generation; arg3 and flags are zero. Both identity components are nonzero. Zero rights means exactly zero, never inheritance. Successful response values are zero.

The native handler must validate the actually held GRANT-bearing install grant, its record, exact expected process/generation, live Created child, grant window, endpoint type ceiling and actual primary endpoint slot. Its rights ceiling must cover the current endpoint rights as well as the requested result; a narrow installer cannot manage a broader existing binding. The new rights must be known, valid for endpoints and a subset of current rights. Update only that existing binding's rights, preserving native object identity, all other bindings and revocation associations. The change allocates no alias and needs no new destination. Repeating the same attenuation may succeed; restoring a removed right must fail. Running, dead, stale, foreign, missing and wrong-type targets must fail without effects.

Admit the operation only on the same Process and ChildPopulate control kinds as exact process-bound installation. Endpoint possession and descriptive IDs alone are insufficient: the actual held scoped grant remains mandatory. The immediate consumer is the future Procd bootstrap transaction, after the actual broad grant returns from Launchd. It will reduce the staged mediator's initial full endpoint to RECV before any private execution, providing independent native proof of that boundary.

Required coverage includes codec/reserved-field rejection, missing and moved grant, wrong process/generation, wrong target/type/window/ceiling, exact attenuation and retry, attempted amplification, post-start refusal, actual CPL3 effect checks and full cleanup. This primitive alone does not admit mediator execution: authenticated grant return, native lifetime and nested revoker custody, minimal root/bootstrap inventory, readiness, configuration/seal and fair retirement remain separate gates. The current ordinary start prohibition stays in force.

Staged mediator handoff contract — 15 September 2026

Reserve Loaderd operation 0x654 (PREPARE_REALM) using the existing exact-executable preparation request/response layout. The operation selects the new Procd lifecycle class 0x448 (REALM_MEDIATOR); role values describe lifecycle policy and confer no capability authority. Launchd explicitly selects this operation after authenticating its executable object. The ordinary operation 0x652 keeps its existing behavior. Responses must echo the selected operation; no fallback is permitted.

Loaderd validates the same sole exact-executable SEND receipt, authenticates the complete image graph, and uses the existing semantic materialization pipeline. The mediator's temporary initial endpoint occupies child-local slot 4, after native root slots 1–3. This slot is an ABI destination, not a realm-count or resource-budget restriction. The child remains staged. Procd retains the actual endpoint master in the existing managed scratch endpoint column; it never exports that master to Loaderd or Launchd. Only the actual move-only install grant travels Procd → Loaderd → Launchd. The derived ordinary stream installer is absent for this class. Reply loss aborts the exact stage and accounts for the retained endpoint, grant and VSpace; cleanup uncertainty remains fail-stop.

Launchd may inspect, abort and stop only its owned lifecycle classes. Root, driver and powerbox routes cannot use the mediator class; generic staged-start, ordinary startup/stream installation and automatic restart reject it. The future separate bootstrap transaction must receive the actual grant back, authenticate the live caller, install a typed receiver/rendezvous inventory using exact process-bound installation, dispose temporary aliases and configure the startup bytes before private execution. No existing start path may bypass that gate.

This staged handoff is the first implementation increment of typed realm bootstrap. Acceptance for this increment requires malformed/foreign operation rejection, exact executable and grant receipts, unstarted materialization, private master retention, no derived stream grant, and rollback coverage across the actual producer paths. It does not establish mediator execution, seal, publication, client I/O, retirement fairness or either complete guest build generation. Those remain required under the existing acceptance criteria. Native VM coverage of the coordinated producer graph is required before claiming runtime acceptance.

Current inventory: 37 Cargo targets (2 lib, 35 test); manifests: Cargo.toml, ipc-syscall-x86_64/Cargo.toml. Include explicit and automatically discovered targets, supported features and target-specific configurations.

Trace authority-bearing inputs through callers and public APIs. Confirm that the library acquires no service, hardware or host authority implicitly. Review startup, teardown and Rootd parity at the caller boundary when this crate owns no process, and justify each applicability decision.

The initial missing-docs gaps at tests/job_authority.rs, tests/launch_inherited_description.rs, tests/process_metrics.rs, tests/serial_input.rs and tests/vfs_touch.rs are corrected with useful crate rustdoc and explicit lint enforcement in WIP PR #2, signed revision 5ff18b2bf62d3103e5b84aa92d1dc1cd096e9725. The same checkpoint adds a pure checked representation of all nine existing native result codes, preserving unknown values and requiring separate route/completion/cleanup context. Its full local IPC/shim matrix passes without warnings; broader authority, private documentation and consumer audits remain open. This does not close the aggregate criteria below.

Current signed checkpoint de6892790de69f40f749c393d24078b287b36175 also defines the consumed local lifetime-revocation ABI/shim from Kernel issue 7. Both crates pass the 52-command strict local matrix, emitted register review and push CI 333/PR CI 334, with no warning candidates. Kernel enforcement, native VM/producer acceptance and the new manual/API refresh remain open in WIP PR #2.

Planned native terminal-generation contract — 17 September 2026: Introduce operation 55 for exact native process/staging-generation/event-kind/status observations. The request has zero flags and arguments; malformed requests fail before dequeue. Successful responses preserve all four 32-bit fields, captured with the actual native terminal transition and retained after destruction. Empty queues return RETRY with zero values. These records constrain existing authority and confer no process-control capability.

Kernel, shared IPC, Procd and Rootd migrate together. Procd must match the native process/generation pair before cleanup, CPU-time observation, restart or service-event publication. Remove the superseded identity-free native selector after all maintained consumers migrate, with no fallback on unsupported kernels. Preserve queue reservation, ordering, wake and failure semantics. Validate actual exit/kill, generation reuse, empty/malformed input and cleanup failure, then strict component checks and original bounded native VMs on a coherent immutable revision graph.

This is the terminal-observation prerequisite for typed mediator bootstrap. The actual returned install grant already has a generation-checked endpoint-attenuation primitive for the first bootstrap effect. Guard custody, final receiver readiness, sealed publication, two mediators with real client I/O and both full guest builds remain separate mandatory work; this planned contract implements none of those by itself.

Authority, security and reliability

Record each finding's affected revision, invariant, reproduction, owner, regression coverage and resolution. Report suspected vulnerabilities through SECURITY.md and keep sensitive details private. Record a result and rationale for each audit criterion, including caller responsibilities when this component has no process or Rust target.

Acceptance criteria

Checklist
  • Record origin, recipient, object, operations, delegation ceiling, lifetime and aliases for each relevant capability or caller-supplied authority-bearing value.
  • Audit ambient discovery/selectors, cwd/PATH/environment, numeric identities, inherited routes and host fallbacks; require explicit authorized intake.
  • Account for residual authority after success, error, cancellation, timeout, restart, failed transfer and teardown, including fork/exec where implemented.
  • Remove unnecessary endpoints, broad rights, duplicate aliases, provider/admin grants and debug routes.
  • Exercise stale generations, replay, pending replies, forged descriptive identity and object/path resolution races at the owned boundary.
  • Prove independent cleanup attempts and caller-specific error precedence; quarantine or terminate when retained authority cannot be accounted for.
  • Review unsafe/FFI/parser/arithmetic/lifetime/lock/publication invariants and add adversarial coverage where practical.
  • Inventory obsolete APIs, wrappers, fallback/dead paths and duplicate validators with their maintained callers.
  • Migrate callers and delete deprecated contracts/shims in a coherent signed revision graph; reject retired input versions where relevant.
  • Classify each size/count/depth/time bound as ABI, hardware, explicit resource policy or accidental limitation.
  • Test beyond removed boundaries and at allocation/ABI limits while preserving exhaustion errors, denial-of-service controls and bounded waits.
  • Keep every tracked authored code/test/script/workflow file below 1000 physical lines through thematic refactoring.
  • Run the deterministic tracked-source size gate, covering executable fixtures/generators and excluding only genuine non-code data or external payloads.
  • Audit production/test feature and symbol separation, including this repository's effect on rootd test orchestration.
  • Supply changes affecting rootd semantic surface to the maintained same-toolchain baseline; record a justified component-specific applicability result.
  • Check bootstrap ownership and development/release authority parity at this repository's producer/consumer boundary.
  • Use maintained integration#3 profiler evidence before optimizing; preserve live access checks, ownership and success criteria.
  • Audit build/CI inputs, secret handling, private outputs, symlink containment, deletion, subprocess bounds, warnings and host dependencies.
  • meaningful public/private inline documentation, crate/target missing_docs enforcement without blanket allowances or hidden-API escapes, warning-denied private-item rustdoc and an undocumented-public-API negative gate.
  • Validation: Run cargo fmt --all -- --check, strict Clippy, unit/doctests and warning-denied builds/rustdoc for every owned crate/target under default and all valid feature, freestanding/host, SMP and profile combinations; test mutually exclusive combinations separately. Add focused VM regressions for runtime behavior and observe the older catalog and unit tests at the exact published heads.
  • Documentation: update applicable README/ARCHITECTURE/ROADMAP in meta's canonical format and affected technical-manual TeX/API references; keep README evergreen and shared governance byte-identical to meta.
  • Evidence: record exact source/dependency revisions, commands, configurations, real exit status, CI run URLs and results; repeat the audit on final heads and obtain independent review of security closures. No skipped/pending/predecessor result counts as a pass.

Alternatives and tradeoffs

Refactor within the component unless shared semantics justify extracting common code. Preserve regression coverage before deleting superseded paths. Profile before optimizing, and document ABI limits, hardware limits and explicit quotas. Preserve security and reliability requirements.

Detailed scope and contracts

Owned invocation wire contract — 15 September 2026

This v1 contract connects the Kernel's native request/result custody to explicit
userspace peers. It is tracked in kernel #11 and lib-ipc #1.
Shared codecs alone do not establish native execution or realm acceptance.

Registers and ownership

All numbers and packet fields are unsigned. Packet integers are little endian
and require no alignment. RAX selects the syscall; arguments are RDI, RSI, RDX,
R10, R8 and R9 in that order. Unlisted arguments must be zero. Return RAX is an
ordinary IPC result code; RDX carries the operation-specific value below and
R8 is zero. A rejected operation returns zero RDX unless SUBMIT explicitly
reports a retained draining owner. Calls do not retain any userspace pointer.

Number Operation Arguments Successful RDX
0x4C REGISTER local RECV slot zero
0x4D SUBMIT local SEND slot, input pointer, input length invocation ID
0x4E CLAIM local RECV slot, receive pointer, receive length delivery ID
0x4F COMPLETE local RECV slot, delivery ID, input pointer, input length zero
0x50 COLLECT invocation ID, receive pointer, receive length zero
0x51 PROGRESS invocation ID packed progress
0x52 RELEASE invocation ID packed transition
0x53 RELINQUISH delivery ID packed transition

IDs are nonzero opaque numbers, scoped to the actual current process, generation
and CSpace. They never choose a process or grant capability authority. REGISTER
requires an existing generic endpoint. SUBMIT requires SEND and additionally
GRANT for capability inputs. CLAIM and COMPLETE require the exact registered
receiver and actual RECV; capability completion additionally requires GRANT.
RELINQUISH acknowledges only an invalidated delivery owned by that serving
process; it does not require a surviving receiver capability. RELEASE abandons
future collection and starts native retirement, without undoing provider effects.

SUBMIT may return a nonzero failure code AND a nonzero invocation ID: ingress
could not be completed but native disposal remains accounted to that owner.
It cannot subsequently be delivered. The caller must retain that ID for progress
and release. A nonzero code with zero ID is an ordinary rejected submission.
CLAIM/COLLECT return RAX zero after a committed delivery even if subsequent
native disposal is draining; the receive header carries that distinction.
Their rejection leaves the receive packet and destination inventory unchanged.
COMPLETE accepts its result exactly once. Repeated COLLECT is descriptive: no
second capability transfer, and the destination list must be empty.

Packed transition uses bit 0 for draining and bits 32–63 for its nonzero native
code; all other bits are zero. Complete is exactly zero. Packed progress uses
bits 0, 1, 2 and 3 for request delivered, completion accepted, result collected
and draining; bit 4 says a first error is present, with that nonzero code in bits
32–63. All other bits are zero. Draining may have no first error when release
awaits server bookkeeping. Progress flags report history, not new authority.

Input packet

The fixed header is 40 bytes, followed by capability inputs and then payload.
The exact packet size is 40 + 8 * capability_count + payload_bytes.

Offset Width Meaning
0 4 ASCII OIV1
4 2 version, exactly 1
6 2 header size, exactly 40
8 8 payload byte count
16 8 capability count
24 8 maximum result bytes reserved by SUBMIT
32 8 maximum result capabilities reserved by SUBMIT

Each capability input is a four-byte current source slot and four-byte requested
rights. COMPLETE requires both result budgets to be zero. The kernel copies
input bytes and retains actual admitted native bindings before returning; caller
mutation or unmapping after return cannot change the accepted request/result.
Possession, type, attenuation, provenance and lifetime checks remain native.

Receive packet

The fixed header is 64 bytes, then four-byte destination slots, then twelve-byte
receipt capacity, then byte capacity. Its exact size is
64 + 4 * destination_count + 12 * receipt_capacity + byte_capacity.

Offset Width Meaning
0 4 ASCII OIR1
4 2 version, exactly 1
6 2 header size, exactly 64
8 8 byte capacity
16 8 destination count
24 8 receipt capacity
32 8 returned byte count, initially zero
40 8 returned receipt count, initially zero
48 4 attested caller process, initially zero
52 4 attested caller generation, initially zero
56 4 draining code, initially zero
60 4 transition flags, initially zero; only bit 0 is defined

Destination and receipt capacities are distinct to support repeat collection.
First delivery requires enough destinations and receipts for all actual inputs;
only the used destination prefix is validated or populated. Spare destinations
and unused receipt/payload capacity remain unchanged, acquire no authority and
are not returned as evidence. A receipt is destination slot, native capability
type and admitted rights, each four bytes. It describes a committed transfer,
not a transferable capability. CLAIM supplies the retained caller's process and
generation. COLLECT leaves those two fields zero. No caller-supplied identity is
accepted. Output counts must fit capacities; draining requires a nonzero code.

Validation and lifetime

Overflow, size mismatch, noncanonical headers, unsupported versions, nonzero
initial output fields and reserved register inputs reject before native custody
changes. There is no inherited 32 KiB CALL limit. Actual addressability, native
CSpace limits, caller budgets and fallible allocation still constrain admission.
The entire input span must be freshly readable; the entire receive span must be
freshly readable and writable in the current process's actual VSpace. Kernel,
noncanonical, stale, overflowed and partly inaccessible spans reject.

Mapping validation, packet admission, native effects and output publication share
one existing process-lifecycle exclusion interval. All allocation and fallible
output checks precede native delivery. Destination input is snapshotted before
outputs are written. No userspace pointer, borrowed descriptor, receiver-selected
CSpace or ambient allocator/provider authority enters retained custody. Hosted
raw-pointer dispatch is refused; safe codec/object tests and actual CPL3 tests
provide distinct evidence. Existing CALL/REPLY semantics remain unchanged.

Acceptance and rollout

Literal packet fixtures, arithmetic/malformed negatives, complete and draining
returns, spare destinations, repeated collection, exact-owner refusal, revoked
bindings, fresh mapping checks and real CPL3 request/capability round trips must
pass. Existing unit and VM regressions remain mandatory. Producers and consumers
select original signed commit pins after strict validation. Realm lifecycle and
complete in-guest builds remain separate gates. A peek/sizing syscall is avoided
by admitting capacity; numeric identities never bypass native ownership checks.

Shared owned-invocation checkpoint — 15 September 2026: Define owned invocation packet codecs and immediate syscall transport, preserving complete raw custody metadata and the existing hosted transport refusal.

Owned invocation wire and native acceptance — 15 September 2026: Signed Kernel 5f497adaefa526108a0439e0e071717dddb85334, shared IPC de968da19898bef532ddb3b5974bb9562f51dee5, capability ABI a001a26f0eb3aebec3f5fd02a28d98f1bc23f8a0 and Integration 9030b217c490db6ad3ec60a799cb025eccbfcdb1 implement and exercise the immediate owned invocation boundary. Destination capacity and descriptive receipt capacity are independent; spare capacity acquires no authority and repeated collection cannot duplicate transfers. The real three-process CPL3 scenario passes all eight operations, full-span pointer/rights/overflow/reserved-field rejection, actual returned selectors, payload/capability/origin checks, collection after server exit and repeated receipts. A second request rejects premature relinquishment, enters draining on caller release and retires only after the exact server acknowledgment. All 162 maintained Integration helper commands pass; three prior correct concurrent-run lock refusals are retained and their sequential checks pass on unchanged executable inputs. Current full-suite acceptance remains open, as does the intermittent quota cause in Integration issue 18. Reachable backend disposal-failure coverage, broader revocation/generation-reuse scenarios, producer adoption, realm runtime, complete authority/inline-documentation audits and both full EriX-in-EriX build generations remain open.

Typed realm bootstrap installation design — 15 September 2026: The next bootstrap producer step requires validating the actual moved install grant against the intended child before any installation. Add Kernel-control operation 52, INSTALL_WITH_GRANT_FOR_PROCESS, using the existing fixed request/reply envelope: flags and arg3 are zero; arg0 packs grant slot in bits 0..31 and source slot in bits 32..63; arg1 packs child destination slot and exact requested rights; arg2 packs nonzero process ID and nonzero staged generation. Both response values remain zero. The operation is admitted only where grant installation is already allowed (process-control and child-population endpoints, with existing bootstrap control policy preserved). The held unique grant remains the authority; the supplied process/generation pair is an additional equality constraint, never a target-selection grant. Revalidate exact native grant binding, GRANT possession, child/staged identity and current staged liveness, slot and type/rights ceilings, actual source binding and empty destination before transfer. Unlike legacy zero-means-inherit installation, this operation always uses the exact supplied rights, including zero. Reject nonzero reserved input and zero identities deterministically; mismatched target identity must produce no installed alias or new revocation lineage. Keep old producer semantics unchanged until explicitly migrated. Share the native installation implementation and split the existing near-1000-line control dispatcher by responsibility. Tests must use actual moved install grants for distinct staged children, wrong/stale generations, occupied destinations, explicit zero rights, invalid fields, denied endpoint policy, preserved source/grant custody and native lifetime/revocation behavior. Connect the new checked operation to typed Procd bootstrap provisioning; a standalone scalar codec or host-only table is not realm runtime acceptance. Complete receiver readiness, setup-authority disposal, fair terminal/provider scheduling, two-realm byte I/O and both full guest builds remain required.

Process-bound native acceptance — 15 September 2026: Signed Kernel 60da5858d7198185efd103f0e91e5ac2e0b63e67 implements control operation 52, checking the actual moved install grant against expected process/generation with exact rights, including zero, under existing endpoint policies. Signed Procd f1105706cc19ed024a6cca79a29abc57c90c6661 uses this operation in its actual ordinary launch-description producer while retaining the narrow SEND receipt, pending state and exact failure cleanup. All 162 Integration helpers pass after updating the exact policy assertion to require the new marker; its initial mismatch remains recorded. Typed realm bootstrap, mediator startup/readiness/configuration/seal, complete consumer image adoption, fair terminal/provider retirement, broader native disposal failures and both full EriX-in-EriX build generations remain open. The new inventory covers 76 repositories, 2,950 code files below 1,000 lines and 158 direct missing_docs crate-root gates; complete inline documentation and whole-codebase authority closure remain open.

The mediator class cannot use ordinary start, immediate commit, TTY provisioning, powerbox installation or automatic restart. Procd has forty native binary builds and six new mediator refusal/cleanup regressions. No Posixd executable or coordinated realm VM acceptance is claimed. Actual grant-return provisioning, authenticated caller ownership, typed startup memory/inventory, readiness, configuration/seal, client I/O, fair retirement, complete consumer image adoption and both full guest build generations remain open.

Native bootstrap destination correction — 15 September 2026

The temporary endpoint destination is now child-local slot 4, after the mandatory CSpace, VSpace and TCB roots in slots 1–3. This proves the constructor boundary; coordinated mediator startup, seal, client I/O, retirement and full guest builds remain open.

Actual grant-return provisioning, authenticated receiver readiness, configuration/seal, client I/O, fair retirement, whole-codebase authority/documentation closure and both complete guest build generations remain required. No runnable Posixd realm or guest-build acceptance is claimed.

Native producer/consumer migration, matching VM execution and full guest builds remain separate acceptance gates.

The existing held Process or Root route remains
required; descriptive identities do not grant authority.

An absent or different generation acknowledges absence of only the requested
instance, with zero response values; it cannot mutate a replacement.

Required evidence includes exact wire and reserved-field controls, actual-object
generation/reuse and failed-release controls, consumer cleanup tests, and bounded
CPL3 native coverage. Ordinary mediator start, whole-image
admission and both complete builds inside EriX remain separate open gates.

Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain separate open acceptance requirements.

The native pending caller must match a retained running
Launchd generation. The actual sole receipt must be INSTALL_GRANT with exactly
GRANT|MINT. Previously guarded, started, stale,
ordinary-role and malformed stages refuse before new effects.

Use the real returned grant and native
operation 53 to narrow the Created child's primary endpoint to RECV. Establish
an ancestor SEND branch under Kernel lifetime custody and a distinct nested
explicit revoker before any export.

Lost reply, rollback, abort, supervisor loss and terminal
cleanup must account for every reused scratch column, actual guard and exact
child identity.

Counted final receivers/configuration,
owned fair intake/provider/retirement progress, private execution, authenticated
readiness, initial receiver disposal, seal/publication, real two-realm client I/O
and both complete builds inside EriX remain required. Host models or this guarded
stage acknowledgment cannot substitute for those acceptance gates.

Native consumer and producer adoption remains open. Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain separate open acceptance requirements.

No grant is constructed, copied, attenuated or retargeted. Malformed register shape rejects before context lookup; caller/window checks precede source lookup, then type/binding checks precede empty-destination admission. Ordinary validation refusal leaves inventory unchanged. Literal register, foreign/terminal caller, missing/fake binding, occupied destination, exact-rights/scope and actual CPL3 controls are required, followed by coordinated producer/consumer adoption and the remaining realm VM gates.

Literal selector and hosted refusal controls pass. Signed Kernel 56d398e0 passes both actual native VMs, including thirty-nine new CPL3 relocation controls; service consumer adoption remains open. Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain separate open acceptance requirements.

Owned receiver request-budget contract — 18 September 2026: Extend register-only REGISTER (0x4C) to take the actual local RECV slot, maximum request payload bytes and maximum request capability count in arguments 0–2; arguments 3–5 remain zero and successful RDX is zero. The byte/slot/receipt receive layout must be addressable and capability capacity must fit native private CSpace storage. The actual Running generation and held generic RECV endpoint remain the registration authority. SUBMIT compares actual payload length and capability count against that exact registration before request allocation, private-space reservation, native transfer or invocation serial acceptance. These budgets describe service-owned receiving storage; they add no global CALL-size ceiling, user-pointer retention, foreign selector or capability grant. Literal malformed/zero/exact registration controls, rejected-inventory checks, actual CPL3 calls and existing VM oracles are required. Actual consumer VMs, complete fair realm progress and both full guest builds remain open acceptance requirements.

The shared RequestBudget and REGISTER shim require explicit byte and capability limits. Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain separate open acceptance requirements.

Existing launch-description staging may be reused only with explicit exclusive ownership and proved completion of its former cleanup; add no broad Process authority or per-realm scratch column. Numeric identity or receipt metadata never replaces actual possession or scope validation.

The running service loop must give native retirement a turn before owned bootstrap and ordinary intake. Complete every independent local and child retirement action before relinquishing bookkeeping; uncertain cleanup cannot return a service to ordinary work.

Success requires a canonical correlated result, actual source-grant absence and complete invocation retirement. Preserve ordinary start refusal until realm configuration, readiness and sealing are complete.

Acceptance requires adversarial ownership/cancellation/partial-cleanup host controls, strict coordinated builds and real producer/consumer VM execution.

The bootstrap request now carries only request/opcode/process/generation in exactly 16 bytes; removed source/destination selectors and the old 32-byte request are rejected. Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain separate open acceptance requirements.

Both are nonzero only for the realm mediator role; both must be zero for every other role. Reject the obsolete 56-byte shape.

The pair describes delegated lifecycle responsibility; numbers alone never confer creation, installation or rollback authority. Guard admission must match the original supervisor, never replace it with a later claimant.

Caller RELEASE initiates cancellation and must precede any ordinary abort request that could wait behind Procd delivery retirement.

Actual Launchd runtime preparation and scheduler adoption, deployment-sized ownership storage, adversarial host controls and real producer/consumer VM execution remain required.

Materialization begin is exactly 64 bytes, with two full-width original supervisor words required for mediators and forbidden for other roles. Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain separate open acceptance requirements.

Client numeric identities or a bearer sender cannot select ownership.

The request carries exactly one actual SEND-only directory endpoint to
the reserved receipt slot. Verify the original caller/job/session/authority realm
again and retire every unretained received capability on refusal. Never imply a Posixd pathname,
Named route, root, cwd, TTY stream, ordinary job or public PreparedProcess input.

They require the same original
Running native owner. READ observes retained state only; ABORT must complete
independent source, invocation and exact-child retirement before its successful
acknowledgment.

Success at BEGIN
requires Reserved, a nonzero complete handle and receipt slot. PREPARE success
requires Guarded; ABORT success requires Retired. READ returns an authenticated
nonzero state.

Require an
explicit deployment value: zero disables new realm reservations, and nonzero
values allocate that many retained records and disjoint receipt slots. Coordinate shared startup codecs, Rootd payloads, Launchd arena and
Integration policy/packaging; old version/width must reject.

Actual scheduler progress must exclude ordinary and indirect blocking
peer calls while any native invocation needs progress. A permanently discharged
source slot is never revisited after reuse. Guarded staging remains private
and unstarted, without exported SEND or a Running job.

Coordinated host negatives, strict source-bound build matrices and real consumer
VM execution are required. Two mediator processes, two clients per realm with
actual mediated I/O, complete fair progress, source/effect/frame admission and
both full builds inside EriX remain separate open acceptance requirements.

Exact UTF-8 selectors borrow input without an extra pathname ceiling; full generational handles and cap-free responses require independent correlation. Descriptions confer no authority. Actual admission dispatch, coordinated consumer VMs, runnable mediators and both full builds inside EriX remain separate open acceptance requirements.

Tracking and rollout

Original FAT/exFAT directory observations and the fixed-root scanner repair are signed and published: lib-ipc bebb7a74, fatd a5481166, docs 18270dc3, integration 26a98467. The independent Integration helper b0255273 precedes final catalogs. The coherent closure contains 56 signed commits across 55 repositories, 206 Cargo selectors and 111 catalog selectors, with exact remote branch equality retained.

Fatd observes directories through original live acquisition/root custody and actual retained dot parents. Physical slot positions preserve full-width input comparison. One admitted continuation per counted handle can skip previously parsed directory content; other seeks prove logical end and whole-name boundaries from the beginning. Layout mutations invalidate all mount aliases before effects, including exact-entry mutations and touch-created files. No cursor, cluster or handle becomes an inode identity. FAT/exFAT identities and unsupported POSIX metadata remain explicitly unavailable. Complete output capacity precedes optional atime writes; uncertain nontransactional publication retains fail-stop without a retryable refusal. End replay performs no media I/O. Shared scanning excludes fixed-root final-sector padding, resolving Fatd #5.

The complete status and seekable-directory feature remains open. Native wire contracts and scoped Vfsd mediation remain accepted. Complete provider POSIX metadata, compatibility stat families, shared readdir/tell/seek/rewind and remaining full-feature controls/publication are unfinished. Current accounting remains 17.96% weighted and 6.41% whole acceptance: 24/460 parents and 456/921 sub-items under 162 decomposed parents. This provider implementation closes no additional full sub-item.

Both complete EriX guest-build generations and rebuilding external Rust/LLVM inside EriX remain required and unperformed.

Fatd directory contract, shared observation contract, descriptor/namespace feature, Phase 6 master. Reviews: lib-ipc, fatd, docs, integration.

Client scratch-column clarification — 25 September 2026: the original five-column design is implemented with C0 master, C1 receiver, C2 installer, C3 outer revoker and C4 temporary SEND. After independent master disposal, derive outer SEND into C0 and bind C3 into actual Procd lifetime; drop/query C4, derive inner SEND into C3 and inner revoker into C4, then drop/query C0. Begin retains C1 RECV, C2 GRANT, C3 SEND and C4 MANAGE. The authenticated first descriptor step follows Launchd’s original Begin RELEASE and drops/queries C1. Commit installs C3 into child slot5, drops/queries C3 and consumes/queries C2 through exact child-lifetime binding. Running custody retains C4; retirement visits C4 first. No sixth column or additional authority is added. Procd's contract describes source, recipient, rights and failure custody.

Complete client lifecycle codecs — 25 September 2026: signed Lib-IPC 461634ed8981908b65bc84b94a774c309e371678 implements the published public configuration/client operations, private streamed client startup and distinct never-started disposal messages. Original identities, counts, operation-specific states and full digest correlation are checked; plan storage must fit the target allocation domain. These codecs establish framing, not native execution acceptance.

Detailed scope and contracts

Counted realm client admission and lifecycle contract

Reviewed shared design, 25 September 2026. This supersedes the earlier
private client-provisioning inventory wherever its wording differs. It completes the proposed
public Launchd and private Procd frames before shared implementation. It changes
no maintained source and claims no runtime or VM acceptance. Integer fields are
little-endian; all complete decoders reject missing/surplus bytes and unknown
selectors. Every encoder preflights the complete shape before changing output.

Existing source and authority boundary

lib-ipc/src/ids/realm_admission.rs assigns only 0x6D0..0x6D4. The current
Launchd RealmOwner authenticates the actual pending native caller against its
original published Running job, process generation, session and authority realm.
Every operation below repeats that proof and matches the complete original
realm handle. No public request contains a native child, mediator, supervisor,
controller, CSpace, install-grant or endpoint-object identity.

Client handles are descriptive nonzero realm-local (id, generation) u64 pairs.
Generations never wrap, and replacement rows never inherit an old generation.
Only actual retained Loaderd/Procd results supply native pairs in RCF/RCS/private
actions. The existing original-parent-loss sweep must cover every new owner.

Public requests/replies have zero capabilities except PrepareClient's exactly
one actual directory SEND COPY. Its destination is reserved by BeginClient; it
is not chosen by request metadata. Malformed, surplus or refused receipts remain
owned and are independently exhausted, including after the first cleanup error.
Unique InstallGrant/RevocationGrant MOVE semantics remain unchanged.

Public Launchd operation allocation and exact fields

The common realm prefix is request_id u32@0, op_id u32@4, realm_id u64@8 and
realm_generation u64@16 (24 bytes). IDs/generations and request_id are nonzero.
The client prefix appends client_id u64@24 and client_generation u64@32 (40).
These layouts preserve the existing realm handle convention.

Selector Operation Request bytes Successful reply
0x6D5 BeginRealmConfiguration 72 realm40, Configuring=8
0x6D6 BeginRealmClient 24 client64, Reserved=1
0x6D7 PrepareRealmClient 64 + selector bytes client64, Guarded=3
0x6D8 AppendRealmConfiguration 48 or 64 realm40, Configuring=8
0x6D9 FreezeRealmConfiguration 24 realm40, Configured=9
0x6DA SealRealm 24 realm40, Sealed=11
0x6DB StartRealmClient 40 client64, Started=7
0x6DC ReadRealmClient 40 client64, exact retained state
0x6DD RetireRealmClient 40 client64, Retired=10

BeginConfiguration72 appends C/D/H/Q u64@24/32/40/48 and mediator request/result
payload budgets u64@56/64. All four counts are positive (disabled bootstrap has
no configuration). Use the existing counted-arena checks, including exact plan
length 96 + 32*C + 24*D + 16*H, representable counts/packet extents and enabled
mediator minima 112/200. It reserves C actual client rows, their capability
columns and the complete canonical-plan byte extent from explicitly supplied
storage before any client authority is admitted. Q is the later mediator ring
extent, not a new Launchd allocation. Reject insufficient storage with explicit
RESOURCE_EXHAUSTED before mutation; reserve atomically. Admission requires this
original mediator to be Guarded and no prior configuration to be in progress.

BeginClient24 names only the realm. It allocates one of that reservation's C
client records and returns the new handle plus its exact empty scope destination.
The C records are the declared membership of this immutable configuration, not
an additional protocol ceiling. No native CREATE occurs during reservation.
This is one initial client set: a retired member's outcome is retained and that
record cannot be silently replaced before or after freeze. If a member retires
before the complete initial set can be frozen, the caller retires this realm and
may reserve a fresh generation/configuration. Later dynamic process spawning is
a separate protocol; no such behavior is claimed for this initial configuration.

PrepareClient appends client request/result budgets u64@40/48, selector byte
length u64@56 and nonempty UTF-8, NUL-free selector bytes@64. Minimum client
budgets are 40/32; checked length arithmetic introduces no new path/count cap.
The actual implementation reports exhaustion for unavailable declared scratch
or existing provider limits, rather than truncating. Require Reserved state and
one actual SEND-only directory receipt in its previously reserved slot. Resolve
the exact executable through this scope; independently dispose the scope before
private Loaderd preparation. Retain exact private materialization, returned
grant and original child cleanup before interpreting subsequent failures.
Success means the original client is guarded/unstarted, with its zero-right
slot4 and install-grant custody retained; it does not install RCS1 or start I/O.

AppendConfiguration appends one global ordinal u64@24 followed by one record@32:

Ordinal interval Public record Whole request
[0,C) client_id u64@0, client_generation u64@8 48
[C,C+D) client_id u64@0, client_generation u64@8, fd i32@16, access u32@20, channel_index u64@24 64
[C+D,C+D+H) channel_index u64@0, capacity u64@8 48

Record kind derives only from the retained counts and ordinal; no standalone
48-byte parse may claim it distinguished client/channel data. Provide a
structural frame plus parse_with_counts or equivalent typed counted admission.
Only the next ordinal is admitted; skipped/replayed/surplus records reject
without effects. Client order is the caller's declared order, not identity sort
order. Resolve full owned public handles to original Guarded native pairs and
canonical indices. Descriptors use nonnegative fd, access Read=1 or Write=2 and
channel index < H; channels are canonical index order with nonzero capacity.
Checked capacity sum must equal Q. All C clients must appear exactly once;
native/public pairs and (client,fd) are unique; every client/channel has a
binding. Retain incremental failures and full final validation before freezing.
All record bytes are copied to owned storage before the immediate packet is
reused. Public request_id is correlation, not cross-invocation deduplication.

Freeze24 requires exactly C+D+H admitted records, complete uniqueness/coverage,
exact channel-byte sum, all original client stages and zero uncertain custody.
It generates native identity fields exclusively from those owners, encodes the
existing exact RCF1 plan, hashes all its bytes, and makes plan membership/order,
budgets and digest immutable. There is no public plan digest or native identity
nomination. Refusal cannot replace partially retained resources or another plan.

Existing START 0x6D4 remains 40 bytes and returns PrivateReady=7. For a configured
realm it requires Configured, and both supplied budgets must equal the reserved
plan's budgets. It provisions the mediator, learns actual Procd context,
provisions/commits every client's RCS startup while all clients remain stopped,
and starts the mediator with its configuration service. Bootstrap-only behavior
and its minimum96 budgets remain unchanged. PrivateReady is not Sealed.

Seal24 requires that configured original realm, advances existing authenticated
Probe/Prepared and Commit/Sealed with independent caller/delivery/source disposal,
and returns Sealed only after both sides' original owners retire. While pending,
ReadRealm may report the added Sealing=10 state. Client Start requires Sealed,
the original provisioned client and all applicable setup/caller retirement.
Started acknowledges exact native START; it makes no liveness guarantee and
does not invent a client Ready/Challenge. ReadClient reports later actual state.

Replies, states, errors and outcome custody

The existing realm reply40 is unchanged: request/op/result/state u32@0/4/8/12,
realm_id/generation u64@16/24, scope_receipt_slot u32@32, reserved-zero u32@36.
All new realm operations require slot0 and their exact successful state; Read
recognizes added states. A refusal preserves raw nonzero result, Unconfirmed=0
and full requested realm handle. Helpers compare original request/op/full handle.

Client reply64 is request/op/result/state u32@0/4/8/12, realm_id/generation
u64@16/24, client_id/generation u64@32/40, scope_receipt_slot u32@48,
terminal_kind u32@52, terminal_status u32@56 and reserved-zero u32@60.

Client states are Unconfirmed=0, Reserved=1, Preparing=2, Guarded=3,
Provisioning=4, Provisioned=5, Starting=6, Started=7, Terminal=8, Retiring=9,
Retired=10. Only successful BeginClient has nonzero scope slot. Failed Begin
echoes the full realm but zeroes the client pair; all later replies echo the full
original client pair. Failures use Unconfirmed and zero slot/kind/status; they
never claim cleanup. Operation-specific success matching prevents substitution.

Read/Retire can carry kind1 Exited or kind2 Killed with every u32 status bit
preserved, exclusively from the original authenticated Procd observation.
States other than Terminal/Retiring/Retired require zero kind/status. Terminal
requires kind1/2. Retiring
may retain an already observed event; Retired may echo it, or kind/status0 for
positively established never-started disposal. Zero is not implicit Exited(0).
Begin/Prepare/Start acknowledgements carry no terminal fields; a process that
exits immediately after START is observed through Read. Numeric metadata never
changes the native event's original process generation internally.

Retire is valid for every admitted client phase, selecting only that exact
retained record. Its successful acknowledgement requires all applicable mediator
binding disposal, actual native child and capability-lineage retirement, resolved
native caller/delivery owners, and retained then acknowledged final CPU accounting.
An actual native terminal observation precedes a kind5 notification; proven
never-started native destruction precedes a kind7 notification. No ordered list
of completion gates substitutes for either required producer proof.
Unknown cleanup remains owned; NOT_FOUND alone proves no prior disposal.
An unstarted child uses the distinct authenticated disposal notification below.
An uncertain START cannot use the never-started shortcut.

Keep client outcome records in their counted reservation until realm retirement,
so Read remains useful after individual Retire. No extra public ACK operation is
needed. Public COMPLETE transfers an immutable cap-free scalar result to the
original caller-owned invocation; it does not prove that caller RELEASE occurred.
The caller collects/validates then retires that owner before its dependent next
step. No result points into a subsequently reused row. Realm/global row reuse
requires all actual resource/caller/serving owners retired and preserves every
nonwrapping generation. A caller that discards an unknown result cannot treat a
fresh NOT_FOUND response as proof its old operation completed.

Use existing full-width status meanings: INVALID_ARGUMENT for malformed scalar
or count shape; DENIED for wrong actual origin or receipt authority; NOT_FOUND
for no matching original handle; CONFLICT for incompatible retained transition;
BUSY/RETRY for explicitly pending resource/operation progress; RESOURCE_EXHAUSTED
for supplied storage; INTERNAL for malformed native evidence. Failed mutation
does not erase prior effects; no accepted native invocation is blindly replayed.

Remaining private Procd operations

The published BeginClient88 0x43C and LoaderClient340/176 0x655 remain unchanged.
The generic Begin64 rejects client role0x449; generic STOP remains unavailable.

Selector Operation Request/reply Successful disposition
0x43D BeginClientProvision 96/176 ClientProvisioning=6
0x43E AppendClientDescriptor 88/72 ClientProvisioning=6
0x43F CommitClientProvision 64/72 existing Provisioned=1
0x440 StartClient 64/72 existing Started=2, native START only
0x441 RetireClient 64/72 existing Retired=3

Begin96: request/op u32@0/4; client process/generation u32@8/12; realm pair
u64@16/24; mediator process/generation u32@32/36; client request/result budgets
u64@40/48; Dclient u64@56; plan SHA256@64..96. Require Dclient>0 and40/32 minima,
original actual Launchd, exact retained client/mediator relation and the
mediator's retained plan/controller context. Input is one exact GRANT-only
InstallGrant MOVE. Reply176 is request/op/result/disposition prefix16 plus the
producer-selected RCS1 header160 and one exact RECV-only Generic endpoint COPY.
Failure has Unconfirmed, zero160 tail and zero result capabilities. Correlation
checks every request-supplied RCS field; actual controller additionally matches
the original ContextProbe. A distinct header-prefix/count API must not claim the
absent descriptor records were parsed or globally validated.

Append88: request/op/client pair/realm pair prefix32, plan SHA256@32..64,
ordinal u64@64 and descriptor16@72 (fd i32, access u32, reserved u64zero).
Only next ordinal is admitted. Existing action reply72 compares complete
request/op/client/realm/plan; the caller retains original ordinal through
retirement. Commit/Start/Retire reuse action64/72 and exact per-selector success
matching. Commit and Start use the complete RCS startup digest; Retire alone
permits zero as unknown-startup sentinel, omitting only digest correlation.
Retire covers Begin never claimed, malformed/uncertain Begin, partial descriptors,
Commit failure and post-start. AbortStaged is only a known pre-Begin fallback.

Commit requires exactly Dclient records and complete header-plus-record hash,
final RO/NX startup and RW/NX packet mappings, guarded SEND installation at
client slot5, lifetime custody, and original Procd RECV source drop plus separate
query proving absence. These are actual gates, not deferred prose obligations.
Client slot4 remains zero-right; ordinary client messages transfer no caps.
Complete startup extents, packet arithmetic, page rounding and native CSpace
capacity are checked before backing/transfer effects. No implicit producer cap.

The Begin receiver COPY does not consume its source. Launchd must collect,
validate/census its actual receipt and retire the original Begin caller before
Append. That next authenticated original request acknowledges the sequencing
boundary; COMPLETE alone cannot report peer RELEASE. Procd then drops and
independently queries its original RECV source before Commit succeeds. Launchd
retains its copied receiver through RCP transfer, mediator Prepared and its own
original delivery retirement, then drops/queries it before seal. All uncertain
original/prospective ownership is retained across refusal and cancellation.

Existing five Procd columns can implement client custody without new authority:
master/grant/RECV/ancestor-SEND/ancestor-revoker, then only after acknowledged
master/ancestor-revoker disposal reuse their columns for inner revoker/SEND.
Inner revocation remains retained, outer lineage binds actual Procd lifetime.
This allocation must be verified by native effects and query evidence, not
inferred from numeric slot descriptions. Cleanup visits the inner revoker first.

Procd validates scalar records, ordinal/count and full incremental startup hash.
It must not claim arbitrary-order fd uniqueness without counted scratch. Launchd
validates complete RCF; Posixd validates actual collected rows; the client parses
complete RCS1 and validates descriptor uniqueness before I/O. Preserve caller
sequence; do not add a sorted-fd restriction. Existing final CPU READ32 0x437,
ACK64 0x438 and response64 cover clients after actual relation/origin admission;
their scalar codecs remain role-neutral and preserve exact-generation snapshots.

Distinct unstarted-client disposal control

Extend RSC1 with ClientDisposed=7 / ClientDisposedAck=8, each exactly112 bytes.
Keep existing header/context/plan offsets: request_id u64@16, context40@24,
plan digest32@64. Append original client process/generation u32@96/100 and
reserved-zero u32@104/108. Use a distinct typed disposal payload; do not create a
ProcessTerminalEvent with kind0. Existing kinds5/6 still require actual Exited or
Killed and preserve every status bit. Requests result0; replies preserve raw
nonzero refusal. All request/op/context/digest/client fields correlate exactly.

Only the actual retained Procd controller may submit disposal, after proving
exact never-started child destruction and required native cleanup. Scalar parsing
does not grant that authority. Posixd closes the exact client's bindings once,
decrements channel references once, and independently retires its receiver and
pending delivery before success. It can admit this before or after seal once
the original row exists. If configuration is in flight, retain the original
obligation and prevent later client-row admission from resurrecting it; wait for
the matching retained row or cancel/clean the affected configuration. Absence or
an unregistered receiver is not a successful disposal acknowledgement. Uncertain
START uses exact running termination/native event custody, never this shortcut.

Explicit Launchd deployment storage successor

Current lib-bootstrap/src/payload_launch.rs is LCH1 version3,72 bytes, with
realm_capacity u32@68 and four columns per realm. It cannot describe the new
client rows or canonical-plan pool. Define LCH1 version4,88 bytes, preserving
all preceding offsets and appending realm_client_capacity u64@72 and
realm_plan_byte_capacity u64@80. Both zero explicitly disable configured clients
while preserving bootstrap-only realms; enabled mode requires both positive and
realm_capacity>0. Reject mixed zero, legacy version/width and unknown extensions;
do not reinterpret old reserved bytes or supply implicit defaults.

Reserve actual non-Copy client rows by the compiled target layout and a separate
counted byte pool for exact canonical plans. Two disjoint columns per client:
scope/grant column reused only after scope query-absence and original callers
retire, plus distinct prospective ingress-RECV destination. The original grant
MOVE and receiver COPY can therefore overlap without slot alias. Never borrow
ordinary intent/manifest bytes or a new endpoint/VSpace/factory capability.
Existing shared exact-executable scratch remains serialized by its owned gate.

Update checked startup geometry, native target arena sizing/layout transcript,
capability interval validation and Integration's deployment config/graph/image
producers together. Required columns include old job/stream/realm terms plus
checked 2*realm_client_capacity; every interval fits the actual declared
window. Counts are constrained by supplied resources and checked addressing,
not a hidden protocol maximum. Plan allocations and row reservations are retained
until full realm teardown, and exhaustion must not steal another realm's rows.

Intake budgets, witness and required controls

Public native intake must retain a complete PrepareClient prefix plus the actual
selector, one prospective directory receipt, and reply64; other public frames
need at most72 request/64 reply with no caps. Use actual supplied packet/scratch
capacity and explicit exhaustion, not a new selector constant. Private Loaderd
needs340/176 and its original grant receipt; Procd needs max112 request/320 reply
for counted mediator Provision and new Begin96/reply176 with one grant/RECV;
RCP needs112 request/200 maxreply with client-only oneRECV; RSC needs112/112,
ordinary client I/O uses explicit >=40/32 and zero caps. Audit both native
registration budgets and packet/receive layouts; a codec size alone is not proof.

Use a dedicated small native realm-byte-client binary in the Posixd package,
consuming only RCS1 and slot5 ordinary byte IPC. No new crate, shell startup,
clock/log/TTY/filesystem/completion authority is needed. Exsh remains the
orchestrator using public owned handles, ReadClient and exact exit outcomes.
Descriptor numbers distinguish deterministic reciprocal roles without argv.
The witness has two realms, two clients and two channels per realm, four total
descriptor bindings per realm, small explicit rings forcing short progress,
independent realm-B traffic after realm-A retirement and exact stale/cross-origin
refusals. Do not put a foreign SEND into an ordinary client for a negative test.

Required host controls: all exact offsets/lengths/count overflow, preserving
output, public handle/op substitution, no native nomination, wrong actual parent,
receipt surplus/prospective custody, skipped/replayed ordinal and wrong record
kind/length, unsorted valid client/fd sequence, uniqueness/coverage/channel sum,
late count/byte exhaustion with no effects, immutable plan, START budget mismatch,
pre-seal client START refusal, full-width terminal status, original outcome after
Retire, lost public/native result, pending disposal before row admission,
uncertain START refusing unstarted shortcut, source drop/query failures, all
generation reuse and full final CPU ownership. Native validation must cover
COPY/source retirement, two-sided seal, real four-client byte progress, exact
terminal/disposal forwarding and repeated cleanup. All remain acceptance work.

Implementation footprint and remaining review boundary

Shared IPC adds thematic public client/configuration modules and focused tests,
private provisioning/header-prefix helpers and exact action/disposition updates,
plus the distinct disposal payload. Bootstrap adds only the explicit v4 storage
successor and geometry controls. Loaderd already has published private client
selection; Procd and Launchd implement retained custody from the exact originals.
Posixd adds disposal control and its dedicated fixture binary; Integration adds
only opt-in packaging/alias/graph/config/scenario support and target geometry.

The two-column Launchd/five-column Procd assignments require actual native proof
in consumer tests; their arithmetic is not such proof. Public Read retention
requires actual final outcome ownership and must not be faked by current PID
lookup. Counted pool allocation and generation preservation need meaningful
reuse tests. These are implementation/validation duties, not additional unnamed
wire operations or accepted behavior.

Full original realm/mediator correlation is preserved before native creation; legacy Begin64 rejects the private client class. Native execution acceptance remains open.

Private client materialization contract — 24 September 2026: the existing materialization-begin frame carries only the supervisor pair. Role recognition alone cannot bind an actual client to its intended mediator before native creation. Use distinct private operations with explicit descriptive correlation, authenticated through the existing Loaderd and Launchd routes; no new capability or ordinary-launch fallback is introduced.

Loader PREPARE_REALM_CLIENT (0x655) is exactly 340 bytes: retain the existing 316-byte exact-executable selection offsets, then realm ID/generation u64 at 316/324 and native mediator process/generation u32 at 332/336. Its distinct 176-byte reply retains the existing 152-byte result/grant/digest fields, then echoes the complete relation at 152/160/168/172 on both success and refusal. Existing failure-zero rules still apply to staged/grant IDs and digest evidence. The old 316/152-byte parsers reject this selector. The exact executable SEND retains COPY semantics and independent source disposal; the staged install grant retains MOVE semantics.

Procd BEGIN_REALM_CLIENT_MATERIALIZATION (0x43C) is exactly 88 bytes: existing 64-byte begin field offsets, then realm ID/generation at 64/72 and native mediator process/generation at 80/84. Require private role 0x449, the original nonzero Launchd pair, and nonzero relation scalars. Generic Begin64 must reject role 0x449; mediator Begin64 remains unchanged. The existing 36-byte noncommit reply recognizes the new selector and echoes request, operation and original transaction, with zero materialization and staged IDs. Encoding preflights the complete request; neither decoding nor scalar correlation authenticates the native origin.

Before client CREATE, Procd authenticates actual Loaderd and the retained running Launchd, resolves the exact original Guarded and unstarted mediator, and checks the same supervisor. Because the final plan digest includes actual client generations, the first admitted client request may bind a previously unbound mediator to that realm pair before creation. Retain this first binding even if client creation later fails. All later client requests and counted Provision must match it. Reject the same realm pair on any other retained mediator belonging to that supervisor, including retirement or uncertain cleanup. Bootstrap-only Provision can still perform the first binding when there are no clients. Preserve the actual parent/mediator/client relationship through active materialization, staged commit, rollback and terminal custody; numeric realm metadata grants no authority.

Client startup, ingress installation, complete configuration, authenticated seal, source disposal and native caller retirement remain separate gates. Clients cannot start until committed seal and its caller retirement are proved. The required two-realm/four-client byte-I/O and cross-realm refusal witness remains open. This is the implementation contract; it adds no native or phase acceptance.

Actual producer/consumer adoption and the native configuration/seal/client-I/O witness remain open.

Wire precision for configuration and seal — 24 September 2026:

RCP1 version1.0 uses Pull=1 and Reply=2. Its 96-byte common header
is magic/version at0/4/6, kind u16 at8, zero flags u16 at10, raw result
u32 at12, nonzero request u64 at16, complete realm context at24..64 and
configuration SHA-256 at64..96. Requests require result0 and add ordinal
u64 at96 plus reserved0 u64 at104. Replies echo ordinal at96. The validated
plan counts and ordinal determine the one allowed record kind and exact length;
payload length alone never selects policy or capability count. Preserve declared
client and descriptor record order; require unique public/native client pairs
and unique client/descriptor bindings without imposing numeric identity order.

RCS1 version1.0 has the160-byte header already specified: magic/version
at0/4/6, header size/flags at8/12, total bytes16, realm pair24/32, native
client40/44, mediator48/52, Procd56/60, CSpace count64, ingress slot72,
zero-right placeholder slot76, request/result bytes80/88, workspace
address/length96/104, configuration digest112..144, descriptor count144
and reserved0 u64 at152. It fixes the intended SEND at slot5 and the
zero-right placeholder at4. At least one initial binding is required, matching
the plan's coverage rule. Request/result minima are40/32 bytes, derived from
the actual Read/empty-Write request and QueryAbi/Write/error reply framing.
These minima guarantee framing only. The count and every packet/mapping extent
are checked; the consumer independently verifies actual mapping, rights and
inventory. Descriptor records preserve plan order and contain no duplicate fd.

RSC1 version1.0 shares the96-byte common header offsets above with its own
magic and kinds SealProbe=1, Prepared=2, SealCommit=3, Sealed=4,
ClientTerminal=5 and ClientTerminalAck=6. Request results are zero; replies
retain raw application result words. The first four kinds are exactly96 bytes.
Both terminal request and acknowledgement are exactly112 bytes: original native
client process/generation at96/100, native terminal kind/status at104/108.
Only the existing Exited/Killed terminal kinds are valid; all32 status bits are
preserved. Acknowledgements echo the entire terminal description even on refusal.
All replies correlate exact kind, request, context, digest and optional terminal
description. Descriptive decoding does not authenticate Procd or prove cleanup.

Private Procd PrepareSeal and CommitSeal use operation selectors0x439/0x43A
with the existing64/72-byte action framing. Their digest is the canonical
configuration digest, with all bit patterns valid; there is no unknown-digest
sentinel for these operations. Successful dispositions Prepared=4/Sealed=5 are
operation-specific; every refusal uses Unconfirmed=0. Start and Retire retain
their existing startup-digest semantics. REALM_CLIENT is the distinct0x449
process class and cannot enter ordinary launch/start/restart policy.

Canonical record indices need not equal physical runtime row positions. Before
serving, Posixd may move whole owned client rows while retaining each canonical
client index, check public/native pair uniqueness by sorting, then use native-pair
order for lookup. Each move retains all receiver custody. Descriptor references
use canonical indices; result regions are assigned after the final order and
before any delivery or I/O effect. No sorting is permitted during serving.
This avoids new arena allocation and repeated quadratic validation in the I/O
path. Configuration must still prove all uniqueness, binding and channel-coverage
invariants before admission. No runtime acceptance is asserted by these codecs.

Counted realm codecs — 24 September 2026: signed Lib-IPC ef30dcca67f43e8491e30cca7e62fab0c60e1681 adds strict counted arena geometry, RBS1 minor1, the Provision successor, authenticated-layout binding framing and repeatable final-accounting READ/ACK framing. It separates absolute address bounds from slice-length bounds, preserves complete counts/digest correlation and rejects retired layouts.

Signed Lib-PosixABI eb00744d7811bb1174a1cfc34cfe062724dfd8e2 supplies the capability-free 1.1 Read/Write/Close codec. Four strict local configurations each pass 83 unit/integration tests and three doctests; GCC/Clang C checks pass. Original CI19/20 now passes with four complete logs, 112,014 bytes and zero warnings or failures. Byte-I/O review remains WIP. Docs 69840bd8ca4aaea2a098d5d85cbea2d5614f7067 and original CI1069/1070 pass the 45 manual controls and full 2,499-page manual, with zero final warnings.

These are library and documentation checkpoints. The accepted native startup still uses its previously recorded revision graph. Counted configuration, seal, actual client byte I/O and final-accounting consumer adoption require the next coherent graph and new native evidence; no runtime or whole-phase acceptance is added. Full EriX builds and an external Rust/LLVM rebuild inside EriX remain required and unproved.

Configuration opcode documentation correction.
Signed d4d32115
corrects the public Provision opcode's remaining rustdoc to describe a copied
configuration sender. All executable Rust, tests and dependency inputs remain
byte-identical to the preceding checkpoint. Fresh format, private rustdoc,
Markdown and diff checks pass without warnings; the prior strict four-profile
main and shim matrices are reused for the unchanged executable inputs.

Both original CI runs pass:
377 and
378. All four complete
terminal job logs total 554,488 retained and hash-verified bytes, with zero
warnings or failures. Each test job reports 957 passing tests across its
configured selections and two existing ignored cases. No workflow was rerun.
This is a documentation correction and requires no runtime consumer repin;
Docs 69840bd8
selects this exact source for the regenerated API reference. The separately
accepted native startup witness remains recorded in
Integration #89 and
Launchd #7.

Counted client configuration continuation — 24 September 2026:

Proposed coordinated continuation: configure each private Posixd instance with two actual staged clients and mediator-owned bounded byte channels. Preserve the existing startup/control handshake and native identity checks. Configuration is canonical, counted and digest-bound; labels select already held owners and never confer authority. This is a first nonblocking byte-I/O slice. Full filesystem/TTY configuration, complete POSIX semantics, libc, all resource-retirement criteria, rebuilding Rust/LLVM inside EriX and both complete EriX guest builds remain required later work.

Add strict versioned startup/Provision successors for the counted client/descriptor/channel/ring policy and canonical plan digest, coordinated across producers and consumers. The proposed startup has a 224-byte header, two 24-byte endpoint records and one 32-byte workspace record, totaling 304. The canonical plan is 96 + 32*C + 24*D + 16*H bytes. Its digest excludes RPC correlations and recipient-local slots, while including the exact realm and mediator pair; client native pairs come from original staged owners. The configuration pull header is 96 bytes; ordinal requests 112, refusal 104, successful header/client/descriptor/channel replies 200/136/128/120. Exactly client replies copy one RECV capability; other replies and ordinary calls have no capabilities.

Keep Ready/Challenge framing capability-free. Separate SealProbe/Prepared from SealCommit/Sealed and exact ClientTerminal/Ack controls, authenticated against native Procd origin. Prepared requires final configuration caller retirement and child SEND disposal. Commit follows Launchd's independent source/delivery cleanup. Lost seal replies cannot authorize client Start. Fixed client startup is 160 + 16*Dclient bytes with exact digest, original identities, supplied workspace/budgets and one intended ingress SEND. Retire replaced startup codecs after coherent adoption; reject unsupported versions/reserved fields rather than maintaining implicit fallback.

RBS1 minor1 preserves the first128 header bytes, appends C/D/H/Q u64 at128/136/144/152, configuration SHA-256 at160 and layout SHA-256 at192. Provision successor0x436 is112 bytes: the existing48-byte prefix followed by counts32 and configuration digest32. Its320-byte reply is the16-byte result prefix plus304 startup bytes; refusal zeros the tail. Counts are all zero for the bootstrap-only mode or all positive for configured storage. Result/receipt capability budgets are one only for configuration-bearing replies; Ready, Challenge and client calls remain zero-transfer. All size, alignment, page-rounding, packet/receipt and ordinal arithmetic must be checked before native effects.

Authenticate target geometry through the existing selected-image path. Posixd exports one immutable 96-byte target-generated descriptor in read-only file-backed ELF load storage: magic16 ERIXPXSCAPLAY001, then ten little-endian u64 words for version1, total size96, ELF machine, pointer bits, and client/descriptor/channel row size/alignment pairs. Sizes are nonzero and alignments powers of two; target fields match the selected executable. Loaderd extracts exactly one complete descriptor from its already authenticated root ELF bytes, refusing missing, duplicate, malformed or writable records. No host-derived type size or reopened pathname supplies geometry.

An exact 144-byte BindRealmLayout request uses the existing authenticated LoaderMaterialization route: request/op u32, original active transaction u64, root ELF SHA-25632 and descriptor96. Its response uses the existing 36-byte materialization shape with zero noncommit materialization/staged fields. Procd accepts it only from actual Loaderd for that original active mediator transaction, retains the description through staged commit/rollback, and requires it before mediator commit. The startup carries the descriptor SHA-256, which Posixd compares against its own compiled descriptor before any typed arena borrow. Canonical checked sizing partitions client rows, descriptor rows, channel rows, plan bytes, ring bytes, retained per-client results and immediate packet storage; every multiplication, alignment, address and page round must fit. This grants no additional endpoint or allocation authority.

Ordinary endpoint transfer copies authority. Every source and possible receive destination remains owned across submission, collection and native retirement, including ambiguous results. Reserve each prospective receive slot before COLLECT; validate its normalized receipt and actual Generic kind/rights, then independently reconcile its disposal before reuse. Unique InstallGrant and RevocationGrant transfers keep MOVE semantics. Do not infer source deletion from successful copy or use deletion to manufacture successful unique-grant movement.

Track this continuation with Posixd realm lifecycle, POSIX ABI and Phase 6 completion. This is a proposed contract; no runtime or implementation acceptance is claimed.

Corrected endpoint COPY versus unique grant MOVE documentation in signed
Lib-IPC commit a8324c136fe1747edd3e7eeea563b2bb87572df1.
Provision transfers one ordinary Generic SEND endpoint by COPY and retains the
sender's original source alias. Launchd must explicitly dispose of that alias
and independently prove absence before Start. A unique InstallGrant still moves;
deleting a residual grant cannot manufacture successful native move evidence.
README, ARCHITECTURE, ROADMAP and provisioning rustdoc now state that distinction.

This checkpoint changes comments and documentation only. Executable Rust, tests,
dependency inputs and wire behavior are byte-identical to the preceding
93bd65388e9bced368b7f3727e4ba0b88e55a860
checkpoint. Fresh formatting, private rustdoc, Markdown, template and diff checks
pass without warnings. The unchanged code retains its prior strict default/all
and development/release matrix: 459 main-crate tests/doctests and 20 syscall-shim
tests, with one existing native-only host ignore, in each selection. That matrix
was reused on the verified unchanged inputs, not rerun locally for this prose
correction. Existing native image consumers may retain their prior exact IPC
selection; this correction requires no executable dependency or image repin.

The runtime consumer fix and native startup acceptance remain pending in
Launchd #7 and Integration #89.
No new runtime or VM validation is claimed. Both original exact-head CI runs pass: run 375, run 376. All four complete terminal job logs (554,500 bytes) are retained and hash-verified, with zero warning or failure candidates. The declared host tests, strict host/freestanding Clippy and builds, private rustdoc and Markdown checks pass. No workflow was rerun.

Start requires a nonzero exact digest; only authenticated retirement accepts a zero unknown-digest sentinel after a lost provisioning result.

The four default/all-feature development/release main-crate selections each pass 459 tests/doctests; each corresponding syscall-shim selection passes 20 tests with the one existing native-only ignored case explicitly retained. Formatting, strict host/native Clippy, warning-denied builds, private rustdoc, Markdown and exact original dependency checks pass with zero warnings.

Actual running mediator readiness/retirement, complete service-image acceptance, configuration/seal, client I/O and both required guest rebuilds remain open.

Tracking: owning issue, WIP PR and Phase 6 acceptance.

The original Clippy style refusal is retained and corrected without relaxing lints.

All reserved bits are rejected; replies carry zero result values and preserve uninterpreted codes.

Seven new controls pass all eight strict library/shim configurations: 419 wire tests and 20 shim tests per configuration, eight freestanding builds, formatting, strict host/native Clippy and private rustdoc, with no warnings. The original kernel-only shim test remains ignored. Original lib-ipc CI 365 and 366 pass from four complete hashed logs, 494,246 bytes, without warnings. Kernel admission, descendant stopping, safe native reclamation progress, coherent consumer adoption and actual CPL3 failure coverage remain open. The shared codec does not enable private mediator execution or alter the current complete image's source graph.

The matching signed Docs PR 4, 54557713f4afad380c1166f6aa1c1622d3959744, updates the TeX chapter and both IPC API views from original signed source. All 45 tests, independent API regeneration, the complete 2,423-page manual, all 446,749 word bounds and nine visually reviewed contract pages pass, with zero final warnings. Original Docs CI 979 and 980 pass from four complete hashed logs, 773,034 bytes. Both runs pass 45 tests and the complete 2,423-page manual; successive TeX passes retain 36/1/0 warning observations, with zero final-pass warnings. No workflow rerun or cancellation supplies this result. Native upstream Rust/LLVM rebuilding and both complete EriX build generations inside EriX remain required.

Runtime dependency alignment — 15 September 2026

This is part of coherent runtime-source adoption, not a new product VM or guest-build acceptance.

Coherent runtime source adoption — 15 September 2026

Full commit selectors remain mandatory.

Construction without child root capabilities — 15 September 2026

Define checked root-capability-free construction framing alongside the existing native authority, owned invocation and staged endpoint contracts. Signed original revision: 7c7712057cc5d16ab16a677a886caeac54814a16. All 381 IPC tests and the syscall shim matrix (20 tests, one existing native-only ignore) pass with strict default/all development/release host/native Clippy, builds, documentation and formatting. CI 345/346 has complete warning-free logs.

Procd adoption, authenticated grant return, guarded bootstrap authority, private mediator execution, readiness, configuration/seal, client I/O, fair retirement and both complete guest build generations remain open. Ordinary mediator start gates remain closed. Whole-codebase semantic authority and private-item documentation audits remain incomplete.

Staged endpoint attenuation checkpoint — 15 September 2026

Define the checked ProcessBoundEndpointAttenuationV1 request and operation 53. Preserve exact packed widths, nonzero identity requirements, reserved-field error precedence and exact zero rights. Scalar decoding conveys no capability or proof of native identity. Signed original revision: 74c75a5db226413c066b6582210a44cb21d968d8. All 376 IPC tests and the syscall shim matrix (20 tests, one existing native-only ignore) pass with strict default/all development/release host/native Clippy, builds, private rustdoc and formatting. CI 343/344 passes with complete warning-free logs.

Authenticated grant return, independently minimal bootstrap/root authority, retained native and nested guards, private mediator execution, configuration/seal, client I/O, fair retirement and both complete guest build generations remain open. Ordinary mediator start gates remain closed. Whole-codebase authority and private-item documentation audits remain incomplete.

Signed Lib-ipc 805717680d9dfb902216550a111d910807f30d23 selects native IPC assembly only for freestanding x86-64 builds. Other targets retain the API for tools and tests, with local DENIED and zero raw transport outputs. Checked helpers preserve their preceding slice validation. The local refusal carries no kernel-attested identity, capability observation or retirement acknowledgment; compile-target selection itself does not authenticate a running kernel.

The backend is extracted and documented inline. Three public host regressions cover register operations, empty identity/authority observations and unchanged message buffers. Static object inspection establishes zero syscall instructions in both hosted profiles before those tests execute. The native backend's emitted instruction sequence is identical in development and release. No new wire result or runtime probe is introduced.

Both crates pass formatting and the complete strict default/all-feature development/release host/freestanding matrix. Each ABI selection passes 359 units plus one doctest; each shim selection passes 18 tests with one existing native-only test ignored. Private rustdoc covers both compiled backend variants. Canonical documents, whitespace, source identities and code-size checks pass without compiler or lint warnings. Current push CI 335 and PR CI 336 pass for this exact signed source. Four complete logs total 409,239 bytes with zero warning candidates. Each test job passes 359 default ABI units plus one doctest, 359 optimized all-feature ABI units and both 18-test shim selections; the existing native-only case remains ignored once per shim selection. All three new host tests pass in both selections. The workflow also passes formatting, strict Clippy, host/freestanding builds and private rustdoc; both ten-file Markdown jobs pass.

The source-matched API export retains all 2,593 ABI and 24 shim public signatures unchanged. The platform manual is accepted at signed Docs 87942ea7675e2a25fe3bf19f3cac19f9c5d8b1e2 in Docs PR 4, with all 45 documentation tests, the complete 2,339-page local manual and CI 843/844 passing with zero final warnings. The earlier native lifetime mechanism remains accepted at its separate Kernel 03e13a78 / Integration 4b65755f graph, with Docs 17b4d52a and green CI 841/842. New realm producers, operation completion, the broader audit and full guest builds remain open.

The matching native lifetime scenario now passes with Kernel 03e13a78 and Integration 4b65755f, whose exact source graph selects this signed IPC revision. Docs 28b44183 publishes the syscall and generated wrapper reference with green CI 839/840. Realm producer adoption, pending-operation completion and full guest builds remain open. See Kernel issue 7 for the exact native image and acceptance boundary.

  • Parent work: erix/integration#2 and erix/docs#1.
  • Branch: feature/posix-compat; update linked WIP PRs after coherent signed checkpoints using canonical CONTRIBUTING.md messages.
  • Baseline revision: b452a46803982c57e474adcc318ce40bd281d621; refresh component/dependency heads and their own CI evidence as implementation advances.
  • Cross-repository dependencies remain full lowercase commit hashes; update the selected graph deliberately. This issue does not authorize merges, release tags or replacement of published images.

Coordinated actual consumers and matching native execution remain open under Kernel design 19. This dependency/wire checkpoint does not establish complete lifecycle acceptance or either full EriX build generation. Phase completion retains native external Rust/LLVM/runtime rebuilding as an independent requirement.

Acknowledged terminal accounting — 21 September 2026: Kernel design 20 specifies final scalar CPU evidence retained independently of native resource reclamation, repeatable observations bound to actual original observer generations, independent authorized observers, exact acknowledgement and claim release on observer death. Both ordinary and mediator consumers must commit terminal measurements and cleanup duties before acknowledgement, including consumer-loss handling.

Shared wire commit 0b889095fd04f6f4b1da1d4c0064150551f52122 is signed and pushed. Four wire configurations pass 427 tests each; four syscall-shim configurations pass 20 each with one existing ignore. Eight native builds, strict host/native Clippy, formatting, private rustdoc, Markdown and dependency checks pass without warnings. Native kernel and consumer adoption, actual CPL3/service VM acceptance and original CI observation remain open.

Canonical completion remains 3.48% weighted; 15 of 460 acceptance items. Full upstream Rust/LLVM/runtime rebuilding inside EriX remains mandatory together with both full EriX guest build generations. No acceptance item closes from this representation checkpoint.

Native producer and actual consumer adoption remains in progress under Kernel design 20. Runtime acceptance remains open; phase completion retains native upstream toolchain rebuilding and both EriX guest generations.

Original special-file metadata design — 30 September 2026

Extend descriptive native node kinds to distinguish retained FIFO, character-device, block-device and socket inodes from absence. Share exact mode/type validation across observations and no-follow candidate framing. E2fsd will retain the original inode for status and directory observations; names and metadata will grant no device, stream or socket access. Existing native content admission remains restricted to regular files and directories, and compatibility open will explicitly refuse unsupported special-file contents before native admission. Prefix search, final no-follow behavior and original cleanup custody remain intact.

Author codec, provider and guarded-service controls for original identity, each special mode, malformed kind/mode combinations, absence, refusal ordering and cleanup. Coordinate immutable dependency revisions and update component contracts and the maintained manual. This remains part of complete status and directory support; provider metadata gaps and pipe/stream status remain unfinished. Tests, builds, lint checks, VM/profiler execution and CI observation remain deferred under the current user instruction.

Original special-inode metadata — 30 September 2026

No device, socket, pipe, clock or new provider endpoint is granted.

The full status/directory item remains open for complete FAT metadata, pipe/stream status, the compatibility special-device-number field and remaining full-item integration. Both complete EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.

Original special-device numbers — 30 September 2026

Compatibility 1.15 will append an unsigned 64-bit device_number at offset 88 of the status reply and prefixed C record, making each status body 96 bytes while retaining the earlier field offsets. This represents the original device inode's major/minor pair, separate from its containing filesystem identity; it never selects or grants a native device endpoint. Rust/C framing, aggregate call controls, producers and native workload consumers will migrate together.

Native conversion requires explicit device-number availability for character/block types, preserving meaningful zero and every represented bit. Non-device types have canonical zero by their established type. Native observations claiming a nonzero number for a non-device will be rejected. E2fsd's retained-inode decoder will distinguish the legacy first-word and extended second-word encodings and preserve both major and minor fields. Metadata remains read-only under original custody, with content admission and cleanup gates unchanged.

Author independent native availability/malformed-value, exact-wire, C aggregate and ext-media controls, and extend the actual native workload to check represented device numbers. All test/build/lint/VM/profiler execution and CI observation remain deferred under the user instruction. Complete provider/pipe/stream metadata and full libc structures remain part of the open status and directory work.

Original represented-device status — 30 September 2026

Existing field offsets are unchanged; earlier wire minors and shorter bodies are refused. Native character/block observations require independent device availability, including meaningful 0:0.

No clock, device, socket, pipe or new provider route is granted; content gates, error ordering, original caller/pin cleanup and alias custody remain unchanged.

The full status/directory feature remains open for complete FAT metadata, pipe/stream status and remaining full-item integration. Both full EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.

Dynamic pipe status and explicit clock custody — 30 September 2026

Cap-free public operations cannot choose a slot or transfer a caller-selected source. Launchd retains prospective counted custody before copying its startup-admitted SEND query endpoint; configuration and inventory admission preserve original receipts. The shared clock has no per-client provider object or Close; recipient alias disposal follows caller retirement and requires DROP plus independent absence QUERY.

No compatibility client receives a native clock capability.

The full status/directory feature remains open: initial configured channels, inherited stream metadata, full FAT identity/owner/mode/time policy and whole-feature integration remain implementation work. Both full EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.

Initial configured FIFO status and atomic writes — 30 September 2026

Bound FIFOs require a valid canonical creator; unbound pools require the all-ones no-creator encoding. Launchd restores original ordering and all creator/credential bytes on acceptance and refusal.

Release precedes original metadata publication and Prepared; native client-disposal acknowledgment cannot overtake query retirement or drop the original clock alias early.

No compatibility client receives a clock capability.

Two ordinary plans require 936 bytes; explicit binding plans require 3752 bytes and 44 authority rows.

The full status/directory feature remains open: inherited stream metadata, complete FAT identity/owner/mode/time policy and whole-feature integration remain implementation work. Both full EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.

Original inherited stream metadata — 30 September 2026

Canonical refusals carry no observations. An explicitly unavailable native source cannot become a successful POSIX status.

Shared observers preserve original inode/node/media evidence; Vfsd shares mounted-filesystem qualification with candidate metadata and never replaces object serials with temporary handles or queue offsets.

Missing required fields return ENOTSUP without changing offsets or descriptor lifetime. No new capability, clock, content grant, heap pool or descriptor ceiling is introduced.

12 new Rust controls are authored and unrun: independent family literals, correlation and capacity rejection; ordinary/acquired handle separation; write-only alias identity; unavailable metadata with continued byte I/O; malformed-response custody; cancellation; original lender forwarding; and PTY/local-buffer observations.

The full status/directory feature remains open: native-buffer/PTY original identity, creator and time policy, complete FAT metadata and whole-feature integration remain implementation work. Both full EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.

Original native stream identities — 30 September 2026

Ordinary namespace and executable routes cannot allocate one.

Original event times remain Unknown; this scalar metadata cannot turn an incomplete observation into successful compatibility status.

They cover literal wire rejection, atomic encoding, administrator isolation, lost-delivery allocation, binding refusal, exhaustion, directional lifetime, teardown/reuse, original ownership, malformed observations and receipt cleanup.

The full status/directory feature remains open for original native event-time capture, complete FAT metadata and whole-feature integration. Both full EriX guest build generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.

Original native stream event times — 30 September 2026

Alias creation, metadata queries, empty or refused operations and terminal device progress do not query a historical clock.

Ttyd receives an exact authenticated SEND-only Timed endpoint for this source purpose; Launchd uses its already admitted endpoint. Clean refusal remains Unknown.

The seeded boundary control retains the whole original object and proves the intended no-clock refusal contract when executed; no runtime reproduction or practical path to 2^64 bytes is claimed.

They cover source-event independence, unknown evidence, full-range dates, malformed replies, receipt cleanup, exact SEND-only admission, alias/retirement/reuse and overflow refusal. The existing realm workload now requires successful inherited fstat and original PTY clock evidence with stable birth before and after realm retirement; its independent transcript remains 385 calls.

The full status/directory feature remains open for complete FAT metadata and whole-feature integration. Both full EriX guest build generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.

Original FAT mount recovery and mutation rollback — 1 October 2026

Ext and memory families cannot reinterpret this flag.

Swallowed wrong-mount or reserved-extent refusals cannot commit.

They include independent FAT12 media, original before-images/checksums, hostile extents, clean and recovery-required read-only mounts, actual mutation rollback, key/handle retirement, nested helpers, wrong-mount refusal and unwinding. Four new native scenarios cover clean admission, interrupted-boot recovery, corrupt counted records and read-only refusal; positive workloads retain existing mounted filesystem/lifecycle gates.

The complete FAT metadata feature and full status/directory feature remain open. Both complete EriX guest generations and external Rust/LLVM guest rebuilding remain required and unperformed.

Conditional retained-entry namespace custody — 1 October 2026

Exact response correlation distinguishes completed effects, definite no-effect refusals and uncertainty.

Missing, malformed or uncorrelated replies preserve cleanup and never permit replay. The installed namespace is currently immutable and append-only; future unmount/reconfiguration requires a persistent nonwrapping epoch.

Ext and FAT return explicit correlated unsupported no-effect dispositions for the new family. Their conditional transactions remain unfinished. Complete compatibility path/dirfd, ACL/sticky, final-link and trailing-separator mediation and legacy cwd migration remain open in the owning design. Required legacy cwd and administrative spelling guards remain.

Thirty-nine new Rust controls are authored and unrun: ten literal wire controls, seventeen RAM provider controls, eight actual Vfsd dispatch controls, and two explicit-refusal controls each for ext and FAT.

Both complete EriX guest generations and external Rust/LLVM rebuilding remain required and unperformed.

Counted authenticated launch-entry evidence

Replace private Vfsd launch-artifact operation 0x613 and its V1 codecs with operation 0x71B and V2 framing. The request retains the original 88-byte correlation/selector prefix and appends u64 maximum exported entry bytes at offset 88, then raw selector bytes at 96. Zero export capacity requests authenticated digest evidence without a display copy. Positive capacity requires the complete available entry, never truncation. Preserve the explicit sidecar flag, source/destination and all transaction/session/realm bindings.

The 184-byte response prefix retains request/op/result/failure at 0/4/8/12, transaction/session/realm at 16/24/32, scope/source/result slots at 40/44/48, mode at 52, size at 56, exported entry length at 64, selector digest at 72 and original object digest at 104. Add authenticated artifact-entry digest at 136, echoed export capacity at 168, echoed flags at 176 and zero reserved at 180; optional complete raw entry bytes follow at 184. Success requires a nonzero entry digest and original object evidence. Refusal preserves original request correlations while zeroing all new object, entry and measurement evidence. Both codecs reject the retired operation with no downgrade.

Vfsd derives entry identity only from complete original-generation evidence retained by the actual native resolution, never from an unchecked caller selector. Hash the existing command-entry domain, u64 little-endian complete byte length and canonical raw entry bytes in place across counted description fragments. For sidecars preserve the explicit derived .lmf requirement; the artifact hash describes the full sidecar entry, while its authenticated manifest contents remain bound to the executable command-entry digest. Missing required binding evidence refuses normally with original cleanup. Display absence cannot manufacture entry identity.

Resolve the executable selector as borrowed bytes. Derive the sidecar by streaming the original selector and literal suffix into the same counted scope traversal, without a 240-byte whole-selector buffer. Preserve known-root interpretation, actual provider authority, active symlink context, source generation and original retirement. Admit caller/transport reply extent and encode complete typed evidence before creating a receiver. Failed publication retires only new custody; uncertain cleanup stops ordinary work.

Launchd validates all original correlations, flags and capacity before accepting evidence. When entry bytes are exported, independently hash their complete bytes and require digest equality. Store the authenticated executable digest independently of its display; Loaderd and manifest binding consume that digest. Manifest evidence needs no retained path cache. Realm/client preparation requests digest-only evidence, removing the display-width obstacle on those paths. Ordinary prompted launches initially advertise their actual existing display storage capacity; continue replacing that retained storage and the coordinated Powerbox/TTY display contract in the same migration. This intermediate capacity is not full counted program-display acceptance.

Author literal wire, atomic capacity, long/raw selector, original-source closure, sidecar derivation, changed entry, retired-operation and cleanup controls. Retain existing content, relation, native receipt and rollback controls. Keep testing, builds and CI observation deferred. Complete retained display, remaining provider/name adapters and coherent deployment adoption before closing the containing native migration or claiming guest self-hosting.

Ordinary V2 response correlation no longer admits retired effect operations.

They retain
root/parent/key fields, full-width handles and timestamps, optional trusted time,
explicit selected fields, invalid destination refusal and untouched short outputs. New literal stat controls cover framing, canaries and retired-family refusal. Retired numeric replies cannot satisfy ordinary V2 or native effect correlation. Vfsd's last old exported-name references become literal timestamp-adapter refusals
for all thirteen retired operations.

The existing superseded-bridge/provider-spelling-pin acceptance criterion in
the native ownership feature
is source-complete. Required imported FAT/exFAT binding and geometry guards remain. The remaining cwd/contextual-serving and complete lifecycle/control/graph criteria
need a current-source acceptance audit and any missing implementation, followed by
coherent runtime adoption. No synthetic weighted sub-item or full lifetime acceptance is added. Recomputed
phase progress remains 18.95% weighted and 6.81% whole acceptance: 25/460 parents
and 480/949 sub-items. Full EriX guest generations and external Rust/LLVM rebuilding
inside EriX remain required and unperformed.

Counted raw program context — producer/consumer design, 1 October 2026

The ordinary prompt boundary must preserve the complete authenticated program entry
without a 240-byte or UTF-8 adapter. This is descriptive data only: Launchd's
entry digest, manifest admission, native scope and object custody remain independent.
Launchd's remaining per-job retained display storage will migrate after this boundary.

Replace the contextual V1 types with PowerboxBeginContextRequestV2 and
TtyPowerboxPromptContextRequestV2 across LibIPC, Launchd, Powerboxd and Ttyd.
The fixed authority-free BEGIN (80 bytes) and prompt (128 bytes), private routes
and answer correlation remain unchanged. V2 context appends job generation u32,
a reserved zero u32 and program length u64; the prompt additionally appends selector
length u64. Prefixes are exactly 96 and 152 bytes. Raw program and then selector
bytes follow. Exact fixed shapes select their fixed codecs; every other shape
selects only V2, without retrying the fixed parser after a contextual failure.
The nonzero legacy contextual length occupies V2's reserved word, so retired V1
contexts reject rather than silently changing interpretation.

Programs use complete absolute normalized raw bytes; generation is nonzero.
Selectors remain complete nonempty NUL-free raw bytes. Counts must fit target
width and exact body extent before borrowing, retaining or encoding. Overflow,
unknown padding, short/long bodies and insufficient output leave storage unchanged.
No opcode, label, generation or byte count creates a capability or changes policy.

Powerbox retains the full original program and selector together in its existing
caller-sized arena, preserves both through compaction and clears retired ranges.
Prompt transport admits the complete body before calling Ttyd. Ttyd escapes each
non-ASCII/control byte, admits the whole rendered review, and retains existing
rollback and visibility-gated secure-input behavior. No truncated prompt or digest
shortcut may authorize consent. Surplus capability receipts retain their existing
independent disposal rules.

Migrate current controls and add raw/long geometry, retired-context refusal,
capacity atomicity, retained arena ownership/compaction and trusted rendering
controls. Document the coordinated immutable revision graph and remaining ordinary
Launchd storage work. Author controls without running tests, builds, checks,
generated documents or CI observation under the current request.

Counted redirection selectors and retired provider adapters

Continue the native name migration with complete raw shell redirection selectors.
The existing request already carries a u64 length and variable tail. Remove its
unrelated legacy pathname-width check; retain exact nonempty/NUL-free bytes,
length, mode, digest and distinct slot validation. Add a public semantic validator
shared by codec and typed Vfsd admission. Vfsd must not encode a temporary fixed
pathname array merely to validate already-borrowed input. Actual caller/transport
and native traversal storage remain explicit resource bounds.

Exsh forwards original bytes and digest through its exact cwd SEND transfer and
requires independent operation/cleanup receipts. Short transport storage refuses
before any call. Vfsd authenticates the original resolver/cwd source, policy and
digest before provider effects; raw selectors do not confer authority. Existing
native scope, conditional creation, retirement and receiver-disposal ownership
remain unchanged. The wire shape and operation are unchanged; older peers may
refuse longer requests, so both compiled consumer edges adopt the signed codec.
No fallback, truncation, UTF-8 conversion or path-derived authority is permitted.

Source audit found the old ProviderBackend exact-entry open/mutate/stat/touch
hooks have no production callers. Remove their fixed-name framing, timestamped
mutation bridge, obsolete result type and operation mapper arms. Retain original-
route metadata transport used by live fixed-entry custody, and preserve current
source-free mutation/touch controls. Shared legacy provider codecs still used by
provider internals remain until their separate storage migration is complete.

Author literal raw-selector/capacity/malformed controls, direct native creation
and refusal/cleanup controls, shell full-byte transport and capacity controls,
and exact original-route metadata correlation/refusal controls. Update component
and authored manual contracts. Tests, builds, generated documents, VM/profiler
execution and CI observation remain deferred. Runtime catalog adoption and the
full cross-provider name-storage migration remain open.

Tracking: native retained ownership,
shared IPC design,
Vfsd PR3,
LibIPC PR2,
Exsh PR3,
Docs PR4.

Counted endpoint-selected exact mutation

Replace the fixed 252-byte public VfsExactMutationRequestV1 with borrowed
VfsExactMutationRequestV2. Its 24-byte prefix contains request ID and the existing
exact operation at offsets 0/4, explicit version 2 at offset 8, reserved zero at
12 and the complete u64 destination-byte length at 16. Rename alone supplies one
raw basename after offset 24; other admitted effects have an empty tail. Empty,
NUL, slash and dot rename components refuse. Checked full extent and actual
caller/transport storage replace the fixed width and UTF-8 restriction. The
version/reserved fields distinguish valid old requests, including two-byte old
rename names, without fallback or retaining the deprecated public API.

The exact endpoint still supplies the original immutable operation and entry;
no source, parent, namespace, handle selector, new endpoint or capability is
introduced. Vfsd admits complete status capacity before provider effects and
passes the borrowed destination through the original retained owner. Existing
one-use/definite-refusal/uncertain-effect consumption and original cleanup rules
remain authoritative. Neither larger names nor descriptive status grant rights.

Migrate LibIPC, Vfsd dispatch and Coreutils source callers and controls in one
signed source graph. Coreutils uses actual encoded length and a single call;
wrong correlation, unknown status, malformed/lost replies or unexpected authority
never trigger effect replay. Retire all unwanted receipts before refusal and
preserve uncertain cleanup classification. Share the exact status-call framing,
receipt retirement and scratch clearing with existing truncation instead of
adding another transport copy. Preserve the caller's original endpoint ownership.

Author literal V2 byte layout, complete raw names, short/surplus tails, version
and reserved separation, bad shape, output canaries, operation ceilings, short
status preflight, original-provider binding/cleanup and real transport controls.
Update component contracts and maintained manual TeX. Tests/builds/checks,
generated documents, VM/profiler execution and CI observation remain deferred.
Both direct compiled IPC selectors in adopting consumers use the new immutable
revision; runtime catalogs and compiled Rootd helpers remain unchanged pending
coherent runtime adoption. Legacy directory/consumer frames and complete
cross-provider/self-hosting acceptance remain open.

Tracking: codec audit/design,
native ownership,
Coreutils audit,
Phase 6 tracker.
Review: LibIPC PR2,
Vfsd PR3,
Coreutils PR2,
Docs PR4.

Counted endpoint-selected directory enumeration

Replace the exact-endpoint use of fixed public readdir frames with dedicated
VfsExactReadDirectoryRequestV2 and VfsExactReadDirectoryResponseV2. The 32-byte
request has correlation/op at 0/4, version 2/reserved zero at 8/12, the original
endpoint-local cursor at 16 and u64 name capacity at 24. There is no public
handle, provider, candidate or namespace selector. The original ENUMERATE
endpoint remains the sole authority. Old 24-byte requests refuse on this route;
generic namespace/provider V1 contracts remain until their live users migrate.

The response has a 56-byte prefix: correlation/op at 0/4, version 2 at 8,
known result at 12, next token at 16, node kind/end flag at 24/28, observed size
at 32, complete u64 name length at 40 and reserved zero at 48. One complete raw
name follows. End and refusal have no entry, zero metadata and no name bytes;
refusal preserves the request token. A successful entry has a known kind and
a distinct nonzero token. Check the complete shape, original correlation and
offered capacity before publishing any caller-visible name or cursor.

Vfsd retains counted full native cursor state and reserves a position before
observation. Preserve native mount composition, original metadata identity and
known-size checks, original candidate retirement and equal-position reuse.
Admit complete response/name storage before publishing the reserved position;
short capacity, malformed input, provider refusal and stale identity release
the reservation without advancing the original token. Complete raw names replace
the fixed 240-byte copy. Preserve original owner retirement and generation
isolation. No path reopening, hidden fallback or name-derived authority.

Coreutils advertises the minimum of actual caller name storage and actual IPC
reply capacity, submits one call to the original endpoint, retires unexpected
receipts, validates all framing/correlation and only then copies complete names.
Erase message scratch on every return; failed admission leaves caller names
unchanged. Keep lease ownership and existing utility cursor behavior unchanged.
Use shared explicit call/disposal effects and independent reply fixtures.

Author literal codec, actual provider/position/metadata, transport cleanup and
long raw utility-listing controls. Update inline/component/manual contracts and
publish signed source with both IPC selectors in Vfsd/Coreutils coordinated.
Runtime catalogs and compiled Rootd helpers remain unchanged. Tests/builds/checks,
generated references, VM/profiler execution and CI observation remain deferred.
Complete cross-provider lifetime/restart and guest self-hosting remain open.

Tracking: codec design,
native ownership,
Coreutils audit,
Phase 6 tracker.

Retire legacy provider pathname and spelling-pin adapters

Current contextual consumers use independently retained native anchors,
conditional component/fixed-entry acquisition and source-free retained effects.
The older provider cwd-open, whole-target readlink and path-selected exact-entry
families now remain in provider dispatch, compatibility adapters and tests.
Inventory every opcode, codec and direct caller before deleting its producer.

Retire cwd component open (0x639), its whole-target link observation (0x63A), and
the obsolete path-selected fixed-entry acquisition/effect adapters where all
ordinary consumers have migrated. Old operation numbers remain unassigned and
must refuse without fallback. Keep actual native metadata, raw link pages,
conditional namespace effects, retained entry effects, original anchors and
acquisition-key retirement. Do not remove ordinary namespace/file interfaces
that still have real users, including generic provider readdir.

Remove cwd spelling-pin fields and their move/unlink guards only after the
corresponding creation paths and dependent tests migrate. Remove legacy exact
binding/parent spelling guards with their final acquisition producers. Preserve
original object, parent and navigation-ceiling ownership; empty directory moves
and detachment must retain actual held objects without pathname reopening or
reuse. Conditional entry freshness, stale-binding refusal, original one-use
effect semantics, permission evidence and positive cleanup remain mandatory.
Imported filesystem-format limits remain explicit and are not bypassed.

Migrate controls to actual native root/anchor/component/fixed-entry acquisition
with original keys known before submission. Do not emulate removed APIs with
test-only path reopeners, fabricated handles, copied identity or renamed legacy
production code. Preserve independent identity/mount separation, maximal ID and
capacity refusal, raw link lifetime, moved/detached ancestors, wrong handle kind,
stale selection/replacement, timestamps, media recovery and cleanup ordering.
Retain literal rejection controls for retired operation numbers. Share cohesive
fixture helpers where useful; all authored code stays below 1,000 lines.

Work through RAM, ext and FAT producers and dependent controls, then remove the
unused shared codecs/IDs and remaining Vfsd adapter references. Publish signed
checkpoints regularly and coordinate adopting immutable dependency revisions.
Update component contracts and authored manual/API addenda. Tests/builds/checks,
generated references, VM/profiler execution and CI observation remain deferred.
Runtime catalogs and both compiled Rootd helper selections remain unchanged
until coherent runtime adoption; full guest EriX and Rust/LLVM rebuilding remains
required. Partial provider retirement does not close the complete lifetime item.

Tracking: codec audit,
RAM audit,
ext audit,
FAT audit,
native ownership,
Phase 6 tracker.

Signed current revision: 69837518.

Related records and contracts
Repository Links
e2fsd issue 15, issue 16, PR 3
fatd issue 6, original-undo.md
integration public-deadlines.md
kernel issue 43, PR 3
launchd issue 15, PR 2
lib-bootstrap PR 2
lib-capabi issue 3, PR 2
lib-ipc conditional-namespace.md, native-activity.md, native-deadlines.md, public-deadlines.md, realm-clock.md, retained-exact-entries.md, stream-metadata.md, stream-readiness.md, child-lifetime-binding.md
lib-stdio PR 2
posixd issue 28, issue 33, PR 5, pipes.md
ramfsd issue 6, PR 2, PR 3
rootd PR 2
timed issue 4, PR 2
ttyd PR 3
vfsd issue 15
## Problem and motivation Audit `lib-ipc` throughout Phase 6. Define IPC wire formats, transfer receipts and service operation contracts, including the nested x86_64 syscall shim. Review each changed boundary at the final published revision. Prioritize security, reliability, then performance. ## Proposed behavior and scope Lost-provision-reply retirement refinement — 24 September 2026 (implementation pending): RETIRE alone permits an all-zero startup digest to explicitly describe an unknown startup after a lost or malformed Provision response. The actual original Launchd caller, complete original child/generation and retained realm binding remain mandatory; the zero sentinel omits only digest correlation and never selects a replacement or confers authority. A supplied nonzero digest must still match exactly. START never permits this sentinel. Known pre-provision staged custody keeps its existing authenticated staged-abort route. Final retirement acknowledgment still requires actual exact-instance disposal and all locally owned transport/authority obligations, rather than native absence alone. Private start admission refinement — 24 September 2026 (implementation pending): add Launchd START_REALM operation `0x6D4` with an exact 40-byte authority-free request: request/op at offsets 0/4, original realm/generation at 8/16, and explicit request/result byte budgets at 24/32. The actual pending native caller must still own that retained realm. Validate packet arithmetic and both minimum 96-byte budgets before effects. Preserve all existing BEGIN/PREPARE/READ/ABORT selectors and the ordinary process-start gate. Extend descriptive realm state with Starting (6) and PrivateReady (7), retaining values 0–5. Reuse the existing 40-byte admission response; a successful START acknowledgment requires PrivateReady. The service retains the original response obligation while its immediate private caller and configuration-server owners progress. READ may describe Starting; a lost public response or cancellation retains exact cleanup. PrivateReady proves the observed native-child Ready and confirmed independent controller challenge plus retirement of Launchd-owned transport handles. It does not claim that server COMPLETE observes Posixd's later caller RELEASE, nor does it seal, publish or grant client access. Private provisioning transport refinement — 24 September 2026 (implementation pending): the guarded preparation request remains non-starting. Add separate typed Procd operations for Provision (`0x433`), private Start (`0x434`) and exact Retire (`0x435`), all admitted only from the original Launchd generation on its held private receiver. Provision carries a 48-byte request with exact child and realm identity plus explicit request/result byte budgets, and exactly one moved Generic SEND configuration receipt. Procd derives the actual child capability extent from its retained creation geometry, installs configuration at child slot 5, and computes page-rounded startup/workspace mappings beyond the recorded executable extent. Its successful 224-byte response returns the canonical 208-byte startup record after a 16-byte correlation/result/state prefix; failure carries no startup bytes. Start and Retire each carry 64 bytes with the original child/realm and canonical startup digest, preventing cross-stage substitution. These bytes constrain actual held routes and never confer authority. Procd has no existing own-process identity in its startup payload. Reuse native caller attribution through a separate 64-byte configuration ContextProbe/Ack before RBS1 construction. The probe carries correlation, realm/child and original Launchd identity, with zero controller fields; Launchd obtains the Procd pair from actual CLAIM, retains that original pair and echoes it in the correlated acknowledgment. Procd retains the accepted invocation through retirement before committing the resulting context. This adds no kernel identity query, process endpoint or permission to trust an arbitrary first challenge. Posixd still requires its supplied controller to match the challenge's actual native caller. Launchd explicitly reserves four capability columns per admitted realm in its authenticated deployment geometry. It creates the configuration receiver before exporting SEND, binds an ancestor revoker to its own native lifetime, keeps a separate nested revoker for early retirement, and removes all bypass source aliases. Original executable-scope storage may be reused for temporary construction only after its absence is acknowledged. Procd retains the received configuration sender in an already empty role-owned scratch column, accounts for every mapped frame and setup alias, consumes the actual GRANT through operation 58 only after provisioning, and records uncertain start disposition before the native start effect. No grant-derived MINT capability or ordinary-start fallback is added. Private Start completes only after native start and the independent control challenge have completed their owned caller cleanup; readiness uses Launchd's separate actual-child CLAIM and full startup digest. Invocation handles and application owners remain retained on cancellation, malformed response, lost reply, supervisor loss and partial disposal. Retire selects running termination after any possibly committed start and waits for exact terminal observation/destruction before acknowledging final retirement. Frame allocation and each handshake must preserve explicit ownership and bounded progress; ordinary staging and all existing refusal/cleanup witnesses remain required. Provision, Start, readiness, seal, publication and client I/O remain distinct acceptance steps. Private mediator execution design — 24 September 2026 (implementation pending): the next native witness executes the actual Posixd binary using the existing serialized process mapping path. Private address-space-root routing remains separate work; source review found no dependency that requires it before this witness. The shared contract will add a distinct counted RBS1 startup image: exact version/byte extent; original realm and generation; native child, Launchd supervisor and Procd controller identity pairs; ordered endpoint and writable-workspace records; explicit capability-window and request/result/receipt storage budgets. The initial schema admits exactly a control RECV endpoint and a configuration SEND endpoint, with no root object, Process route or factory. Reject unknown roles, surplus records, duplicate slots, reserved bits, arithmetic overflow and overlapping storage. Counts describe the supported bootstrap roles, while deployment inputs set storage budgets. Startup bytes are child-read-only/NX; Procd verifies installed inventory and separate private RW/NX workspace before execution. The consumer checks actual local capability types/rights. The complete canonical bytes are SHA-256 correlated in readiness and the independent control challenge; parsing and digests grant no authority. Provisioning finishes by consuming the existing GRANT-only installer through native child-lifetime binding (operation 58), without adding MINT or another installer. Record uncertain binding/start effects before replying. Native start independently requires an empty installer census. Adopt generation-bound native running termination through a new Process operation 61: original child/generation and kill reason, zero reserved fields, no extra route or rights. The generation comparison and terminal transition share native lifecycle serialization; stale requests must never select a replacement. Its acknowledgment is distinct from terminal observation, invocation retirement and native destruction. Posixd will register only its declared control receiver and use immediate owned operations to submit readiness through its declared configuration SEND while continuing bounded control progress. Launchd authenticates readiness from actual CLAIM origin. Procd independently challenges its retained control endpoint; COLLECT payloads do not attest a server identity. Both exchanges carry exact original identities and startup digest, admit no capabilities at this bootstrap stage, and retain every accepted native handle even on unusual immediate status. Configuration, sealing and client publication remain later separate gates. Required evidence includes strict codecs and actual inventory denial; committed-effect/lost-reply ownership; wrong/stale caller and generation denial; running-child retirement; supervisor loss; and a maintained VM executing Posixd with native readiness and challenge. Existing unstarted staging regressions remain required. Subsequent acceptance still requires two mediators, two clients each, mediated byte I/O, cross-realm refusal and full retirement, followed by the external toolchain rebuild and both complete guest OS build generations. <details> <summary>Detailed scope and contracts</summary> ### Original PTY readiness checkpoint — 2 October 2026 Original cancellation, acknowledged draining, definite result-capacity refusal and uncertain publication remain distinct; unknown custody forbids replay and requires terminal teardown. TTYd registers original private input/output receivers before either bootstrap or dynamic session creation exports SEND aliases. Actual occupancy, capacity and closure drive readiness; unchanged waits issue no repeated status RPC or native custody probe. The signed image requires explicit TTY waiter capacity, admits pristine compiler geometry, checks alignment/native extent and places exact trailing waiter rows above core state and below the terminal stack. This checkpoint adds no whole-feature acceptance: Launchd delegated-view forwarding, original descriptor subscriptions, complete POSIX consumers, signal/deadline composition and end-to-end native readiness workloads remain unfinished. Both complete EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed. ### Counted public clock deadlines — 2 October 2026 One earliest native timer uses only Timed's existing Time SEND binding; no Time capability is delegated to clients. Original caller cancellation, source failure, definite result-capacity refusal and uncertain timer/result custody remain distinct. Image packaging requires explicit waiter capacity, validates pristine compiler geometry and checked native extent, expands the signed arena and shifts its terminal stack. Zero capacity deliberately refuses deferred admissions; padding never adds rows. Its required TIMED_DEADLINES_OK marker follows all assertions. The dedicated scenario retains a 90-second external diagnostic budget; the existing time profile also requires the workload and actual APIC wake backend. Hosted adapters cannot fabricate guest success. Original descriptor/provider subscriptions, mediator/client consumers, signal masks and complete poll/select workloads remain unfinished. Overall phase checklist acceptance is unchanged. Both complete EriX guest generations and rebuilding external Rust/LLVM inside EriX remain required and unperformed. ### Authorized native deadlines — 2 October 2026 ARM_DEADLINE (0x59) derives the actual current running process, generation and CSpace, validates the original dedicated Time SEND binding and syscall window, admits a calibrated clock and real interrupt source, and reserves storage before returning an original timer selector. No extra service grant, copied capability, retained user pointer, relative overflow or arbitrary duration/count ceiling is introduced. Binding loss retains one final original wake; terminal cleanup ends all custody, and serials never wrap/reset. Runtime and owned-invocation images include the real APIC backend; unsupported profiles refuse timer admission. Elapsed decisions use calibrated monotonic nanoseconds, never interrupt counts. It requires actual native blocking, increased hardware acknowledgment, a newer epoch, elapsed status and GP/direction canaries, then cancels the original timer. The required deadline marker follows every native/user assertion. This prerequisite adds no phase acceptance. Timed still needs counted original public deadline waiters/cancellation; descriptor/provider subscriptions, mediator/client consumers, signals and complete poll/select workloads remain unfinished. A service must cover every real event source before replacing cooperative yielding with atomic waiting. Both complete EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed. ### Explicit legacy receiver watches — 2 October 2026 WATCH_RECEIVER (0x57) authenticates the actual current running generation, CSpace, syscall window and original generic endpoint RECV binding. Registration receives no data, retains no capability, creates no owned-request intake and grants no implicit clock or provider route. Repeated registration of the same binding is idempotent; serials never wrap, including across quiescent storage resets. Backpressure does not claim CALL acceptance or move capabilities. Ten new native unit controls cover original versus foreign watchers, observe/arm arrival, identical registration, SEND denial, absence of implicit owned intake, alias and binding retirement, same-slot replacement, transfer rendezvous, allocation refusal, exact register shapes and process teardown. Its required legacy-watch marker follows all native and user assertions. This prerequisite adds no phase acceptance. Authorized monotonic deadlines, counted original waiters, descriptor/provider subscriptions, mediator/client consumers, signals and complete poll/select workloads remain unfinished. A service must cover every real event source before replacing cooperative yielding with atomic waiting. Both complete EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed. ### Original native activity and atomic wait — 2 October 2026 Epoch exhaustion refuses sleep without wrap. Accepted COMPLETE ends serving observation custody, so the former server cannot observe later caller collection or retirement. Ten new native-object and scheduling controls are authored, alongside extended literal and hosted-refusal controls. The original real-CPL3 scenario now makes the server capture its actual epoch and sleep; cancellation of its original delivery wakes it, and user instructions require a strictly newer returned epoch before acknowledgment. The scenario requires the activity-wake marker only after the complete original workload. This is prerequisite implementation, with no new checklist acceptance. Explicit legacy receiver watches, authorized finite deadlines, original descriptor subscriptions, mediator/provider consumers, signal handling and full poll/select workloads remain unfinished. Mixed legacy/native loops must not yet replace their yielding with native-only waiting. Both complete EriX guest generations and external Rust/LLVM rebuilding remain required and unperformed. VFS requires frozen Write for regular-file resize and live admitted file/directory custody for sync. Known refusals preserve original admission; uncertainty keeps cleanup-only custody, with no retry or pathname reopen. No request or adapter adds a device, mount, credentials, new native rights or capability transfer. They cover literal framing, unchanged output on refusal, full correlation, access direction, actual aliases and zero growth, storage/format refusal, clean recovery ownership, lost barriers/replies, retained cleanup and short reply capacity. Existing ext logical-range conversions and sparse-gap traversal still need the size-boundary audit; compatibility truncate/ftruncate/fsync/fdatasync consumers, complete cancellation controls and new live workloads remain unfinished. Current phase completion remains **19.20% weighted**, 7.61% whole acceptance: 27/460 parents and 486/949 children. Both full guest EriX generations and external Rust/LLVM rebuilding remain required and unperformed. ### Staged construction without root capabilities — 15 September 2026 Add kernel-control operation 54, CREATE_STAGED_PROCESS_WITHOUT_ROOT_CAPS, and checked StagedProcessWithoutRootCapsV1 scalar framing. Successful creation returns a live Created process and nonzero generation whose CSpace contains exactly its requested primary endpoint, with no CNode, VSpace or TCB capabilities. Native CSpace/TCB/VSpace objects and the process's VSpace lifetime reference still exist. No child code executes during construction. The endpoint initially retains its ordinary full endpoint rights; operation 53 independently narrows it before bootstrap execution. Keep the existing creation operation 32 and its producer behavior unchanged. The new selector is independently recognized: an older kernel refuses it, and callers must not fall back to old ignored flags or a child self-report. Admit it only on the existing Process endpoint family, without adding a capability type, endpoint factory or ChildPopulate creation authority. Use the existing fixed request envelope. arg0 contains the caller-local install-grant destination in its low 32 bits; its upper half is zero. arg1 low/high halves contain child-local primary endpoint and caller-local endpoint-master destinations. arg2 low/high halves contain the child window base and optional caller-local VSpace destination. arg3 contains the 32-bit window length, with a zero upper half. Flag bit 0 means that the VSpace receipt is requested; all other flag bits are zero. When the bit is clear, arg2's upper half must be zero. This explicit presence bit distinguishes an omitted receipt from a real receipt in slot zero. All slot fields retain their full unsigned width; slot zero and otherwise vacant former root positions are ordinary requested slots, subject to native bounds, actual caller-window visibility and occupancy. The checked codec validates framing, not native capacity or authority. The native constructor requires a valid child window containing the primary endpoint. The caller receives only its actual unique stage-bound install grant, endpoint master and optional MAP-only VSpace receipt. The grant is bound to the returned process/generation and exact child window. Existing capability ceilings, actual object identity and explicit disposal rules remain in force. Temporary native setup bindings must be gone before constructing the final primary endpoint and publishing the grant; otherwise former root positions would remain an unnecessary destination restriction. The TCB's independently held VSpace reference must keep backing alive even without any child or parent VSpace capability. On failure, destroy the partial child and dispose only successfully created parent receipts. Preserve pre-existing or overlapping destinations and the original failure; uncertain cleanup fail-stops. Never treat a requested slot as evidence that its capability was created. The new contract supplies an initial inventory, not a permanent prohibition on later explicitly authorized installations or a sealed realm. The returned grant remains a real pre-start population authority that its owner must account for and retire. Required checks include full-width codec/reserved-field cases, omitted versus slot-zero VSpace receipts, zero/former-root/last-slot endpoint destinations, invalid or inaccessible windows, occupied/overlapping outputs, exact parent and child inventories, no residual native objects, mapping/startup backing retention, attenuation through the actual grant and abort/terminal cleanup. Actual CPL3 creation/refusal/disposal must complement host tests. Procd adoption must select this operation only for the mediator role and preserve all ordinary start gates until authenticated grant return, minimum typed startup, retained native/nested guards, readiness, configuration/seal and fair retirement are independently implemented. No runnable realm or guest build is established by this constructor alone. ### Native staged endpoint attenuation — 15 September 2026 Add kernel-control operation 53, ATTENUATE_STAGED_ENDPOINT_WITH_GRANT, with a checked ProcessBoundEndpointAttenuationV1 request. This is a new recognized operation; an older kernel must refuse it, and producers must never fall back to an unchecked or post-execution self-report. No syscall number or service endpoint permission is added. Use the existing fixed KernelControlRequestV1 layout: arg0 low/high halves are the caller's actual install-grant slot and child endpoint destination; arg1 is the exact 32-bit rights mask, with its upper half zero; arg2 low/high halves are expected process and staging generation; arg3 and flags are zero. Both identity components are nonzero. Zero rights means exactly zero, never inheritance. Successful response values are zero. The native handler must validate the actually held GRANT-bearing install grant, its record, exact expected process/generation, live Created child, grant window, endpoint type ceiling and actual primary endpoint slot. Its rights ceiling must cover the current endpoint rights as well as the requested result; a narrow installer cannot manage a broader existing binding. The new rights must be known, valid for endpoints and a subset of current rights. Update only that existing binding's rights, preserving native object identity, all other bindings and revocation associations. The change allocates no alias and needs no new destination. Repeating the same attenuation may succeed; restoring a removed right must fail. Running, dead, stale, foreign, missing and wrong-type targets must fail without effects. Admit the operation only on the same Process and ChildPopulate control kinds as exact process-bound installation. Endpoint possession and descriptive IDs alone are insufficient: the actual held scoped grant remains mandatory. The immediate consumer is the future Procd bootstrap transaction, after the actual broad grant returns from Launchd. It will reduce the staged mediator's initial full endpoint to RECV before any private execution, providing independent native proof of that boundary. Required coverage includes codec/reserved-field rejection, missing and moved grant, wrong process/generation, wrong target/type/window/ceiling, exact attenuation and retry, attempted amplification, post-start refusal, actual CPL3 effect checks and full cleanup. This primitive alone does not admit mediator execution: authenticated grant return, native lifetime and nested revoker custody, minimal root/bootstrap inventory, readiness, configuration/seal and fair retirement remain separate gates. The current ordinary start prohibition stays in force. ### Staged mediator handoff contract — 15 September 2026 Reserve Loaderd operation `0x654` (PREPARE_REALM) using the existing exact-executable preparation request/response layout. The operation selects the new Procd lifecycle class `0x448` (REALM_MEDIATOR); role values describe lifecycle policy and confer no capability authority. Launchd explicitly selects this operation after authenticating its executable object. The ordinary operation `0x652` keeps its existing behavior. Responses must echo the selected operation; no fallback is permitted. Loaderd validates the same sole exact-executable SEND receipt, authenticates the complete image graph, and uses the existing semantic materialization pipeline. The mediator's temporary initial endpoint occupies child-local slot 4, after native root slots 1–3. This slot is an ABI destination, not a realm-count or resource-budget restriction. The child remains staged. Procd retains the actual endpoint master in the existing managed scratch endpoint column; it never exports that master to Loaderd or Launchd. Only the actual move-only install grant travels Procd → Loaderd → Launchd. The derived ordinary stream installer is absent for this class. Reply loss aborts the exact stage and accounts for the retained endpoint, grant and VSpace; cleanup uncertainty remains fail-stop. Launchd may inspect, abort and stop only its owned lifecycle classes. Root, driver and powerbox routes cannot use the mediator class; generic staged-start, ordinary startup/stream installation and automatic restart reject it. The future separate bootstrap transaction must receive the actual grant back, authenticate the live caller, install a typed receiver/rendezvous inventory using exact process-bound installation, dispose temporary aliases and configure the startup bytes before private execution. No existing start path may bypass that gate. This staged handoff is the first implementation increment of typed realm bootstrap. Acceptance for this increment requires malformed/foreign operation rejection, exact executable and grant receipts, unstarted materialization, private master retention, no derived stream grant, and rollback coverage across the actual producer paths. It does not establish mediator execution, seal, publication, client I/O, retirement fairness or either complete guest build generation. Those remain required under the existing acceptance criteria. Native VM coverage of the coordinated producer graph is required before claiming runtime acceptance. Current inventory: 37 Cargo targets (2 lib, 35 test); manifests: `Cargo.toml`, `ipc-syscall-x86_64/Cargo.toml`. Include explicit and automatically discovered targets, supported features and target-specific configurations. Trace authority-bearing inputs through callers and public APIs. Confirm that the library acquires no service, hardware or host authority implicitly. Review startup, teardown and Rootd parity at the caller boundary when this crate owns no process, and justify each applicability decision. The initial missing-docs gaps at `tests/job_authority.rs`, `tests/launch_inherited_description.rs`, `tests/process_metrics.rs`, `tests/serial_input.rs` and `tests/vfs_touch.rs` are corrected with useful crate rustdoc and explicit lint enforcement in [WIP PR #2](https://git.erikinkinen.fi/erix/lib-ipc/pulls/2), signed revision `5ff18b2bf62d3103e5b84aa92d1dc1cd096e9725`. The same checkpoint adds a pure checked representation of all nine existing native result codes, preserving unknown values and requiring separate route/completion/cleanup context. Its full local IPC/shim matrix passes without warnings; broader authority, private documentation and consumer audits remain open. This does not close the aggregate criteria below. Current signed checkpoint `de6892790de69f40f749c393d24078b287b36175` also defines the consumed local lifetime-revocation ABI/shim from [Kernel issue 7](https://git.erikinkinen.fi/erix/kernel/issues/7). Both crates pass the 52-command strict local matrix, emitted register review and [push CI 333](https://git.erikinkinen.fi/erix/lib-ipc/actions/runs/333)/[PR CI 334](https://git.erikinkinen.fi/erix/lib-ipc/actions/runs/334), with no warning candidates. Kernel enforcement, native VM/producer acceptance and the new manual/API refresh remain open in [WIP PR #2](https://git.erikinkinen.fi/erix/lib-ipc/pulls/2). Planned native terminal-generation contract — 17 September 2026: Introduce operation 55 for exact native process/staging-generation/event-kind/status observations. The request has zero flags and arguments; malformed requests fail before dequeue. Successful responses preserve all four 32-bit fields, captured with the actual native terminal transition and retained after destruction. Empty queues return RETRY with zero values. These records constrain existing authority and confer no process-control capability. Kernel, shared IPC, Procd and Rootd migrate together. Procd must match the native process/generation pair before cleanup, CPU-time observation, restart or service-event publication. Remove the superseded identity-free native selector after all maintained consumers migrate, with no fallback on unsupported kernels. Preserve queue reservation, ordering, wake and failure semantics. Validate actual exit/kill, generation reuse, empty/malformed input and cleanup failure, then strict component checks and original bounded native VMs on a coherent immutable revision graph. This is the terminal-observation prerequisite for typed mediator bootstrap. The actual returned install grant already has a generation-checked endpoint-attenuation primitive for the first bootstrap effect. Guard custody, final receiver readiness, sealed publication, two mediators with real client I/O and both full guest builds remain separate mandatory work; this planned contract implements none of those by itself. </details> ## Authority, security and reliability Record each finding's affected revision, invariant, reproduction, owner, regression coverage and resolution. Report suspected vulnerabilities through SECURITY.md and keep sensitive details private. Record a result and rationale for each audit criterion, including caller responsibilities when this component has no process or Rust target. ## Acceptance criteria <details> <summary>Checklist</summary> - [ ] Record origin, recipient, object, operations, delegation ceiling, lifetime and aliases for each relevant capability or caller-supplied authority-bearing value. - [ ] Audit ambient discovery/selectors, cwd/PATH/environment, numeric identities, inherited routes and host fallbacks; require explicit authorized intake. - [ ] Account for residual authority after success, error, cancellation, timeout, restart, failed transfer and teardown, including fork/exec where implemented. - [ ] Remove unnecessary endpoints, broad rights, duplicate aliases, provider/admin grants and debug routes. - [ ] Exercise stale generations, replay, pending replies, forged descriptive identity and object/path resolution races at the owned boundary. - [ ] Prove independent cleanup attempts and caller-specific error precedence; quarantine or terminate when retained authority cannot be accounted for. - [ ] Review unsafe/FFI/parser/arithmetic/lifetime/lock/publication invariants and add adversarial coverage where practical. - [ ] Inventory obsolete APIs, wrappers, fallback/dead paths and duplicate validators with their maintained callers. - [ ] Migrate callers and delete deprecated contracts/shims in a coherent signed revision graph; reject retired input versions where relevant. - [ ] Classify each size/count/depth/time bound as ABI, hardware, explicit resource policy or accidental limitation. - [ ] Test beyond removed boundaries and at allocation/ABI limits while preserving exhaustion errors, denial-of-service controls and bounded waits. - [ ] Keep every tracked authored code/test/script/workflow file below 1000 physical lines through thematic refactoring. - [ ] Run the deterministic tracked-source size gate, covering executable fixtures/generators and excluding only genuine non-code data or external payloads. - [ ] Audit production/test feature and symbol separation, including this repository's effect on rootd test orchestration. - [ ] Supply changes affecting rootd semantic surface to the maintained same-toolchain baseline; record a justified component-specific applicability result. - [ ] Check bootstrap ownership and development/release authority parity at this repository's producer/consumer boundary. - [ ] Use maintained [integration#3](https://git.erikinkinen.fi/erix/integration/issues/3) profiler evidence before optimizing; preserve live access checks, ownership and success criteria. - [ ] Audit build/CI inputs, secret handling, private outputs, symlink containment, deletion, subprocess bounds, warnings and host dependencies. - [ ] meaningful public/private inline documentation, crate/target `missing_docs` enforcement without blanket allowances or hidden-API escapes, warning-denied private-item rustdoc and an undocumented-public-API negative gate. - [ ] Validation: Run `cargo fmt --all -- --check`, strict Clippy, unit/doctests and warning-denied builds/rustdoc for every owned crate/target under default and all valid feature, freestanding/host, SMP and profile combinations; test mutually exclusive combinations separately. Add focused VM regressions for runtime behavior and observe the older catalog and unit tests at the exact published heads. - [ ] Documentation: update applicable README/ARCHITECTURE/ROADMAP in meta's canonical format and affected technical-manual TeX/API references; keep README evergreen and shared governance byte-identical to meta. - [ ] Evidence: record exact source/dependency revisions, commands, configurations, real exit status, CI run URLs and results; repeat the audit on final heads and obtain independent review of security closures. No skipped/pending/predecessor result counts as a pass. </details> ## Alternatives and tradeoffs Refactor within the component unless shared semantics justify extracting common code. Preserve regression coverage before deleting superseded paths. Profile before optimizing, and document ABI limits, hardware limits and explicit quotas. Preserve security and reliability requirements. <details> <summary>Detailed scope and contracts</summary> ### Owned invocation wire contract — 15 September 2026 This v1 contract connects the Kernel's native request/result custody to explicit userspace peers. It is tracked in [kernel #11][kernel] and [lib-ipc #1][ipc]. Shared codecs alone do not establish native execution or realm acceptance. ### Registers and ownership All numbers and packet fields are unsigned. Packet integers are little endian and require no alignment. RAX selects the syscall; arguments are RDI, RSI, RDX, R10, R8 and R9 in that order. Unlisted arguments must be zero. Return RAX is an ordinary IPC result code; RDX carries the operation-specific value below and R8 is zero. A rejected operation returns zero RDX unless SUBMIT explicitly reports a retained draining owner. Calls do not retain any userspace pointer. | Number | Operation | Arguments | Successful RDX | | --- | --- | --- | --- | | 0x4C | REGISTER | local RECV slot | zero | | 0x4D | SUBMIT | local SEND slot, input pointer, input length | invocation ID | | 0x4E | CLAIM | local RECV slot, receive pointer, receive length | delivery ID | | 0x4F | COMPLETE | local RECV slot, delivery ID, input pointer, input length | zero | | 0x50 | COLLECT | invocation ID, receive pointer, receive length | zero | | 0x51 | PROGRESS | invocation ID | packed progress | | 0x52 | RELEASE | invocation ID | packed transition | | 0x53 | RELINQUISH | delivery ID | packed transition | IDs are nonzero opaque numbers, scoped to the actual current process, generation and CSpace. They never choose a process or grant capability authority. REGISTER requires an existing generic endpoint. SUBMIT requires SEND and additionally GRANT for capability inputs. CLAIM and COMPLETE require the exact registered receiver and actual RECV; capability completion additionally requires GRANT. RELINQUISH acknowledges only an invalidated delivery owned by that serving process; it does not require a surviving receiver capability. RELEASE abandons future collection and starts native retirement, without undoing provider effects. SUBMIT may return a nonzero failure code AND a nonzero invocation ID: ingress could not be completed but native disposal remains accounted to that owner. It cannot subsequently be delivered. The caller must retain that ID for progress and release. A nonzero code with zero ID is an ordinary rejected submission. CLAIM/COLLECT return RAX zero after a committed delivery even if subsequent native disposal is draining; the receive header carries that distinction. Their rejection leaves the receive packet and destination inventory unchanged. COMPLETE accepts its result exactly once. Repeated COLLECT is descriptive: no second capability transfer, and the destination list must be empty. Packed transition uses bit 0 for draining and bits 32–63 for its nonzero native code; all other bits are zero. Complete is exactly zero. Packed progress uses bits 0, 1, 2 and 3 for request delivered, completion accepted, result collected and draining; bit 4 says a first error is present, with that nonzero code in bits 32–63. All other bits are zero. Draining may have no first error when release awaits server bookkeeping. Progress flags report history, not new authority. ### Input packet The fixed header is 40 bytes, followed by capability inputs and then payload. The exact packet size is `40 + 8 * capability_count + payload_bytes`. | Offset | Width | Meaning | | --- | --- | --- | | 0 | 4 | ASCII `OIV1` | | 4 | 2 | version, exactly 1 | | 6 | 2 | header size, exactly 40 | | 8 | 8 | payload byte count | | 16 | 8 | capability count | | 24 | 8 | maximum result bytes reserved by SUBMIT | | 32 | 8 | maximum result capabilities reserved by SUBMIT | Each capability input is a four-byte current source slot and four-byte requested rights. COMPLETE requires both result budgets to be zero. The kernel copies input bytes and retains actual admitted native bindings before returning; caller mutation or unmapping after return cannot change the accepted request/result. Possession, type, attenuation, provenance and lifetime checks remain native. ### Receive packet The fixed header is 64 bytes, then four-byte destination slots, then twelve-byte receipt capacity, then byte capacity. Its exact size is `64 + 4 * destination_count + 12 * receipt_capacity + byte_capacity`. | Offset | Width | Meaning | | --- | --- | --- | | 0 | 4 | ASCII `OIR1` | | 4 | 2 | version, exactly 1 | | 6 | 2 | header size, exactly 64 | | 8 | 8 | byte capacity | | 16 | 8 | destination count | | 24 | 8 | receipt capacity | | 32 | 8 | returned byte count, initially zero | | 40 | 8 | returned receipt count, initially zero | | 48 | 4 | attested caller process, initially zero | | 52 | 4 | attested caller generation, initially zero | | 56 | 4 | draining code, initially zero | | 60 | 4 | transition flags, initially zero; only bit 0 is defined | Destination and receipt capacities are distinct to support repeat collection. First delivery requires enough destinations and receipts for all actual inputs; only the used destination prefix is validated or populated. Spare destinations and unused receipt/payload capacity remain unchanged, acquire no authority and are not returned as evidence. A receipt is destination slot, native capability type and admitted rights, each four bytes. It describes a committed transfer, not a transferable capability. CLAIM supplies the retained caller's process and generation. COLLECT leaves those two fields zero. No caller-supplied identity is accepted. Output counts must fit capacities; draining requires a nonzero code. ### Validation and lifetime Overflow, size mismatch, noncanonical headers, unsupported versions, nonzero initial output fields and reserved register inputs reject before native custody changes. There is no inherited 32 KiB CALL limit. Actual addressability, native CSpace limits, caller budgets and fallible allocation still constrain admission. The entire input span must be freshly readable; the entire receive span must be freshly readable and writable in the current process's actual VSpace. Kernel, noncanonical, stale, overflowed and partly inaccessible spans reject. Mapping validation, packet admission, native effects and output publication share one existing process-lifecycle exclusion interval. All allocation and fallible output checks precede native delivery. Destination input is snapshotted before outputs are written. No userspace pointer, borrowed descriptor, receiver-selected CSpace or ambient allocator/provider authority enters retained custody. Hosted raw-pointer dispatch is refused; safe codec/object tests and actual CPL3 tests provide distinct evidence. Existing CALL/REPLY semantics remain unchanged. ### Acceptance and rollout Literal packet fixtures, arithmetic/malformed negatives, complete and draining returns, spare destinations, repeated collection, exact-owner refusal, revoked bindings, fresh mapping checks and real CPL3 request/capability round trips must pass. Existing unit and VM regressions remain mandatory. Producers and consumers select original signed commit pins after strict validation. Realm lifecycle and complete in-guest builds remain separate gates. A peek/sizing syscall is avoided by admitting capacity; numeric identities never bypass native ownership checks. [kernel]: https://git.erikinkinen.fi/erix/kernel/issues/11 [ipc]: https://git.erikinkinen.fi/erix/lib-ipc/issues/1 Shared owned-invocation checkpoint — 15 September 2026: Define owned invocation packet codecs and immediate syscall transport, preserving complete raw custody metadata and the existing hosted transport refusal. Owned invocation wire and native acceptance — 15 September 2026: Signed Kernel `5f497adaefa526108a0439e0e071717dddb85334`, shared IPC `de968da19898bef532ddb3b5974bb9562f51dee5`, capability ABI `a001a26f0eb3aebec3f5fd02a28d98f1bc23f8a0` and Integration `9030b217c490db6ad3ec60a799cb025eccbfcdb1` implement and exercise the immediate owned invocation boundary. Destination capacity and descriptive receipt capacity are independent; spare capacity acquires no authority and repeated collection cannot duplicate transfers. The real three-process CPL3 scenario passes all eight operations, full-span pointer/rights/overflow/reserved-field rejection, actual returned selectors, payload/capability/origin checks, collection after server exit and repeated receipts. A second request rejects premature relinquishment, enters draining on caller release and retires only after the exact server acknowledgment. All 162 maintained Integration helper commands pass; three prior correct concurrent-run lock refusals are retained and their sequential checks pass on unchanged executable inputs. Current full-suite acceptance remains open, as does the intermittent quota cause in Integration issue 18. Reachable backend disposal-failure coverage, broader revocation/generation-reuse scenarios, producer adoption, realm runtime, complete authority/inline-documentation audits and both full EriX-in-EriX build generations remain open. Typed realm bootstrap installation design — 15 September 2026: The next bootstrap producer step requires validating the actual moved install grant against the intended child before any installation. Add Kernel-control operation 52, INSTALL_WITH_GRANT_FOR_PROCESS, using the existing fixed request/reply envelope: flags and arg3 are zero; arg0 packs grant slot in bits 0..31 and source slot in bits 32..63; arg1 packs child destination slot and exact requested rights; arg2 packs nonzero process ID and nonzero staged generation. Both response values remain zero. The operation is admitted only where grant installation is already allowed (process-control and child-population endpoints, with existing bootstrap control policy preserved). The held unique grant remains the authority; the supplied process/generation pair is an additional equality constraint, never a target-selection grant. Revalidate exact native grant binding, GRANT possession, child/staged identity and current staged liveness, slot and type/rights ceilings, actual source binding and empty destination before transfer. Unlike legacy zero-means-inherit installation, this operation always uses the exact supplied rights, including zero. Reject nonzero reserved input and zero identities deterministically; mismatched target identity must produce no installed alias or new revocation lineage. Keep old producer semantics unchanged until explicitly migrated. Share the native installation implementation and split the existing near-1000-line control dispatcher by responsibility. Tests must use actual moved install grants for distinct staged children, wrong/stale generations, occupied destinations, explicit zero rights, invalid fields, denied endpoint policy, preserved source/grant custody and native lifetime/revocation behavior. Connect the new checked operation to typed Procd bootstrap provisioning; a standalone scalar codec or host-only table is not realm runtime acceptance. Complete receiver readiness, setup-authority disposal, fair terminal/provider scheduling, two-realm byte I/O and both full guest builds remain required. Process-bound native acceptance — 15 September 2026: Signed Kernel `60da5858d7198185efd103f0e91e5ac2e0b63e67` implements control operation 52, checking the actual moved install grant against expected process/generation with exact rights, including zero, under existing endpoint policies. Signed Procd `f1105706cc19ed024a6cca79a29abc57c90c6661` uses this operation in its actual ordinary launch-description producer while retaining the narrow SEND receipt, pending state and exact failure cleanup. All 162 Integration helpers pass after updating the exact policy assertion to require the new marker; its initial mismatch remains recorded. Typed realm bootstrap, mediator startup/readiness/configuration/seal, complete consumer image adoption, fair terminal/provider retirement, broader native disposal failures and both full EriX-in-EriX build generations remain open. The new inventory covers 76 repositories, 2,950 code files below 1,000 lines and 158 direct missing_docs crate-root gates; complete inline documentation and whole-codebase authority closure remain open. The mediator class cannot use ordinary start, immediate commit, TTY provisioning, powerbox installation or automatic restart. Procd has forty native binary builds and six new mediator refusal/cleanup regressions. No Posixd executable or coordinated realm VM acceptance is claimed. Actual grant-return provisioning, authenticated caller ownership, typed startup memory/inventory, readiness, configuration/seal, client I/O, fair retirement, complete consumer image adoption and both full guest build generations remain open. ### Native bootstrap destination correction — 15 September 2026 The temporary endpoint destination is now child-local slot 4, after the mandatory CSpace, VSpace and TCB roots in slots 1–3. This proves the constructor boundary; coordinated mediator startup, seal, client I/O, retirement and full guest builds remain open. Actual grant-return provisioning, authenticated receiver readiness, configuration/seal, client I/O, fair retirement, whole-codebase authority/documentation closure and both complete guest build generations remain required. No runnable Posixd realm or guest-build acceptance is claimed. Native producer/consumer migration, matching VM execution and full guest builds remain separate acceptance gates. The existing held Process or Root route remains required; descriptive identities do not grant authority. An absent or different generation acknowledges absence of only the requested instance, with zero response values; it cannot mutate a replacement. Required evidence includes exact wire and reserved-field controls, actual-object generation/reuse and failed-release controls, consumer cleanup tests, and bounded CPL3 native coverage. Ordinary mediator start, whole-image admission and both complete builds inside EriX remain separate open gates. Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain separate open acceptance requirements. The native pending caller must match a retained running Launchd generation. The actual sole receipt must be INSTALL_GRANT with exactly GRANT|MINT. Previously guarded, started, stale, ordinary-role and malformed stages refuse before new effects. Use the real returned grant and native operation 53 to narrow the Created child's primary endpoint to RECV. Establish an ancestor SEND branch under Kernel lifetime custody and a distinct nested explicit revoker before any export. Lost reply, rollback, abort, supervisor loss and terminal cleanup must account for every reused scratch column, actual guard and exact child identity. Counted final receivers/configuration, owned fair intake/provider/retirement progress, private execution, authenticated readiness, initial receiver disposal, seal/publication, real two-realm client I/O and both complete builds inside EriX remain required. Host models or this guarded stage acknowledgment cannot substitute for those acceptance gates. Native consumer and producer adoption remains open. Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain separate open acceptance requirements. No grant is constructed, copied, attenuated or retargeted. Malformed register shape rejects before context lookup; caller/window checks precede source lookup, then type/binding checks precede empty-destination admission. Ordinary validation refusal leaves inventory unchanged. Literal register, foreign/terminal caller, missing/fake binding, occupied destination, exact-rights/scope and actual CPL3 controls are required, followed by coordinated producer/consumer adoption and the remaining realm VM gates. Literal selector and hosted refusal controls pass. Signed Kernel 56d398e0 passes both actual native VMs, including thirty-nine new CPL3 relocation controls; service consumer adoption remains open. Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain separate open acceptance requirements. Owned receiver request-budget contract — 18 September 2026: Extend register-only REGISTER (0x4C) to take the actual local RECV slot, maximum request payload bytes and maximum request capability count in arguments 0–2; arguments 3–5 remain zero and successful RDX is zero. The byte/slot/receipt receive layout must be addressable and capability capacity must fit native private CSpace storage. The actual Running generation and held generic RECV endpoint remain the registration authority. SUBMIT compares actual payload length and capability count against that exact registration before request allocation, private-space reservation, native transfer or invocation serial acceptance. These budgets describe service-owned receiving storage; they add no global CALL-size ceiling, user-pointer retention, foreign selector or capability grant. Literal malformed/zero/exact registration controls, rejected-inventory checks, actual CPL3 calls and existing VM oracles are required. Actual consumer VMs, complete fair realm progress and both full guest builds remain open acceptance requirements. The shared RequestBudget and REGISTER shim require explicit byte and capability limits. Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain separate open acceptance requirements. Existing launch-description staging may be reused only with explicit exclusive ownership and proved completion of its former cleanup; add no broad Process authority or per-realm scratch column. Numeric identity or receipt metadata never replaces actual possession or scope validation. The running service loop must give native retirement a turn before owned bootstrap and ordinary intake. Complete every independent local and child retirement action before relinquishing bookkeeping; uncertain cleanup cannot return a service to ordinary work. Success requires a canonical correlated result, actual source-grant absence and complete invocation retirement. Preserve ordinary start refusal until realm configuration, readiness and sealing are complete. Acceptance requires adversarial ownership/cancellation/partial-cleanup host controls, strict coordinated builds and real producer/consumer VM execution. The bootstrap request now carries only request/opcode/process/generation in exactly 16 bytes; removed source/destination selectors and the old 32-byte request are rejected. Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain separate open acceptance requirements. Both are nonzero only for the realm mediator role; both must be zero for every other role. Reject the obsolete 56-byte shape. The pair describes delegated lifecycle responsibility; numbers alone never confer creation, installation or rollback authority. Guard admission must match the original supervisor, never replace it with a later claimant. Caller RELEASE initiates cancellation and must precede any ordinary abort request that could wait behind Procd delivery retirement. Actual Launchd runtime preparation and scheduler adoption, deployment-sized ownership storage, adversarial host controls and real producer/consumer VM execution remain required. Materialization begin is exactly 64 bytes, with two full-width original supervisor words required for mediators and forbidden for other roles. Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain separate open acceptance requirements. Client numeric identities or a bearer sender cannot select ownership. The request carries exactly one actual SEND-only directory endpoint to the reserved receipt slot. Verify the original caller/job/session/authority realm again and retire every unretained received capability on refusal. Never imply a Posixd pathname, Named route, root, cwd, TTY stream, ordinary job or public PreparedProcess input. They require the same original Running native owner. READ observes retained state only; ABORT must complete independent source, invocation and exact-child retirement before its successful acknowledgment. Success at BEGIN requires Reserved, a nonzero complete handle and receipt slot. PREPARE success requires Guarded; ABORT success requires Retired. READ returns an authenticated nonzero state. Require an explicit deployment value: zero disables new realm reservations, and nonzero values allocate that many retained records and disjoint receipt slots. Coordinate shared startup codecs, Rootd payloads, Launchd arena and Integration policy/packaging; old version/width must reject. Actual scheduler progress must exclude ordinary and indirect blocking peer calls while any native invocation needs progress. A permanently discharged source slot is never revisited after reuse. Guarded staging remains private and unstarted, without exported SEND or a Running job. Coordinated host negatives, strict source-bound build matrices and real consumer VM execution are required. Two mediator processes, two clients per realm with actual mediated I/O, complete fair progress, source/effect/frame admission and both full builds inside EriX remain separate open acceptance requirements. Exact UTF-8 selectors borrow input without an extra pathname ceiling; full generational handles and cap-free responses require independent correlation. Descriptions confer no authority. Actual admission dispatch, coordinated consumer VMs, runnable mediators and both full builds inside EriX remain separate open acceptance requirements. </details> ## Tracking and rollout Original FAT/exFAT directory observations and the fixed-root scanner repair are signed and published: [lib-ipc `bebb7a74`](https://git.erikinkinen.fi/erix/lib-ipc/commit/bebb7a740d1eb665e7325e5c6f3a7a0ec501032d), [fatd `a5481166`](https://git.erikinkinen.fi/erix/fatd/commit/a548116665dcd8f9d19730904a75a0d3d7620b52), [docs `18270dc3`](https://git.erikinkinen.fi/erix/docs/commit/18270dc36c7e2f61b338c531b8422f856e5983cd), [integration `26a98467`](https://git.erikinkinen.fi/erix/integration/commit/26a9846747b9b022cff6f3260aa791745a5ad0d7). The independent [Integration helper `b0255273`](https://git.erikinkinen.fi/erix/integration/commit/b0255273ee25e85cc5a4a2d538d3e122b7b5de04) precedes final catalogs. The coherent closure contains 56 signed commits across 55 repositories, 206 Cargo selectors and 111 catalog selectors, with exact remote branch equality retained. Fatd observes directories through original live acquisition/root custody and actual retained dot parents. Physical slot positions preserve full-width input comparison. One admitted continuation per counted handle can skip previously parsed directory content; other seeks prove logical end and whole-name boundaries from the beginning. Layout mutations invalidate all mount aliases before effects, including exact-entry mutations and touch-created files. No cursor, cluster or handle becomes an inode identity. FAT/exFAT identities and unsupported POSIX metadata remain explicitly unavailable. Complete output capacity precedes optional atime writes; uncertain nontransactional publication retains fail-stop without a retryable refusal. End replay performs no media I/O. Shared scanning excludes fixed-root final-sector padding, resolving [Fatd #5](https://git.erikinkinen.fi/erix/fatd/issues/5). The complete [status and seekable-directory feature](https://git.erikinkinen.fi/erix/posixd/issues/25) remains open. Native wire contracts and scoped Vfsd mediation remain accepted. Complete provider POSIX metadata, compatibility stat families, shared readdir/tell/seek/rewind and remaining full-feature controls/publication are unfinished. Current accounting remains 17.96% weighted and 6.41% whole acceptance: 24/460 parents and 456/921 sub-items under 162 decomposed parents. This provider implementation closes no additional full sub-item. Both complete EriX guest-build generations and rebuilding external Rust/LLVM inside EriX remain required and unperformed. [Fatd directory contract](https://git.erikinkinen.fi/erix/fatd/src/branch/feature/posix-compat/docs/directory-observations.md), [shared observation contract](https://git.erikinkinen.fi/erix/lib-ipc/src/branch/feature/posix-compat/docs/seekable-directories.md), [descriptor/namespace feature](https://git.erikinkinen.fi/erix/posixd/issues/2), [Phase 6 master](https://git.erikinkinen.fi/erix/integration/issues/65). Reviews: [lib-ipc](https://git.erikinkinen.fi/erix/lib-ipc/pulls/2), [fatd](https://git.erikinkinen.fi/erix/fatd/pulls/3), [docs](https://git.erikinkinen.fi/erix/docs/pulls/4), [integration](https://git.erikinkinen.fi/erix/integration/pulls/12). Client scratch-column clarification — 25 September 2026: the original five-column design is implemented with C0 master, C1 receiver, C2 installer, C3 outer revoker and C4 temporary SEND. After independent master disposal, derive outer SEND into C0 and bind C3 into actual Procd lifetime; drop/query C4, derive inner SEND into C3 and inner revoker into C4, then drop/query C0. Begin retains C1 RECV, C2 GRANT, C3 SEND and C4 MANAGE. The authenticated first descriptor step follows Launchd’s original Begin RELEASE and drops/queries C1. Commit installs C3 into child slot5, drops/queries C3 and consumes/queries C2 through exact child-lifetime binding. Running custody retains C4; retirement visits C4 first. No sixth column or additional authority is added. [Procd's contract](https://git.erikinkinen.fi/erix/procd/src/commit/3b84f4b0155525876f1c79ca55171cddcb501adc/docs/realm-process-custody.md) describes source, recipient, rights and failure custody. Complete client lifecycle codecs — 25 September 2026: signed Lib-IPC `461634ed8981908b65bc84b94a774c309e371678` implements the published public configuration/client operations, private streamed client startup and distinct never-started disposal messages. Original identities, counts, operation-specific states and full digest correlation are checked; plan storage must fit the target allocation domain. These codecs establish framing, not native execution acceptance. <details> <summary>Detailed scope and contracts</summary> ### Counted realm client admission and lifecycle contract Reviewed shared design, 25 September 2026. This supersedes the earlier private client-provisioning inventory wherever its wording differs. It completes the proposed public Launchd and private Procd frames before shared implementation. It changes no maintained source and claims no runtime or VM acceptance. Integer fields are little-endian; all complete decoders reject missing/surplus bytes and unknown selectors. Every encoder preflights the complete shape before changing output. #### Existing source and authority boundary `lib-ipc/src/ids/realm_admission.rs` assigns only 0x6D0..0x6D4. The current Launchd `RealmOwner` authenticates the actual pending native caller against its original published Running job, process generation, session and authority realm. Every operation below repeats that proof and matches the complete original realm handle. No public request contains a native child, mediator, supervisor, controller, CSpace, install-grant or endpoint-object identity. Client handles are descriptive nonzero realm-local `(id, generation)` u64 pairs. Generations never wrap, and replacement rows never inherit an old generation. Only actual retained Loaderd/Procd results supply native pairs in RCF/RCS/private actions. The existing original-parent-loss sweep must cover every new owner. Public requests/replies have zero capabilities except PrepareClient's exactly one actual directory SEND COPY. Its destination is reserved by BeginClient; it is not chosen by request metadata. Malformed, surplus or refused receipts remain owned and are independently exhausted, including after the first cleanup error. Unique InstallGrant/RevocationGrant MOVE semantics remain unchanged. #### Public Launchd operation allocation and exact fields The common realm prefix is request_id u32@0, op_id u32@4, realm_id u64@8 and realm_generation u64@16 (24 bytes). IDs/generations and request_id are nonzero. The client prefix appends client_id u64@24 and client_generation u64@32 (40). These layouts preserve the existing realm handle convention. | Selector | Operation | Request bytes | Successful reply | | --- | --- | --- | --- | | 0x6D5 | BeginRealmConfiguration | 72 | realm40, Configuring=8 | | 0x6D6 | BeginRealmClient | 24 | client64, Reserved=1 | | 0x6D7 | PrepareRealmClient | 64 + selector bytes | client64, Guarded=3 | | 0x6D8 | AppendRealmConfiguration | 48 or 64 | realm40, Configuring=8 | | 0x6D9 | FreezeRealmConfiguration | 24 | realm40, Configured=9 | | 0x6DA | SealRealm | 24 | realm40, Sealed=11 | | 0x6DB | StartRealmClient | 40 | client64, Started=7 | | 0x6DC | ReadRealmClient | 40 | client64, exact retained state | | 0x6DD | RetireRealmClient | 40 | client64, Retired=10 | BeginConfiguration72 appends C/D/H/Q u64@24/32/40/48 and mediator request/result payload budgets u64@56/64. All four counts are positive (disabled bootstrap has no configuration). Use the existing counted-arena checks, including exact plan length `96 + 32*C + 24*D + 16*H`, representable counts/packet extents and enabled mediator minima 112/200. It reserves C actual client rows, their capability columns and the complete canonical-plan byte extent from explicitly supplied storage before any client authority is admitted. Q is the later mediator ring extent, not a new Launchd allocation. Reject insufficient storage with explicit RESOURCE_EXHAUSTED before mutation; reserve atomically. Admission requires this original mediator to be Guarded and no prior configuration to be in progress. BeginClient24 names only the realm. It allocates one of that reservation's C client records and returns the new handle plus its exact empty scope destination. The C records are the declared membership of this immutable configuration, not an additional protocol ceiling. No native CREATE occurs during reservation. This is one initial client set: a retired member's outcome is retained and that record cannot be silently replaced before or after freeze. If a member retires before the complete initial set can be frozen, the caller retires this realm and may reserve a fresh generation/configuration. Later dynamic process spawning is a separate protocol; no such behavior is claimed for this initial configuration. PrepareClient appends client request/result budgets u64@40/48, selector byte length u64@56 and nonempty UTF-8, NUL-free selector bytes@64. Minimum client budgets are 40/32; checked length arithmetic introduces no new path/count cap. The actual implementation reports exhaustion for unavailable declared scratch or existing provider limits, rather than truncating. Require Reserved state and one actual SEND-only directory receipt in its previously reserved slot. Resolve the exact executable through this scope; independently dispose the scope before private Loaderd preparation. Retain exact private materialization, returned grant and original child cleanup before interpreting subsequent failures. Success means the original client is guarded/unstarted, with its zero-right slot4 and install-grant custody retained; it does not install RCS1 or start I/O. AppendConfiguration appends one global ordinal u64@24 followed by one record@32: | Ordinal interval | Public record | Whole request | | --- | --- | --- | | `[0,C)` | client_id u64@0, client_generation u64@8 | 48 | | `[C,C+D)` | client_id u64@0, client_generation u64@8, fd i32@16, access u32@20, channel_index u64@24 | 64 | | `[C+D,C+D+H)` | channel_index u64@0, capacity u64@8 | 48 | Record kind derives only from the retained counts and ordinal; no standalone 48-byte parse may claim it distinguished client/channel data. Provide a structural frame plus `parse_with_counts` or equivalent typed counted admission. Only the next ordinal is admitted; skipped/replayed/surplus records reject without effects. Client order is the caller's declared order, not identity sort order. Resolve full owned public handles to original Guarded native pairs and canonical indices. Descriptors use nonnegative fd, access Read=1 or Write=2 and channel index < H; channels are canonical index order with nonzero capacity. Checked capacity sum must equal Q. All C clients must appear exactly once; native/public pairs and `(client,fd)` are unique; every client/channel has a binding. Retain incremental failures and full final validation before freezing. All record bytes are copied to owned storage before the immediate packet is reused. Public request_id is correlation, not cross-invocation deduplication. Freeze24 requires exactly C+D+H admitted records, complete uniqueness/coverage, exact channel-byte sum, all original client stages and zero uncertain custody. It generates native identity fields exclusively from those owners, encodes the existing exact RCF1 plan, hashes all its bytes, and makes plan membership/order, budgets and digest immutable. There is no public plan digest or native identity nomination. Refusal cannot replace partially retained resources or another plan. Existing START 0x6D4 remains 40 bytes and returns PrivateReady=7. For a configured realm it requires Configured, and both supplied budgets must equal the reserved plan's budgets. It provisions the mediator, learns actual Procd context, provisions/commits every client's RCS startup while all clients remain stopped, and starts the mediator with its configuration service. Bootstrap-only behavior and its minimum96 budgets remain unchanged. PrivateReady is not Sealed. Seal24 requires that configured original realm, advances existing authenticated Probe/Prepared and Commit/Sealed with independent caller/delivery/source disposal, and returns Sealed only after both sides' original owners retire. While pending, ReadRealm may report the added Sealing=10 state. Client Start requires Sealed, the original provisioned client and all applicable setup/caller retirement. Started acknowledges exact native START; it makes no liveness guarantee and does not invent a client Ready/Challenge. ReadClient reports later actual state. #### Replies, states, errors and outcome custody The existing realm reply40 is unchanged: request/op/result/state u32@0/4/8/12, realm_id/generation u64@16/24, scope_receipt_slot u32@32, reserved-zero u32@36. All new realm operations require slot0 and their exact successful state; Read recognizes added states. A refusal preserves raw nonzero result, Unconfirmed=0 and full requested realm handle. Helpers compare original request/op/full handle. Client reply64 is request/op/result/state u32@0/4/8/12, realm_id/generation u64@16/24, client_id/generation u64@32/40, scope_receipt_slot u32@48, terminal_kind u32@52, terminal_status u32@56 and reserved-zero u32@60. Client states are Unconfirmed=0, Reserved=1, Preparing=2, Guarded=3, Provisioning=4, Provisioned=5, Starting=6, Started=7, Terminal=8, Retiring=9, Retired=10. Only successful BeginClient has nonzero scope slot. Failed Begin echoes the full realm but zeroes the client pair; all later replies echo the full original client pair. Failures use Unconfirmed and zero slot/kind/status; they never claim cleanup. Operation-specific success matching prevents substitution. Read/Retire can carry kind1 Exited or kind2 Killed with every u32 status bit preserved, exclusively from the original authenticated Procd observation. States other than Terminal/Retiring/Retired require zero kind/status. Terminal requires kind1/2. Retiring may retain an already observed event; Retired may echo it, or kind/status0 for positively established never-started disposal. Zero is not implicit Exited(0). Begin/Prepare/Start acknowledgements carry no terminal fields; a process that exits immediately after START is observed through Read. Numeric metadata never changes the native event's original process generation internally. Retire is valid for every admitted client phase, selecting only that exact retained record. Its successful acknowledgement requires all applicable mediator binding disposal, actual native child and capability-lineage retirement, resolved native caller/delivery owners, and retained then acknowledged final CPU accounting. An actual native terminal observation precedes a kind5 notification; proven never-started native destruction precedes a kind7 notification. No ordered list of completion gates substitutes for either required producer proof. Unknown cleanup remains owned; NOT_FOUND alone proves no prior disposal. An unstarted child uses the distinct authenticated disposal notification below. An uncertain START cannot use the never-started shortcut. Keep client outcome records in their counted reservation until realm retirement, so Read remains useful after individual Retire. No extra public ACK operation is needed. Public COMPLETE transfers an immutable cap-free scalar result to the original caller-owned invocation; it does not prove that caller RELEASE occurred. The caller collects/validates then retires that owner before its dependent next step. No result points into a subsequently reused row. Realm/global row reuse requires all actual resource/caller/serving owners retired and preserves every nonwrapping generation. A caller that discards an unknown result cannot treat a fresh NOT_FOUND response as proof its old operation completed. Use existing full-width status meanings: INVALID_ARGUMENT for malformed scalar or count shape; DENIED for wrong actual origin or receipt authority; NOT_FOUND for no matching original handle; CONFLICT for incompatible retained transition; BUSY/RETRY for explicitly pending resource/operation progress; RESOURCE_EXHAUSTED for supplied storage; INTERNAL for malformed native evidence. Failed mutation does not erase prior effects; no accepted native invocation is blindly replayed. #### Remaining private Procd operations The published BeginClient88 0x43C and LoaderClient340/176 0x655 remain unchanged. The generic Begin64 rejects client role0x449; generic STOP remains unavailable. | Selector | Operation | Request/reply | Successful disposition | | --- | --- | --- | --- | | 0x43D | BeginClientProvision | 96/176 | ClientProvisioning=6 | | 0x43E | AppendClientDescriptor | 88/72 | ClientProvisioning=6 | | 0x43F | CommitClientProvision | 64/72 | existing Provisioned=1 | | 0x440 | StartClient | 64/72 | existing Started=2, native START only | | 0x441 | RetireClient | 64/72 | existing Retired=3 | Begin96: request/op u32@0/4; client process/generation u32@8/12; realm pair u64@16/24; mediator process/generation u32@32/36; client request/result budgets u64@40/48; Dclient u64@56; plan SHA256@64..96. Require Dclient>0 and40/32 minima, original actual Launchd, exact retained client/mediator relation and the mediator's retained plan/controller context. Input is one exact GRANT-only InstallGrant MOVE. Reply176 is request/op/result/disposition prefix16 plus the producer-selected RCS1 header160 and one exact RECV-only Generic endpoint COPY. Failure has Unconfirmed, zero160 tail and zero result capabilities. Correlation checks every request-supplied RCS field; actual controller additionally matches the original ContextProbe. A distinct header-prefix/count API must not claim the absent descriptor records were parsed or globally validated. Append88: request/op/client pair/realm pair prefix32, plan SHA256@32..64, ordinal u64@64 and descriptor16@72 (fd i32, access u32, reserved u64zero). Only next ordinal is admitted. Existing action reply72 compares complete request/op/client/realm/plan; the caller retains original ordinal through retirement. Commit/Start/Retire reuse action64/72 and exact per-selector success matching. Commit and Start use the complete RCS startup digest; Retire alone permits zero as unknown-startup sentinel, omitting only digest correlation. Retire covers Begin never claimed, malformed/uncertain Begin, partial descriptors, Commit failure and post-start. AbortStaged is only a known pre-Begin fallback. Commit requires exactly Dclient records and complete header-plus-record hash, final RO/NX startup and RW/NX packet mappings, guarded SEND installation at client slot5, lifetime custody, and original Procd RECV source drop plus separate query proving absence. These are actual gates, not deferred prose obligations. Client slot4 remains zero-right; ordinary client messages transfer no caps. Complete startup extents, packet arithmetic, page rounding and native CSpace capacity are checked before backing/transfer effects. No implicit producer cap. The Begin receiver COPY does not consume its source. Launchd must collect, validate/census its actual receipt and retire the original Begin caller before Append. That next authenticated original request acknowledges the sequencing boundary; COMPLETE alone cannot report peer RELEASE. Procd then drops and independently queries its original RECV source before Commit succeeds. Launchd retains its copied receiver through RCP transfer, mediator Prepared and its own original delivery retirement, then drops/queries it before seal. All uncertain original/prospective ownership is retained across refusal and cancellation. Existing five Procd columns can implement client custody without new authority: master/grant/RECV/ancestor-SEND/ancestor-revoker, then only after acknowledged master/ancestor-revoker disposal reuse their columns for inner revoker/SEND. Inner revocation remains retained, outer lineage binds actual Procd lifetime. This allocation must be verified by native effects and query evidence, not inferred from numeric slot descriptions. Cleanup visits the inner revoker first. Procd validates scalar records, ordinal/count and full incremental startup hash. It must not claim arbitrary-order fd uniqueness without counted scratch. Launchd validates complete RCF; Posixd validates actual collected rows; the client parses complete RCS1 and validates descriptor uniqueness before I/O. Preserve caller sequence; do not add a sorted-fd restriction. Existing final CPU READ32 0x437, ACK64 0x438 and response64 cover clients after actual relation/origin admission; their scalar codecs remain role-neutral and preserve exact-generation snapshots. #### Distinct unstarted-client disposal control Extend RSC1 with ClientDisposed=7 / ClientDisposedAck=8, each exactly112 bytes. Keep existing header/context/plan offsets: request_id u64@16, context40@24, plan digest32@64. Append original client process/generation u32@96/100 and reserved-zero u32@104/108. Use a distinct typed disposal payload; do not create a ProcessTerminalEvent with kind0. Existing kinds5/6 still require actual Exited or Killed and preserve every status bit. Requests result0; replies preserve raw nonzero refusal. All request/op/context/digest/client fields correlate exactly. Only the actual retained Procd controller may submit disposal, after proving exact never-started child destruction and required native cleanup. Scalar parsing does not grant that authority. Posixd closes the exact client's bindings once, decrements channel references once, and independently retires its receiver and pending delivery before success. It can admit this before or after seal once the original row exists. If configuration is in flight, retain the original obligation and prevent later client-row admission from resurrecting it; wait for the matching retained row or cancel/clean the affected configuration. Absence or an unregistered receiver is not a successful disposal acknowledgement. Uncertain START uses exact running termination/native event custody, never this shortcut. #### Explicit Launchd deployment storage successor Current `lib-bootstrap/src/payload_launch.rs` is LCH1 version3,72 bytes, with realm_capacity u32@68 and four columns per realm. It cannot describe the new client rows or canonical-plan pool. Define LCH1 version4,88 bytes, preserving all preceding offsets and appending realm_client_capacity u64@72 and realm_plan_byte_capacity u64@80. Both zero explicitly disable configured clients while preserving bootstrap-only realms; enabled mode requires both positive and realm_capacity>0. Reject mixed zero, legacy version/width and unknown extensions; do not reinterpret old reserved bytes or supply implicit defaults. Reserve actual non-Copy client rows by the compiled target layout and a separate counted byte pool for exact canonical plans. Two disjoint columns per client: scope/grant column reused only after scope query-absence and original callers retire, plus distinct prospective ingress-RECV destination. The original grant MOVE and receiver COPY can therefore overlap without slot alias. Never borrow ordinary intent/manifest bytes or a new endpoint/VSpace/factory capability. Existing shared exact-executable scratch remains serialized by its owned gate. Update checked startup geometry, native target arena sizing/layout transcript, capability interval validation and Integration's deployment config/graph/image producers together. Required columns include old job/stream/realm terms plus checked `2*realm_client_capacity`; every interval fits the actual declared window. Counts are constrained by supplied resources and checked addressing, not a hidden protocol maximum. Plan allocations and row reservations are retained until full realm teardown, and exhaustion must not steal another realm's rows. #### Intake budgets, witness and required controls Public native intake must retain a complete PrepareClient prefix plus the actual selector, one prospective directory receipt, and reply64; other public frames need at most72 request/64 reply with no caps. Use actual supplied packet/scratch capacity and explicit exhaustion, not a new selector constant. Private Loaderd needs340/176 and its original grant receipt; Procd needs max112 request/320 reply for counted mediator Provision and new Begin96/reply176 with one grant/RECV; RCP needs112 request/200 maxreply with client-only oneRECV; RSC needs112/112, ordinary client I/O uses explicit >=40/32 and zero caps. Audit both native registration budgets and packet/receive layouts; a codec size alone is not proof. Use a dedicated small native realm-byte-client binary in the Posixd package, consuming only RCS1 and slot5 ordinary byte IPC. No new crate, shell startup, clock/log/TTY/filesystem/completion authority is needed. Exsh remains the orchestrator using public owned handles, ReadClient and exact exit outcomes. Descriptor numbers distinguish deterministic reciprocal roles without argv. The witness has two realms, two clients and two channels per realm, four total descriptor bindings per realm, small explicit rings forcing short progress, independent realm-B traffic after realm-A retirement and exact stale/cross-origin refusals. Do not put a foreign SEND into an ordinary client for a negative test. Required host controls: all exact offsets/lengths/count overflow, preserving output, public handle/op substitution, no native nomination, wrong actual parent, receipt surplus/prospective custody, skipped/replayed ordinal and wrong record kind/length, unsorted valid client/fd sequence, uniqueness/coverage/channel sum, late count/byte exhaustion with no effects, immutable plan, START budget mismatch, pre-seal client START refusal, full-width terminal status, original outcome after Retire, lost public/native result, pending disposal before row admission, uncertain START refusing unstarted shortcut, source drop/query failures, all generation reuse and full final CPU ownership. Native validation must cover COPY/source retirement, two-sided seal, real four-client byte progress, exact terminal/disposal forwarding and repeated cleanup. All remain acceptance work. #### Implementation footprint and remaining review boundary Shared IPC adds thematic public client/configuration modules and focused tests, private provisioning/header-prefix helpers and exact action/disposition updates, plus the distinct disposal payload. Bootstrap adds only the explicit v4 storage successor and geometry controls. Loaderd already has published private client selection; Procd and Launchd implement retained custody from the exact originals. Posixd adds disposal control and its dedicated fixture binary; Integration adds only opt-in packaging/alias/graph/config/scenario support and target geometry. The two-column Launchd/five-column Procd assignments require actual native proof in consumer tests; their arithmetic is not such proof. Public Read retention requires actual final outcome ownership and must not be faked by current PID lookup. Counted pool allocation and generation preservation need meaningful reuse tests. These are implementation/validation duties, not additional unnamed wire operations or accepted behavior. Full original realm/mediator correlation is preserved before native creation; legacy Begin64 rejects the private client class. Native execution acceptance remains open. Private client materialization contract — 24 September 2026: the existing materialization-begin frame carries only the supervisor pair. Role recognition alone cannot bind an actual client to its intended mediator before native creation. Use distinct private operations with explicit descriptive correlation, authenticated through the existing Loaderd and Launchd routes; no new capability or ordinary-launch fallback is introduced. Loader `PREPARE_REALM_CLIENT` (`0x655`) is exactly 340 bytes: retain the existing 316-byte exact-executable selection offsets, then realm ID/generation u64 at 316/324 and native mediator process/generation u32 at 332/336. Its distinct 176-byte reply retains the existing 152-byte result/grant/digest fields, then echoes the complete relation at 152/160/168/172 on both success and refusal. Existing failure-zero rules still apply to staged/grant IDs and digest evidence. The old 316/152-byte parsers reject this selector. The exact executable SEND retains COPY semantics and independent source disposal; the staged install grant retains MOVE semantics. Procd `BEGIN_REALM_CLIENT_MATERIALIZATION` (`0x43C`) is exactly 88 bytes: existing 64-byte begin field offsets, then realm ID/generation at 64/72 and native mediator process/generation at 80/84. Require private role `0x449`, the original nonzero Launchd pair, and nonzero relation scalars. Generic Begin64 must reject role `0x449`; mediator Begin64 remains unchanged. The existing 36-byte noncommit reply recognizes the new selector and echoes request, operation and original transaction, with zero materialization and staged IDs. Encoding preflights the complete request; neither decoding nor scalar correlation authenticates the native origin. Before client CREATE, Procd authenticates actual Loaderd and the retained running Launchd, resolves the exact original Guarded and unstarted mediator, and checks the same supervisor. Because the final plan digest includes actual client generations, the first admitted client request may bind a previously unbound mediator to that realm pair before creation. Retain this first binding even if client creation later fails. All later client requests and counted Provision must match it. Reject the same realm pair on any other retained mediator belonging to that supervisor, including retirement or uncertain cleanup. Bootstrap-only Provision can still perform the first binding when there are no clients. Preserve the actual parent/mediator/client relationship through active materialization, staged commit, rollback and terminal custody; numeric realm metadata grants no authority. Client startup, ingress installation, complete configuration, authenticated seal, source disposal and native caller retirement remain separate gates. Clients cannot start until committed seal and its caller retirement are proved. The required two-realm/four-client byte-I/O and cross-realm refusal witness remains open. This is the implementation contract; it adds no native or phase acceptance. Actual producer/consumer adoption and the native configuration/seal/client-I/O witness remain open. Wire precision for configuration and seal — 24 September 2026: `RCP1` version1.0 uses Pull=1 and Reply=2. Its 96-byte common header is magic/version at0/4/6, kind u16 at8, zero flags u16 at10, raw result u32 at12, nonzero request u64 at16, complete realm context at24..64 and configuration SHA-256 at64..96. Requests require result0 and add ordinal u64 at96 plus reserved0 u64 at104. Replies echo ordinal at96. The validated plan counts and ordinal determine the one allowed record kind and exact length; payload length alone never selects policy or capability count. Preserve declared client and descriptor record order; require unique public/native client pairs and unique client/descriptor bindings without imposing numeric identity order. `RCS1` version1.0 has the160-byte header already specified: magic/version at0/4/6, header size/flags at8/12, total bytes16, realm pair24/32, native client40/44, mediator48/52, Procd56/60, CSpace count64, ingress slot72, zero-right placeholder slot76, request/result bytes80/88, workspace address/length96/104, configuration digest112..144, descriptor count144 and reserved0 u64 at152. It fixes the intended SEND at slot5 and the zero-right placeholder at4. At least one initial binding is required, matching the plan's coverage rule. Request/result minima are40/32 bytes, derived from the actual Read/empty-Write request and QueryAbi/Write/error reply framing. These minima guarantee framing only. The count and every packet/mapping extent are checked; the consumer independently verifies actual mapping, rights and inventory. Descriptor records preserve plan order and contain no duplicate fd. `RSC1` version1.0 shares the96-byte common header offsets above with its own magic and kinds SealProbe=1, Prepared=2, SealCommit=3, Sealed=4, ClientTerminal=5 and ClientTerminalAck=6. Request results are zero; replies retain raw application result words. The first four kinds are exactly96 bytes. Both terminal request and acknowledgement are exactly112 bytes: original native client process/generation at96/100, native terminal kind/status at104/108. Only the existing Exited/Killed terminal kinds are valid; all32 status bits are preserved. Acknowledgements echo the entire terminal description even on refusal. All replies correlate exact kind, request, context, digest and optional terminal description. Descriptive decoding does not authenticate Procd or prove cleanup. Private Procd PrepareSeal and CommitSeal use operation selectors0x439/0x43A with the existing64/72-byte action framing. Their digest is the canonical configuration digest, with all bit patterns valid; there is no unknown-digest sentinel for these operations. Successful dispositions Prepared=4/Sealed=5 are operation-specific; every refusal uses Unconfirmed=0. Start and Retire retain their existing startup-digest semantics. REALM_CLIENT is the distinct0x449 process class and cannot enter ordinary launch/start/restart policy. Canonical record indices need not equal physical runtime row positions. Before serving, Posixd may move whole owned client rows while retaining each canonical client index, check public/native pair uniqueness by sorting, then use native-pair order for lookup. Each move retains all receiver custody. Descriptor references use canonical indices; result regions are assigned after the final order and before any delivery or I/O effect. No sorting is permitted during serving. This avoids new arena allocation and repeated quadratic validation in the I/O path. Configuration must still prove all uniqueness, binding and channel-coverage invariants before admission. No runtime acceptance is asserted by these codecs. Counted realm codecs — 24 September 2026: signed Lib-IPC `ef30dcca67f43e8491e30cca7e62fab0c60e1681` adds strict counted arena geometry, RBS1 minor1, the Provision successor, authenticated-layout binding framing and repeatable final-accounting READ/ACK framing. It separates absolute address bounds from slice-length bounds, preserves complete counts/digest correlation and rejects retired layouts. Signed Lib-PosixABI `eb00744d7811bb1174a1cfc34cfe062724dfd8e2` supplies the capability-free 1.1 Read/Write/Close codec. Four strict local configurations each pass 83 unit/integration tests and three doctests; GCC/Clang C checks pass. Original CI19/20 now passes with four complete logs, 112,014 bytes and zero warnings or failures. [Byte-I/O review](https://git.erikinkinen.fi/erix/lib-posixabi/pulls/3) remains WIP. Docs `69840bd8ca4aaea2a098d5d85cbea2d5614f7067` and original CI1069/1070 pass the 45 manual controls and full 2,499-page manual, with zero final warnings. These are library and documentation checkpoints. The accepted native startup still uses its previously recorded revision graph. Counted configuration, seal, actual client byte I/O and final-accounting consumer adoption require the next coherent graph and new native evidence; no runtime or whole-phase acceptance is added. Full EriX builds and an external Rust/LLVM rebuild inside EriX remain required and unproved. **Configuration opcode documentation correction.** Signed [`d4d32115`](https://git.erikinkinen.fi/erix/lib-ipc/commit/d4d32115b8cc446a337de3f12d31016df6ad624d) corrects the public Provision opcode's remaining rustdoc to describe a copied configuration sender. All executable Rust, tests and dependency inputs remain byte-identical to the preceding checkpoint. Fresh format, private rustdoc, Markdown and diff checks pass without warnings; the prior strict four-profile main and shim matrices are reused for the unchanged executable inputs. Both original CI runs pass: [377](https://git.erikinkinen.fi/erix/lib-ipc/actions/runs/377) and [378](https://git.erikinkinen.fi/erix/lib-ipc/actions/runs/378). All four complete terminal job logs total 554,488 retained and hash-verified bytes, with zero warnings or failures. Each test job reports 957 passing tests across its configured selections and two existing ignored cases. No workflow was rerun. This is a documentation correction and requires no runtime consumer repin; [Docs `69840bd8`](https://git.erikinkinen.fi/erix/docs/commit/69840bd8ca4aaea2a098d5d85cbea2d5614f7067) selects this exact source for the regenerated API reference. The separately accepted native startup witness remains recorded in [Integration #89](https://git.erikinkinen.fi/erix/integration/issues/89) and [Launchd #7](https://git.erikinkinen.fi/erix/launchd/issues/7). Counted client configuration continuation — 24 September 2026: Proposed coordinated continuation: configure each private Posixd instance with two actual staged clients and mediator-owned bounded byte channels. Preserve the existing startup/control handshake and native identity checks. Configuration is canonical, counted and digest-bound; labels select already held owners and never confer authority. This is a first nonblocking byte-I/O slice. Full filesystem/TTY configuration, complete POSIX semantics, libc, all resource-retirement criteria, rebuilding Rust/LLVM inside EriX and both complete EriX guest builds remain required later work. Add strict versioned startup/Provision successors for the counted client/descriptor/channel/ring policy and canonical plan digest, coordinated across producers and consumers. The proposed startup has a 224-byte header, two 24-byte endpoint records and one 32-byte workspace record, totaling 304. The canonical plan is `96 + 32*C + 24*D + 16*H` bytes. Its digest excludes RPC correlations and recipient-local slots, while including the exact realm and mediator pair; client native pairs come from original staged owners. The configuration pull header is 96 bytes; ordinal requests 112, refusal 104, successful header/client/descriptor/channel replies 200/136/128/120. Exactly client replies copy one RECV capability; other replies and ordinary calls have no capabilities. Keep Ready/Challenge framing capability-free. Separate SealProbe/Prepared from SealCommit/Sealed and exact ClientTerminal/Ack controls, authenticated against native Procd origin. Prepared requires final configuration caller retirement and child SEND disposal. Commit follows Launchd's independent source/delivery cleanup. Lost seal replies cannot authorize client Start. Fixed client startup is `160 + 16*Dclient` bytes with exact digest, original identities, supplied workspace/budgets and one intended ingress SEND. Retire replaced startup codecs after coherent adoption; reject unsupported versions/reserved fields rather than maintaining implicit fallback. RBS1 minor1 preserves the first128 header bytes, appends C/D/H/Q u64 at128/136/144/152, configuration SHA-256 at160 and layout SHA-256 at192. Provision successor0x436 is112 bytes: the existing48-byte prefix followed by counts32 and configuration digest32. Its320-byte reply is the16-byte result prefix plus304 startup bytes; refusal zeros the tail. Counts are all zero for the bootstrap-only mode or all positive for configured storage. Result/receipt capability budgets are one only for configuration-bearing replies; Ready, Challenge and client calls remain zero-transfer. All size, alignment, page-rounding, packet/receipt and ordinal arithmetic must be checked before native effects. Authenticate target geometry through the existing selected-image path. Posixd exports one immutable 96-byte target-generated descriptor in read-only file-backed ELF load storage: magic16 `ERIXPXSCAPLAY001`, then ten little-endian u64 words for version1, total size96, ELF machine, pointer bits, and client/descriptor/channel row size/alignment pairs. Sizes are nonzero and alignments powers of two; target fields match the selected executable. Loaderd extracts exactly one complete descriptor from its already authenticated root ELF bytes, refusing missing, duplicate, malformed or writable records. No host-derived type size or reopened pathname supplies geometry. An exact 144-byte BindRealmLayout request uses the existing authenticated LoaderMaterialization route: request/op u32, original active transaction u64, root ELF SHA-25632 and descriptor96. Its response uses the existing 36-byte materialization shape with zero noncommit materialization/staged fields. Procd accepts it only from actual Loaderd for that original active mediator transaction, retains the description through staged commit/rollback, and requires it before mediator commit. The startup carries the descriptor SHA-256, which Posixd compares against its own compiled descriptor before any typed arena borrow. Canonical checked sizing partitions client rows, descriptor rows, channel rows, plan bytes, ring bytes, retained per-client results and immediate packet storage; every multiplication, alignment, address and page round must fit. This grants no additional endpoint or allocation authority. Ordinary endpoint transfer copies authority. Every source and possible receive destination remains owned across submission, collection and native retirement, including ambiguous results. Reserve each prospective receive slot before COLLECT; validate its normalized receipt and actual Generic kind/rights, then independently reconcile its disposal before reuse. Unique InstallGrant and RevocationGrant transfers keep MOVE semantics. Do not infer source deletion from successful copy or use deletion to manufacture successful unique-grant movement. Track this continuation with [Posixd realm lifecycle](https://git.erikinkinen.fi/erix/posixd/issues/1), [POSIX ABI](https://git.erikinkinen.fi/erix/lib-posixabi/issues/1) and [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). This is a proposed contract; no runtime or implementation acceptance is claimed. Corrected endpoint COPY versus unique grant MOVE documentation in signed Lib-IPC commit [`a8324c136fe1747edd3e7eeea563b2bb87572df1`](https://git.erikinkinen.fi/erix/lib-ipc/commit/a8324c136fe1747edd3e7eeea563b2bb87572df1). Provision transfers one ordinary Generic SEND endpoint by COPY and retains the sender's original source alias. Launchd must explicitly dispose of that alias and independently prove absence before Start. A unique InstallGrant still moves; deleting a residual grant cannot manufacture successful native move evidence. README, ARCHITECTURE, ROADMAP and provisioning rustdoc now state that distinction. This checkpoint changes comments and documentation only. Executable Rust, tests, dependency inputs and wire behavior are byte-identical to the preceding [`93bd65388e9bced368b7f3727e4ba0b88e55a860`](https://git.erikinkinen.fi/erix/lib-ipc/commit/93bd65388e9bced368b7f3727e4ba0b88e55a860) checkpoint. Fresh formatting, private rustdoc, Markdown, template and diff checks pass without warnings. The unchanged code retains its prior strict default/all and development/release matrix: 459 main-crate tests/doctests and 20 syscall-shim tests, with one existing native-only host ignore, in each selection. That matrix was reused on the verified unchanged inputs, not rerun locally for this prose correction. Existing native image consumers may retain their prior exact IPC selection; this correction requires no executable dependency or image repin. The runtime consumer fix and native startup acceptance remain pending in [Launchd #7](https://git.erikinkinen.fi/erix/launchd/issues/7) and [Integration #89](https://git.erikinkinen.fi/erix/integration/issues/89). No new runtime or VM validation is claimed. Both original exact-head CI runs pass: [run 375](https://git.erikinkinen.fi/erix/lib-ipc/actions/runs/375), [run 376](https://git.erikinkinen.fi/erix/lib-ipc/actions/runs/376). All four complete terminal job logs (554,500 bytes) are retained and hash-verified, with zero warning or failure candidates. The declared host tests, strict host/freestanding Clippy and builds, private rustdoc and Markdown checks pass. No workflow was rerun. Start requires a nonzero exact digest; only authenticated retirement accepts a zero unknown-digest sentinel after a lost provisioning result. The four default/all-feature development/release main-crate selections each pass 459 tests/doctests; each corresponding syscall-shim selection passes 20 tests with the one existing native-only ignored case explicitly retained. Formatting, strict host/native Clippy, warning-denied builds, private rustdoc, Markdown and exact original dependency checks pass with zero warnings. Actual running mediator readiness/retirement, complete service-image acceptance, configuration/seal, client I/O and both required guest rebuilds remain open. Tracking: [owning issue](https://git.erikinkinen.fi/erix/lib-ipc/issues/1), [WIP PR](https://git.erikinkinen.fi/erix/lib-ipc/pulls/2) and [Phase 6 acceptance](https://git.erikinkinen.fi/erix/integration/issues/65). The original Clippy style refusal is retained and corrected without relaxing lints. All reserved bits are rejected; replies carry zero result values and preserve uninterpreted codes. Seven new controls pass all eight strict library/shim configurations: 419 wire tests and 20 shim tests per configuration, eight freestanding builds, formatting, strict host/native Clippy and private rustdoc, with no warnings. The original kernel-only shim test remains ignored. Original [lib-ipc CI 365](https://git.erikinkinen.fi/erix/lib-ipc/actions/runs/365) and [366](https://git.erikinkinen.fi/erix/lib-ipc/actions/runs/366) pass from four complete hashed logs, 494,246 bytes, without warnings. Kernel admission, descendant stopping, safe native reclamation progress, coherent consumer adoption and actual CPL3 failure coverage remain open. The shared codec does not enable private mediator execution or alter the current complete image's source graph. The matching signed [Docs PR 4](https://git.erikinkinen.fi/erix/docs/pulls/4), `54557713f4afad380c1166f6aa1c1622d3959744`, updates the TeX chapter and both IPC API views from original signed source. All 45 tests, independent API regeneration, the complete 2,423-page manual, all 446,749 word bounds and nine visually reviewed contract pages pass, with zero final warnings. Original [Docs CI 979](https://git.erikinkinen.fi/erix/docs/actions/runs/979) and [980](https://git.erikinkinen.fi/erix/docs/actions/runs/980) pass from four complete hashed logs, 773,034 bytes. Both runs pass 45 tests and the complete 2,423-page manual; successive TeX passes retain 36/1/0 warning observations, with zero final-pass warnings. No workflow rerun or cancellation supplies this result. Native upstream Rust/LLVM rebuilding and both complete EriX build generations inside EriX remain required. ### Runtime dependency alignment — 15 September 2026 This is part of coherent runtime-source adoption, not a new product VM or guest-build acceptance. ### Coherent runtime source adoption — 15 September 2026 Full commit selectors remain mandatory. ### Construction without child root capabilities — 15 September 2026 Define checked root-capability-free construction framing alongside the existing native authority, owned invocation and staged endpoint contracts. Signed original revision: `7c7712057cc5d16ab16a677a886caeac54814a16`. All 381 IPC tests and the syscall shim matrix (20 tests, one existing native-only ignore) pass with strict default/all development/release host/native Clippy, builds, documentation and formatting. CI 345/346 has complete warning-free logs. Procd adoption, authenticated grant return, guarded bootstrap authority, private mediator execution, readiness, configuration/seal, client I/O, fair retirement and both complete guest build generations remain open. Ordinary mediator start gates remain closed. Whole-codebase semantic authority and private-item documentation audits remain incomplete. ### Staged endpoint attenuation checkpoint — 15 September 2026 Define the checked ProcessBoundEndpointAttenuationV1 request and operation 53. Preserve exact packed widths, nonzero identity requirements, reserved-field error precedence and exact zero rights. Scalar decoding conveys no capability or proof of native identity. Signed original revision: `74c75a5db226413c066b6582210a44cb21d968d8`. All 376 IPC tests and the syscall shim matrix (20 tests, one existing native-only ignore) pass with strict default/all development/release host/native Clippy, builds, private rustdoc and formatting. CI 343/344 passes with complete warning-free logs. Authenticated grant return, independently minimal bootstrap/root authority, retained native and nested guards, private mediator execution, configuration/seal, client I/O, fair retirement and both complete guest build generations remain open. Ordinary mediator start gates remain closed. Whole-codebase authority and private-item documentation audits remain incomplete. Signed Lib-ipc `805717680d9dfb902216550a111d910807f30d23` selects native IPC assembly only for freestanding x86-64 builds. Other targets retain the API for tools and tests, with local `DENIED` and zero raw transport outputs. Checked helpers preserve their preceding slice validation. The local refusal carries no kernel-attested identity, capability observation or retirement acknowledgment; compile-target selection itself does not authenticate a running kernel. The backend is extracted and documented inline. Three public host regressions cover register operations, empty identity/authority observations and unchanged message buffers. Static object inspection establishes zero syscall instructions in both hosted profiles before those tests execute. The native backend's emitted instruction sequence is identical in development and release. No new wire result or runtime probe is introduced. Both crates pass formatting and the complete strict default/all-feature development/release host/freestanding matrix. Each ABI selection passes 359 units plus one doctest; each shim selection passes 18 tests with one existing native-only test ignored. Private rustdoc covers both compiled backend variants. Canonical documents, whitespace, source identities and code-size checks pass without compiler or lint warnings. Current [push CI 335](https://git.erikinkinen.fi/erix/lib-ipc/actions/runs/335) and [PR CI 336](https://git.erikinkinen.fi/erix/lib-ipc/actions/runs/336) pass for this exact signed source. Four complete logs total 409,239 bytes with zero warning candidates. Each test job passes 359 default ABI units plus one doctest, 359 optimized all-feature ABI units and both 18-test shim selections; the existing native-only case remains ignored once per shim selection. All three new host tests pass in both selections. The workflow also passes formatting, strict Clippy, host/freestanding builds and private rustdoc; both ten-file Markdown jobs pass. The source-matched API export retains all 2,593 ABI and 24 shim public signatures unchanged. The platform manual is accepted at signed Docs `87942ea7675e2a25fe3bf19f3cac19f9c5d8b1e2` in [Docs PR 4](https://git.erikinkinen.fi/erix/docs/pulls/4), with all 45 documentation tests, the complete 2,339-page local manual and CI 843/844 passing with zero final warnings. The earlier native lifetime mechanism remains accepted at its separate Kernel `03e13a78` / Integration `4b65755f` graph, with Docs `17b4d52a` and green CI 841/842. New realm producers, operation completion, the broader audit and full guest builds remain open. The matching native lifetime scenario now passes with Kernel `03e13a78` and Integration `4b65755f`, whose exact source graph selects this signed IPC revision. Docs `28b44183` publishes the syscall and generated wrapper reference with green CI 839/840. Realm producer adoption, pending-operation completion and full guest builds remain open. See [Kernel issue 7](https://git.erikinkinen.fi/erix/kernel/issues/7) for the exact native image and acceptance boundary. - Parent work: https://git.erikinkinen.fi/erix/integration/issues/2 and https://git.erikinkinen.fi/erix/docs/issues/1. - Branch: `feature/posix-compat`; update linked WIP PRs after coherent signed checkpoints using canonical CONTRIBUTING.md messages. - Baseline revision: `b452a46803982c57e474adcc318ce40bd281d621`; refresh component/dependency heads and their own CI evidence as implementation advances. - Cross-repository dependencies remain full lowercase commit hashes; update the selected graph deliberately. This issue does not authorize merges, release tags or replacement of published images. Coordinated actual consumers and matching native execution remain open under [Kernel design 19](https://git.erikinkinen.fi/erix/kernel/issues/19). This dependency/wire checkpoint does not establish complete lifecycle acceptance or either full EriX build generation. [Phase completion](https://git.erikinkinen.fi/erix/integration/issues/65) retains native external Rust/LLVM/runtime rebuilding as an independent requirement. Acknowledged terminal accounting — 21 September 2026: [Kernel design 20](https://git.erikinkinen.fi/erix/kernel/issues/20) specifies final scalar CPU evidence retained independently of native resource reclamation, repeatable observations bound to actual original observer generations, independent authorized observers, exact acknowledgement and claim release on observer death. Both ordinary and mediator consumers must commit terminal measurements and cleanup duties before acknowledgement, including consumer-loss handling. Shared wire commit [0b889095fd04f6f4b1da1d4c0064150551f52122](https://git.erikinkinen.fi/erix/lib-ipc/commit/0b889095fd04f6f4b1da1d4c0064150551f52122) is signed and pushed. Four wire configurations pass 427 tests each; four syscall-shim configurations pass 20 each with one existing ignore. Eight native builds, strict host/native Clippy, formatting, private rustdoc, Markdown and dependency checks pass without warnings. Native kernel and consumer adoption, actual CPL3/service VM acceptance and original CI observation remain open. Canonical completion remains **3.48% weighted; 15 of 460 acceptance items**. Full upstream Rust/LLVM/runtime rebuilding inside EriX remains mandatory together with both full EriX guest build generations. No acceptance item closes from this representation checkpoint. Native producer and actual consumer adoption remains in progress under [Kernel design 20](https://git.erikinkinen.fi/erix/kernel/issues/20). Runtime acceptance remains open; [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65) retains native upstream toolchain rebuilding and both EriX guest generations. ### Original special-file metadata design — 30 September 2026 Extend descriptive native node kinds to distinguish retained FIFO, character-device, block-device and socket inodes from absence. Share exact mode/type validation across observations and no-follow candidate framing. E2fsd will retain the original inode for status and directory observations; names and metadata will grant no device, stream or socket access. Existing native content admission remains restricted to regular files and directories, and compatibility open will explicitly refuse unsupported special-file contents before native admission. Prefix search, final no-follow behavior and original cleanup custody remain intact. Author codec, provider and guarded-service controls for original identity, each special mode, malformed kind/mode combinations, absence, refusal ordering and cleanup. Coordinate immutable dependency revisions and update component contracts and the maintained manual. This remains part of [complete status and directory support](https://git.erikinkinen.fi/erix/posixd/issues/25); provider metadata gaps and pipe/stream status remain unfinished. Tests, builds, lint checks, VM/profiler execution and CI observation remain deferred under the current user instruction. ### Original special-inode metadata — 30 September 2026 No device, socket, pipe, clock or new provider endpoint is granted. The [full status/directory item](https://git.erikinkinen.fi/erix/posixd/issues/25) remains open for complete FAT metadata, pipe/stream status, the compatibility special-device-number field and remaining full-item integration. Both complete EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed. ### Original special-device numbers — 30 September 2026 Compatibility 1.15 will append an unsigned 64-bit device_number at offset 88 of the status reply and prefixed C record, making each status body 96 bytes while retaining the earlier field offsets. This represents the original device inode's major/minor pair, separate from its containing filesystem identity; it never selects or grants a native device endpoint. Rust/C framing, aggregate call controls, producers and native workload consumers will migrate together. Native conversion requires explicit device-number availability for character/block types, preserving meaningful zero and every represented bit. Non-device types have canonical zero by their established type. Native observations claiming a nonzero number for a non-device will be rejected. E2fsd's retained-inode decoder will distinguish the legacy first-word and extended second-word encodings and preserve both major and minor fields. Metadata remains read-only under original custody, with content admission and cleanup gates unchanged. Author independent native availability/malformed-value, exact-wire, C aggregate and ext-media controls, and extend the actual native workload to check represented device numbers. All test/build/lint/VM/profiler execution and CI observation remain deferred under the user instruction. Complete provider/pipe/stream metadata and full libc structures remain part of the open [status and directory work](https://git.erikinkinen.fi/erix/posixd/issues/25). ### Original represented-device status — 30 September 2026 Existing field offsets are unchanged; earlier wire minors and shorter bodies are refused. Native character/block observations require independent device availability, including meaningful 0:0. No clock, device, socket, pipe or new provider route is granted; content gates, error ordering, original caller/pin cleanup and alias custody remain unchanged. The [full status/directory feature](https://git.erikinkinen.fi/erix/posixd/issues/25) remains open for complete FAT metadata, pipe/stream status and remaining full-item integration. Both full EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed. ### Dynamic pipe status and explicit clock custody — 30 September 2026 Cap-free public operations cannot choose a slot or transfer a caller-selected source. Launchd retains prospective counted custody before copying its startup-admitted SEND query endpoint; configuration and inventory admission preserve original receipts. The shared clock has no per-client provider object or Close; recipient alias disposal follows caller retirement and requires DROP plus independent absence QUERY. No compatibility client receives a native clock capability. The [full status/directory feature](https://git.erikinkinen.fi/erix/posixd/issues/25) remains open: initial configured channels, inherited stream metadata, full FAT identity/owner/mode/time policy and whole-feature integration remain implementation work. Both full EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed. ### Initial configured FIFO status and atomic writes — 30 September 2026 Bound FIFOs require a valid canonical creator; unbound pools require the all-ones no-creator encoding. Launchd restores original ordering and all creator/credential bytes on acceptance and refusal. Release precedes original metadata publication and Prepared; native client-disposal acknowledgment cannot overtake query retirement or drop the original clock alias early. No compatibility client receives a clock capability. Two ordinary plans require 936 bytes; explicit binding plans require 3752 bytes and 44 authority rows. The [full status/directory feature](https://git.erikinkinen.fi/erix/posixd/issues/25) remains open: inherited stream metadata, complete FAT identity/owner/mode/time policy and whole-feature integration remain implementation work. Both full EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed. ### Original inherited stream metadata — 30 September 2026 Canonical refusals carry no observations. An explicitly unavailable native source cannot become a successful POSIX status. Shared observers preserve original inode/node/media evidence; Vfsd shares mounted-filesystem qualification with candidate metadata and never replaces object serials with temporary handles or queue offsets. Missing required fields return ENOTSUP without changing offsets or descriptor lifetime. No new capability, clock, content grant, heap pool or descriptor ceiling is introduced. 12 new Rust controls are authored and unrun: independent family literals, correlation and capacity rejection; ordinary/acquired handle separation; write-only alias identity; unavailable metadata with continued byte I/O; malformed-response custody; cancellation; original lender forwarding; and PTY/local-buffer observations. The [full status/directory feature](https://git.erikinkinen.fi/erix/posixd/issues/25) remains open: native-buffer/PTY original identity, creator and time policy, complete FAT metadata and whole-feature integration remain implementation work. Both full EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed. ### Original native stream identities — 30 September 2026 Ordinary namespace and executable routes cannot allocate one. Original event times remain Unknown; this scalar metadata cannot turn an incomplete observation into successful compatibility status. They cover literal wire rejection, atomic encoding, administrator isolation, lost-delivery allocation, binding refusal, exhaustion, directional lifetime, teardown/reuse, original ownership, malformed observations and receipt cleanup. The [full status/directory feature](https://git.erikinkinen.fi/erix/posixd/issues/25) remains open for original native event-time capture, complete FAT metadata and whole-feature integration. Both full EriX guest build generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed. ### Original native stream event times — 30 September 2026 Alias creation, metadata queries, empty or refused operations and terminal device progress do not query a historical clock. Ttyd receives an exact authenticated SEND-only Timed endpoint for this source purpose; Launchd uses its already admitted endpoint. Clean refusal remains Unknown. The seeded boundary control retains the whole original object and proves the intended no-clock refusal contract when executed; no runtime reproduction or practical path to 2^64 bytes is claimed. They cover source-event independence, unknown evidence, full-range dates, malformed replies, receipt cleanup, exact SEND-only admission, alias/retirement/reuse and overflow refusal. The existing realm workload now requires successful inherited fstat and original PTY clock evidence with stable birth before and after realm retirement; its independent transcript remains 385 calls. The [full status/directory feature](https://git.erikinkinen.fi/erix/posixd/issues/25) remains open for complete FAT metadata and whole-feature integration. Both full EriX guest build generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed. ### Original FAT mount recovery and mutation rollback — 1 October 2026 Ext and memory families cannot reinterpret this flag. Swallowed wrong-mount or reserved-extent refusals cannot commit. They include independent FAT12 media, original before-images/checksums, hostile extents, clean and recovery-required read-only mounts, actual mutation rollback, key/handle retirement, nested helpers, wrong-mount refusal and unwinding. Four new native scenarios cover clean admission, interrupted-boot recovery, corrupt counted records and read-only refusal; positive workloads retain existing mounted filesystem/lifecycle gates. The [complete FAT metadata feature](https://git.erikinkinen.fi/erix/fatd/issues/8) and [full status/directory feature](https://git.erikinkinen.fi/erix/posixd/issues/25) remain open. Both complete EriX guest generations and external Rust/LLVM guest rebuilding remain required and unperformed. ### Conditional retained-entry namespace custody — 1 October 2026 Exact response correlation distinguishes completed effects, definite no-effect refusals and uncertainty. Missing, malformed or uncorrelated replies preserve cleanup and never permit replay. The installed namespace is currently immutable and append-only; future unmount/reconfiguration requires a persistent nonwrapping epoch. Ext and FAT return explicit correlated unsupported no-effect dispositions for the new family. Their conditional transactions remain unfinished. Complete compatibility path/dirfd, ACL/sticky, final-link and trailing-separator mediation and legacy cwd migration remain open in [the owning design](https://git.erikinkinen.fi/erix/posixd/issues/27). Required legacy cwd and administrative spelling guards remain. Thirty-nine new Rust controls are authored and unrun: ten literal wire controls, seventeen RAM provider controls, eight actual Vfsd dispatch controls, and two explicit-refusal controls each for ext and FAT. Both complete EriX guest generations and external Rust/LLVM rebuilding remain required and unperformed. ### Counted authenticated launch-entry evidence Replace private Vfsd launch-artifact operation 0x613 and its V1 codecs with operation 0x71B and V2 framing. The request retains the original 88-byte correlation/selector prefix and appends u64 maximum exported entry bytes at offset 88, then raw selector bytes at 96. Zero export capacity requests authenticated digest evidence without a display copy. Positive capacity requires the complete available entry, never truncation. Preserve the explicit sidecar flag, source/destination and all transaction/session/realm bindings. The 184-byte response prefix retains request/op/result/failure at 0/4/8/12, transaction/session/realm at 16/24/32, scope/source/result slots at 40/44/48, mode at 52, size at 56, exported entry length at 64, selector digest at 72 and original object digest at 104. Add authenticated artifact-entry digest at 136, echoed export capacity at 168, echoed flags at 176 and zero reserved at 180; optional complete raw entry bytes follow at 184. Success requires a nonzero entry digest and original object evidence. Refusal preserves original request correlations while zeroing all new object, entry and measurement evidence. Both codecs reject the retired operation with no downgrade. Vfsd derives entry identity only from complete original-generation evidence retained by the actual native resolution, never from an unchecked caller selector. Hash the existing command-entry domain, u64 little-endian complete byte length and canonical raw entry bytes in place across counted description fragments. For sidecars preserve the explicit derived .lmf requirement; the artifact hash describes the full sidecar entry, while its authenticated manifest contents remain bound to the executable command-entry digest. Missing required binding evidence refuses normally with original cleanup. Display absence cannot manufacture entry identity. Resolve the executable selector as borrowed bytes. Derive the sidecar by streaming the original selector and literal suffix into the same counted scope traversal, without a 240-byte whole-selector buffer. Preserve known-root interpretation, actual provider authority, active symlink context, source generation and original retirement. Admit caller/transport reply extent and encode complete typed evidence before creating a receiver. Failed publication retires only new custody; uncertain cleanup stops ordinary work. Launchd validates all original correlations, flags and capacity before accepting evidence. When entry bytes are exported, independently hash their complete bytes and require digest equality. Store the authenticated executable digest independently of its display; Loaderd and manifest binding consume that digest. Manifest evidence needs no retained path cache. Realm/client preparation requests digest-only evidence, removing the display-width obstacle on those paths. Ordinary prompted launches initially advertise their actual existing display storage capacity; continue replacing that retained storage and the coordinated Powerbox/TTY display contract in the same migration. This intermediate capacity is not full counted program-display acceptance. Author literal wire, atomic capacity, long/raw selector, original-source closure, sidecar derivation, changed entry, retired-operation and cleanup controls. Retain existing content, relation, native receipt and rollback controls. Keep testing, builds and CI observation deferred. Complete retained display, remaining provider/name adapters and coherent deployment adoption before closing the containing native migration or claiming guest self-hosting. Ordinary V2 response correlation no longer admits retired effect operations. They retain root/parent/key fields, full-width handles and timestamps, optional trusted time, explicit selected fields, invalid destination refusal and untouched short outputs. New literal stat controls cover framing, canaries and retired-family refusal. Retired numeric replies cannot satisfy ordinary V2 or native effect correlation. Vfsd's last old exported-name references become literal timestamp-adapter refusals for all thirteen retired operations. The existing superseded-bridge/provider-spelling-pin acceptance criterion in [the native ownership feature](https://git.erikinkinen.fi/erix/vfsd/issues/16) is source-complete. Required imported FAT/exFAT binding and geometry guards remain. The remaining cwd/contextual-serving and complete lifecycle/control/graph criteria need a current-source acceptance audit and any missing implementation, followed by coherent runtime adoption. No synthetic weighted sub-item or full lifetime acceptance is added. Recomputed phase progress remains 18.95% weighted and 6.81% whole acceptance: 25/460 parents and 480/949 sub-items. Full EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed. ### Counted raw program context — producer/consumer design, 1 October 2026 The ordinary prompt boundary must preserve the complete authenticated program entry without a 240-byte or UTF-8 adapter. This is descriptive data only: Launchd's entry digest, manifest admission, native scope and object custody remain independent. Launchd's remaining per-job retained display storage will migrate after this boundary. Replace the contextual V1 types with PowerboxBeginContextRequestV2 and TtyPowerboxPromptContextRequestV2 across LibIPC, Launchd, Powerboxd and Ttyd. The fixed authority-free BEGIN (80 bytes) and prompt (128 bytes), private routes and answer correlation remain unchanged. V2 context appends job generation u32, a reserved zero u32 and program length u64; the prompt additionally appends selector length u64. Prefixes are exactly 96 and 152 bytes. Raw program and then selector bytes follow. Exact fixed shapes select their fixed codecs; every other shape selects only V2, without retrying the fixed parser after a contextual failure. The nonzero legacy contextual length occupies V2's reserved word, so retired V1 contexts reject rather than silently changing interpretation. Programs use complete absolute normalized raw bytes; generation is nonzero. Selectors remain complete nonempty NUL-free raw bytes. Counts must fit target width and exact body extent before borrowing, retaining or encoding. Overflow, unknown padding, short/long bodies and insufficient output leave storage unchanged. No opcode, label, generation or byte count creates a capability or changes policy. Powerbox retains the full original program and selector together in its existing caller-sized arena, preserves both through compaction and clears retired ranges. Prompt transport admits the complete body before calling Ttyd. Ttyd escapes each non-ASCII/control byte, admits the whole rendered review, and retains existing rollback and visibility-gated secure-input behavior. No truncated prompt or digest shortcut may authorize consent. Surplus capability receipts retain their existing independent disposal rules. Migrate current controls and add raw/long geometry, retired-context refusal, capacity atomicity, retained arena ownership/compaction and trusted rendering controls. Document the coordinated immutable revision graph and remaining ordinary Launchd storage work. Author controls without running tests, builds, checks, generated documents or CI observation under the current request. ### Counted redirection selectors and retired provider adapters Continue the native name migration with complete raw shell redirection selectors. The existing request already carries a u64 length and variable tail. Remove its unrelated legacy pathname-width check; retain exact nonempty/NUL-free bytes, length, mode, digest and distinct slot validation. Add a public semantic validator shared by codec and typed Vfsd admission. Vfsd must not encode a temporary fixed pathname array merely to validate already-borrowed input. Actual caller/transport and native traversal storage remain explicit resource bounds. Exsh forwards original bytes and digest through its exact cwd SEND transfer and requires independent operation/cleanup receipts. Short transport storage refuses before any call. Vfsd authenticates the original resolver/cwd source, policy and digest before provider effects; raw selectors do not confer authority. Existing native scope, conditional creation, retirement and receiver-disposal ownership remain unchanged. The wire shape and operation are unchanged; older peers may refuse longer requests, so both compiled consumer edges adopt the signed codec. No fallback, truncation, UTF-8 conversion or path-derived authority is permitted. Source audit found the old ProviderBackend exact-entry open/mutate/stat/touch hooks have no production callers. Remove their fixed-name framing, timestamped mutation bridge, obsolete result type and operation mapper arms. Retain original- route metadata transport used by live fixed-entry custody, and preserve current source-free mutation/touch controls. Shared legacy provider codecs still used by provider internals remain until their separate storage migration is complete. Author literal raw-selector/capacity/malformed controls, direct native creation and refusal/cleanup controls, shell full-byte transport and capacity controls, and exact original-route metadata correlation/refusal controls. Update component and authored manual contracts. Tests, builds, generated documents, VM/profiler execution and CI observation remain deferred. Runtime catalog adoption and the full cross-provider name-storage migration remain open. Tracking: [native retained ownership](https://git.erikinkinen.fi/erix/vfsd/issues/16), [shared IPC design](https://git.erikinkinen.fi/erix/lib-ipc/issues/1), [Vfsd PR3](https://git.erikinkinen.fi/erix/vfsd/pulls/3), [LibIPC PR2](https://git.erikinkinen.fi/erix/lib-ipc/pulls/2), [Exsh PR3](https://git.erikinkinen.fi/erix/exsh/pulls/3), [Docs PR4](https://git.erikinkinen.fi/erix/docs/pulls/4). ### Counted endpoint-selected exact mutation Replace the fixed 252-byte public VfsExactMutationRequestV1 with borrowed VfsExactMutationRequestV2. Its 24-byte prefix contains request ID and the existing exact operation at offsets 0/4, explicit version 2 at offset 8, reserved zero at 12 and the complete u64 destination-byte length at 16. Rename alone supplies one raw basename after offset 24; other admitted effects have an empty tail. Empty, NUL, slash and dot rename components refuse. Checked full extent and actual caller/transport storage replace the fixed width and UTF-8 restriction. The version/reserved fields distinguish valid old requests, including two-byte old rename names, without fallback or retaining the deprecated public API. The exact endpoint still supplies the original immutable operation and entry; no source, parent, namespace, handle selector, new endpoint or capability is introduced. Vfsd admits complete status capacity before provider effects and passes the borrowed destination through the original retained owner. Existing one-use/definite-refusal/uncertain-effect consumption and original cleanup rules remain authoritative. Neither larger names nor descriptive status grant rights. Migrate LibIPC, Vfsd dispatch and Coreutils source callers and controls in one signed source graph. Coreutils uses actual encoded length and a single call; wrong correlation, unknown status, malformed/lost replies or unexpected authority never trigger effect replay. Retire all unwanted receipts before refusal and preserve uncertain cleanup classification. Share the exact status-call framing, receipt retirement and scratch clearing with existing truncation instead of adding another transport copy. Preserve the caller's original endpoint ownership. Author literal V2 byte layout, complete raw names, short/surplus tails, version and reserved separation, bad shape, output canaries, operation ceilings, short status preflight, original-provider binding/cleanup and real transport controls. Update component contracts and maintained manual TeX. Tests/builds/checks, generated documents, VM/profiler execution and CI observation remain deferred. Both direct compiled IPC selectors in adopting consumers use the new immutable revision; runtime catalogs and compiled Rootd helpers remain unchanged pending coherent runtime adoption. Legacy directory/consumer frames and complete cross-provider/self-hosting acceptance remain open. Tracking: [codec audit/design](https://git.erikinkinen.fi/erix/lib-ipc/issues/1), [native ownership](https://git.erikinkinen.fi/erix/vfsd/issues/16), [Coreutils audit](https://git.erikinkinen.fi/erix/coreutils/issues/1), [Phase 6 tracker](https://git.erikinkinen.fi/erix/integration/issues/65). Review: [LibIPC PR2](https://git.erikinkinen.fi/erix/lib-ipc/pulls/2), [Vfsd PR3](https://git.erikinkinen.fi/erix/vfsd/pulls/3), [Coreutils PR2](https://git.erikinkinen.fi/erix/coreutils/pulls/2), [Docs PR4](https://git.erikinkinen.fi/erix/docs/pulls/4). ### Counted endpoint-selected directory enumeration Replace the exact-endpoint use of fixed public readdir frames with dedicated VfsExactReadDirectoryRequestV2 and VfsExactReadDirectoryResponseV2. The 32-byte request has correlation/op at 0/4, version 2/reserved zero at 8/12, the original endpoint-local cursor at 16 and u64 name capacity at 24. There is no public handle, provider, candidate or namespace selector. The original ENUMERATE endpoint remains the sole authority. Old 24-byte requests refuse on this route; generic namespace/provider V1 contracts remain until their live users migrate. The response has a 56-byte prefix: correlation/op at 0/4, version 2 at 8, known result at 12, next token at 16, node kind/end flag at 24/28, observed size at 32, complete u64 name length at 40 and reserved zero at 48. One complete raw name follows. End and refusal have no entry, zero metadata and no name bytes; refusal preserves the request token. A successful entry has a known kind and a distinct nonzero token. Check the complete shape, original correlation and offered capacity before publishing any caller-visible name or cursor. Vfsd retains counted full native cursor state and reserves a position before observation. Preserve native mount composition, original metadata identity and known-size checks, original candidate retirement and equal-position reuse. Admit complete response/name storage before publishing the reserved position; short capacity, malformed input, provider refusal and stale identity release the reservation without advancing the original token. Complete raw names replace the fixed 240-byte copy. Preserve original owner retirement and generation isolation. No path reopening, hidden fallback or name-derived authority. Coreutils advertises the minimum of actual caller name storage and actual IPC reply capacity, submits one call to the original endpoint, retires unexpected receipts, validates all framing/correlation and only then copies complete names. Erase message scratch on every return; failed admission leaves caller names unchanged. Keep lease ownership and existing utility cursor behavior unchanged. Use shared explicit call/disposal effects and independent reply fixtures. Author literal codec, actual provider/position/metadata, transport cleanup and long raw utility-listing controls. Update inline/component/manual contracts and publish signed source with both IPC selectors in Vfsd/Coreutils coordinated. Runtime catalogs and compiled Rootd helpers remain unchanged. Tests/builds/checks, generated references, VM/profiler execution and CI observation remain deferred. Complete cross-provider lifetime/restart and guest self-hosting remain open. Tracking: [codec design](https://git.erikinkinen.fi/erix/lib-ipc/issues/1), [native ownership](https://git.erikinkinen.fi/erix/vfsd/issues/16), [Coreutils audit](https://git.erikinkinen.fi/erix/coreutils/issues/1), [Phase 6 tracker](https://git.erikinkinen.fi/erix/integration/issues/65). ### Retire legacy provider pathname and spelling-pin adapters Current contextual consumers use independently retained native anchors, conditional component/fixed-entry acquisition and source-free retained effects. The older provider cwd-open, whole-target readlink and path-selected exact-entry families now remain in provider dispatch, compatibility adapters and tests. Inventory every opcode, codec and direct caller before deleting its producer. Retire cwd component open (0x639), its whole-target link observation (0x63A), and the obsolete path-selected fixed-entry acquisition/effect adapters where all ordinary consumers have migrated. Old operation numbers remain unassigned and must refuse without fallback. Keep actual native metadata, raw link pages, conditional namespace effects, retained entry effects, original anchors and acquisition-key retirement. Do not remove ordinary namespace/file interfaces that still have real users, including generic provider readdir. Remove cwd spelling-pin fields and their move/unlink guards only after the corresponding creation paths and dependent tests migrate. Remove legacy exact binding/parent spelling guards with their final acquisition producers. Preserve original object, parent and navigation-ceiling ownership; empty directory moves and detachment must retain actual held objects without pathname reopening or reuse. Conditional entry freshness, stale-binding refusal, original one-use effect semantics, permission evidence and positive cleanup remain mandatory. Imported filesystem-format limits remain explicit and are not bypassed. Migrate controls to actual native root/anchor/component/fixed-entry acquisition with original keys known before submission. Do not emulate removed APIs with test-only path reopeners, fabricated handles, copied identity or renamed legacy production code. Preserve independent identity/mount separation, maximal ID and capacity refusal, raw link lifetime, moved/detached ancestors, wrong handle kind, stale selection/replacement, timestamps, media recovery and cleanup ordering. Retain literal rejection controls for retired operation numbers. Share cohesive fixture helpers where useful; all authored code stays below 1,000 lines. Work through RAM, ext and FAT producers and dependent controls, then remove the unused shared codecs/IDs and remaining Vfsd adapter references. Publish signed checkpoints regularly and coordinate adopting immutable dependency revisions. Update component contracts and authored manual/API addenda. Tests/builds/checks, generated references, VM/profiler execution and CI observation remain deferred. Runtime catalogs and both compiled Rootd helper selections remain unchanged until coherent runtime adoption; full guest EriX and Rust/LLVM rebuilding remains required. Partial provider retirement does not close the complete lifetime item. Tracking: [codec audit](https://git.erikinkinen.fi/erix/lib-ipc/issues/1), [RAM audit](https://git.erikinkinen.fi/erix/ramfsd/issues/1), [ext audit](https://git.erikinkinen.fi/erix/e2fsd/issues/1), [FAT audit](https://git.erikinkinen.fi/erix/fatd/issues/1), [native ownership](https://git.erikinkinen.fi/erix/vfsd/issues/16), [Phase 6 tracker](https://git.erikinkinen.fi/erix/integration/issues/65). Signed current revision: [69837518](https://git.erikinkinen.fi/erix/lib-ipc/commit/6983751827d3dceafeb2139320cbc7eabb3b7954). </details> <details> <summary>Related records and contracts</summary> | Repository | Links | | --- | --- | | e2fsd | [issue 15](https://git.erikinkinen.fi/erix/e2fsd/issues/15), [issue 16](https://git.erikinkinen.fi/erix/e2fsd/issues/16), [PR 3](https://git.erikinkinen.fi/erix/e2fsd/pulls/3) | | fatd | [issue 6](https://git.erikinkinen.fi/erix/fatd/issues/6), [original-undo.md](https://git.erikinkinen.fi/erix/fatd/src/branch/feature/posix-compat/docs/original-undo.md) | | integration | [public-deadlines.md](https://git.erikinkinen.fi/erix/integration/src/branch/feature/posix-compat/docs/public-deadlines.md) | | kernel | [issue 43](https://git.erikinkinen.fi/erix/kernel/issues/43), [PR 3](https://git.erikinkinen.fi/erix/kernel/pulls/3) | | launchd | [issue 15](https://git.erikinkinen.fi/erix/launchd/issues/15), [PR 2](https://git.erikinkinen.fi/erix/launchd/pulls/2) | | lib-bootstrap | [PR 2](https://git.erikinkinen.fi/erix/lib-bootstrap/pulls/2) | | lib-capabi | [issue 3](https://git.erikinkinen.fi/erix/lib-capabi/issues/3), [PR 2](https://git.erikinkinen.fi/erix/lib-capabi/pulls/2) | | lib-ipc | [conditional-namespace.md](https://git.erikinkinen.fi/erix/lib-ipc/src/branch/feature/posix-compat/docs/conditional-namespace.md), [native-activity.md](https://git.erikinkinen.fi/erix/lib-ipc/src/branch/feature/posix-compat/docs/native-activity.md), [native-deadlines.md](https://git.erikinkinen.fi/erix/lib-ipc/src/branch/feature/posix-compat/docs/native-deadlines.md), [public-deadlines.md](https://git.erikinkinen.fi/erix/lib-ipc/src/branch/feature/posix-compat/docs/public-deadlines.md), [realm-clock.md](https://git.erikinkinen.fi/erix/lib-ipc/src/branch/feature/posix-compat/docs/realm-clock.md), [retained-exact-entries.md](https://git.erikinkinen.fi/erix/lib-ipc/src/branch/feature/posix-compat/docs/retained-exact-entries.md), [stream-metadata.md](https://git.erikinkinen.fi/erix/lib-ipc/src/branch/feature/posix-compat/docs/stream-metadata.md), [stream-readiness.md](https://git.erikinkinen.fi/erix/lib-ipc/src/branch/feature/posix-compat/docs/stream-readiness.md), [child-lifetime-binding.md](https://git.erikinkinen.fi/erix/lib-ipc/src/commit/aaf2df39700b43507b23ff2007bc0d573c4eea30/docs/child-lifetime-binding.md) | | lib-stdio | [PR 2](https://git.erikinkinen.fi/erix/lib-stdio/pulls/2) | | posixd | [issue 28](https://git.erikinkinen.fi/erix/posixd/issues/28), [issue 33](https://git.erikinkinen.fi/erix/posixd/issues/33), [PR 5](https://git.erikinkinen.fi/erix/posixd/pulls/5), [pipes.md](https://git.erikinkinen.fi/erix/posixd/src/branch/feature/posix-compat/docs/pipes.md) | | ramfsd | [issue 6](https://git.erikinkinen.fi/erix/ramfsd/issues/6), [PR 2](https://git.erikinkinen.fi/erix/ramfsd/pulls/2), [PR 3](https://git.erikinkinen.fi/erix/ramfsd/pulls/3) | | rootd | [PR 2](https://git.erikinkinen.fi/erix/rootd/pulls/2) | | timed | [issue 4](https://git.erikinkinen.fi/erix/timed/issues/4), [PR 2](https://git.erikinkinen.fi/erix/timed/pulls/2) | | ttyd | [PR 3](https://git.erikinkinen.fi/erix/ttyd/pulls/3) | | vfsd | [issue 15](https://git.erikinkinen.fi/erix/vfsd/issues/15) | </details>
erikinkinen changed title from [FEATURE] [P02.R48] Audit authority, code quality and documentation in lib-ipc to [FEATURE] Audit authority, code quality and documentation in lib-ipc 2026-09-12 08:02:31 +02:00
Author
Owner

The remaining fixed-width filesystem, bootstrap and launch interfaces now have a coordinated migration design. It reuses counted native requests while preserving original root/cwd grants, provider format limits, caller storage budgets and acquisition cleanup. The old codecs and convenience callers must be removed together after their replacements are in use.

The remaining fixed-width filesystem, bootstrap and launch interfaces now have a [coordinated migration design](https://git.erikinkinen.fi/erix/lib-ipc/issues/9). It reuses counted native requests while preserving original root/cwd grants, provider format limits, caller storage budgets and acquisition cleanup. The old codecs and convenience callers must be removed together after their replacements are in use.
Author
Owner

Published read response header encoders so fixed VFS, candidate and stream replies can write their header beside caller-owned data. The existing full encoders share those headers and retain their wire formats and error order. This supports the Vfsd read-path repair; guest confirmation remains open.

Published [read response header encoders](https://git.erikinkinen.fi/erix/lib-ipc/commit/61b43723e9b6c434c4dc51eaa9709625c1a2d475) so fixed VFS, candidate and stream replies can write their header beside caller-owned data. The existing full encoders share those headers and retain their wire formats and error order. This supports the [Vfsd read-path repair](https://git.erikinkinen.fi/erix/vfsd/issues/33); guest confirmation remains open.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:46 +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#1
No description provided.