[FEATURE] Enforce deny-only realm credentials and access ACLs after native admission #10

Open
opened 2026-09-29 07:04:36 +02:00 by erikinkinen · 0 comments
Owner

Problem and motivation

Compatibility mode/status values currently describe metadata, but do not implement credential or ACL checks. Numeric IDs and permission bits must never create native authority. Unknown provider metadata and an absent ACL are distinct states, and a successful pure policy calculation cannot substitute for actual native admission.

Proposed behavior and scope

Compatibility 1.2 carries only an original directory role/selector and requested access bits. Actual sealed CLAIM clients select immutable effective credentials and original directory receipts. Vfsd checks the live metadata-directory operation and inherited namespace/write ceiling before fetching provider evidence. ReadWrite configuration cannot restore native rights. Complete canonical ACL pages preserve object/revision/count/range, order, required bases/masks and mode correspondence before any deny-only result. Partial ACLs, UID zero and combined partial group grants cannot bypass policy. Zero bits still require actual original-provider existence.

Per-query state retains one snapshot and a bounded streaming fold without a fixed ACL-entry limit. Original outbound and inbound owners remain attached through cancellation, result release and one-shot COMPLETE. Acknowledged Draining(NOT_FOUND) preserves route-loss retirement; unknown failures and unexplained absence keep custody. Stream and directory paths share the original caller helper and host fixture.

Final source review flattened the native client refusal condition without changing its requests or expected outcomes. Two additional signed cleanup/adoption commits select the final source; the implemented scope and twenty-four authored controls are unchanged. No tests, builds or CI observation were run.

Twenty-four new host controls and the extended native binding workload are authored and unrun. The native client requires seven directory-existence queries, five configured write refusals and absent-selector refusal before its inherited stream controls. Existing deadlines and resource policy are unchanged. Rustfmt was applied; all changed code remains below 1,000 lines (maximum 900) with inline rustdoc and missing_docs retained. Contracts and manual TeX are updated. Tests, builds, lint checks, rustdoc, VM/manual/profiler runs and CI observation remain deferred by user instruction; no pass, warning-free build or measured speedup is claimed. Generated API exports retain their explicit older source identity until generation resumes.

Native permission enforcement remains open for complete pathname/open/stat/mutation mediation and remaining provider support. Both EriX guest-build generations and rebuilding Rust/LLVM inside EriX remain required and unproved. Phase completion is 16.23% weighted, 4.81% whole-item, with 20/460 parents and 436/896 sub-items complete.

Only original job-lifetime READ_METADATA directory endpoints serve selector-free snapshots and bounded ACL pages. Vfsd uses the retained mount/provider handle and fresh private correlation, checks framing, handle, kind, revision and range, then replaces private identifiers with caller request correlation and the live VFS record ID. It does not reopen paths, synthesize ACL absence or broaden another endpoint's operation ceiling. Unknown evidence stays unknown, refused staging is cleared, and original owned completion custody prevents refetch/replay after refusal. Actual buffer geometry bounds pages without a new complete-ACL limit; entries remain in existing staging while the fixed prefix is rewritten.

Eighteen controls are authored and unrun: five wire, five provider transport, seven real-dispatch and one owned-completion. The original transport interface is shared and native path codecs/resolver fixtures are split; changed code remains below 1,000 lines (maximum 898), with inline rustdoc and missing_docs retained. Component contracts and the technical manual are updated. Tests, builds, lint checks, rustdoc, VM/manual/profiler runs and CI observation remain deferred by user instruction. No pass, warning-free build or measured speedup is claimed.

Native permission enforcement remains open: trusted credentials, full ACL acquisition and actual operation-specific effects still need to be connected. Value-inode ACL payloads and ACL-aware persistent mutation also remain unfinished. Both complete EriX guest-build generations and the Rust/LLVM guest rebuild remain required and unproved. Phase completion is 16.22% weighted, 4.81% whole-item, with 20/460 parents and 435/895 sub-items complete.

Launchd registers original realm stream receivers before exporting SEND views and serves actual owned CLAIM/COMPLETE/RELINQUISH. Each noncopyable row retains its exact Reply result. Vfsd registers exact endpoints before Powerbox, Launchd and cwd export, preserves legacy users and reserves original delivery storage independently of copied handle metadata. Every allocation family respects that reservation through provider Close and native/receiver settlement. Neither path replays an operation or COMPLETE after refusal. Native route invalidation retains draining custody until acknowledgment; request abandonment preserves an open stream and explicit Close preserves the lender.

Compiler-derived rows account for full protocol packets; Vfsd capacity descriptor version two includes mount, handle and invocation regions. Cleanup scrubs only written packet extents, conservatively retaining the full extent for unknown native output. This is a source cost reduction, not a measured performance result. Eight Launchd, nine Vfsd and four packaging controls are authored but unrun; existing arena controls are updated. The existing native binding workload exercises external writes, Close, exact process exits and lender preservation under unchanged gates.

Inline/component/manual contracts and coherent catalog adoption are updated. Changed code files remain below 1,000 lines (maximum 957); missing_docs enforcement remains and Rust formatting was applied. Tests, builds, lint checks, rustdoc, VM/manual/profiler runs and CI observation remain deferred by user instruction. No execution pass or warning-free build is claimed. The transport defect and stream feature are implemented; native filesystem permission policy, both complete EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished.

Phase completion is 16.21% weighted, 4.81% whole-item, with 20/460 parents and 434/894 sub-items complete. Binding cleanup acceptance is restored for completed implementation; waived testing is not a test pass.

Exact canonical pages bind the original handle/revision, complete count and contiguous range. E2fsd rechecks complete metadata and both attribute stores, preserves valid observations for later pages/conditional effects, and retires observed failures while clearing staging. Ramfsd explicitly refuses pages for absent storage. Libposixabi joins pages in caller-owned storage, poisons and clears failed or abandoned assembly, and exposes only complete canonical, mode-consistent metadata. Known absence has a separate constructor. No codec, ID, hash or collected view supplies native caller/provider authentication or authority.

Nineteen controls are authored but unrun: six wire, seven collection, four actual ext dispatch and two Ramfsd dispatch controls. They cover full IDs, large ACLs, malformed/mixed/stale evidence, incomplete cleanup, reply capacity, close and later conditional truncation. The original reduced decoder and checked ACL fixture are shared. Changed Rust files are below 1,000 lines (maximum 891), inline rustdoc and existing missing_docs enforcement are retained, and Rust 2021 formatting is applied. Component contracts and both relevant manual sections are updated. Full ext scans per page cost O(A * P) ACL work; no measured performance claim is made.

Native Vfsd/Posixd caller/route/effect integration, value-inode ACL payloads, persistent ACL-aware mutation and remaining provider effects remain open in the permission feature.

The distinct snapshot contract carries original retained handle/revision, explicit known mode/ownership and unknown/absent/present access-ACL evidence. Legacy stat is never converted into authenticated permission evidence. Full-width zero/MAX IDs and complete ACL counts have no small entry ceiling. Unknown or incomplete ACL evidence cannot become mode-only admission. Conditional truncation accepts explicit optional native time, so clock unavailability introduces no new operation restriction.

Ramfsd reads actual retained node ownership and establishes absent ACLs from its implementation. Both metadata setters share per-node revision updates before any selected fields or timestamps change. Change-and-restore cannot revive old evidence; aliases share revisions, unrelated nodes do not, and exhaustion refuses without partial mutation. Conditional truncation compares and resizes the same retained file in one exclusive provider turn, preflights reply storage and shares the existing resize helper with one handle lookup. No path resolution, capability acquisition or receipt transfer is added. Numeric handles and matching revisions remain descriptive.

Ten new controls are authored but unrun: four independent shared-wire controls and six actual Ramfsd state/dispatch controls for ownership/ACL evidence, stale/restore/exhaustion, aliases, closed/reused/wrong-kind handles, optional/malformed time and short reply storage. Source review removes duplicate metadata assignment and handle scans; changed Rust files are below 1,000 lines, with a maximum of 891. Rust formatting was applied. Tests, builds, lint checks, rustdoc, manual builds, profiler runs and CI observation remain deferred by instruction. No execution pass, warning-free build or measured performance result is claimed.

The master checklist exposes the completed shared ABI and Ramfsd portions separately. Native CLAIM/route integration in Vfsd/Posixd, complete filesystem ACL acquisition and remaining operation-specific effects remain unfinished; the overall permission feature stays open. Progress is 16.17% weighted, 4.81% whole-item, 20/460 parents and 431/891 sub-items. Both full EriX guest-build generations and rebuilding Rust/LLVM inside EriX remain unproved. Provider contract, Ramfsd implementation, permission design, native mediator review, coordinated images, Phase 6 completion.

Provider design, recorded before ABI implementation: add a distinct private retained-handle permission snapshot with explicit known-field bits, full UID/GID/mode, ACL state (unknown, proven absent, or present), complete ACL entry count, the original provider handle and a nonzero permission revision. A zero ID remains a real ID only when its known bit is set. Legacy stat is never converted to this contract. No snapshot, revision, handle number, credential or successful policy comparison grants native authority.

The consumer must first admit the original native caller and retained route, correlate the exact provider reply, retain the original provider endpoint/handle lifetime, and apply deny-only policy. Snapshot-dependent mutations carry the same revision to a provider operation that compares it and performs its effect in one serialized turn. Permission changes advance the per-object revision before changing state; exhaustion refuses without partial mutation. Changing permissions back does not revive an earlier revision. Handle close/reuse, route retirement and uncertain completion retain their existing cleanup rules. Already-open descriptor read/write behavior is not changed into repeated mode checking.

