[FEATURE] Implement POSIX file descriptors and namespace semantics within delegated roots #2
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/posixd#2
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Current implementation status
The status/directory feature is source-complete, including the selected original FAT catalog. Its umbrella criterion is now checked to match the completed feature and phase master. Execution remains waived, not passed. Complete namespace mutation and lifetime is the next active item; the broader umbrella remains open. Earlier dated checkpoints retain their original scope.
Problem and motivation
Cargo, compilers and build scripts require shared open-file descriptions, atomic filesystem operations, locking and race-free readiness. Native pathname and held-directory behavior must be reconciled with these semantics without weakening object identity.
Proposed behavior and scope
Implement fd allocation/duplication, short and positioned I/O, pipes, directory/status operations, link/rename/truncate/durability, scoped temporary files, locks, readiness and only manifest-required local sockets. Exercise parallel build-style workloads and resource exhaustion.
This issue records planned work; its unchecked criteria are not implementation proof. The normative basis is Phase 6 and AC1–AC24.
Authority, security and reliability
Resolve each operation within delegated roots and exact-entry rights. Preserve native admission before deny-only modes/ACLs, retire descriptor aliases and wake only affected waiters, and reject cross-realm traversal or stale object reuse. Network or device names cannot grant network/device access.
Apply the priority order: security, reliability, then performance. Keep suspected vulnerabilities in the repository’s restricted SECURITY.md reporting channel.
Acceptance criteria
Checklist
rights, offset, status flags, inheritance and alias count.
lowest-free allocation and complete transfer cleanup.
zero/short I/O, shared offsets, append atomicity, EINTR and nonblocking.
descriptor closure must wake exactly the affected waiters.
stable identity, correct dot entries, mode/size/link counts and source-qualified
ctime/mtime/atime behavior.
workload, with exact-entry authority and atomic visibility; cross-filesystem operations fail
deterministically without partial mutation.
rename/unlink expectations; implement safe object lifetime and namespace detachment without
reverting to path-based reopening or stale grants.
contracts; test concurrent access, ENOSPC and interrupted failure.
trusted metadata source. ACL byte preservation alone is not permission enforcement;
unsupported provider behavior must be explicit.
delegated tmp/output trees; no host
/tmpor ambient search.contention, cancellation and crash cleanup for Cargo/Git/build tools.
registration rather than periodic busy loops or fake timeouts.
endpoints. Network sockets remain unavailable without later networking authority; device-node
names alone grant no device access.
directory lifetime, revoked handles and mutation outside scope.
locks, large trees, long paths and explicit resource exhaustion.
For each implementation slice, retain actual formatting, strict Clippy, unit/doctest and warning-denied build results for all altered Rust repositories and valid configurations. Add relevant runtime VM coverage, monitor older unit/VM regressions in exact-head CI, and update canonical component documents and affected technical-manual/API material. Every authored code file must remain below 1,000 physical lines, with meaningful inline documentation and missing_docs enforcement in Rust crates.
Alternatives and tradeoffs
Reopening by path or loosening provider pins can substitute an object after authorization. Preserve open-object identity and specify namespace detachment and rollback explicitly, with unsupported provider behavior reported as an error.
Tracking and rollout
Original FAT/exFAT directory observations and the fixed-root scanner repair are signed and published: lib-ipc
bebb7a74, fatda5481166, docs18270dc3, integration26a98467. The independent Integration helperb0255273precedes 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.
Blocking native-stream calls are implemented and signed/published: docs
6357b008, integration6805aad8, lib-posixabifb5ea7e0, posixd7d248ad5, rootd5fcfa912. The independent Integration helper14f8e9f2remains separate from the final catalogs. Publication comprises six signed commits in five repositories, three Cargo selectors and nine catalog selectors, with exact original remote equality and clean feature trees.Typed stream/candidate selection preserves the original description generation before translating an alias into its immutable provider selector. An initial fd may already be closed; its old number never supplies status from a replacement binding. Ordinary stream turns recheck the admitted client, original generation, access and received provider row. Shared modes can clear NONBLOCK without changing access or local inheritance. APPEND is harmless for ordered nonseekable streams. The temporary unsupported-mode refusal is removed with actual implementation.
Only fully correlated native RETRY with zero byte progress and no read flags permits another conditional attempt, after complete retirement of that original provider caller and fresh status. Effect-free status queries may similarly wait after canonical RETRY. Staged write bytes survive every no-progress cycle. OPEN with zero buffered bytes cannot prove EOF or waiting: the actual read may explicitly report EOF while OPEN. Positive short progress finishes immediately; nonblocking EAGAIN remains unchanged. Unknown, malformed, lost or uncertain effects never authorize another attempt. Native caller loss, acknowledged draining, terminal teardown and refused COMPLETE preserve original custody without replay or fabricated EINTR.
Stream admission, wire behavior and state now occupy a dedicated thematic module, separate from common external framing and caller cleanup. Inline rustdoc describes original-generation, no-progress and retirement invariants. Twelve new sealed-service unit controls are authored and unrun, covering zero/EOF, vector waits, source preservation, nonblocking refusal, closed-original aliases, cursor races, malformed retry, peer closure, cancellation, release failure, terminal teardown and completion refusal. The prior mode-refusal control now verifies supported changes preserve identity and access.
The native inherited-stream workload changes mode through an alias, queries the original fd to see the same mode, closes that number after first progress and continues blocking writes through its alias. EAGAIN is not accepted as a blocking result. Original lender, authority, timeout and exit gates remain. Scheduling does not prove a particular wait occurred. Existing cooperative bounded turns remain; no new grant, allocation, deadline, fixed retry count or native protocol family is introduced. Event-driven poll/select remains separate required work; no measured speedup is claimed.
Four of the five concrete I/O implementation substeps are now complete under the testing waiver. Authenticated caught-signal interruption remains unfinished, so complete I/O acceptance stays open. Phase progress is 17.36% weighted and 5.61% whole acceptance: 22/460 parents and 446/907 sub-items, under 160 decomposed parents. Existing parent/section weights are unchanged. Both full EriX guest-build generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.
Reviews: Posixd, Integration, Rootd, ABI contract, manual.
Shared status replacement and retained blocking channels are signed and published: docs
cd5d00fd, integrationb1b94bc6, lib-posixabid3f6937f, posixd8d475984, rootde458ca88. The independent Integration helper1e6543a9remains selected separately from final catalogs. Publication comprises six signed commits in five repositories, three Cargo selectors and nine catalog selectors, with original remote equality receipts and clean feature trees.Compatibility1.9 extends OpenStatus with exact query/replacement mode, full checked shared bits and reserved-zero framing. Successful replacements echo all requested bits. Complete result preparation precedes mutation; aliases share status while immutable access, file cursor and local fd flags remain separate. Native streams refuse unsupported status changes until provider readiness exists.
Positive would-block channel calls with NONBLOCK clear retain the original serving owner, validated description generation and complete request in counted client storage. A fair turn probes only that original native caller and checks its selected ring. Observed invalidation cancels without an effect or invented EINTR; draining and terminal cleanup retain custody. Unknown absence or malformed evidence freezes ordinary effects. Queued data, free space or final peer closure yields short progress, EOF or EPIPE. Empty I/O remains immediate after access checks. Prepared results survive refused COMPLETE without replay.
Waiting turns do not recopy source bytes or rescan vectors or unrelated clients. The existing cooperative native probe loop remains; no kernel event facility or measured speedup is claimed. Sixteen new unit controls are authored and unrun: three compatibility controls and thirteen Posixd status/wait/lifetime controls. The native peers change original-alias modes, perform an acyclic one-byte handshake and retain a single EOF call until peer closure. Actual scheduling is not evidence that a particular handshake call waited. Existing authority, timeout and exit gates remain intact.
The source audit also fixes stale independent codec minors: descriptor literals carried minor5 and Open extent controls restored minor7 under the previous minor8 parser. Current independent fixtures use minor9; malformed and obsolete-minor controls remain explicit. The bug report uses the canonical template and distinguishes source inference from executed reproduction.
The complete I/O scope remains open for authenticated caught-signal delivery and required native-stream blocking readiness. Three published implementation substeps and two unfinished substeps now divide the existing parent weight, exposing actual partial completion without changing its weight or closing the parent. Phase progress is 17.28% weighted; whole acceptance remains 5.61% with 22/460 parents, 445/907 sub-items and 160 decomposed parents. Both full EriX guest-build generations and rebuilding external Rust/LLVM inside EriX remain required and unperformed. Tests, builds, lint checks, generated docs, VM/profiler execution and CI observation remain deferred by user instruction; no test pass or warning-free build is claimed.
Reviews: ABI, Posixd, Rootd, Integration, manual.
The positioned/vector I/O and shared-seeking implementation is signed and published: lib-ipc
727b1470, lib-posixabiddc59f2c, posixd1fd58a05, vfsd020e9feb, e2fsda9b91e44, ramfsd03bea99f, fatd8ab6df60, integratione0c9cfc1, docs2c521015. Complete file I/O remains open for actual signal interruption and blocking/wait integration. Checkpoint publication does not accept that unfinished runtime scope.Compatibility1.8 defines exact positioned/vector/seek families, checked borrowed vector sums and signed positions. Pread/Pwrite preserve the shared cursor; Pwrite ignores APPEND. One gathered prefix preserves native append atomicity. Fresh END/DATA/HOLE size comes from the same live admitted candidate and original provider object, including write-only descriptions, without new read authority or path reopening. Streams/channels retain nonblocking behavior and reject positioning. Access checks precede empty I/O.
Disjoint candidate-write version two replaces the superseded API and carries an explicit full-width end limit. Ext/RAM choose EOF, clip the prefix and write in one exclusive turn. Signed boundary writes report EFBIG before effects; boundary reads distinguish EOVERFLOW before EOF from actual EOF. Positive result correlation checks the limit, while zero progress preserves content, timestamps and the shared cursor. Native callers retain their own full-width limits.
Canonical correlated BUSY/RETRY without progress preserves the original fd for a later new call. Malformed/lost/uncertain results retain cleanup-only custody; refused completion never replays an effect. This fixes VFS transient admission, Posixd transient admission and signed offset maxima. The reports use the bug template and remain source-derived, without executed reproduction claims.
Thirty-seven new unit controls are authored and unrun: seven compatibility codec, five IPC codec, two ext, two RAM, two FAT/exFAT, five VFS and fourteen Posixd file/stream/channel controls. The native realm workload covers positioned cursor preservation, append independence, gathered/scattered bytes, shared seeks, fresh EOF after an independent writer and sparse growth. Original native authority and exit/deadline gates are preserved.
Current phase progress is 17.04% weighted and 5.61% whole-item acceptance: 22/460 parents and 442/902 sub-items. Actual signal delivery and blocking waits remain unfinished; transport failure or caller disappearance never fabricates EINTR. Both full EriX guest-build generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.
Complete native Open/openat implementation is signed and published: lib-ipc
6b96c569, e2fsdaedb65bb, ramfsddc1de465, fatd0e209121, vfsda368b741, posixd85efb7f9, exsh3ee15a96, docsc8565b7b, integration9fb56e3d. Dynamic acquisition is accepted under the testing waiver, completing the Open/Close/duplication checklist item. Other filesystem mediation, libc/process integration and self-hosting remain unfinished.Conditional creation uses distinct exact native/private families under the existing acquisition scope and original provider root. Posixd captures the authenticated current process mask and derives owner/group policy from fresh complete parent write/search evidence only after final-name absence. Parent setgid and selected-group membership constrain group/special bits; UID zero adds no privilege. VFS requires a writable scope and actual mount even for a Read descriptor and retains original candidate/provider/result cleanup before effects. Ext captures committed inode identity inside the full regular-file transaction, including complete default ACL inheritance and independent child storage; RAM reserves node/handle capacity under proven ACL absence. FAT/exFAT explicitly refuses unknown POSIX metadata.
Created access is frozen independently of the resulting mode, so mode-000 creating descriptors remain usable. Only original successful COMPLETE publishes the fd. A definite nonexclusive conflict retires the failed key before fresh search; stale evidence, malformed results and uncertain effects never replay creation. Cancellation and failed publication retire pins/callers without unlinking committed names. Shared parent/fence helpers and result framing remove duplication; ext publication adds no later fallible media read. No measured speedup is claimed.
Nineteen new unit controls are authored and unrun: four wire, two ext-media, two RAM, one FAT, three VFS and seven sealed-client controls. They cover full IDs/framing, policy and capacity refusals, mode-zero access, current masks, inherited groups, complete multipage ACLs, dangling links and directory suffixes, conflict/stale evidence, lost/malformed replies and refused publication. The native binding workload now checks mode-zero writes, exclusive conflicts, later DAC refusal, post-close persistent bytes, append at real EOF, conditional Open truncation, changed current-mask removal of owner-read permission and restoration, and denied creation by its Read-only peer. It reuses the existing correlated mask-exchange helper. Only its first explicit peer receives inherited acquisition access; realm/generation-separated names prevent fixture collisions. Existing literal producer controls and scenario exit/deadline requirements are preserved.
Current phase progress: 17.04% weighted, 5.61% whole-item acceptance; 22/460 parents and 442/902 sub-items. Both full EriX guest-build generations and rebuilding external Rust/LLVM inside EriX remain required and unperformed. Test-only execution is waived, never reported as a pass.
Dependencies: lib-posixabi#1, posixd#1
Dependencies identify required contracts and closure gates; preparatory inventory/design can proceed in parallel under one owner per edited file. Link bounded implementation issues and their PRs here before claiming acceptance. Use
feature/posix-compat, regular signed commits in the canonical contribution format, and WIP PRs linked to the exact coherent component graph. All cross-repository Cargo/catalog selections and CI helpers use full 40-character lowercase commit hashes, including transitive dependencies; do not substitute branch, tag or implicit HEAD selection.Close criteria only with their own reviewed deliverables and validation evidence. Pending, skipped, cancelled, failed or predecessor-only results remain distinct. Keep main images unchanged until explicit promotion direction; technical completion does not authorize merges, release tags or publication.
Counted pipes and original-controller native SIGPIPE are implemented in the signed pipe feature. Authored controls remain unrun; testing and CI observation are waived. Current source, acceptance and review links are recorded in the Phase6 master.
Detailed scope and contracts
Original-object advisory lock completion — 2 October 2026
Tests/builds/lint/generated documentation, VM/profiler execution and CI observation remain deferred; guest rebuilding remains required.
Conditional native permission updates — 2 October 2026
Native RAM/ext/FAT/VFS metadata updates and restricted policy helpers are implemented; compatibility chmod/chown/access consumers remain open.
Compatibility truncate and sync — implemented, 2 October 2026
Names, numeric identifiers and credentials grant no new device, mount or endpoint authority.
One shared control mapper admits complete capacity, correlates original object/command/argument/persistence, and preserves exact native refusal domains. Definite refusal permits later use without automatic retry.
Current-minor fixtures and error-precedence restoration are corrected; repeated rejection arrays are simplified.
No executed conformance, warning-free build, measured speedup or complete system security acceptance is claimed.
Phase completion is 19.44% weighted, 8.01% whole acceptance: 28/460 parents and 489/949 children. Both full EriX guest generations and external Rust/LLVM guest rebuilding remain required and unperformed. Complete libc entry points and subsequent filesystem/compatibility features remain open.
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.
Original filesystem persistence — signed source acceptance, 2 October 2026
Compatibility truncate/ftruncate and fsync/fdatasync serving, its complete native workloads and full-item acceptance remain open in retained-description persistence.
They separate volatile/persisted bytes and cover writer and full/fast-recovery interruption boundaries, lost replies, partial checkpoints, original routes, capacity/refusal, checksum dialects, wrapped descriptors and identities, later revocations, imported superblocks and actual clock-free file operations.
Source acceptance is not an executed persistence result, warning-free build or measured speedup. Both full EriX guest generations and external Rust/LLVM rebuilding in EriX remain required and unperformed.
Phase progress is 19.20% weighted, 7.61% whole acceptance: 27/460 parents and 486/949 children.
Cross-provider filesystem lifetime — signed source acceptance, 2 October 2026
Two live binding scenarios cover RAM, ext and separately selected FAT32/exFAT: conditional replacement/unlink, retained aliases and original identities, moved/detached directories, name reuse, supported links and read-only, cross-filesystem and unsupported-link refusals. Final media observers require reclaimed allocations, consistent reverse indices and clear undo ownership.
Both full EriX guest generations and external Rust/LLVM guest rebuilding remain required and unperformed.
Phase progress: 19.12% weighted, 7.61% whole acceptance; 27/460 parents and 485/949 sub-items.
Signed lifetime source acceptance:
Current-source acceptance now covers cwd navigation and contextual launch,
exact object/entry and redirection serving, together with compatibility shared
descriptions through namespace changes and original cleanup.
Vfsd's cwd and contextual
serving criteria are accepted; its original ownership and retired-bridge criteria
were already complete. The namespace issue also reconciles its provider criterion
with prior signed RAM/ext/FAT completion. Complete cross-provider live conditional
workloads, resource/refusal, recovery/reuse coverage and coherent runtime graph
adoption remain open. Full EriX guest generations and external Rust/LLVM rebuilding remain
required and unperformed.
Recomputed progress: 19.02% weighted, 6.81% whole acceptance; 25/460 parents and 482/949 sub-items.
Original-object file status — 30 September 2026
Explicit native conversion requires complete known fields and three independent source-qualified times.
Prefix search remains mandatory. No additional native route or clock grant is introduced.
They cover hostile framing, missing observations, exact correlation, capacity, prefix denial, mode-zero final objects, real bases, symlinks, write-only aliases, cursors and cancellation.
Complete provider metadata, pipe/stream status and shared seekable directory streams remain unfinished in the status and directory implementation. No additional checklist acceptance is claimed. Both full EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.
Shared directory descriptions — 30 September 2026
Tell retains metadata-only bookmarks in the actual counted description arena and reuses existing associations; seek requires the original full description key.
Complete native correlation and output admission precede cursor progress; capacity and unknown-identity refusals preserve it. No new native route or clock grant is added.
The full status/directory work remains open: complete provider metadata/identity, pipe/stream status, remaining controls and full-parent reconciliation are unfinished. Both full EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.
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 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.
Original FAT-family timestamp evidence — 30 September 2026
Unknown offset bits cannot invent UTC.
Full compatibility status still refuses incomplete required metadata.
Existing date quantization assertions and actual VM/image checks remain and now require truthful UTC availability.
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 namespace mutation plan and provider custody — 1 October 2026
The complete namespace feature remains open.
Known pre-effect refusal preserves original pending custody; existing-object touch and absent no-create observations retain their distinct lifetimes.
They cover original-name admission, actual RAM/literal-ext effects, hardlink entry distinction, known refusal, completed-operation retirement, cleanup and namespace reuse.
The namespace umbrella now checks its completed status/directory criterion, matching the already accepted feature and phase master. No new namespace criterion is accepted for the provider prerequisite. Both complete EriX guest generations and external Rust/LLVM rebuilding remain required and unperformed.
RAM open-object lifetime implemented — 1 October 2026
Completed exact-entry cleanup never selects a reused node. Same-name rename is a metadata-preserving no-op; trusted change events remain on held displaced objects and clockless effects invalidate the affected observation.
Both existing VM scenarios require the new OPEN_UNLINK_OK marker. Namespace output capacity is admitted before effects; changed provider controls preserve their original custody/refusal coverage with the new detachment behavior.
The complete namespace mutation and lifetime design remains open: RAM hardlink storage, directory navigation/detachment, ext/FAT object lifetime, complete conditional native contracts and compatibility namespace serving are unfinished. No broader namespace acceptance is inferred from this provider boundary.
Both complete EriX guest generations and external Rust/LLVM rebuilding remain required and unperformed.
Independent RAM entries and retained directories — 1 October 2026
Unlink/relink of the same object and name cannot revive an old exact-entry grant. Creation beneath a removed directory refuses before effects.
Ext/FAT original-object lifetime and complete compatibility namespace serving also remain unfinished in the owning design.
All 37 runtime configurations, packaging, fixtures, CLI/shell routing and reports adopt the new quota; obsolete layouts and missing entry policy are refused. Nineteen Rust and four Python controls, plus two shell policy refusal cases, are authored and unrun. The twenty-operation native VFS transcript requires shared hardlink metadata, retained bytes after both names disappear, and removal of a held empty directory before its final close. Both existing RAM VM scenarios require the corresponding observations.
Both complete EriX guest generations and external Rust/LLVM 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 namespace intents and original raw readlink — 1 October 2026
Unused fields are canonical zero; names and symbolic targets carry no native authority.
Only the admitted prefix is staged; actual counted storage exhaustion refuses without silently shortening success. Final target bytes are never traversed, no content grant or fd is acquired, and all original callers, parents, links and expansion owners retire before delivery.
Complete mutation permission/effect mediation, two-path rename/link, legacy cwd migration and ext/FAT conditional transactions remain unfinished. Raw readlink is split from the previous combined two-path criterion to record one fully implemented operation boundary; the full namespace parent remains open. The existing native binding workload now requires seven raw-target observations/refusals per peer, including readlinkat and the read-only scope, without new authority or fixture budgets.
Both complete EriX guest generations and external Rust/LLVM rebuilding remain required and unperformed.
Original-entry namespace mutation mediation — 1 October 2026
Hardlink source requires parent search; changed directories require write/search.
Ordinary final-link/trailing-directory probes cannot substitute for entry evidence. Cleanup cannot undo a completed mutation.
The independent filesystem model keeps real initial directory entries, so a removed name cannot reappear from a fixture fallback.
They cover independent dirfds, link following, same-object rename, complete ACL/sticky policy, exact refusals, original detached content, cancellation and uncertain completion. The read-only peer requires all five mutation families to refuse.
The exact wire/migration, actual permission/effect mediation and two-path semantic criteria are source-accepted. The full namespace parent stays open: legacy cwd migration, required ext/FAT conditional transactions and cross-provider lifetime remain unfinished. Both complete EriX guest generations and external Rust/LLVM guest rebuilding remain required and unperformed.
Related records and contracts
[FEATURE] [P07] Implement POSIX file descriptors and namespace semantics within delegated rootsto [FEATURE] Implement POSIX file descriptors and namespace semantics within delegated rootserikinkinen referenced this issue from erix/integration2026-09-24 21:10:13 +02:00
erikinkinen referenced this issue from erix/launchd2026-09-24 21:10:14 +02:00
erikinkinen referenced this issue from erix/launchd2026-09-24 21:10:15 +02:00
erikinkinen referenced this issue from erix/launchd2026-09-24 21:10:16 +02:00
erikinkinen referenced this issue from erix/procd2026-09-24 21:10:18 +02:00
erikinkinen referenced this issue from erix/procd2026-09-24 21:10:19 +02:00
erikinkinen referenced this issue2026-09-24 21:10:20 +02:00
erikinkinen referenced this issue from erix/integration2026-09-24 21:10:24 +02:00
erikinkinen referenced this issue from erix/integration2026-09-24 21:10:26 +02:00
erikinkinen referenced this issue from erix/docs2026-09-30 11:56:33 +02:00
erikinkinen referenced this issue from erix/integration2026-09-30 11:56:43 +02:00
erikinkinen referenced this issue from erix/lib-posixabi2026-09-30 11:56:50 +02:00
erikinkinen referenced this issue2026-09-30 11:56:55 +02:00
erikinkinen referenced this issue from erix/rootd2026-09-30 11:56:58 +02:00
erikinkinen referenced this issue2026-09-30 13:23:19 +02:00
erikinkinen referenced this issue from erix/blockd2026-09-30 14:16:04 +02:00
erikinkinen referenced this issue from erix/coreutils2026-09-30 14:16:05 +02:00
erikinkinen referenced this issue from erix/crashd2026-09-30 14:16:05 +02:00
erikinkinen referenced this issue from erix/deviced2026-09-30 14:16:05 +02:00
erikinkinen referenced this issue from erix/drv-acpi2026-09-30 14:16:07 +02:00
erikinkinen referenced this issue from erix/drv-i80422026-09-30 14:16:07 +02:00
erikinkinen referenced this issue from erix/drv-ps2-keyboard2026-09-30 14:16:08 +02:00
erikinkinen referenced this issue from erix/drv-ps2-mouse2026-09-30 14:16:08 +02:00
erikinkinen referenced this issue from erix/drv-rtc-cmos2026-09-30 14:16:09 +02:00
erikinkinen referenced this issue from erix/drv-serial2026-09-30 14:16:10 +02:00
erikinkinen referenced this issue from erix/drv-virtio-block2026-09-30 14:16:12 +02:00
erikinkinen referenced this issue from erix/dynlinkd2026-09-30 14:16:12 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-09-30 14:16:13 +02:00
erikinkinen referenced this issue from erix/exsh2026-09-30 14:16:14 +02:00
erikinkinen referenced this issue from erix/extop2026-09-30 14:16:15 +02:00
erikinkinen referenced this issue from erix/fatd2026-09-30 14:16:15 +02:00
erikinkinen referenced this issue from erix/fbcond2026-09-30 14:16:16 +02:00
erikinkinen referenced this issue from erix/hotplugd2026-09-30 14:16:17 +02:00
erikinkinen referenced this issue from erix/inputd2026-09-30 14:16:18 +02:00
erikinkinen referenced this issue from erix/irqd2026-09-30 14:16:20 +02:00
erikinkinen referenced this issue from erix/kernel2026-09-30 14:16:20 +02:00
erikinkinen referenced this issue from erix/keyd2026-09-30 14:16:21 +02:00
erikinkinen referenced this issue from erix/launchd2026-09-30 14:16:22 +02:00
erikinkinen referenced this issue from erix/lib-block2026-09-30 14:16:22 +02:00
erikinkinen referenced this issue from erix/lib-bootstrap2026-09-30 14:16:22 +02:00
erikinkinen referenced this issue from erix/lib-capabi2026-09-30 14:16:23 +02:00
erikinkinen referenced this issue from erix/lib-driver2026-09-30 14:16:23 +02:00
erikinkinen referenced this issue from erix/lib-input2026-09-30 14:16:23 +02:00
erikinkinen referenced this issue from erix/lib-interrupt2026-09-30 14:16:24 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-09-30 14:16:25 +02:00
erikinkinen referenced this issue from erix/lib-log2026-09-30 14:16:25 +02:00
erikinkinen referenced this issue from erix/lib-service2026-09-30 14:16:26 +02:00
erikinkinen referenced this issue from erix/lib-stdio2026-09-30 14:16:26 +02:00
erikinkinen referenced this issue from erix/lib-time2026-09-30 14:16:27 +02:00
erikinkinen referenced this issue from erix/lib-tty2026-09-30 14:16:27 +02:00
erikinkinen referenced this issue from erix/lib-vfs2026-09-30 14:16:27 +02:00
erikinkinen referenced this issue from erix/loaderd2026-09-30 14:16:28 +02:00
erikinkinen referenced this issue from erix/logd2026-09-30 14:16:28 +02:00
erikinkinen referenced this issue from erix/memd2026-09-30 14:16:28 +02:00
erikinkinen referenced this issue from erix/named2026-09-30 14:16:29 +02:00
erikinkinen referenced this issue from erix/pagerd2026-09-30 14:16:29 +02:00
erikinkinen referenced this issue from erix/powerboxd2026-09-30 14:16:30 +02:00
erikinkinen referenced this issue from erix/probed2026-09-30 14:16:30 +02:00
erikinkinen referenced this issue from erix/procd2026-09-30 14:16:31 +02:00
erikinkinen referenced this issue from erix/ramfsd2026-09-30 14:16:31 +02:00
erikinkinen referenced this issue from erix/seriald2026-09-30 14:16:32 +02:00
erikinkinen referenced this issue from erix/timed2026-09-30 14:16:33 +02:00
erikinkinen referenced this issue from erix/ttyd2026-09-30 14:16:33 +02:00
erikinkinen referenced this issue from erix/vfsd2026-09-30 14:16:34 +02:00
erikinkinen referenced this issue from erix/vspaced2026-09-30 14:16:34 +02:00
erikinkinen referenced this issue from erix/docs2026-10-01 02:02:46 +02:00
erikinkinen referenced this issue2026-10-01 02:02:48 +02:00
erikinkinen referenced this issue from erix/integration2026-10-01 02:02:48 +02:00
erikinkinen referenced this issue from erix/rootd2026-10-01 02:30:59 +02:00