Implementation sequence within this feature: shared snapshot and conditional-operation frames; Ramfsd's actual node ownership, proven ACL absence and revision-checked truncation; then Vfsd and Posixd native-route integration, filesystem ACL acquisition and the remaining operation-specific effects. Ramfsd's first provider implementation does not complete the realm policy feature. E2fsd must inspect both inode-body and external ACL metadata; FAT must not fabricate known ownership from legacy zero fields. Present ACLs need complete canonical entries from the same object/revision, with counted/chunked transport rather than an arbitrary small entry limit; unknown, unsupported, malformed or incomplete evidence must refuse policy admission.

The first provider controls will cover wire literals and atomic encoding refusal, real zero/max ownership, unknown versus absent ACLs, same-object revision changes including restoration, foreign/closed handles, unchanged filesystem contents on stale truncation, and counter exhaustion before any metadata/timestamp mutation. Later native controls must demonstrate both denial and permitted effects after original CLAIM/route admission, plus revocation, replay and cleanup. Tests are authored but not executed under the current testing/CI deferral. Implementation and integration remain open.

Dependencies and review: shared ABI, Ramfsd, Vfsd, Posixd, and Phase 6 tracking.

Final contract reconciliation — 29 September 2026: launchd dfb7fcde, posixd 0d5a3ba6, docs 7429b15c, integration 1bc91ad2. Four additional signed documentation/catalog commits remove superseded adoption-pending claims and correct remaining minor-version text. This continuation now totals 59 signed commits across 54 repositories; runtime implementation and native scenario gates are unchanged. Trusted credential intake is complete; provider-backed permission effects remain open. Checklist accounting remains 16.15% weighted, 20/460 parents and 429/888 sub-items. Tests, builds and CI observation remain deferred; no execution result or complete guest OS/toolchain rebuild is claimed.

The next provider boundary must distinguish known UID/GID/mode and proven ACL absence from unavailable metadata. The existing descriptive stat response permits zero for unknown ownership and has no coherent ACL-support/lifetime evidence, so it cannot be used as authenticated permission input. Bind any new snapshot and effect to the exact retained native object, metadata revision and original caller; never treat unknown support as absent ACL. Permission design, credential custody, Phase 6 completion.

The authenticated configuration owner selects explicit real/effective/saved UID/GID values. Launchd derives native identity from guarded child custody, preserves complete client records through reversible sorting and freezes every group word. Group pulls follow all authority records and transfer no capability. Procd retains G in original provisioning and startup; its native receiver ceiling remains C+A+6. Posixd binds canonical indices to actual original receiver owners and full native generations, retaining the immutable plan for the service lifetime. Credential and authority selection share the sealed, live-client gate; retirement immediately disables both. Real/effective selection is explicit. Borrowed canonical wire groups need no copy, alignment cast, repeated validation or small fixed count limit.

Seven new controls are authored for exact group pulls, restoration, large-group startup, sealed receiver selection and retirement, valid scalar substitution, surplus receipts and unaligned membership. Existing native reciprocal, owner-loss and binding diagnostics carry disjoint groups including zero and UINT32_MAX. Their two-plan budgets are 792 and 2840 bytes respectively, with original capability budgets, exits, markers and deadlines retained. Source audit also corrected remaining literal START budgets and a missing explicit fixture group count. Changed code files are at most 726 lines, with inline rustdoc and existing missing_docs enforcement retained.

Formatting is applied. Tests, builds, lint checks, rustdoc, manual builds, profiler runs and CI observation remain deferred by instruction; testing is waived, never reported as passed. Trusted per-client credential intake is implemented. Provider-backed ownership/mode/ACL evidence and actual native-before-policy operation effects remain unfinished, so the overall permission feature stays open. Completion is now 16.15% weighted, 4.81% whole-item, 20/460 parents and 429/888 sub-items. Both full EriX guest-build generations and rebuilding Rust/LLVM inside EriX remain unproved. Credential lifetime, permission design, runtime review, coordinated images, Phase 6 completion.

The exact plan is 112+72C+24D+16H+64A+4G bytes. The original reserved validation word remains intact. RBS1 minor three is 320 bytes, public reservation 88, and private provisioning 128/336; G is retained explicitly and earlier incompatible framing refuses. Group replies require zero receipts. None of this authenticates a client, selects host identity or adds native authority.

Ten new controls are authored, with existing literal fixtures updated for exact framing, malformed membership, count correlation, capability counts and failure-preserving output. Source review and Rust formatting are complete; tests, builds, lint checks, rustdoc, manual builds, profiler runs and CI observation remain deferred. No pass, warning-free build or native permission result is claimed.

This shared source checkpoint precedes coordinated Launchd, Procd, Posixd and fixture changes. Existing Cargo consumers and image catalogs retain their preceding immutable revision. Trusted runtime credential intake and provider-backed operation gates remain unfinished; the permission item stays open and checklist completion remains 16.07%, 20/460 parents and 428/888 sub-items. Both full EriX guest-build generations and the guest Rust/LLVM rebuild remain unproved. Wire contract, storage contract, runtime design, codec review, manual review, Phase 6 completion.

Counted credential intake design — 29 September 2026: retain explicit real/effective/saved UID/GID values and a canonical supplementary-group range for every original client. The realm configuration owner chooses these compatibility labels through its already authenticated native configuration route; ordinary clients, request text and environment cannot mutate them. Every value, including zero and the full unsigned maximum, remains descriptive within the existing native ceiling.

Extend shared configuration counts with a separate supplementary-group count G. Store groups as canonical little-endian u32 entries in the immutable plan after existing authority records, with no extra capability or hidden group heap. Per-client ranges must partition that tail exactly in client order; each range is strictly increasing and unique. Group views decode bytes safely without alignment casts. This retains complete membership and enables binary-search lookup without a fixed small group limit.

The coordinated contract uses a 112-byte plan header and 72-byte client records, preserving the original reserved word used by reversible global validation. Exact plan bytes are 112+72C+24D+16H+64A+4G. Pull framing retains its original native receipt obligations; group records carry no capability. Startup and provisioning carry G explicitly, and old incompatible framing is rejected. Runtime consumers must bind these records to actual original receiver custody, full generations and the frozen plan before ordinary effects, preserving retirement and stale-client refusal.

This is an implementation sequence for the existing feature, not completed runtime enforcement. Shared codecs, Launchd production, Procd storage/startup, Posixd intake, fixture producers, immutable dependency adoption and authored native controls must all be coordinated. Provider-backed mode/ACL snapshots and effect gates remain required afterward. Tests, builds and CI observation remain deferred by instruction.

UID zero has no bypass, matched classes cannot fall through, duplicate qualifiers are refused and a combined group request must be covered by one matching entry.

Native admission and exact original client/provider provenance remain mandatory. Unknown ACL support cannot become absence. Trusted per-client credential intake, coherent provider snapshots and actual native operation gates are still unfinished implementation. The helper must not be indiscriminately inserted before reads/writes of already opened descriptors. The feature issue remains open with enhancement, security and phase-6 metadata.

Twelve original controls are authored but unrun, covering direct permission outcomes, masks and combined requests, UID zero, special bits, full-width IDs, malformed metadata and large caller-owned storage. Rust formatting was applied. Tests, builds, lint checks, rustdoc, manual builds, profiler runs and CI observation remain deferred; no pass or warning-free result is claimed. The metadata substep is implemented, while the complete permission-enforcement item remains open. Both EriX guest-build generations and the guest Rust/LLVM rebuild remain unproved. Permission contract, runtime design, Phase 6 completion.

Completion is 16.07% weighted, 20/460 parents and 428/888 sub-items across 158 decomposed parents. Reviews: library, mediator, catalogs, manual.

Define checked borrowed credential groups, permission sets and access ACL views in Lib-posixabi, with explicit normalization over caller-owned storage and no incidental entry/group ceiling. Implement owner, named-user, matching-group and other checks with the ACL mask and mode consistency. UID zero receives no implicit bypass, and set-ID or executable bits supply no native privilege. Select effective or real IDs explicitly at the owning operation adapter.

Wire trusted per-client credentials into the original realm/process identity, bind object metadata to the exact native-admitted operation, and apply the policy before effects. Authenticate provider support, object identity, snapshot freshness and ACL absence; unknown or malformed metadata must not silently become an empty ACL or permissive mode. Preserve the original route, requested operation, native ceiling and cleanup lifetime across metadata updates and revocation. Directory/default-ACL creation and mutation belong to coordinated filesystem semantics; this feature must not claim enforcement from ACL byte preservation alone.

Authority, security and reliability

Native admission precedes compatibility policy. The operation uses only an already held and natively authenticated object/route within its selected rights. A credential/ACL result is descriptive and never mints, discovers, transfers or restores a capability. UID zero, chmod/chown-like changes, executable mode and group changes may alter compatibility denials only within that original native ceiling. Trust comes from retained process and provider ownership, never request-authored IDs or digests. Missing evidence blocks effects; partial acquisition and cleanup retain original owners.

Acceptance criteria

  • Checked full-width UID/GID and normalized group/ACL storage with no fixed small limits; reject duplicate ACL qualifiers, invalid permissions and inconsistent mode/mask metadata.
  • Owner and named-user precedence, mask application, primary/supplementary groups, no other-class fallback after a matching denial, and combined-access behavior follow the selected profile.
  • Native caller/realm/process, receipt, object and operation evidence precedes policy, including revoked/missing routes and stale generations.
  • UID zero, permissive mode/ACL, changed ownership and executable bits cannot recover missing rights or choose an undelegated route.
  • Trusted credentials and provider metadata reach actual runtime checks; pure policy tests alone do not complete this feature.
  • Appropriate positive, negative, cleanup and bounded native scenarios are authored. Tests, builds, lint checks, profiler runs and CI observation remain deferred by user instruction; no execution pass is implied.
  • Update component/manual documentation, signed immutable dependent revisions and linked tracking.

Alternatives and tradeoffs

Keep checked metadata separate from native custody. Borrow normalized caller-owned slices rather than allocate hidden storage or impose incidental table limits. Standard mode rules follow the Open Group file-access specification; access ACL semantics follow the maintained ACL specification, an optional compatibility profile rather than a POSIX.1 base requirement. Default ACL inheritance, persistence and complete chmod/chown APIs need the separately coordinated filesystem metadata contract. No third-party implementation is copied.

Tracking and rollout

Complete native Open/openat implementation is signed and published: lib-ipc 6b96c569, e2fsd aedb65bb, ramfsd dc1de465, fatd 0e209121, vfsd a368b741, posixd 85efb7f9, exsh 3ee15a96, docs c8565b7b, integration 9fb56e3d. 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.

Counted bound-file resize — 29 September 2026: lib-ipc 93920c87, lib-posixabi d63943f4, launchd 92c27f94, vfsd 080f48dd, posixd c5fab30e, exsh 836d2da2, docs 7b5ca67e, integration 4ed92218, rootd cb910991.

The bound-file feature now connects authenticated supervisor preparation to sealed-client permission mediation and original provider cleanup. Dedicated public begin/prepare and private resolve operations preserve the actual scope receipt, full generations and explicit ResizeFile/Write purpose, including an empty original file. Shared filesystem custody retains original provider identity before alias movement and across partial or uncertain effects. Obsolete directory-only API names are removed; the existing private retirement wire remains stable.

Compatibility 1.3 adds FileResize using only that client's frozen selector and a full-width length. The shared directory/file permission owner requires complete mode/owner/ACL evidence under actual sealed credentials before one conditional effect on the same object/revision. UID zero has no override. Stale comparisons refuse without replay; malformed effects, cancellation and refused completion preserve original custody and fixed results.

Nineteen new host controls are authored and unrun: three shared-IPC, three compatibility-codec, four Launchd, two Vfsd and seven Posixd. Existing producer transcript and scenario controls are updated. The native workload creates an empty file through ordinary shell redirection, requires owner growth and nonowner/absent-selector refusal, then independently reads seven zero bytes plus EOF after all realms retire. Explicit fixture storage is 3096 plan bytes, 36 authorities and 22 Ramfsd handles; existing process and capability pools and lifecycle gates remain. The nested conditional-resize test module path is also corrected after rustfmt exposed its source-resolution error.

All 55 affected repositories are published in 56 signed commits, updating 206 Cargo and 111 catalog selectors. Rootd and both helper catalogs retain the independent Rust helper eee623e3, separate from the final catalog head. Read-only inventory covers 3387 source files in 76 repositories, all below one thousand lines; the largest changed source has 990 lines. Component contracts and technical manual are updated, and rustfmt was applied.

Broader filesystem mediation, dynamic descriptor/pathname operations, both full EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished functional requirements.

Explicit native conditional resize — 29 September 2026: lib-ipc d785e672, vfsd 660d0fa1, powerboxd 52a5636e, launchd ba2d2a87, ttyd f220da8e, docs 51e49f5d, integration 47fb79a7, rootd 37ca91ad.

The separate RESIZE_FILE grant is implemented for one retained regular file. Original byte WRITE and directory READ_METADATA operation families remain unchanged. Vfsd forwards original permission snapshots and complete ACL pages, admits the retained write ceiling, matches the public object correlation and reserves fixed result space before trusted time or provider effects. The conditional adapter uses the original private handle/revision and a fresh private request correlation. Only a correctly framed provider RETRY denotes definite staleness; uncertain transport and malformed replies become INTERNAL. There is no replay, name lookup or unconditional resize fallback.

Original native CLAIM/COMPLETE/RELINQUISH custody keeps one fixed result through completion refusal and cancellation. Metadata observations preserve one-shot custody, explicit Close covers every supported resize lifetime, and receiver-disposal failure retains the counted row. Canonical operation recognition replaces duplicated launch/broker/session lists without widening bootstrap defaults or bypassing explicit manifest, session, approval and lifetime limits. Trusted review describes permission observation and conditional resizing together.

Twenty-three new controls are authored and unrun: four wire/domain, fourteen Vfsd transport/resolver/dispatch/native-custody, two broker, one launch and two session/review controls. Component contracts and the filesystem manual are updated. Rustfmt was applied; the largest changed source has 902 lines. The read-only inventory covers 76 repositories and 3377 source files, all below one thousand lines. Fifty-five repositories are published in 56 signed commits, with 206 Cargo and 111 catalog selectors updated. Rootd's two Cargo edges and both helper catalogs retain the independent Rust-helper 5b9676ff; the later Integration catalog head stays distinct.

Counted realm preparation and sealed-client conditional mediation, their native workload, other filesystem operations, both complete EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished.

Related reviews: wire, Vfsd, broker, launch, session, manual, Integration. Fresh fixed-parent accounting is 16.24% weighted, 4.81% whole-item, 20/460 parents and 438/898 sub-items. The native layer receives its completed sub-item; the broader permission item remains open.

Native ACL metadata coverage — 29 September 2026: integration e9dbf028, e2fsd cc3d02a0, docs 829c91a8, rootd 93e2d63b.

The dedicated scenario uses a separate ext4 image and Rootd's existing explicitly writable VFS fixture. Twenty-five original native requests cover local/value ACL mode and full-owner changes, owner-only preservation, rejected type changes with unchanged metadata, special bits, an untouched peer, deletion and definite second-unlink absence. A directory retains its original default ACL. No new capability, realm binding, provider selector or production policy is added.

Independent post-VM host decoding compares every access/default ACL entry, unrelated attributes and original payloads, confirms local/value storage, and retains the mandatory read-only e2fsck step. The constructor proves actual storage kinds before boot; 512 named entries are fixture geometry, not a provider limit. Bounded host reads avoid copying a complete disk. Five Rust orchestration controls and seven Python oracle controls are authored and unrun. Rustfmt was applied; changed source stays below one thousand lines. A read-only inventory covers 76 repositories and 3359 source files; none reaches that threshold.

The provider acquisition/mutation/lifetime scope, including its native scenario authoring, is implemented and is accepted under the testing waiver. Four repositories are published in five signed commits. Rootd's two Cargo selectors and both independent helper catalog selectors select the original helper 5284c4a6; seven catalog edges adopt that helper, its consumer and maintained contracts. The later catalog-only head is distinct. Related reviews: Integration, Rootd, provider, manual.

No fixture generation, tests, builds, lint checks, Rustdoc generation, VM/manual/profiler runs or CI observation were executed. No pass, warning-free build, measured speedup or guest-build result is claimed. Native conditional mediation remains open: current realm directory-metadata/byte-stream bindings must not be broadened into file-mutation grants. Dedicated operation authority and conditional effects remain implementation work. Both full EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished.

Fresh checklist arithmetic remains 16.23% weighted, 4.81% whole-item, 20/460 parents and 437/897 sub-items. This completes coverage within an already accepted provider sub-item and adds no duplicate runtime-feature credit.

Persistent ACL metadata checkpoint — 29 September 2026: e2fsd ac258003, docs 2d3de8f0, integration cd4f7625.

The original ext metadata operation now preflights all selected fields and complete access ACLs, changes only owner/group-or-mask/other permissions, and preserves named/default entries and full-width owner IDs. Shared tables and immutable values use copy-on-write with exact reference lifetimes. Local alias pressure uses actual table geometry, the other attribute store or value-inode storage. Root metadata follows the original native scope; the full nonzero table reference domain has no separate 1024-owner ceiling. The incompatible Hurd/EA count-word layout refuses during mount parsing.

Mode/ACL coherence and attribute accounting are implemented. Modern charges follow every descriptor's owner; legacy values retain original independent quota identities. Growth, truncation and inline conversion conserve charges, fast symlinks distinguish attributes from data, and retained inline payload is persisted before quota scanning reuses its scratch. Every edit retains the original transaction, checksums and permission epoch. Uncertain persistent completion remains fail-stop without replay. No capability, endpoint or private inode-selector ABI is added.

Twenty-four new controls are authored and unrun, covering actual media/provider metadata, sharing, full IDs, root, both storage-movement directions, large immutable ACLs, count/space exhaustion, quota identity/cluster charges, real quota-file inline conversion, growth/truncation, fast symlinks, journal rollback and uncertain writes. Rustfmt was applied. Changed Rust source remains below one thousand lines (maximum 922), with inline rustdoc and missing_docs retained. A read-only inventory covers 76 repositories and 3355 tracked source files; none reaches one thousand lines. Duplicate raw quota decoding was removed and directory allocation I/O was moved into its existing module.

The provider permission pass continues with operation-specific conditional native effects and native scenario authoring. Native filesystem mediation, both complete EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished. The checklist now exposes the completed provider media portion separately; recalculation is 16.23% weighted, 4.81% whole-item, 20/460 parents and 437/897 sub-items. The weighted percentage still rounds to 16.23%; it has been recalculated. Reviews: provider, manual, Integration.

Ext value-inode acquisition and cleanup checkpoint — 29 September 2026: e2fsd 407efa3e, docs 6d5da74b, integration 328c153f.

The original provider now streams complete access ACLs from local and EA-inode storage with exact size/role, original inode checksums, modern CRC32C binding or legacy owner/generation validation. One cached data block and fixed owned scratch admit large ACLs without a new total-size or entry-count cap. Failed or changed evidence clears staged pages and retires the matching original observation. No capability, endpoint or credential authority is added.

Shared and inline cleanup is implemented: both stores are preflighted, repeated references cannot undercount the original value, shared external tables retain their own value references, and only a final value reference disposes storage. Raw hash/count fields are distinct from timestamps, EA-only inodes refuse ordinary file selection, and uncertain nonjournaled writes retain provider fail-stop without replay. Seventeen new media/provider controls are authored and unrun, including actual retained dispatch and ACLs above 64 KiB/8191 entries.

The provider permission pass remains open for ACL-aware persistent mode changes and the remaining operation-specific effects. Native filesystem mediation, both complete EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished. Canonical phase completion remains 16.23% weighted, 4.81% whole-item, 20/460 parents and 436/896 sub-items; no new small canonical completion item is added for this checkpoint. Reviews: provider, manual, Integration.

Native external-call prerequisite: inherited stream dispatch. Actual CLAIM admission currently serves internal channels only; external stream use will establish retained outbound ownership without adding mode rechecks to already-open descriptors. Filesystem ACL policy and operation effects remain open.

Canonical ACL transport design: Transport complete access ACL entries on retained permission revisions. The planned paged wire contract and caller-storage assembler retain complete original handle/revision/count correlation; native custody and operation enforcement remain separate unfinished work.

Retained ext permission evidence — 29 September 2026: e2fsd 15a9e671, docs 7c1f39e3, integration f0ab7f5c. E2fsd#7 implements actual private snapshot and conditional-truncate dispatch using original checked inode metadata and complete local access ACLs. Both physical stores are examined; canonical structure, full qualifiers, required masks and mode correspondence are checked. Unsupported value-inode ACL payloads refuse rather than becoming absent evidence.

Each retained handle stores a unique snapshot revision, metadata epoch and full fingerprint. Both metadata setters invalidate before selected permission/flag attempts. A conditional effect consumes matching evidence, re-reads complete permissions and reaches the shared retained-object resize only after an exact fingerprint match. Short replies refuse before I/O. Close/reset cannot revive revisions; compiled record geometry sizes the existing arena. Native endpoint authority and ordinary open-descriptor semantics remain required.

Seventeen new controls are authored but unrun, including actual wire dispatch and resize effects. The provider contract, ext review, manual review and catalog review record the boundary. Three immutable catalog entries select the original signed provider/manual revisions. Formatting was applied; tests, builds, lint checks, rustdoc, VM/manual/profiler runs and CI observation remain deferred. No pass or warning-free build is claimed.

The completed provider sub-item raises weighted checklist progress to 16.19%; the parent remains open. Value-inode payload integrity/acquisition, canonical ACL entry transport, ACL-aware persistent metadata mutation and native caller/route/policy enforcement remain unfinished. Both full EriX guest builds and the external Rust/LLVM guest rebuild remain required and unproved.

Duplicate selected keys and malformed trailing/external data refuse; private staging is cleared.

Thirteen regression controls are authored but unrun, including the actual file-read boundary and value-inode traversal. Parsing, body geometry, rewriting and fixtures are split into documented modules below 1,000 lines. See the provider contract, E2fsd review, manual review and Integration review. Three catalog entries select the original signed provider/manual revisions; the independent orchestration helper and kernel-lifetime catalog are unchanged. Formatting was applied. Tests, builds, lint checks, rustdoc, VM/manual/profiler runs and CI observation remain deferred; no pass or warning-free build is claimed.

This is structural preservation, not complete ACL policy: value-inode payload acquisition, ACL decoding, trusted provider revision snapshots and native caller/operation enforcement remain unfinished. Completion remains 16.17% without new canonical checklist credit. Both complete EriX guest builds and the external Rust/LLVM guest rebuild remain required and unproved.

Realm design, compatibility ABI design, filesystem audit, Phase 6 completion. Begin with checked policy types and independent controls, then trusted runtime intake and native-before-policy enforcement, then bounded native scenarios and coordinated publication. Keep this issue open until all implementation obligations are met, regardless of the execution waiver.

Related records and contracts
Repository Links
e2fsd issue 6
exsh PR 3
posixd issue 12, issue 13
vfsd issue 5
## Problem and motivation Compatibility mode/status values currently describe metadata, but do not implement credential or ACL checks. Numeric IDs and permission bits must never create native authority. Unknown provider metadata and an absent ACL are distinct states, and a successful pure policy calculation cannot substitute for actual native admission. ## Proposed behavior and scope Compatibility 1.2 carries only an original directory role/selector and requested access bits. Actual sealed CLAIM clients select immutable effective credentials and original directory receipts. Vfsd checks the live metadata-directory operation and inherited namespace/write ceiling before fetching provider evidence. ReadWrite configuration cannot restore native rights. Complete canonical ACL pages preserve object/revision/count/range, order, required bases/masks and mode correspondence before any deny-only result. Partial ACLs, UID zero and combined partial group grants cannot bypass policy. Zero bits still require actual original-provider existence. Per-query state retains one snapshot and a bounded streaming fold without a fixed ACL-entry limit. Original outbound and inbound owners remain attached through cancellation, result release and one-shot COMPLETE. Acknowledged Draining(NOT_FOUND) preserves route-loss retirement; unknown failures and unexplained absence keep custody. Stream and directory paths share the original caller helper and host fixture. Final source review flattened the native client refusal condition without changing its requests or expected outcomes. Two additional signed cleanup/adoption commits select the final source; the implemented scope and twenty-four authored controls are unchanged. No tests, builds or CI observation were run. Twenty-four new host controls and the extended native binding workload are authored and unrun. The native client requires seven directory-existence queries, five configured write refusals and absent-selector refusal before its inherited stream controls. Existing deadlines and resource policy are unchanged. Rustfmt was applied; all changed code remains below 1,000 lines (maximum 900) with inline rustdoc and missing_docs retained. Contracts and manual TeX are updated. Tests, builds, lint checks, rustdoc, VM/manual/profiler runs and CI observation remain deferred by user instruction; no pass, warning-free build or measured speedup is claimed. Generated API exports retain their explicit older source identity until generation resumes. [Native permission enforcement](https://git.erikinkinen.fi/erix/posixd/issues/10) remains open for complete pathname/open/stat/mutation mediation and remaining provider support. Both EriX guest-build generations and rebuilding Rust/LLVM inside EriX remain required and unproved. [Phase completion](https://git.erikinkinen.fi/erix/integration/issues/65) is **16.23% weighted**, **4.81% whole-item**, with **20/460 parents** and **436/896 sub-items** complete. Only original job-lifetime READ_METADATA directory endpoints serve selector-free snapshots and bounded ACL pages. Vfsd uses the retained mount/provider handle and fresh private correlation, checks framing, handle, kind, revision and range, then replaces private identifiers with caller request correlation and the live VFS record ID. It does not reopen paths, synthesize ACL absence or broaden another endpoint's operation ceiling. Unknown evidence stays unknown, refused staging is cleared, and original owned completion custody prevents refetch/replay after refusal. Actual buffer geometry bounds pages without a new complete-ACL limit; entries remain in existing staging while the fixed prefix is rewritten. Eighteen controls are authored and unrun: five wire, five provider transport, seven real-dispatch and one owned-completion. The original transport interface is shared and native path codecs/resolver fixtures are split; changed code remains below 1,000 lines (maximum 898), with inline rustdoc and missing_docs retained. Component contracts and the technical manual are updated. Tests, builds, lint checks, rustdoc, VM/manual/profiler runs and CI observation remain deferred by user instruction. No pass, warning-free build or measured speedup is claimed. [Native permission enforcement](https://git.erikinkinen.fi/erix/posixd/issues/10) remains open: trusted credentials, full ACL acquisition and actual operation-specific effects still need to be connected. Value-inode ACL payloads and ACL-aware persistent mutation also remain unfinished. Both complete EriX guest-build generations and the Rust/LLVM guest rebuild remain required and unproved. [Phase completion](https://git.erikinkinen.fi/erix/integration/issues/65) is **16.22% weighted**, **4.81% whole-item**, with **20/460 parents** and **435/895 sub-items** complete. Launchd registers original realm stream receivers before exporting SEND views and serves actual owned CLAIM/COMPLETE/RELINQUISH. Each noncopyable row retains its exact Reply result. Vfsd registers exact endpoints before Powerbox, Launchd and cwd export, preserves legacy users and reserves original delivery storage independently of copied handle metadata. Every allocation family respects that reservation through provider Close and native/receiver settlement. Neither path replays an operation or COMPLETE after refusal. Native route invalidation retains draining custody until acknowledgment; request abandonment preserves an open stream and explicit Close preserves the lender. Compiler-derived rows account for full protocol packets; Vfsd capacity descriptor version two includes mount, handle and invocation regions. Cleanup scrubs only written packet extents, conservatively retaining the full extent for unknown native output. This is a source cost reduction, not a measured performance result. Eight Launchd, nine Vfsd and four packaging controls are authored but unrun; existing arena controls are updated. The existing native binding workload exercises external writes, Close, exact process exits and lender preservation under unchanged gates. Inline/component/manual contracts and coherent catalog adoption are updated. Changed code files remain below 1,000 lines (maximum 957); missing_docs enforcement remains and Rust formatting was applied. Tests, builds, lint checks, rustdoc, VM/manual/profiler runs and CI observation remain deferred by user instruction. No execution pass or warning-free build is claimed. The [transport defect](https://git.erikinkinen.fi/erix/integration/issues/100) and [stream feature](https://git.erikinkinen.fi/erix/posixd/issues/11) are implemented; [native filesystem permission policy](https://git.erikinkinen.fi/erix/posixd/issues/10), both complete EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished. [Phase completion](https://git.erikinkinen.fi/erix/integration/issues/65) is **16.21% weighted**, **4.81% whole-item**, with **20/460 parents** and **434/894 sub-items** complete. Binding cleanup acceptance is restored for completed implementation; waived testing is not a test pass. Exact canonical pages bind the original handle/revision, complete count and contiguous range. E2fsd rechecks complete metadata and both attribute stores, preserves valid observations for later pages/conditional effects, and retires observed failures while clearing staging. Ramfsd explicitly refuses pages for absent storage. Libposixabi joins pages in caller-owned storage, poisons and clears failed or abandoned assembly, and exposes only complete canonical, mode-consistent metadata. Known absence has a separate constructor. No codec, ID, hash or collected view supplies native caller/provider authentication or authority. Nineteen controls are authored but unrun: six wire, seven collection, four actual ext dispatch and two Ramfsd dispatch controls. They cover full IDs, large ACLs, malformed/mixed/stale evidence, incomplete cleanup, reply capacity, close and later conditional truncation. The original reduced decoder and checked ACL fixture are shared. Changed Rust files are below 1,000 lines (maximum 891), inline rustdoc and existing missing_docs enforcement are retained, and Rust 2021 formatting is applied. Component contracts and both relevant manual sections are updated. Full ext scans per page cost O(A * P) ACL work; no measured performance claim is made. Native Vfsd/Posixd caller/route/effect integration, value-inode ACL payloads, persistent ACL-aware mutation and remaining provider effects remain open in [the permission feature](https://git.erikinkinen.fi/erix/posixd/issues/10). The distinct snapshot contract carries original retained handle/revision, explicit known mode/ownership and unknown/absent/present access-ACL evidence. Legacy stat is never converted into authenticated permission evidence. Full-width zero/MAX IDs and complete ACL counts have no small entry ceiling. Unknown or incomplete ACL evidence cannot become mode-only admission. Conditional truncation accepts explicit optional native time, so clock unavailability introduces no new operation restriction. Ramfsd reads actual retained node ownership and establishes absent ACLs from its implementation. Both metadata setters share per-node revision updates before any selected fields or timestamps change. Change-and-restore cannot revive old evidence; aliases share revisions, unrelated nodes do not, and exhaustion refuses without partial mutation. Conditional truncation compares and resizes the same retained file in one exclusive provider turn, preflights reply storage and shares the existing resize helper with one handle lookup. No path resolution, capability acquisition or receipt transfer is added. Numeric handles and matching revisions remain descriptive. Ten new controls are authored but unrun: four independent shared-wire controls and six actual Ramfsd state/dispatch controls for ownership/ACL evidence, stale/restore/exhaustion, aliases, closed/reused/wrong-kind handles, optional/malformed time and short reply storage. Source review removes duplicate metadata assignment and handle scans; changed Rust files are below 1,000 lines, with a maximum of 891. Rust formatting was applied. Tests, builds, lint checks, rustdoc, manual builds, profiler runs and CI observation remain deferred by instruction. No execution pass, warning-free build or measured performance result is claimed. The master checklist exposes the completed shared ABI and Ramfsd portions separately. Native CLAIM/route integration in Vfsd/Posixd, complete filesystem ACL acquisition and remaining operation-specific effects remain unfinished; the overall permission feature stays open. Progress is **16.17% weighted**, **4.81% whole-item**, **20/460** parents and **431/891** sub-items. Both full EriX guest-build generations and rebuilding Rust/LLVM inside EriX remain unproved. [Provider contract](https://git.erikinkinen.fi/erix/lib-ipc/src/commit/737ef52bc3b572bf5949d9102c3591ad1559dcfa/docs/provider-permissions.md), [Ramfsd implementation](https://git.erikinkinen.fi/erix/ramfsd/pulls/2), [permission design](https://git.erikinkinen.fi/erix/posixd/issues/10), [native mediator review](https://git.erikinkinen.fi/erix/posixd/pulls/5), [coordinated images](https://git.erikinkinen.fi/erix/integration/pulls/12), [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). Provider design, recorded before ABI implementation: add a distinct private retained-handle permission snapshot with explicit known-field bits, full UID/GID/mode, ACL state (unknown, proven absent, or present), complete ACL entry count, the original provider handle and a nonzero permission revision. A zero ID remains a real ID only when its known bit is set. Legacy stat is never converted to this contract. No snapshot, revision, handle number, credential or successful policy comparison grants native authority. The consumer must first admit the original native caller and retained route, correlate the exact provider reply, retain the original provider endpoint/handle lifetime, and apply deny-only policy. Snapshot-dependent mutations carry the same revision to a provider operation that compares it and performs its effect in one serialized turn. Permission changes advance the per-object revision before changing state; exhaustion refuses without partial mutation. Changing permissions back does not revive an earlier revision. Handle close/reuse, route retirement and uncertain completion retain their existing cleanup rules. Already-open descriptor read/write behavior is not changed into repeated mode checking. Implementation sequence within this feature: shared snapshot and conditional-operation frames; Ramfsd's actual node ownership, proven ACL absence and revision-checked truncation; then Vfsd and Posixd native-route integration, filesystem ACL acquisition and the remaining operation-specific effects. Ramfsd's first provider implementation does not complete the realm policy feature. E2fsd must inspect both inode-body and external ACL metadata; FAT must not fabricate known ownership from legacy zero fields. Present ACLs need complete canonical entries from the same object/revision, with counted/chunked transport rather than an arbitrary small entry limit; unknown, unsupported, malformed or incomplete evidence must refuse policy admission. The first provider controls will cover wire literals and atomic encoding refusal, real zero/max ownership, unknown versus absent ACLs, same-object revision changes including restoration, foreign/closed handles, unchanged filesystem contents on stale truncation, and counter exhaustion before any metadata/timestamp mutation. Later native controls must demonstrate both denial and permitted effects after original CLAIM/route admission, plus revocation, replay and cleanup. Tests are authored but not executed under the current testing/CI deferral. Implementation and integration remain open. Dependencies and review: [shared ABI](https://git.erikinkinen.fi/erix/lib-ipc/pulls/2), [Ramfsd](https://git.erikinkinen.fi/erix/ramfsd/pulls/2), [Vfsd](https://git.erikinkinen.fi/erix/vfsd/pulls/3), [Posixd](https://git.erikinkinen.fi/erix/posixd/pulls/5), and [Phase 6 tracking](https://git.erikinkinen.fi/erix/integration/issues/65). Final contract reconciliation — 29 September 2026: [launchd `dfb7fcde`](https://git.erikinkinen.fi/erix/launchd/commit/dfb7fcdef79184c42afa45b2d10ee3d88569933b), [posixd `0d5a3ba6`](https://git.erikinkinen.fi/erix/posixd/commit/0d5a3ba644aa9f275bd8e7d62afa0f4979a60c43), [docs `7429b15c`](https://git.erikinkinen.fi/erix/docs/commit/7429b15c5db76ade58b414c6ea2a6345c169c952), [integration `1bc91ad2`](https://git.erikinkinen.fi/erix/integration/commit/1bc91ad2e953f780dc382f2e46459311f198a9b7). Four additional signed documentation/catalog commits remove superseded adoption-pending claims and correct remaining minor-version text. This continuation now totals 59 signed commits across 54 repositories; runtime implementation and native scenario gates are unchanged. Trusted credential intake is complete; provider-backed permission effects remain open. Checklist accounting remains **16.15% weighted**, **20/460 parents** and **429/888 sub-items**. Tests, builds and CI observation remain deferred; no execution result or complete guest OS/toolchain rebuild is claimed. The next provider boundary must distinguish known UID/GID/mode and proven ACL absence from unavailable metadata. The existing descriptive stat response permits zero for unknown ownership and has no coherent ACL-support/lifetime evidence, so it cannot be used as authenticated permission input. Bind any new snapshot and effect to the exact retained native object, metadata revision and original caller; never treat unknown support as absent ACL. [Permission design](https://git.erikinkinen.fi/erix/posixd/issues/10), [credential custody](https://git.erikinkinen.fi/erix/posixd/src/commit/0d5a3ba644aa9f275bd8e7d62afa0f4979a60c43/docs/credentials.md), [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). The authenticated configuration owner selects explicit real/effective/saved UID/GID values. Launchd derives native identity from guarded child custody, preserves complete client records through reversible sorting and freezes every group word. Group pulls follow all authority records and transfer no capability. Procd retains G in original provisioning and startup; its native receiver ceiling remains C+A+6. Posixd binds canonical indices to actual original receiver owners and full native generations, retaining the immutable plan for the service lifetime. Credential and authority selection share the sealed, live-client gate; retirement immediately disables both. Real/effective selection is explicit. Borrowed canonical wire groups need no copy, alignment cast, repeated validation or small fixed count limit. Seven new controls are authored for exact group pulls, restoration, large-group startup, sealed receiver selection and retirement, valid scalar substitution, surplus receipts and unaligned membership. Existing native reciprocal, owner-loss and binding diagnostics carry disjoint groups including zero and UINT32_MAX. Their two-plan budgets are 792 and 2840 bytes respectively, with original capability budgets, exits, markers and deadlines retained. Source audit also corrected remaining literal START budgets and a missing explicit fixture group count. Changed code files are at most 726 lines, with inline rustdoc and existing missing_docs enforcement retained. Formatting is applied. Tests, builds, lint checks, rustdoc, manual builds, profiler runs and CI observation remain deferred by instruction; testing is waived, never reported as passed. Trusted per-client credential intake is implemented. Provider-backed ownership/mode/ACL evidence and actual native-before-policy operation effects remain unfinished, so the overall permission feature stays open. Completion is now **16.15% weighted**, **4.81% whole-item**, **20/460** parents and **429/888** sub-items. Both full EriX guest-build generations and rebuilding Rust/LLVM inside EriX remain unproved. [Credential lifetime](https://git.erikinkinen.fi/erix/posixd/src/commit/411edfc864235e233dc1d251150ec3ca0150af15/docs/credentials.md), [permission design](https://git.erikinkinen.fi/erix/posixd/issues/10), [runtime review](https://git.erikinkinen.fi/erix/posixd/pulls/5), [coordinated images](https://git.erikinkinen.fi/erix/integration/pulls/12), [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). The exact plan is 112+72C+24D+16H+64A+4G bytes. The original reserved validation word remains intact. RBS1 minor three is 320 bytes, public reservation 88, and private provisioning 128/336; G is retained explicitly and earlier incompatible framing refuses. Group replies require zero receipts. None of this authenticates a client, selects host identity or adds native authority. Ten new controls are authored, with existing literal fixtures updated for exact framing, malformed membership, count correlation, capability counts and failure-preserving output. Source review and Rust formatting are complete; tests, builds, lint checks, rustdoc, manual builds, profiler runs and CI observation remain deferred. No pass, warning-free build or native permission result is claimed. This shared source checkpoint precedes coordinated Launchd, Procd, Posixd and fixture changes. Existing Cargo consumers and image catalogs retain their preceding immutable revision. Trusted runtime credential intake and provider-backed operation gates remain unfinished; the permission item stays open and checklist completion remains **16.07%**, **20/460** parents and **428/888** sub-items. Both full EriX guest-build generations and the guest Rust/LLVM rebuild remain unproved. [Wire contract](https://git.erikinkinen.fi/erix/lib-ipc/src/commit/c73b1b23366858bed1112e5a42c50d1430a16407/docs/realm-configuration.md), [storage contract](https://git.erikinkinen.fi/erix/lib-ipc/src/commit/c73b1b23366858bed1112e5a42c50d1430a16407/docs/realm-storage.md), [runtime design](https://git.erikinkinen.fi/erix/posixd/issues/10), [codec review](https://git.erikinkinen.fi/erix/lib-ipc/pulls/2), [manual review](https://git.erikinkinen.fi/erix/docs/pulls/4), [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). Counted credential intake design — 29 September 2026: retain explicit real/effective/saved UID/GID values and a canonical supplementary-group range for every original client. The realm configuration owner chooses these compatibility labels through its already authenticated native configuration route; ordinary clients, request text and environment cannot mutate them. Every value, including zero and the full unsigned maximum, remains descriptive within the existing native ceiling. Extend shared configuration counts with a separate supplementary-group count G. Store groups as canonical little-endian u32 entries in the immutable plan after existing authority records, with no extra capability or hidden group heap. Per-client ranges must partition that tail exactly in client order; each range is strictly increasing and unique. Group views decode bytes safely without alignment casts. This retains complete membership and enables binary-search lookup without a fixed small group limit. The coordinated contract uses a 112-byte plan header and 72-byte client records, preserving the original reserved word used by reversible global validation. Exact plan bytes are 112+72C+24D+16H+64A+4G. Pull framing retains its original native receipt obligations; group records carry no capability. Startup and provisioning carry G explicitly, and old incompatible framing is rejected. Runtime consumers must bind these records to actual original receiver custody, full generations and the frozen plan before ordinary effects, preserving retirement and stale-client refusal. This is an implementation sequence for the existing feature, not completed runtime enforcement. Shared codecs, Launchd production, Procd storage/startup, Posixd intake, fixture producers, immutable dependency adoption and authored native controls must all be coordinated. Provider-backed mode/ACL snapshots and effect gates remain required afterward. Tests, builds and CI observation remain deferred by instruction. UID zero has no bypass, matched classes cannot fall through, duplicate qualifiers are refused and a combined group request must be covered by one matching entry. Native admission and exact original client/provider provenance remain mandatory. Unknown ACL support cannot become absence. Trusted per-client credential intake, coherent provider snapshots and actual native operation gates are still unfinished implementation. The helper must not be indiscriminately inserted before reads/writes of already opened descriptors. [The feature issue](https://git.erikinkinen.fi/erix/posixd/issues/10) remains open with enhancement, security and phase-6 metadata. Twelve original controls are authored but unrun, covering direct permission outcomes, masks and combined requests, UID zero, special bits, full-width IDs, malformed metadata and large caller-owned storage. Rust formatting was applied. Tests, builds, lint checks, rustdoc, manual builds, profiler runs and CI observation remain deferred; no pass or warning-free result is claimed. The metadata substep is implemented, while the complete permission-enforcement item remains open. Both EriX guest-build generations and the guest Rust/LLVM rebuild remain unproved. [Permission contract](https://git.erikinkinen.fi/erix/lib-posixabi/src/commit/0a27be14820446f6a29ba2ffe656a2df8a95782b/docs/permissions.md), [runtime design](https://git.erikinkinen.fi/erix/posixd/issues/10), [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). Completion is **16.07%** weighted, **20/460** parents and **428/888** sub-items across **158** decomposed parents. Reviews: [library](https://git.erikinkinen.fi/erix/lib-posixabi/pulls/3), [mediator](https://git.erikinkinen.fi/erix/posixd/pulls/5), [catalogs](https://git.erikinkinen.fi/erix/integration/pulls/12), [manual](https://git.erikinkinen.fi/erix/docs/pulls/4). Define checked borrowed credential groups, permission sets and access ACL views in Lib-posixabi, with explicit normalization over caller-owned storage and no incidental entry/group ceiling. Implement owner, named-user, matching-group and other checks with the ACL mask and mode consistency. UID zero receives no implicit bypass, and set-ID or executable bits supply no native privilege. Select effective or real IDs explicitly at the owning operation adapter. Wire trusted per-client credentials into the original realm/process identity, bind object metadata to the exact native-admitted operation, and apply the policy before effects. Authenticate provider support, object identity, snapshot freshness and ACL absence; unknown or malformed metadata must not silently become an empty ACL or permissive mode. Preserve the original route, requested operation, native ceiling and cleanup lifetime across metadata updates and revocation. Directory/default-ACL creation and mutation belong to coordinated filesystem semantics; this feature must not claim enforcement from ACL byte preservation alone. ## Authority, security and reliability Native admission precedes compatibility policy. The operation uses only an already held and natively authenticated object/route within its selected rights. A credential/ACL result is descriptive and never mints, discovers, transfers or restores a capability. UID zero, chmod/chown-like changes, executable mode and group changes may alter compatibility denials only within that original native ceiling. Trust comes from retained process and provider ownership, never request-authored IDs or digests. Missing evidence blocks effects; partial acquisition and cleanup retain original owners. ## Acceptance criteria - Checked full-width UID/GID and normalized group/ACL storage with no fixed small limits; reject duplicate ACL qualifiers, invalid permissions and inconsistent mode/mask metadata. - Owner and named-user precedence, mask application, primary/supplementary groups, no other-class fallback after a matching denial, and combined-access behavior follow the selected profile. - Native caller/realm/process, receipt, object and operation evidence precedes policy, including revoked/missing routes and stale generations. - UID zero, permissive mode/ACL, changed ownership and executable bits cannot recover missing rights or choose an undelegated route. - Trusted credentials and provider metadata reach actual runtime checks; pure policy tests alone do not complete this feature. - Appropriate positive, negative, cleanup and bounded native scenarios are authored. Tests, builds, lint checks, profiler runs and CI observation remain deferred by user instruction; no execution pass is implied. - Update component/manual documentation, signed immutable dependent revisions and linked tracking. ## Alternatives and tradeoffs Keep checked metadata separate from native custody. Borrow normalized caller-owned slices rather than allocate hidden storage or impose incidental table limits. Standard mode rules follow the [Open Group file-access specification](https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/V1_chap04.html); access ACL semantics follow the [maintained ACL specification](https://man7.org/linux/man-pages/man5/acl.5.html), an optional compatibility profile rather than a POSIX.1 base requirement. Default ACL inheritance, persistence and complete chmod/chown APIs need the separately coordinated filesystem metadata contract. No third-party implementation is copied. ## Tracking and rollout Complete native Open/openat implementation is signed and published: [lib-ipc `6b96c569`](https://git.erikinkinen.fi/erix/lib-ipc/commit/6b96c5698a736000e314a4c3abbcfa76132c492c), [e2fsd `aedb65bb`](https://git.erikinkinen.fi/erix/e2fsd/commit/aedb65bb5d41613adb00625124422af490dec6d0), [ramfsd `dc1de465`](https://git.erikinkinen.fi/erix/ramfsd/commit/dc1de465be087e6c8f22523c665d2aad1464644f), [fatd `0e209121`](https://git.erikinkinen.fi/erix/fatd/commit/0e209121d7b1e802809e99910c14cf5c4acf42ed), [vfsd `a368b741`](https://git.erikinkinen.fi/erix/vfsd/commit/a368b741c87c0b5f0cf947dc4e03f8a0d036d11e), [posixd `85efb7f9`](https://git.erikinkinen.fi/erix/posixd/commit/85efb7f985c04a737b147689bd7a6126b94a1817), [exsh `3ee15a96`](https://git.erikinkinen.fi/erix/exsh/commit/3ee15a96f2b4def52860fcd423615f3d3367f667), [docs `c8565b7b`](https://git.erikinkinen.fi/erix/docs/commit/c8565b7b3a5c77f1e3d5a9e3b3a06994bfde505b), [integration `9fb56e3d`](https://git.erikinkinen.fi/erix/integration/commit/9fb56e3d618588969bdc9a01b507ab094f92a4e1). [Dynamic acquisition](https://git.erikinkinen.fi/erix/posixd/issues/17) 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. Counted bound-file resize — 29 September 2026: [lib-ipc `93920c87`](https://git.erikinkinen.fi/erix/lib-ipc/commit/93920c87bac94ae783ead8735e0ca9673fbcfdf4), [lib-posixabi `d63943f4`](https://git.erikinkinen.fi/erix/lib-posixabi/commit/d63943f49badce77d1cfd143e674c87a20d7ed5a), [launchd `92c27f94`](https://git.erikinkinen.fi/erix/launchd/commit/92c27f943641d1ee57ba064c3cf0c6caf5091218), [vfsd `080f48dd`](https://git.erikinkinen.fi/erix/vfsd/commit/080f48dd71b957ac19c1fad1dd4a8bb819fb80c6), [posixd `c5fab30e`](https://git.erikinkinen.fi/erix/posixd/commit/c5fab30e9689ea99ed0b7149cca75ac629bc37c7), [exsh `836d2da2`](https://git.erikinkinen.fi/erix/exsh/commit/836d2da2606e5f5152f1de293b923b95eb475d46), [docs `7b5ca67e`](https://git.erikinkinen.fi/erix/docs/commit/7b5ca67e1c8d83434f08b022fef11c3ac17f4ee8), [integration `4ed92218`](https://git.erikinkinen.fi/erix/integration/commit/4ed922187e36f689b32c0cc0c067ada54e68336f), [rootd `cb910991`](https://git.erikinkinen.fi/erix/rootd/commit/cb910991ca155c6830312f9811d92e8d38ce51af). The [bound-file feature](https://git.erikinkinen.fi/erix/posixd/issues/14) now connects authenticated supervisor preparation to sealed-client permission mediation and original provider cleanup. Dedicated public begin/prepare and private resolve operations preserve the actual scope receipt, full generations and explicit ResizeFile/Write purpose, including an empty original file. Shared filesystem custody retains original provider identity before alias movement and across partial or uncertain effects. Obsolete directory-only API names are removed; the existing private retirement wire remains stable. Compatibility 1.3 adds FileResize using only that client's frozen selector and a full-width length. The shared directory/file permission owner requires complete mode/owner/ACL evidence under actual sealed credentials before one conditional effect on the same object/revision. UID zero has no override. Stale comparisons refuse without replay; malformed effects, cancellation and refused completion preserve original custody and fixed results. Nineteen new host controls are authored and unrun: three shared-IPC, three compatibility-codec, four Launchd, two Vfsd and seven Posixd. Existing producer transcript and scenario controls are updated. The native workload creates an empty file through ordinary shell redirection, requires owner growth and nonowner/absent-selector refusal, then independently reads seven zero bytes plus EOF after all realms retire. Explicit fixture storage is 3096 plan bytes, 36 authorities and 22 Ramfsd handles; existing process and capability pools and lifecycle gates remain. [The nested conditional-resize test module path](https://git.erikinkinen.fi/erix/vfsd/issues/7) is also corrected after rustfmt exposed its source-resolution error. All 55 affected repositories are published in 56 signed commits, updating 206 Cargo and 111 catalog selectors. Rootd and both helper catalogs retain [the independent Rust helper `eee623e3`](https://git.erikinkinen.fi/erix/integration/commit/eee623e35cc961b9b0bd10503ad5bd106e23dd2f), separate from the final catalog head. Read-only inventory covers 3387 source files in 76 repositories, all below one thousand lines; the largest changed source has 990 lines. Component contracts and technical manual are updated, and rustfmt was applied. [Broader filesystem mediation](https://git.erikinkinen.fi/erix/posixd/issues/10), dynamic descriptor/pathname operations, both full EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished functional requirements. Explicit native conditional resize — 29 September 2026: [lib-ipc `d785e672`](https://git.erikinkinen.fi/erix/lib-ipc/commit/d785e67275cd6e89140d0d4c4020fd8075316ced), [vfsd `660d0fa1`](https://git.erikinkinen.fi/erix/vfsd/commit/660d0fa1b3d30b2e712692d03cd78878adf03bf7), [powerboxd `52a5636e`](https://git.erikinkinen.fi/erix/powerboxd/commit/52a5636e0136a46e018f3628df240a560913d102), [launchd `ba2d2a87`](https://git.erikinkinen.fi/erix/launchd/commit/ba2d2a8717cd6e94ead5adb1fb82f2e0365052c3), [ttyd `f220da8e`](https://git.erikinkinen.fi/erix/ttyd/commit/f220da8e001f3d7f58c0b71c863aafcc198fc136), [docs `51e49f5d`](https://git.erikinkinen.fi/erix/docs/commit/51e49f5d8ed35bb16cd9fdb5dd66a5f1e4f0b7a0), [integration `47fb79a7`](https://git.erikinkinen.fi/erix/integration/commit/47fb79a7e963553902321f5db0e6341eb83cc253), [rootd `37ca91ad`](https://git.erikinkinen.fi/erix/rootd/commit/37ca91ad1371493968140322dd1ae2317d1c3e86). The [separate RESIZE_FILE grant](https://git.erikinkinen.fi/erix/vfsd/issues/6) is implemented for one retained regular file. Original byte WRITE and directory READ_METADATA operation families remain unchanged. Vfsd forwards original permission snapshots and complete ACL pages, admits the retained write ceiling, matches the public object correlation and reserves fixed result space before trusted time or provider effects. The conditional adapter uses the original private handle/revision and a fresh private request correlation. Only a correctly framed provider RETRY denotes definite staleness; uncertain transport and malformed replies become INTERNAL. There is no replay, name lookup or unconditional resize fallback. Original native CLAIM/COMPLETE/RELINQUISH custody keeps one fixed result through completion refusal and cancellation. Metadata observations preserve one-shot custody, explicit Close covers every supported resize lifetime, and receiver-disposal failure retains the counted row. Canonical operation recognition replaces duplicated launch/broker/session lists without widening bootstrap defaults or bypassing explicit manifest, session, approval and lifetime limits. Trusted review describes permission observation and conditional resizing together. Twenty-three new controls are authored and unrun: four wire/domain, fourteen Vfsd transport/resolver/dispatch/native-custody, two broker, one launch and two session/review controls. Component contracts and the filesystem manual are updated. Rustfmt was applied; the largest changed source has 902 lines. The read-only inventory covers 76 repositories and 3377 source files, all below one thousand lines. Fifty-five repositories are published in 56 signed commits, with 206 Cargo and 111 catalog selectors updated. Rootd's two Cargo edges and both helper catalogs retain [the independent Rust-helper `5b9676ff`](https://git.erikinkinen.fi/erix/integration/commit/5b9676ff151e1f1400aa8f9eed22cd39b833c287); the later Integration catalog head stays distinct. [Counted realm preparation and sealed-client conditional mediation](https://git.erikinkinen.fi/erix/posixd/issues/10), their native workload, other filesystem operations, both complete EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished. Related reviews: [wire](https://git.erikinkinen.fi/erix/lib-ipc/pulls/2), [Vfsd](https://git.erikinkinen.fi/erix/vfsd/pulls/3), [broker](https://git.erikinkinen.fi/erix/powerboxd/pulls/2), [launch](https://git.erikinkinen.fi/erix/launchd/pulls/2), [session](https://git.erikinkinen.fi/erix/ttyd/pulls/3), [manual](https://git.erikinkinen.fi/erix/docs/pulls/4), [Integration](https://git.erikinkinen.fi/erix/integration/pulls/12). Fresh fixed-parent accounting is **16.24% weighted**, **4.81% whole-item**, **20/460 parents** and **438/898 sub-items**. The native layer receives its completed sub-item; the broader permission item remains open. Native ACL metadata coverage — 29 September 2026: [integration `e9dbf028`](https://git.erikinkinen.fi/erix/integration/commit/e9dbf028b70763f68f944313edfa956a1451ec10), [e2fsd `cc3d02a0`](https://git.erikinkinen.fi/erix/e2fsd/commit/cc3d02a07a53c9595a8029566d66be02066ea5f0), [docs `829c91a8`](https://git.erikinkinen.fi/erix/docs/commit/829c91a83232e92e99e64a12f971b8d368407126), [rootd `93e2d63b`](https://git.erikinkinen.fi/erix/rootd/commit/93e2d63b6d54f181b485a742f3c3ca7921ed005f). The [dedicated scenario](https://git.erikinkinen.fi/erix/integration/src/commit/e9dbf028b70763f68f944313edfa956a1451ec10/tests/scenarios/subsystem-ext4-acl-metadata-positive.toml) uses a separate ext4 image and Rootd's existing explicitly writable VFS fixture. Twenty-five original native requests cover local/value ACL mode and full-owner changes, owner-only preservation, rejected type changes with unchanged metadata, special bits, an untouched peer, deletion and definite second-unlink absence. A directory retains its original default ACL. No new capability, realm binding, provider selector or production policy is added. Independent post-VM host decoding compares every access/default ACL entry, unrelated attributes and original payloads, confirms local/value storage, and retains the mandatory read-only e2fsck step. The constructor proves actual storage kinds before boot; 512 named entries are fixture geometry, not a provider limit. Bounded host reads avoid copying a complete disk. Five Rust orchestration controls and seven Python oracle controls are authored and unrun. Rustfmt was applied; changed source stays below one thousand lines. A read-only inventory covers 76 repositories and 3359 source files; none reaches that threshold. The [provider acquisition/mutation/lifetime scope](https://git.erikinkinen.fi/erix/e2fsd/issues/8), including its native scenario authoring, is implemented and is accepted under the testing waiver. Four repositories are published in five signed commits. Rootd's two Cargo selectors and both independent helper catalog selectors select [the original helper `5284c4a6`](https://git.erikinkinen.fi/erix/integration/commit/5284c4a619516d53675b081b313eb2fef8433ba6); seven catalog edges adopt that helper, its consumer and maintained contracts. The later catalog-only head is distinct. Related reviews: [Integration](https://git.erikinkinen.fi/erix/integration/pulls/12), [Rootd](https://git.erikinkinen.fi/erix/rootd/pulls/2), [provider](https://git.erikinkinen.fi/erix/e2fsd/pulls/3), [manual](https://git.erikinkinen.fi/erix/docs/pulls/4). No fixture generation, tests, builds, lint checks, Rustdoc generation, VM/manual/profiler runs or CI observation were executed. No pass, warning-free build, measured speedup or guest-build result is claimed. [Native conditional mediation](https://git.erikinkinen.fi/erix/posixd/issues/10) remains open: current realm directory-metadata/byte-stream bindings must not be broadened into file-mutation grants. Dedicated operation authority and conditional effects remain implementation work. Both full EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished. Fresh checklist arithmetic remains **16.23% weighted**, **4.81% whole-item**, **20/460 parents** and **437/897 sub-items**. This completes coverage within an already accepted provider sub-item and adds no duplicate runtime-feature credit. Persistent ACL metadata checkpoint — 29 September 2026: [e2fsd `ac258003`](https://git.erikinkinen.fi/erix/e2fsd/commit/ac2580033ecc3176faea703be41d0c947c0abd1f), [docs `2d3de8f0`](https://git.erikinkinen.fi/erix/docs/commit/2d3de8f040764eb6e236e4c1f88f71c9d693df12), [integration `cd4f7625`](https://git.erikinkinen.fi/erix/integration/commit/cd4f762543502a9d785331a2c001f26e0b1ce92a). The original ext metadata operation now preflights all selected fields and complete access ACLs, changes only owner/group-or-mask/other permissions, and preserves named/default entries and full-width owner IDs. Shared tables and immutable values use copy-on-write with exact reference lifetimes. Local alias pressure uses actual table geometry, the other attribute store or value-inode storage. Root metadata follows the original native scope; the full nonzero table reference domain has no separate 1024-owner ceiling. The incompatible Hurd/EA count-word layout refuses during mount parsing. [Mode/ACL coherence](https://git.erikinkinen.fi/erix/e2fsd/issues/10) and [attribute accounting](https://git.erikinkinen.fi/erix/e2fsd/issues/11) are implemented. Modern charges follow every descriptor's owner; legacy values retain original independent quota identities. Growth, truncation and inline conversion conserve charges, fast symlinks distinguish attributes from data, and retained inline payload is persisted before quota scanning reuses its scratch. Every edit retains the original transaction, checksums and permission epoch. Uncertain persistent completion remains fail-stop without replay. No capability, endpoint or private inode-selector ABI is added. Twenty-four new controls are authored and unrun, covering actual media/provider metadata, sharing, full IDs, root, both storage-movement directions, large immutable ACLs, count/space exhaustion, quota identity/cluster charges, real quota-file inline conversion, growth/truncation, fast symlinks, journal rollback and uncertain writes. Rustfmt was applied. Changed Rust source remains below one thousand lines (maximum 922), with inline rustdoc and missing_docs retained. A read-only inventory covers 76 repositories and 3355 tracked source files; none reaches one thousand lines. Duplicate raw quota decoding was removed and directory allocation I/O was moved into its existing module. The [provider permission pass](https://git.erikinkinen.fi/erix/e2fsd/issues/8) continues with operation-specific conditional native effects and native scenario authoring. [Native filesystem mediation](https://git.erikinkinen.fi/erix/posixd/issues/10), both complete EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished. The checklist now exposes the completed provider media portion separately; recalculation is **16.23% weighted**, **4.81% whole-item**, **20/460 parents** and **437/897 sub-items**. The weighted percentage still rounds to 16.23%; it has been recalculated. Reviews: [provider](https://git.erikinkinen.fi/erix/e2fsd/pulls/3), [manual](https://git.erikinkinen.fi/erix/docs/pulls/4), [Integration](https://git.erikinkinen.fi/erix/integration/pulls/12). Ext value-inode acquisition and cleanup checkpoint — 29 September 2026: [e2fsd `407efa3e`](https://git.erikinkinen.fi/erix/e2fsd/commit/407efa3ea1580a74806d6040e8cd05f2f81d932a), [docs `6d5da74b`](https://git.erikinkinen.fi/erix/docs/commit/6d5da74bc0f99234f650641b248e8156a34b952f), [integration `328c153f`](https://git.erikinkinen.fi/erix/integration/commit/328c153f6420049d75a57230d78c27703ce4bead). The original provider now streams complete access ACLs from local and EA-inode storage with exact size/role, original inode checksums, modern CRC32C binding or legacy owner/generation validation. One cached data block and fixed owned scratch admit large ACLs without a new total-size or entry-count cap. Failed or changed evidence clears staged pages and retires the matching original observation. No capability, endpoint or credential authority is added. [Shared and inline cleanup](https://git.erikinkinen.fi/erix/e2fsd/issues/9) is implemented: both stores are preflighted, repeated references cannot undercount the original value, shared external tables retain their own value references, and only a final value reference disposes storage. Raw hash/count fields are distinct from timestamps, EA-only inodes refuse ordinary file selection, and uncertain nonjournaled writes retain provider fail-stop without replay. Seventeen new media/provider controls are authored and unrun, including actual retained dispatch and ACLs above 64 KiB/8191 entries. The [provider permission pass](https://git.erikinkinen.fi/erix/e2fsd/issues/8) remains open for ACL-aware persistent mode changes and the remaining operation-specific effects. [Native filesystem mediation](https://git.erikinkinen.fi/erix/posixd/issues/10), both complete EriX guest-build generations and the external Rust/LLVM guest rebuild remain unfinished. Canonical phase completion remains **16.23% weighted**, **4.81% whole-item**, **20/460 parents** and **436/896 sub-items**; no new small canonical completion item is added for this checkpoint. Reviews: [provider](https://git.erikinkinen.fi/erix/e2fsd/pulls/3), [manual](https://git.erikinkinen.fi/erix/docs/pulls/4), [Integration](https://git.erikinkinen.fi/erix/integration/pulls/12). Native external-call prerequisite: [inherited stream dispatch](https://git.erikinkinen.fi/erix/posixd/issues/11). Actual CLAIM admission currently serves internal channels only; external stream use will establish retained outbound ownership without adding mode rechecks to already-open descriptors. Filesystem ACL policy and operation effects remain open. Canonical ACL transport design: [Transport complete access ACL entries on retained permission revisions](https://git.erikinkinen.fi/erix/lib-ipc/issues/3). The planned paged wire contract and caller-storage assembler retain complete original handle/revision/count correlation; native custody and operation enforcement remain separate unfinished work. Retained ext permission evidence — 29 September 2026: [e2fsd `15a9e671`](https://git.erikinkinen.fi/erix/e2fsd/commit/15a9e6711fe4c09c98c8306b4873f0e368e2b3a1), [docs `7c1f39e3`](https://git.erikinkinen.fi/erix/docs/commit/7c1f39e3e20b3e7388a39891d0335de9910faf23), [integration `f0ab7f5c`](https://git.erikinkinen.fi/erix/integration/commit/f0ab7f5c716980775728ef39d5d04777441634a5). [E2fsd#7](https://git.erikinkinen.fi/erix/e2fsd/issues/7) implements actual private snapshot and conditional-truncate dispatch using original checked inode metadata and complete local access ACLs. Both physical stores are examined; canonical structure, full qualifiers, required masks and mode correspondence are checked. Unsupported value-inode ACL payloads refuse rather than becoming absent evidence. Each retained handle stores a unique snapshot revision, metadata epoch and full fingerprint. Both metadata setters invalidate before selected permission/flag attempts. A conditional effect consumes matching evidence, re-reads complete permissions and reaches the shared retained-object resize only after an exact fingerprint match. Short replies refuse before I/O. Close/reset cannot revive revisions; compiled record geometry sizes the existing arena. Native endpoint authority and ordinary open-descriptor semantics remain required. Seventeen new controls are authored but unrun, including actual wire dispatch and resize effects. [The provider contract](https://git.erikinkinen.fi/erix/e2fsd/src/commit/15a9e6711fe4c09c98c8306b4873f0e368e2b3a1/docs/permission-evidence.md), [ext review](https://git.erikinkinen.fi/erix/e2fsd/pulls/3), [manual review](https://git.erikinkinen.fi/erix/docs/pulls/4) and [catalog review](https://git.erikinkinen.fi/erix/integration/pulls/12) record the boundary. Three immutable catalog entries select the original signed provider/manual revisions. Formatting was applied; tests, builds, lint checks, rustdoc, VM/manual/profiler runs and CI observation remain deferred. No pass or warning-free build is claimed. The completed provider sub-item raises weighted checklist progress to 16.19%; the parent remains open. Value-inode payload integrity/acquisition, canonical ACL entry transport, ACL-aware persistent metadata mutation and native caller/route/policy enforcement remain unfinished. Both full EriX guest builds and the external Rust/LLVM guest rebuild remain required and unproved. Duplicate selected keys and malformed trailing/external data refuse; private staging is cleared. Thirteen regression controls are authored but unrun, including the actual file-read boundary and value-inode traversal. Parsing, body geometry, rewriting and fixtures are split into documented modules below 1,000 lines. See the [provider contract](https://git.erikinkinen.fi/erix/e2fsd/src/commit/d586bf51393af68ea416f4e453018e6760ff44fa/docs/xattr-storage.md), [E2fsd review](https://git.erikinkinen.fi/erix/e2fsd/pulls/3), [manual review](https://git.erikinkinen.fi/erix/docs/pulls/4) and [Integration review](https://git.erikinkinen.fi/erix/integration/pulls/12). Three catalog entries select the original signed provider/manual revisions; the independent orchestration helper and kernel-lifetime catalog are unchanged. Formatting was applied. Tests, builds, lint checks, rustdoc, VM/manual/profiler runs and CI observation remain deferred; no pass or warning-free build is claimed. This is structural preservation, not complete ACL policy: value-inode payload acquisition, ACL decoding, trusted provider revision snapshots and native caller/operation enforcement remain unfinished. Completion remains 16.17% without new canonical checklist credit. Both complete EriX guest builds and the external Rust/LLVM guest rebuild remain required and unproved. [Realm design](https://git.erikinkinen.fi/erix/posixd/issues/1), [compatibility ABI design](https://git.erikinkinen.fi/erix/lib-posixabi/issues/1), [filesystem audit](https://git.erikinkinen.fi/erix/vfsd/issues/1), [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). Begin with checked policy types and independent controls, then trusted runtime intake and native-before-policy enforcement, then bounded native scenarios and coordinated publication. Keep this issue open until all implementation obligations are met, regardless of the execution waiver. <details> <summary>Related records and contracts</summary> | Repository | Links | | --- | --- | | e2fsd | [issue 6](https://git.erikinkinen.fi/erix/e2fsd/issues/6) | | exsh | [PR 3](https://git.erikinkinen.fi/erix/exsh/pulls/3) | | posixd | [issue 12](https://git.erikinkinen.fi/erix/posixd/issues/12), [issue 13](https://git.erikinkinen.fi/erix/posixd/issues/13) | | vfsd | [issue 5](https://git.erikinkinen.fi/erix/vfsd/issues/5) | </details>
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:05 +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/posixd#10
No description provided.