[FEATURE] Enforce complete inline documentation and warning-free documentation builds #1

Open
opened 2026-09-12 07:56:22 +02:00 by erikinkinen · 0 comments
Owner

Problem and motivation

Auditable Rust APIs need documented ownership, authority, failure and unsafe invariants across every target. Existing prose and a public-item lint alone cannot demonstrate that private code, build scripts, examples and manual outputs are adequately documented.

Proposed behavior and scope

Inventory every crate target, enforce missing_docs without blanket escape hatches, document public and private contracts, and run warning-denied rustdoc with private items. Reconcile canonical component documents, headers, API references, manual pages and the technical manual.

This issue records planned work; its unchecked criteria are not implementation proof. The normative basis is Phase 6 and AC1–AC24.

Authority, security and reliability

Documentation must state real capability sources, lifetimes, denial and cleanup behavior rather than infer authority from names. Shared governance remains byte-identical to meta. Non-Rust code uses the language’s own comment format, and security-sensitive details stay in restricted reporting channels.

Apply the priority order: security, reliability, then performance. Keep suspected vulnerabilities in the repository’s restricted SECURITY.md reporting channel.

Acceptance criteria

Checklist
  • Inventory every crate root and target, including binary-only, build-script,
    test/example and nested crates; identify existing missing_docs enforcement and every local
    allow/expect/doc-hidden escape.
  • Document crate/module purpose, trust boundary, owned/borrowed state, lifecycle,
    authority and error contracts using //!//// rustdoc comments.
  • Document every public item, field, variant, constant, associated item, macro and
    FFI export with semantics, units, ranges and failure behavior.
  • Document private functions, structures, fields and non-obvious algorithms as well;
    explain concurrency, mutation order, cleanup, complexity and invariants. missing_docs alone
    is not a private-code completeness audit.
  • Give unsafe APIs # Safety, and fallible/panicking APIs accurate # Errors/# Panics sections where applicable. Document each unsafe block's concrete invariant and why
    safe alternatives do not cover the operation.
  • Enforce #![deny(missing_docs)] or an equally non-bypassable shared lint policy in
    every EriX-authored crate/target; reject weakening attributes. Do not use blanket allowances,
    dummy comments or doc-hidden to pass the gate.
  • Add private-item documentation review/check coverage and run Rustdoc with
    --document-private-items; validate broken links and examples with RUSTDOCFLAGS="-D warnings" across supported target/feature profiles.
  • Ensure CI actually checks missing_docs in default and alternate feature builds, not
    only one public-library configuration; add a negative fixture proving undocumented public API
    fails the shared policy check.
  • Document non-Rust authored code inline in its language's supported comment format,
    including shell/Python tools and assembly boundary contracts. Do not pretend rustdoc parses
    unrelated languages.
  • Update meta standards/templates and propagate necessary policy changes
    deliberately. Repair stale canonical GenAI policy links to
    docs/policies/generative-ai-contributions.md; keep attribution optional.
  • Update README/ARCHITECTURE/ROADMAP and relevant manual chapters for each
    implemented ABI, realm, POSIX service, toolchain, profiler and build step; keep historical
    measurements separate from current guarantees.
  • Regenerate API references, test examples, build the whole manual, check final
    warnings/overflow/links and visually inspect changed rendered pages. Record toolchain/source
    provenance for the generated documentation.
  • Update canonical templates and every repository README to remove
    current-status/progress/checkpoint sections; put concise current state in ROADMAP/ARCHITECTURE
    and detailed historical evidence in linked issue/reports.
  • Refactor long README/ARCHITECTURE/ROADMAP paragraphs and exhaustive lists into
    short summaries plus focused design/API/operator documents. Preserve canonical headings,
    discoverability and normative invariants; do not hide important authority limitations or move
    status into another README section.
  • Keep help text, man pages, rustdoc, C headers, IPC specifications and technical
    manual consistent through shared semantic metadata where useful; validate coverage and
    examples, not merely that generated files exist.

For each implementation slice, retain actual formatting, strict Clippy, unit/doctest and warning-denied build results for all altered Rust repositories and valid configurations. Add relevant runtime VM coverage, monitor older unit/VM regressions in exact-head CI, and update canonical component documents and affected technical-manual/API material. Every authored code file must remain below 1,000 physical lines, with meaningful inline documentation and missing_docs enforcement in Rust crates.

Alternatives and tradeoffs

Dummy comments, hidden APIs and lint allowances make checks green without helping a reviewer. Keep useful inline invariants, concise canonical navigation and detailed contracts in their owning API/manual documents.

Validation checkpoint — 14 September 2026: Signed Posixd 52ef820d33399490c121aad3af1409139e4a8f44 selects the proposed realm custody owner: Procd deposits an ancestor SEND-lineage revoker into its exact native generation before export and retains a nested guard for earlier realm retirement. Exported aliases descend from the nested guard; ancestor-only bypass and setup aliases must be removed before publication. Runtime producer adoption, realm byte I/O and both complete guest build generations remain open.

Its private records cannot survive userspace scheduling and own no retained source authority.

Reachable backend disposal-failure coverage, sustained invocation-workload profiling, realm producer adoption, whole-codebase authority/private-rustdoc closure and both complete EriX-in-EriX build generations remain open. No new syscall number or wire record is assigned; the existing CALL/RECV/REPLY ABI is unchanged.

Sustained invocation-workload profiling, syscall wire and fresh-buffer/fault/overlap validation, actual owned CPL3 peers, reachable backend disposal-failure coverage, realm producer adoption, whole authority/private-rustdoc closure and both complete EriX-in-EriX build generations remain open.

Every sample checks exact bytes and SEND capability bindings, authenticated origin, foreign selection, duplicate completion refusal, FIFO position reuse, one-time collection and final invocation disposal. Native syscall adapters, actual owned CPL3 peers, reachable backend disposal-failure coverage, realm adoption, full authority/private-documentation closure and both complete EriX-in-EriX build generations remain open.

Measured native invocation lookup refinement — 15 September 2026: Signed Kernel 8349d68636382cc7e25a3347f5f1df216554203a retains only numeric carrier-search positions. No successful authorization, capability or reference is cached. These are host operation wall times, not guest startup/build acceptance or a statistical guarantee. Current full-suite CI remains required; stopped cohorts are not polled again. Owned syscall wire adapters, actual owned CPL3 peers, fresh-buffer validation, reachable backend disposal-failure coverage, realm adoption, full authority/private-documentation closure and both complete EriX-in-EriX build generations remain open.

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

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

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

Descriptor startup rejects short or dirty cleanup storage before metadata effects; transactions exclusively reborrow the complete slice and erase it after emergency cleanup.

All 961 Rust tests pass in each default/all-feature/production development/release configuration, with formatting, strict host/native Clippy, private rustdoc and eight native builds without warnings. Four added tests cover workspace disjointness, malformed backing, complete caller extent and consecutive cleanup reuse; existing cleanup controls now also check buffer canaries and erasure. All 73 warning-denied checker tests pass.

Both actual optimized native fallbacks measure 48 local bytes, compared with the retained prior 32,816-byte frames. Their full checker reports remain INCOMPLETE: runtime/all graphs contain 691/604 unresolved observations, and the old 32 KiB initial stack-reservation requirement still needs a workspace-specific evidence contract. Ordinary-source membership and direct-versus-nested early-drop bounds remain open. The 8/33/56 KiB upper limits and 64 KiB stack are unchanged; this measurement is not an all-path stack-safety claim.

Matching producer 38424571b76b36c1e631d99fd2c859fb32311eea exports/consumes 96 capacity words plus 72 target layout words, reserves both transport arrays first and rejects old/mixed layouts. Packaging both actual optimized shell configurations under canonical dev/release policies derives 4,300,800 workspace bytes, with unchanged executable bytes and a separate 64 KiB stack. All 162 Integration helper commands and its strict 320/321-test Rust matrix pass, including four native builds. These are private artifact and host checks, not guest execution. The product catalog still selects the earlier shell; coordinated catalog adoption and matching runtime VMs remain required.

Documentation 79cdd4c3694e800091b55c737fca04c7bdd3d071 describes the ownership and compatibility contract. Its 45 tests and canonical checks pass. The full manual renders 2,375 pages without final warnings; all 433,713 word boxes are in bounds and changed page 2280 passes visual review. API snapshots are unchanged. Exsh CI 225/226 fails only the incomplete frame gate after 961 Rust and 73 checker tests; all four logs total 311,820 bytes with zero warnings. CI runtime/all graph observations are 662/587 and both fallbacks measure 48 bytes; these artifacts remain distinct from local images. Docs CI 883/884 passes with all four complete logs (762,212 bytes); reference passes converge with 35/1/0 warnings and zero final warnings. These component cohorts are fully classified. Integration CI 1637/1638 remains queued at its first observation. No full build within EriX or whole-codebase authority closure is claimed.

Complete native companion checkpoint — 15 September 2026:

Signed Integration db80a2c1dfc669bd724762d476f5f5c0da005ff6 centralizes the complete eight assembly input roles plus the original producer script. Source selection and support-manifest validation share those roles; both outer artifact keys bind the contract module. The catalog changes only native lib-cstd to original bdcbbea43550e8b99cd9a8221e4bc5a645637990. Exact path/byte, tool, waited status, cleanup and output checks remain required.

Actual hidden/public production and missing/extra/altered receipt controls pass, as do both outer cache-key controls. All 162 helper commands are covered: 160 pass in the full run, and the two corrected test-only fixtures pass separately. The original missing-module and unclosed-fixture-stream failures are retained. The strict 320/321-test Rust matrix, Clippy, formatting, private rustdoc and four native builds pass without warnings.

A host-built diagnostic native image contains 38 executables and 27 shared objects, passes closure checks and builds without warnings. Its SHA-256 is ff5d774308cdf236c860a2423adab6e2594bf3c0991b26eb37cb3c64af96ddfe. It uses 73 original component selections with 72 coherent Cargo manifests and the five explicitly recorded helper corrections whose bytes match this signed checkpoint. It is not an unmodified product catalog. The unchanged editor/history, inherited-stream timing and runtime-error VM probes all pass with their original 120/15/10-second budgets and exact output checks; each leaves the source image unchanged.

Signed Docs 31bd9524c31c9d8d6a8f00248f702e6b7d428106 explains the complete source contract. All 45 tests and canonical checks pass. The complete manual renders 2,375 pages without final warnings; all 433,817 word boxes are in bounds and changed page 2281 passes visual review. Original API snapshots are unchanged. Docs CI 885/886 passes with all four complete logs (762,204 bytes); reference passes converge with 35/1/0 warnings and zero final warnings. Integration CI 1639/1640 remains queued at its first observation; the build compatibility issue stays open pending its complete CI. Full Exsh frame proof, coherent product adoption and both complete EriX-in-EriX build generations remain open.

Paired workspace and literal command evidence — 15 September 2026:

Signed Docs 5d77dc2b82bf5439e58234d901e30f4565aaa81a documents the independent pristine/packaged ELF workspace mapping domain, its native-loader assumption and the separate source borrowing, erasure and all-path frame obligations. It also fixes 24 existing inline long options and argument delimiters whose ASCII double hyphens previously became an en dash (issue #8). Numeric ranges, prose punctuation, verbatim command blocks and original signed API snapshots remain unchanged.

All 45 documentation tests, canonical and Markdown checks pass. The complete manual has 2,375 pages, 433,924 in-bounds word boxes and zero final warnings. Text extraction confirms literal option bytes, including embedded set -- and standalone delimiters; nine affected pages pass visual review. PDF SHA-256: fd33102422cc80697ead3f5c939b39d1e9c6bf69ce06475be4ce8767cafb2f23. The first render's punctuation failure remains recorded separately; the accepted PDF comes from the final corrected source. Docs CI 887/888 passes with all four complete classified logs (762,236 bytes). Both manual jobs pass 45 tests and converge with 35/1/0 reference warnings, leaving zero final warnings; both Markdown jobs pass. Rust and VM checks do not apply to these documentation-only edits.

This checkpoint does not establish complete runtime permission, frame, authority, realm or guest-build acceptance.

Separate one-CPU and two-CPU diagnostic VMs pass the unchanged native command sequence. A read-only hardware observer matches all 233,755 selected coreutils executable bytes, verifies CPL3 and enabled paging/execute-disable state, and confirms both observed RELRO pages are user-readable, read-only and non-executable; the current stack is user-writable and non-executable. Both processors report execute-disable enabled. This is an exact process-entry/table observation, not an injected instruction-fault test or whole-system permission proof. The diagnostic image SHA-256 is 8c3c24639e8e1ca8c4f2ad4e485323abf32ec07408241c3e4fa9713f6e07e812.

Signed Docs d221e725c2543316680e63fc5e8314ce0fe3bdf1 documents the mapping and processor contracts. All 45 documentation tests and canonical checks pass; the 2,375-page manual has 434,308 in-bounds word boxes and zero final warnings, with three changed pages visually reviewed. Exported API snapshots are unchanged. Kernel CI 574/575 passes with four complete warning-free logs (708,112 bytes), including existing optimized workload examples. Docs CI 891/892 passes all four complete logs (762,176 bytes), with 45 tests per manual job and zero final warnings. The later maintained permission regression is recorded below. Full frame proof, whole-codebase authority/documentation review, runnable realms and both complete guest build generations remain open.

Actual one-CPU and two-CPU runs on the repaired diagnostic image pass the original native-time command sequence and the expanded hardware checks: all 58 selected code pages are user-readable, read-only and executable; both RELRO pages are read-only/non-executable; the current stack is writable/non-executable. Complete executable bytes match and NX interpretation is enabled on every selected processor. An earlier image is rejected by the maintained observer. Both child outcomes, exact original input bytes and temporary cleanup are retained, with empty debugger stderr in both positive runs. The final cleanup code also preserves reaping when a direct child exits between poll and termination.

The command's image CI gate awaits adoption of a coherent product catalog containing both required component fixes. Its explicit diagnostic invocations do not silently replace the older maintained image graph. Signed Docs 3fb0b12ff55d044cc4bbe142418ab7a5b07bb42d documents the maintained operator contract. All 45 tests and canonical checks pass; the 2,377-page manual has 434,563 in-bounds word boxes with zero final warnings, and the changed subsection passes visual review. Exported API snapshots are unchanged. The preceding Docs CI result is recorded below; current Integration CI, complete frame proof, whole-codebase authority/documentation closure, runnable realms and both guest-build generations remain open.

It shares the relocation inventory with guarded tables and rejects overlapping or executable-byte writes.

Replaying both unique original pristine/packaged artifact pairs preserves their hashes and all original stack/resource budgets. Runtime/all-feature reports retain 641/591 new call/tail proofs and reach 266/240 functions; unresolved observations fall from 691/604 to 271/232. Workspace mapping passes. Both full reports remain incomplete: unknown indirect control flow, non-returning semantics and source/direct-versus-nested boundaries remain separate obligations. These are partial static admission results, not a complete frame or authority proof.

Signed Docs 83b2d4a2dfc473bb8a99719f86fa1c3c33effa53 explains the proof contract and its limits. All 45 documentation tests and canonical checks pass; the 2,377-page manual has 434,680 in-bounds word boxes, zero final warnings and a visually reviewed changed page. API snapshots are unchanged. The preceding Docs permission-observer checkpoint passes CI 893/894 with four complete logs (762,616 bytes) and zero final warnings. Exsh CI 231/232 is fully classified: all 961 Rust tests, 102 checker tests and all four workspace domains pass, with four complete logs totaling 314,760 bytes and zero warnings. Only the complete frame gate fails. Its separately selected CI artifacts report 273/230 unresolved observations; these do not replace the retained local artifact identities/counts. The preceding Docs CI result is recorded below. All 2,997 inventoried authored code files remain below 1,000 lines; semantic authority/documentation closure, product catalog adoption, runnable realms and both complete guest builds remain open.

Unknown calls, unsupported instructions, malformed boundaries and unproved tail cycles cannot establish facts.

All 114 checker tests pass, including twelve new literal controls and a 1,200-function chain requiring at most two body visits per function. All six strict Rust feature/profile configurations pass 961 tests each, with six native builds, host/native Clippy, formatting and private rustdoc. Runtime Rust, linker scripts and Cargo selections are unchanged. The physical inventory now covers 2,999 authored code files, all below 1,000 lines.

The same retained original artifact pairs yield thirteen grounded facts each. Runtime/all-feature unresolved observations fall from 271/232 to 181/150; every function-end boundary error disappears under the stated ordinary-call model. The work queue performs 347/313 body evaluations for 266/240 discovered functions and retains 263/237 in the final reachable graph. This is an analysis-work count, not a claimed runtime speedup. Remaining observations are 140/111 unknown calls, 40/38 unknown branches and one unsupported instruction per mode. Both workspace mappings pass; whole frame and source domains remain incomplete with unchanged budgets. A separate proof audit verifies earlier dependencies and retained terminal callees.

Signed Docs 97ce65dcb8cef7232b50d53af90ff8673d623e05 documents the refinement. All 45 tests and canonical checks pass, and the 2,377-page manual has 434,800 in-bounds word boxes, zero final warnings and a visually reviewed changed page. Exported API snapshots are unchanged. Exsh CI 233/234 is fully classified: 961 Rust tests, all 114 checker tests and four workspace mappings pass, while the full frame gate remains incomplete. All four logs total 314,776 bytes with zero warnings. Those separately selected CI artifacts retain 183/145 unresolved observations, distinct from the retained local pair counts. Matching Docs CI 897/898 passes with all four complete logs across the two terminal observations (762,600 bytes), 45 tests per manual job and zero final warnings. The preceding Docs target-contract checkpoint passes CI 895/896 with four complete logs totaling 762,636 bytes and zero final warnings. Full indirect/source proof, coherent catalog adoption, whole-codebase authority/documentation closure, runnable realms and both full guest-build generations remain open.

No guest authority, acceptance oracle, error precedence or 120/15/10-second limit changes.

All 172 host cases in eleven suites pass, including 28 diagnostic cases and eight new independent producer, malformed-prefix, private-receipt and actual-wrapper controls. The strict default/all-feature development/release matrix passes 320/321 tests per mode, host/native Clippy, four native builds, formatting and private rustdoc without warnings. A documentation line wrap is the only source change after the Rust matrix. One initial negative fixture had identical transport bytes when both exits were unknown; a distinct contradiction replaces it. An initially over-isolated console-suite invocation is corrected to its maintained CI invocation, without changing that suite or the watchdog.

Signed Docs c4bfc12245036f069d178a10183bb1ed15b4aab5 updates the operator manual. All 45 tests, canonical checks and full rendering pass: 2,377 pages, 435,037 in-bounds word boxes, zero final warnings and both changed pages visually reviewed. API snapshots are unchanged. Matching CI is pending. Release interrupt reuse #54 and release COM1 shell lines #55 remain open: missing original inner artifacts are not recovered, no shared cause is proved, and this checkpoint adds no successful guest run or full guest build.

Integration diagnostic CI 1645/1646 remains queued at its signed head; original release-input bugs 54/55 remain open.

All 138 checker tests, formatting, canonical document checks and an independent original-byte/load/relocation and earlier no-return dependency audit pass. Retained runtime/all artifact pairs gain 16/18 register edges; the all-feature graph reaches one additional function. Remaining unresolved sites are 164/132, with thirteen grounded no-return facts per mode. Both workspace mappings pass. Full frame/source gates remain incomplete with actual exit 1 and unchanged 60/15-second and 64 MiB budgets. Every Rust/Cargo/linker/build/workflow byte is unchanged from six strict 961-test configurations and six native builds; no new Rust build or guest execution is claimed.

Profiling identified unnecessary effect parsing when all registers were unknown. Skipping those identity transfers and compiling fixed effect patterns once preserves every report decision, reducing runtime effect-parser calls from 34,901 to 1,334 and all-feature calls from 33,398 to 1,348. One before/after observation per identical pair measures 5.089 to 4.385 seconds and 4.997 to 4.358 seconds respectively, including observer overhead. These are bounded host work measurements, not a statistical timing guarantee or guest speedup.

Signed Docs 4f770bee4c6a4784b4fcce6ae606d1fc10b328da documents register provenance and limits. All 45 tests and the 2,377-page manual render pass, with 435,231 word boxes inside page bounds, no final warnings and visual review of the changed page. All 3,001 authored code files remain below 1,000 physical lines. Matching Exsh/Docs CI is pending. Complete source domains, authority closure, executable realms and both complete guest-build generations remain open.

Register checkpoint CI — 16 September 2026: Exsh da8b75c9063c52de2149f2a6c7ed170f720a6c62 is terminal in CI 239/240. Both runs pass 961 Rust tests, all 138 checker tests, strict warning-denied Rust checks and Markdown. All four paired workspace domains pass in each run. The required full-frame gate remains incomplete, with 168/131 unresolved observations on these CI artifacts, so both runs correctly fail overall. Four complete logs total 314,840 bytes and contain no compiler/lint warnings. These CI artifact observations remain distinct from the retained local pairs.

Docs 4f770bee4c6a4784b4fcce6ae606d1fc10b328da passes CI 901/902. Four complete logs total 762,604 bytes; each manual job passes 45 tests and renders 2,377 pages. Initial reference-resolution warnings clear during the normal three LaTeX passes; final renders have zero warnings. The full source/frame proof, coherent catalog adoption, authority closure and both complete confined guest-build generations remain open.

Every selected immutable table byte, matching base addition and candidate instruction boundary must be proved before retaining any successor or branch evidence. Numeric/table values cannot authorize function calls.

All 157 checker tests pass, including complete 256/65,536-entry domains, nonzero and signed read windows, extended register fields, joins, bypasses, loops, width controls and immutable/boundary refusals. Original-byte function/table/base/index/addition audits, formatting, Markdown and canonical checks pass. Final original runtime/all pairs admit two table branches each and retain 164/132 unresolved obligations: two entry branches resolve, while two newly exposed guard-interior conflicts remain. Both workspace mappings and thirteen grounded no-return facts per mode are retained. Full frame/source status remains incomplete with actual exit 1 and unchanged budgets. Initial partial-set exploration is diagnostic negative evidence, not accepted coverage.

Profiling identified repeated compilation of fixed stack patterns. Compiling sixteen unchanged patterns once and sharing the existing padding pattern preserves all report decisions and matching operations. One baseline/optimized observation per original pair reduces runtime/all regex-cache lookups from 651,254/627,530 to 135,274/131,391. Profiled times are 5.994 to 5.445 and 5.756 to 5.179 seconds, including overhead and waiting. These measurements establish reduced host work, not a timing guarantee or guest speedup. The final source has a clarified module docstring and separately reconciled complete replay decisions.

Every Rust/Cargo/linker/build/workflow byte retains the existing strict matrix; no new Rust build or guest execution is claimed. Signed Docs 242b78c8f35aeaef879f819c670574a4c1d95c3f explains complete read windows and target-set admission. All 45 tests and the 2,379-page render pass, with 435,421 word boxes inside page bounds, zero final warnings and visual review of both changed pages. All 3,003 authored code files remain below 1,000 physical lines. Matching CI is pending. Explicit flag/guard refinement, full source/frame proof, coherent catalog adoption, authority closure and both complete confined guest-build generations remain required.

The required full-frame gate remains incomplete with 168/131 unresolved observations on the CI artifacts, so both runs fail overall. No incomplete proof is treated as acceptance.

Signed Docs 242b78c8f35aeaef879f819c670574a4c1d95c3f passes CI 903/904. All four logs are complete (763,044 bytes); each manual job passes 45 tests and renders 2,379 pages. Initial reference warnings clear in the normal LaTeX passes; final renders have zero warnings. An expanded local source/config inventory additionally checks 685 files, bringing the combined physical ceiling audit to 3,688 files, all below 1,000 lines. Flag/guard refinement, source/frame closure, coherent catalog adoption, complete authority review and both full confined guest-build generations remain required.

A 32-bit comparison never zeroes upper bits. Every complete immutable target set remains mandatory, and numeric/table values cannot authorize function calls.

All 176 checker tests pass, including an independent exhaustive interval oracle, high-register dispatch, sign extension, bypasses, conflicting/unknown joins, stale proofs, complete table arms and large arithmetic loops. Independent original-byte audits check 354/321 comparison edges, eleven table branches per mode, protected function loads and thirteen earlier grounded no-return facts per mode. Original runtime/all pairs reach 271/246 functions and retain 158/126 unresolved observations, down from 164/132. Workspace domains pass; full frame/source status remains incomplete with actual exit 1 and unchanged budgets.

The audit also reproduces and fixes terminal-call discovery loss. A prior successor diagnostic no longer suppresses recomputation of a revisited call. Three independent controls retain grounded no-return, returning and unknown-target behavior. Original byte/range inspection corrects earlier descriptions of two guard-interior conflicts: these were fallthrough exactly at declared function ends. Padding remains outside those functions; callee names never supply no-return proof. Matching CI remains required before closing the defect.

Profiling identified repeated decoder-effect work. Sharing immutable effects only within one function-body analysis reduces runtime/all effect decoding from 72,668/69,784 to 34,499/32,576 and operand parsing from 75,637/72,547 to 37,468/35,339. Complete paired decisions remain identical. Final single paired profiled observations are 6.633 to 6.425 and 6.416 to 6.269 seconds, including overhead and waiting. The final baseline overlaps host test execution, and earlier pairs show timing variability; these diagnostic durations do not isolate a speedup. This establishes reduced host work, not a timing guarantee or guest speedup.

Every Rust/Cargo/linker/build/workflow byte retains the existing strict six-configuration 961-test matrix and six native builds. Formatting, Markdown and canonical checks pass. Signed Docs d8fbc3a1f3696e02954b81f23511cee513ddfa8c passes all 45 tests and complete 2,379-page rendering: 435,637 in-bounds word boxes, zero final warnings and two visually reviewed pages. The physical audit covers 3,005 authored code files below 1,000 lines. Matching CI is pending. Remaining indirect calls/branches, full source/direct-versus-nested proof, coherent catalog adoption, complete realm authority and both full confined guest-build generations remain required.

Comparison checkpoint CI — 16 September 2026: Exsh CI 243 and 244 are terminal. All four complete logs total 314,904 bytes with no compiler/lint warnings. Strict Rust checks, 961 Rust tests, 176 checker tests, Markdown and all four workspace domains per run pass. The required full-frame gate remains failed with 163/126 unresolved observations on these CI artifacts; their identities are distinct from the original static replay pairs. No full frame or guest-build acceptance is claimed.

Docs CI 905 and 906 pass with all four complete logs (763,056 bytes), 45 tests and 2,379-page manuals. Both final renders have zero warnings after ordinary reference convergence. The terminal-call discovery controls pass in both Exsh runs, resolving the scoped defect in Exsh #6 while the complete emitted-proof defect stays open. The current physical audit covers 3,690 authored source/config files below 1,000 lines; semantic authority and complete private documentation closure remain required. Original unfinished Integration jobs continue under their existing handles.

Full 64-bit comparisons may use the architectural numeric domain while keeping protected typed identities separate; narrow comparisons still require independent upper-bit proof.

All 191 checker tests pass, including independent exhaustive concrete arithmetic and modular-interval oracles, wraparound and authority-negative controls. Original runtime/all artifact pairs admit fifteen table branches each and reach 271/246 functions, with 156/124 unresolved observations. Both workspace mappings pass; actual full-frame exits remain 1 and full source/direct domains remain incomplete. Independent original-byte audits check arithmetic/conditional/table premises, 16/18 protected register edges and thirteen grounded no-return facts per pair.

Profiling identified repeated stack-neutral grammar evaluation. A cache scoped to one function reduces those evaluations from 95,643 to 43,169 for runtime and 92,608 to 41,053 for all features, with complete paired report decisions equal. Cached values include refusals and contain no path facts. Timing observations include observer overhead and do not isolate a statistical speedup or guest performance.

Formatting, Markdown, whitespace and all 45 Docs tests pass. The 2,379-page manual has 435,808 in-bounds word boxes, zero final warnings and visual review of the changed pages. The physical inventory covers 3,691 authored source/configuration files, all below 1,000 lines. Semantic authority and complete private rustdoc closure remain open. Rust/Cargo/linker/build/workflow bytes are unchanged from the retained strict matrix and classified CI 243/244; new Exsh CI 245/246 independently reruns those checks. Docs CI 907/908 also runs. Matching CI is pending, and no full confined guest build or coherent product-catalog adoption is claimed.

Test-import correction and CI classification — 16 September 2026: original Exsh CI 245/246 failed before the frame gate because the arithmetic test could not import its checker module. They attempted 177 tests: 176 passed and one module import failed. The preceding 961 Rust tests and strict build stages passed; all four complete logs total 309,708 bytes with zero compiler/lint warnings. The earlier local 191-test pass used an explicitly supplied PYTHONPATH and did not prove equivalence to the clean workflow. This regression is retained in Exsh #7.

Signed correction 12331e26f3bb7a25c0146c8b314eef46dd451099 loads the repository's literal fixture setup before implementation imports in both affected modules. A new regression imports every checker test module in a fresh isolated interpreter; it reproduces both failures before correction and passes afterward. The exact clean workflow command now passes all 192 tests without PYTHONPATH. Formatting, Markdown and whitespace pass. Checker/runtime/Cargo/workflow bytes are unchanged, so the prior original-artifact and profiler evidence retains its exact scope. New CI 247/248 runs against the corrected source; issue #7 remains open pending matching CI.

Docs CI 907/908 now passes with four complete logs totaling 763,024 bytes, all 45 tests and 2,379-page manuals. Both final renders have zero warnings after ordinary reference convergence. Full frame/source proof, coherent catalog adoption and complete confined guest builds remain outstanding.

Both runs reach and fail the required full-frame gate. All four workspace mappings per run pass, while the emitted CI pairs retain unresolved counts [161, 161, 124, 124]; these artifacts are distinct from the original static pairs' 156/124 observations. Full source/direct domains remain incomplete, and Exsh #4 remains open. The original import-failed runs 245/246 stay classified and are not relabeled as passing.

Docs CI 907/908 passes all 45 tests and 2,379-page manuals with zero final warnings; four complete logs total 763,024 bytes. Signed trees are clean, canonical issue/PR metadata remains applied, and the 3,691-file physical inventory remains below 1,000 lines per authored source/configuration file. Semantic authority and private documentation closure, coherent catalog adoption, runnable realms and both full confined guest build generations remain outstanding. Original unfinished Integration runs continue under their existing handles and budgets.

Complete original bodies and earlier callee facts now prove never-written register families.

All 213 clean-environment checker tests pass, including 21 new controls, eleven isolated module imports and a 1,200-function grounded dependency chain. All six strict Rust feature/profile configurations pass 961 tests each, with host/native Clippy, private rustdoc and six native builds; no warnings. Original runtime/all artifact pairs retain 65/72 protected register edges and 70/77 load origins, reducing unresolved observations from 156/124 to 107/70. Both workspace mappings pass; full source/frame/direct gates retain actual exit 1. Independent audits bind 7,795/7,503 used-contract instructions and complete earlier-proof closure to the original captured bytes.

Profiling identified unnecessary empty-state scans and rejected-body suffix work. Removing them preserves every paired report decision and reduces total profiled Python calls from 32,160,478 to 26,673,252 and from 30,880,221 to 25,402,446. Single paired timings include observer overhead; they do not establish statistical or guest performance. Original timer, byte and stack budgets remain unchanged.

All 45 Docs tests, formatting, Markdown and canonical checks pass. The 2,379-page manual has 436,058 in-bounds word boxes, zero final warnings and visual review of both changed pages. The physical audit covers 3,693 source/configuration files, all below 1,000 lines. Semantic authority/private-documentation closure, product adoption, complete source/frame admission, runnable realms and both full in-EriX build generations remain open. Automatic CI for both exact signed heads is being followed; local passes are not reported as CI acceptance.

Matching preservation CI — 16 September 2026: Exsh 249 and 250 are fully classified at 641ac2fc7c3fba3ab351f2863df7e35117b2732a. Both pass all 213 checker tests, including eleven isolated imports and the stale-frame controls, all 961 Rust tests and preceding strict host/native Clippy, rustdoc and native build stages. Markdown and all four workspace mappings per run pass. The remaining full frame gate fails as required; original CI artifact observations are 111, 111, 74, 74], [111, 111, 74, 74. All four complete logs total 314,995 bytes without warnings. The independently retained local pairs remain 107/70, with their own original identities.

Docs 909 and 910 pass at 7a7c3ff0095de8f008c9b534fd993554df37f976. All four complete logs total 763,088 bytes; both manual jobs pass 45 tests and render 2,379 pages with zero final warnings after ordinary reference convergence. The corrected frame-pointer issue is closed on this matching evidence; the full source/frame issue remains open. No full confined build, runnable realm or coherent product-catalog adoption is established.

Checked symbolic relocations contribute write footprints, never local targets or library-discovery authority. Code/dynamic metadata mutation, unknown streams, malformed names/links, resolver symbols and invalid relative prefixes refuse intake.

All 231 checker controls (18 new) and 12 isolated test modules pass in a clean environment. All six strict Rust configurations pass 961 tests each, host/native Clippy, private rustdoc and six native builds without warnings; formatting and canonical checks pass. Both retained standalone pairs have exactly unchanged proof decisions (107/70 unresolved). The original native pair inventories 1,345 functions, reaches 220, proves workspace mapping and retains 299 unresolved observations, including 102 symbolic-target refusals. The shell entry has 6,864 partially accounted bytes; its incomplete paths do not establish an upper bound. Independent original-byte audit checks all 1,086,955 executable bytes, exactly 154 changed capacity bytes and 627 relative call-load proofs. Full source/frame/direct gates remain incomplete, actual checker exit 1.

Native original SHA-256 879579542895f2f3fbda38972ebaaaf55e05857ffc456342117624a9bc8d24a9 and packaged SHA-256 183a1a2f1f4192ffd0b9c123ca50d33af6c584940ca51b156198f8822b718feb retain their original Exsh runtime selection b12e172e7b266842a8659104894f6821166165fb. The native producer already retains the original; no duplicate artifact or producer mutation was required. Profiling all three original pairs takes 16.60/16.47/17.02 seconds including observer work under unchanged 60/15-second and 64 MiB budgets. These are individual static observations, not guest performance claims.

Signed Docs 12c6d0a91e5e9c5f170d6d0aa7f050dd60e883ef documents the contract. All 45 tests and a complete 2,381-page manual pass, with 436,247 in-bounds word boxes, zero final warnings and changed-page visual review. The physical inventory covers 3,695 source/configuration files, all below 1,000 lines; semantic authority/private documentation closure remains open. New Exsh CI 251/252 and Docs CI 911/912 are running at their exact signed heads. Complete source membership, native dependency closure, coherent catalog adoption, runnable realms and both full guest builds remain required.

Matching native intake CI — 16 September 2026: Exsh 251 and 252 are fully classified at d67dcb963f1aa265b13dd0609a5f8488784b5822. Both pass 231 checker tests, twelve isolated imports, 961 Rust tests and the strict preceding Clippy/rustdoc/native build stages. All four workspace mappings per run and Markdown pass. The required full frame gate remains incomplete; the CI artifact counts are 111/111/74/74 unresolved observations in each run. Four complete logs total 315,371 bytes, with zero warnings. Retained local standalone and native artifacts keep their own separate identities and 107/70/299 counts.

Docs 911 and 912 pass at 12c6d0a91e5e9c5f170d6d0aa7f050dd60e883ef. Four complete logs total 763,452 bytes; each manual job passes 45 tests and renders 2,381 pages, with ordinary reference convergence followed by zero final warnings. No full source/frame proof, native dependency closure, runnable confined realm or full EriX-in-EriX build is established.

A separate original-source relocation calculation defect is now reproduced and tracked with the canonical bug template in lib-dynlink #2. Its two host failures do not imply a guest regression. All 107 symbol-only relocations in the seven retained native artifacts have zero addends; the supported nonzero-field case still requires correction before broader native binding admission.

Original dynlinkd, loaderd and bootloader source candidates, each changing only the library's full commit selector in an isolated exact-commit worktree, pass four strict configurations: 13/105/41 tests respectively, with twelve native builds and private rustdoc, zero warnings. Published consumer commits remain unchanged pending coherent adoption.

The retained Exsh executable and six explicit libraries yield 1,608 independently expected relocation writes under caller-selected hypothetical load biases. Both original and corrected planners match those original zero-addend inputs. All 107 symbol-only writes remain identical under positive, negative and extreme unused-addend variants with the fix; the original planner fails the addend-16 control (actual Cargo exit 101). The original/packaged dynamic tables are byte-identical and all artifact/manifest hashes are retained. This host metadata replay performs no target mapping or execution and does not admit native frame paths.

Signed Docs 214b08666b8b36ad4270bcfee3b3379d8dc08a79 documents the expressions and regenerates only the library's 103-route API reference from exact signed-source rustdoc JSON. All 45 documentation tests, Markdown and canonical checks pass. The full manual has 2,383 pages, 436,424 in-bounds word boxes, zero final warnings and four visually reviewed changed pages. All 3,696 inventoried code/configuration files remain below 1,000 lines; complete semantic authority and private documentation closure remains open.

Matching library CI 30/31 passes with four complete logs (36,856 bytes), 47 tests per run, strict builds/rustdoc and zero warnings. Docs CI 913/914 passes with four complete logs (763,872 bytes), 45 tests and 2,383-page renders, zero final warnings. Coherent catalog adoption, complete native source/frame evidence, runnable realms and both full guest build generations remain open.

Complete file hashes, manifest records, package/feature identities and both needed-name inventories must agree. Library stripping permits only independently checked administrative header selectors, never executable-byte changes.

The retained native closure binds seven objects, 2,373 ordinary functions and 1,608 relocation records. Intake does not yet resolve symbolic providers or compose cross-library frames. All 259 checker controls (28 new) and 16 isolated modules pass; six strict Rust configurations pass 961 tests each, host/native Clippy, private rustdoc and six native builds with zero warnings. Formatting, Markdown and canonical checks pass. All three retained artifact replays preserve their previous frame decisions: 107/70/299 unresolved observations for standalone runtime/all/native. Full frame/source gates retain actual exit 1. Profiling records 0.181 seconds in native dependency intake and 23.17/25.51/24.59 seconds for the three complete profiled runs, within unchanged 60/15-second and 64 MiB budgets. Concurrent Rust validation changes host contention, so elapsed differences from earlier runs are not a speedup or regression claim.

Signed Docs 88537b23e1def210eeff40b7ef90fce92fe2009e documents this contract. All 45 tests and the complete 2,383-page manual pass, with 436,642 in-bounds word boxes, zero final warnings and visual review of the changed page. An initial double-hyphen ligature was corrected and the full render revalidated. The physical census covers 3,704 source/configuration files, all below 1,000 lines; complete semantic authority and private documentation closure remain open. Exact-head Exsh CI 253/254 and Docs CI 915/916 are running. Symbol providers, ordered runtime binding, cross-object frame paths, source membership, coherent catalog adoption, runnable realms and both complete guest builds remain required.

Matching closed dependency intake CI — 16 September 2026: Exsh 253 and 254, exact 9827896d1cb5ad834589045ee03390aec650df84, pass 259 checker controls, 16 isolated imports, 961 Rust tests and the strict preceding build/Clippy/rustdoc stages. All four workspace domains per run and Markdown pass. The required full frame gate remains incomplete, with 111/111/74/74 unresolved observations in each CI artifact set. Four complete logs total 315,052 bytes and contain zero warnings. Original local runtime/all/native replays retain separate input identities and 107/70/299 counts.

Docs 915 and 916, exact 88537b23e1def210eeff40b7ef90fce92fe2009e, pass 45 tests and complete 2,383-page renders. Four complete logs total 763,918 bytes. Reference convergence is 35/1/0 warnings across the three TeX passes, with zero final warnings. Both cohorts are classified without rerunning jobs or changing their budgets. The seven-object native dependency inventory is now checked; symbolic providers, ordered runtime binding, cross-object frames and source membership remain incomplete. No runnable realm, coherent product adoption or complete in-EriX build is established.

S-only relocations ignore addends, while S+A must retain an exact original executable entry.

All 276 checker tests, 17 isolated modules and six strict Rust configurations (961 tests each) pass, including host/native Clippy, rustdoc and six warning-free native builds. Independent original-byte inventory matches all 117 symbolic records: 112 exact function identities and five refused data targets. Provider indexing/reporting takes approximately 16 ms in the captured native profile. Original standalone runtime/all/native replays preserve 107/70/299 unresolved observations and actual exit 1 under unchanged budgets. This is conditional relative identity evidence only: load-base arithmetic, protected slots, cross-object calls/frames and source membership remain incomplete.

Signed Docs 24cefeb2dc6d3f163140d32f5fed5a7e1a768ebd updates the manual contract. All 45 documentation tests pass; the complete 2,383-page render has 436,737 in-bounds word boxes, zero final warnings and visual review of pages 2284–2285. The physical audit covers 3,706 source/configuration files, all below 1,000 lines. No runtime Rust, dependency, linker or workflow inputs changed. New host/CLI controls cover the analyzer behavior; no new guest feature is asserted. Exsh CI 255/256 is terminal: unit/strict/workspace stages pass, and the required full-frame gate remains incomplete. Docs CI 917/918 passes. Acceptance remains 15/459 leaves, 3.48% weighted. Both full in-EriX builds and the complete semantic authority audit remain open.

Ordered-provider automatic CI classification — 17 September 2026: Exsh 255/256 at 469bf1f1b9d8301cf98a79d16c7c27660ecda2a1 passes 961 Rust tests, the combined 276-test checker suite, strict preceding stages and all four workspace domains per run. The required full-frame gate fails with 111/111/74/74 unresolved observations per run. Four complete logs total 315,035 bytes with zero warnings. The 17 separate module executions are local evidence; CI uses combined test discovery.

Docs 917/918 at 24cefeb2dc6d3f163140d32f5fed5a7e1a768ebd passes 45 tests and the complete 2,383-page manual. Four complete logs total 763,878 bytes. Reference-resolution passes produce 35/1/0 warnings; final output has zero warnings and no layout overflow. Original API snapshots remain unchanged. Both cohorts are fully classified, without restarting workflows or changing thresholds. Original Integration layout, quota and FAT32 failures remain open, including #58 in Integration. Acceptance remains 15/459 leaves, 3.48% weighted. Complete native source/frame proof, a runnable realm, the full semantic authority audit and both full in-EriX builds remain required.

Local control-flow offsets cannot alias a foreign function or transfer the root fallback role. Every captured decode shares the original output/time budgets; a late failure rejects the invocation.

All 299 checker tests and 20 separately executed module suites pass. Six strict Rust configurations pass 961 tests each, host/native Clippy, rustdoc and six warning-free native builds; formatting and Markdown checks pass. Original runtime/all replays retain 107/70 unresolved observations. The composed native graph reaches 275 functions with 111 unresolved observations; all three actual checker exits remain 1. Native slots assume successful checked linking and unchanged disjoint mappings. Actual load bases, complete source/frame acceptance and coherent runtime adoption remain open.

Profiling identified redundant root-only analysis in native mode. Removing it preserved every composed decision while one profile changed from 41.52 to 25.81 seconds and 64.37M to 39.61M calls. This host profile pair includes observer overhead and gives no general or guest timing guarantee. The final source replay also preserves every decision; three register-proof records now correctly identify symbolic load provenance.

Signed Docs 44cd6c4aa95bebfa08c99804fab0f1551f537ae1 specifies the contract. All 45 documentation tests pass; the complete 2,383-page manual has 436,894 in-bounds word boxes, zero final warnings and visual review of the changed page. All 3,713 inventoried source/configuration files are below 1,000 lines. The broader documentation audit retains 108 unchanged older test definitions needing inline docstrings; current production and all new/modified definitions are documented. Runtime Rust, dependency, linker and workflow inputs are unchanged; added behavior has host and real CLI regressions, with no new guest runtime feature asserted. Original Exsh CI 257/258 passes unit/strict/workspace stages and retains the required full-frame failure; Docs CI 919/920 passes. Both cohorts are fully classified. Both full builds inside EriX and complete semantic authority acceptance remain open.

Cross-object checkpoint CI classification — 17 September 2026: Exsh 257/258 at ac9646c84e432129a872737789a9be08f984b881 passes 961 Rust tests, the combined 299-test checker suite, strict preceding stages and four workspace domains per run. Combined discovery also checks isolated module imports; the 20 separate module-suite executions are additional local evidence. The required full-frame gate fails with 111/111/74/74 unresolved observations on the four original CI artifact selections. Four complete logs total 315,180 bytes with zero warnings. Those CI selections remain distinct from the retained seven-object native replay.

Docs 919/920 at 44cd6c4aa95bebfa08c99804fab0f1551f537ae1 passes 45 tests and the complete 2,383-page manual. Four complete logs total 763,906 bytes; reference-resolution passes have 35/1/0 warnings, with zero final warnings or layout overflow. Both automatic cohorts are fully classified without workflow restarts or threshold changes. Existing Integration layout, quota and FAT32 regressions remain open. Full native source/frame acceptance, coherent runtime adoption, the semantic authority audit and both full builds inside EriX remain required.

Entry tokens carry equality only; they never supply a pointer or call target. A separate earlier callee contract must prove private stack writes before caller slots survive a call.

All 329 checker tests and 22 separately executed module suites pass. Six strict Rust configurations pass 961 tests each, host/native Clippy, rustdoc and six warning-free native builds; formatting and Markdown checks pass. Independent eager scheduling controls agree with both filtered worklist orders. Original runtime/all/native replays retain 107/70/111 unresolved observations and actual checker exit 1. The native graph still reaches 275 functions. The startup iterator's unknown pointer writes remain a refusal; complete source/frame and runtime acceptance remain open.

Two initial native profiles exhausted the original 60-second budget and produced empty reports; both failures are retained. Immutable decode caches, retirement of exhausted equality state, fact-sensitive wakeups and dependency-first scheduling brought the final native replay within the unchanged budget: 57.45 seconds wall time, 53.94 profiled seconds and 72.27M calls. All 2,373 bodies are inspected once. This bounds one retained host replay and makes no general speedup or guest timing claim. Report schemas and original source, stack, byte and time gates are unchanged.

Signed Docs c3401e5f6bbc19a0ba695219ed551e29a29677ed specifies the contract. All 45 documentation tests pass; the complete 2,383-page manual has 436,968 in-bounds word boxes, zero final warnings and visual review of both changed continuation pages. All 3,717 inventoried source/configuration files are below 1,000 lines. The touched preservation tests now document 21 older methods; 87 unchanged older test definitions remain in the inline documentation audit. Current production and all new/modified definitions are documented. Runtime Rust, dependency, linker and workflow inputs are unchanged; no new guest runtime feature is asserted. Original Exsh CI 259/260 passes unit/strict/workspace stages and retains the required full-frame failure; Docs CI 921/922 passes. Both cohorts are fully classified. Both full builds inside EriX and complete semantic authority acceptance remain open.

Saved-value checkpoint CI classification — 17 September 2026: Exsh 259/260 at 8b6b93a329757ae7f106e235761912b58a67deff passes 961 Rust tests, the combined 329-test checker suite, strict preceding stages and four workspace domains per run. Combined discovery checks isolated module imports; the 22 separate module-suite executions are additional local evidence. The required full-frame gate fails with 111/111/74/74 unresolved observations on its four original CI artifact selections. Four complete logs total 315,234 bytes with zero warnings. These CI selections remain distinct from the retained seven-object native replay.

Docs 921/922 at c3401e5f6bbc19a0ba695219ed551e29a29677ed passes 45 tests and the complete 2,383-page manual. Four complete logs total 763,958 bytes; reference-resolution passes have 35/1/0 warnings, with zero final warnings or layout overflow. Both automatic cohorts are fully classified without workflow restarts or threshold changes. Existing Integration layout, quota and FAT32 regressions remain open. Full native source/frame acceptance, coherent runtime adoption, the semantic authority audit and both full builds inside EriX remain required.

Scoped masks never enter the unconditional function index; loaded words, unknown contents, released storage and recursive assumptions supply no binding.

All 355 checker tests and 23 separately executed module suites pass. Six strict Rust configurations pass 961 tests each, host/native Clippy, private rustdoc and six warning-free native builds. Formatting, templates and Markdown pass. Original runtime/all/native replays retain 97/60/97 unresolved observations and actual exit 1. The native graph reaches 275 functions; the startup iterator now has caller-bound preservation for its exact live buffers. Complete source/frame and runtime acceptance remain open.

Profiling exposed repeated failed argument specializations. Mandatory opaque-prefix refusals, conservative GP demand and rejection-only control candidates avoid unnecessary interpretations without changing the original 60-second limit. Candidate records cannot become proofs, and incompatible fact kinds defer to actual interpretation: losing pointer identity can enable numeric refinement. Positive and negative controls compare filtered and eager behavior. Each CFG site has at most one pending visit and later changes still enqueue it without an iteration cap; every native proof decision agrees with the prior queue.

The final ordinary native replay takes 39.80 seconds. Complete tracing still exhausted the original deadline; failures and empty reports are retained. A separately identified selective profile measures only caller-context analysis: the complete invocation takes 56.59 seconds, with 26.92 profiled seconds in that scope. Instrumentation preserves the complete proof result. Different profiling scopes are not timing comparisons, and no guest performance claim is made. The replay selects 367 instances, evaluates 587 bodies, proves 190 and defers 51 candidate bodies for incompatible domains.

Signed Docs fc3ee44748c20a3aa6f55bd85ac1913c707e5d4e specifies these contracts. All 45 documentation tests pass. The complete 2,385-page manual has 437,275 in-bounds word boxes, zero final warnings and visual review of the changed pages. All 3,721 inventoried source/configuration files are below 1,000 lines. All new/modified definitions are documented; 87 unchanged older test definitions remain in the audit. Runtime Rust, dependencies, linker and workflow inputs are unchanged. Original Exsh CI 261/262 passes unit/strict/workspace stages and retains the required full-frame failure; Docs CI 923/924 passes. Both cohorts are fully classified. Complete semantic authority acceptance, coherent runtime adoption and both full builds inside EriX remain required.

Caller-bound checkpoint CI classification — 17 September 2026: Exsh 261/262 at e7ba974e96ee77a41c6a861150da843d4c84c7d6 passes 961 Rust tests, the combined 355-test checker suite, strict preceding stages and four workspace domains per run. Combined discovery checks isolated module imports; the 23 separate module-suite executions are additional local evidence. The required full-frame gate fails with 101/101/64/64 unresolved observations on its four original CI artifact selections. Four complete logs total 315,210 bytes with zero warnings. These CI selections remain distinct from the retained seven-object native replay.

Docs 923/924 at fc3ee44748c20a3aa6f55bd85ac1913c707e5d4e passes 45 tests and the complete 2,385-page manual. Four complete logs total 764,350 bytes; reference-resolution passes have 35/1/0 warnings, with zero final warnings or layout overflow. Both automatic cohorts are fully classified without workflow restarts or threshold changes. Existing Integration layout, quota and FAT32 regressions remain open. Full native source/frame acceptance, coherent runtime adoption, the semantic authority audit and both full builds inside EriX remain required.

Removed selector 0x70 remains explicitly rejected; runtime ABI and generated API snapshots are unchanged.

All 45 documentation tests, Markdown and template checks pass. The complete 2,385-page manual has 437,463 in-bounds word boxes, no final warnings, and visual review of pages 142 and 163. Rust and VM checks are inapplicable to these two prose-only changes. Original automatic CI 927 and CI 928 both pass. All four complete terminal logs total 764,750 bytes; reference passes resolve with 36/1/0 warnings and the final manual is warning-free. Issue 9 is repaired and closed. No full self-hosting acceptance is claimed.

All 45 documentation tests and Markdown/template checks pass. The complete 2,387-page manual has 437,732 in-bounds word boxes and no final warnings; pages 146, 166, 168 and 169 were visually reviewed. Runtime tests are inapplicable to this documentation-only change. Original CI 929 and CI 930 both pass. All four complete terminal logs are classified; both full 2,387-page manual builds have zero final warnings. Issue 10 is closed for the corrected documentation drift. No complete guest build is established.

Both complete guest builds and dependent runtime/source proof remain open.

Borrowed syscall capture reference — 17 September 2026: signed 2435bf5ed105fbe2af0349088b2ae600d4b598fd
documents the complete entry prefix and refusal before operation dispatch. This documentation checkpoint
does not imply runtime or complete guest-build acceptance.

Runtime and full
guest-build acceptance remain separate.

Complete compiler-source admission, ordinary runtime adoption and both full guest builds remain open.

Complete compiler-source admission, ordinary runtime adoption and both full guest builds remain open.

Typed mediator bootstrap, ordinary service-image adoption and both complete EriX builds inside EriX remain open.

Complete builds inside EriX
and ordinary service-image adoption remain open.

Corrected original manual CI — 18 September 2026: Docs 10ea454ebab2cb0ca465cedf52ff619c1fc7efd4 passes original CI 947 and CI 948. All four logs are complete (765,634 bytes), all 45 tests pass, and the complete 2,389-page manual has zero final warnings after reference passes of 36/1/0 warnings. The later generation-bound cleanup manual update is still under local validation.

Generation-bound cleanup consumer acceptance — 18 September 2026: Signed revision 323da983653e6d6d25d012c2354f97afaaaa0699 is pushed. Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain open.

Original cleanup manual CI acceptance — 18 September 2026: Signed Docs 323da983653e6d6d25d012c2354f97afaaaa0699 passes CI 949 and CI 950. This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements.

Returned-grant bootstrap custody design — 18 September 2026: Add distinct Procd PREPARE_REALM_BOOTSTRAP (0x432) on the existing
private Launchd route. The native pending caller must match a retained running
Launchd generation. Its exact 32-byte request carries u32 request ID, opcode,
original process/generation, source and original destination install-grant slots,
then two zero words. The actual sole receipt must be INSTALL_GRANT with exactly
GRANT|MINT. Slots are full-width descriptions; receipt, live inventory and native
matching-grant checks establish custody. Previously guarded, started, stale,
ordinary-role and malformed stages refuse before new effects.

Reserve exact rollback ownership first. Use the real returned grant and native
operation 53 to narrow the Created child's primary endpoint to RECV. Establish
an ancestor SEND branch under Kernel lifetime custody and a distinct nested
explicit revoker before any export. Retain the nested sender privately; dispose
the original master, unguarded sender and ancestor-only bypass aliases. The
returned install grant stays exclusively owned for later typed installation.
No new endpoint factory or expanded Process endpoint policy is implied.

The exact 32-byte capability-free reply echoes request/opcode/result/process/
generation, followed by a u32 custody state and two zero words. State 1 occurs
exactly with OK and confirms only guarded unstarted-stage custody; failure state
0 is not absence proof. Lost reply, rollback, abort, supervisor loss and terminal
cleanup must account for every reused scratch column, actual guard and exact
child identity. Uncertain disposal prevents reuse and ordinary continuation.

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

Runtime realm orchestration, actual consumer VM execution, fair progress and both complete builds inside EriX remain open requirements.

Runtime consumer VM, complete realm fairness and full guest-build acceptance remain open.

Caller-local grant relocation design — 18 September 2026: Add immediate x86_64 syscall 0x54, RELOCATE_LOCAL_GRANT, taking source slot in argument 0 and destination slot in argument 1. Both fit u32, are nonzero and distinct; arguments 2–5 are zero. The return is the exact result in rax with zero auxiliary value. Admission uses the actual current Running native process and nonzero generation, checks both slots against its syscall window, and accepts only an actual held INSTALL_GRANT or REVOCATION_GRANT with its matching native record. Movement uses the existing unique-record rebinding within that same native CSpace; rights, child/generation installation scope and revocation lineage are preserved. No grant is constructed, copied, attenuated or retargeted. Malformed register shape rejects before context lookup; caller/window checks precede source lookup, then type/binding checks precede empty-destination admission. Ordinary validation refusal leaves inventory unchanged. The transition is serialized with process-terminal and reply-authority lifecycle changes. Owned CLAIM already selects receiving destinations before exposing request bytes; this operation lets a producer validate the received grant and then relocate it into an existing per-process custody slot. The operation itself does not validate a bootstrap request, install child authority or acknowledge application retirement. It adds no Process endpoint selector or general CNode route. Literal register, foreign/terminal caller, missing/fake binding, occupied destination, exact-rights/scope and actual CPL3 controls are required, followed by coordinated producer/consumer adoption and the remaining realm VM gates.

Original deferred-cleanup manual CI acceptance — 18 September 2026: Signed Docs da66c0efd61fc05be023210e1c0c58196b51b878 passes CI 953 and CI 954. This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements.

Actual owned service adoption, consumer VMs, complete realm fairness and both full builds inside EriX remain open.

Owned receiver request-budget contract — 18 September 2026: Extend register-only REGISTER (0x4C) to take the actual local RECV slot, maximum request payload bytes and maximum request capability count in arguments 0–2; arguments 3–5 remain zero and successful RDX is zero. Both budget values are explicit receiver declarations. Zero/zero admits only empty requests. The byte/slot/receipt receive layout must be addressable and capability capacity must fit native private CSpace storage. The actual Running generation and held generic RECV endpoint remain the registration authority. Exact repeated registration is idempotent only with the same budget; a different budget or owner conflicts without modifying the original registration. Replacement follows the existing actual receiver-binding removal and exact native retirement rules. SUBMIT compares actual payload length and capability count against that exact registration before request allocation, private-space reservation, native transfer or invocation serial acceptance. Oversized requests return ordinary INVALID_ARGUMENT with zero owner ID and unchanged source custody. The packet decoder passes its checked capability iterator directly to native preparation, removing its redundant temporary vector. Accepted invocation, result-budget, delivery, draining and retirement contracts remain explicit. Migrate every producer and fixture to the new signature without a deprecated unbounded fallback. These budgets describe service-owned receiving storage; they add no global CALL-size ceiling, user-pointer retention, foreign selector or capability grant. Literal malformed/zero/exact registration controls, rejected-inventory checks, actual CPL3 calls and existing VM oracles are required. Then connect the owned Procd/Launchd bootstrap path through its held private route, actual claimed caller identity, server-chosen grant receipt and local relocation, retaining each committed/draining owner through exhaustive cleanup. Actual consumer VMs, complete fair realm progress and both full guest builds remain open acceptance requirements.

Original local grant relocation manual CI acceptance — 18 September 2026: Signed Docs 623609ee627a4afba1340ee06c53678c4a562a88 passes CI 955 and CI 956. This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements.

Explicit owned receiver admission acceptance — 18 September 2026: Signed 8361618f3f047479a9e52ffaba7f2607be99413c. The manual documents explicit receiver request limits, complete layout addressability, immutable registration and pre-custody refusal, with accurate allocation-observation scope. Actual owned Procd/Launchd service adoption, consumer VM execution, complete realm fairness/readiness/sealing and both full builds inside EriX remain open.

Owned guarded-bootstrap service contract — 18 September 2026: Migrate PREPARE_REALM_BOOTSTRAP to native owned request/result custody on the already held private Launchd-to-Procd endpoint. Its exact 16-byte body contains request/opcode/process/generation only; remove obsolete source and destination slot descriptions. The canonical capability-free response remains 32 bytes. No legacy bootstrap transport fallback is retained.

Procd registers explicit 16-byte/one-capability request limits, supplies an actually empty local receiving slot, validates the committed receipt type and rights and matches the native claimed origin to the retained Running Launchd generation. It validates the exact staged mediator row and actual grant scope before adopting the grant into that row through caller-local relocation. Existing launch-description staging may be reused only with explicit exclusive ownership and proved completion of its former cleanup; add no broad Process authority or per-realm scratch column. Numeric identity or receipt metadata never replaces actual possession or scope validation.

The running service loop must give native retirement a turn before owned bootstrap and ordinary intake. Retain nonzero delivery/invocation owners, received authority, exact child rollback and first cleanup failure through committed/draining outcomes. Complete every independent local and child retirement action before relinquishing bookkeeping; uncertain cleanup cannot return a service to ordinary work. Authenticate actual native origin and revalidate the original supervisor before effects; do not manufacture legacy pending-caller or source-slot receipts.

Replace Launchd synchronous bootstrap exchange with retained progress driven by its actual runtime orchestration. Success requires a canonical correlated result, actual source-grant absence and complete invocation retirement. Connect this to authenticated staged realm preparation, with no public numeric shortcut into a prepared process. Preserve ordinary start refusal until realm configuration, readiness and sealing are complete.

Acceptance requires adversarial ownership/cancellation/partial-cleanup host controls, strict coordinated builds and real producer/consumer VM execution. Native primitives alone do not establish service adoption, complete fairness or a full guest build. Existing ordinary source/effect/frame and two complete EriX-in-EriX build gates remain unchanged.

Original receiver admission manual CI acceptance — 18 September 2026: Signed Docs 8361618f3f047479a9e52ffaba7f2607be99413c passes CI 957 and CI 958. This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements.

Actual Launchd runtime orchestration, consumer VM execution and both complete guest builds remain open.

Original owned bootstrap manual CI acceptance — 18 September 2026: Signed Docs 5c1cf6da319787738fa03f3cc6f526e49604aa09 passes CI 959 and CI 960. This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements.

Original realm supervisor and producer cancellation contract — 18 September 2026: Extend BEGIN_MATERIALIZATION to an exact 64-byte body. Its existing 56-byte semantic image description is followed by two full-width u32 fields: original supervisor process ID and generation. Both are nonzero only for the realm mediator role; both must be zero for every other role. Reject the obsolete 56-byte shape. Coordinate the shared codec, Loaderd and Procd through one original pinned dependency graph.

On PREPARE_REALM, Loaderd obtains the supervisor pair from the actual native pending caller on its private Launchd receiver. Procd authenticates the actual Loaderd caller on its materialization receiver and matches the forwarded supervisor to its retained Running Launchd generation before any child effect. The pair describes delegated lifecycle responsibility; numbers alone never confer creation, installation or rollback authority. Retain that original owner before materialization and through grant handoff, native submit/claim and guarded staging. Supervisor terminality retires active preparation and every corresponding stage before unrelated provider cleanup. Guard admission must match the original supervisor, never replace it with a later claimant.

Launchd retains child rollback and native invocation ownership separately. Caller RELEASE initiates cancellation and must precede any ordinary abort request that could wait behind Procd delivery retirement. RELEASE is not an application rollback acknowledgment: preserve the exact child obligation until its separate cleanup proof. Procd exhausts independent local and child cleanup before server RELINQUISH. Both parties retain nonzero native IDs and the first cleanup failure through draining; no uncertain state returns to ordinary work.

Actual Launchd runtime preparation and scheduler adoption, deployment-sized ownership storage, adversarial host controls and real producer/consumer VM execution remain required. Guarded staging does not authorize ordinary start or establish configuration, readiness, sealing, complete fairness or either full EriX build inside EriX. Existing source, effect and frame gates remain.

Actual Launchd owned runtime adoption, consumer VM execution and both full guest builds remain open.

Original supervisor manual CI acceptance — 18 September 2026: Signed Docs a410759e5515b18107f25efb0319ad7c85871a64 passes CI 961 and CI 962. This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements.

Caller-bound realm admission and retained storage contract — 18 September 2026

Use distinct Launchd operations BEGIN_REALM 0x6D0, PREPARE_REALM 0x6D1,
ABORT_REALM 0x6D2 and READ_REALM 0x6D3. The existing 0x6B0–0x6BF range belongs
to filesystem providers and is not reused. Little-endian bodies are exact, with
nonzero request correlation and no fallback to ordinary launch transactions.

BEGIN_REALM is an authority-free 8-byte request (request ID, operation). Derive
session, authority realm, original process/generation and Running job from the
actual native pending caller. Reserve an independently budgeted realm record,
a nonwrapping generation and one disjoint executable-scope receipt slot before
replying. Client numeric identities or a bearer sender cannot select ownership.

PREPARE_REALM has a 32-byte prefix: request ID and operation (u32), realm record
ID and generation (u64 each), and selector byte length (u64), followed by exactly
that nonempty UTF-8 selector without NUL. Parsing adds no pathname or packet-size
ceiling. The request carries exactly one actual SEND-only directory endpoint to
the reserved receipt slot. Verify the original caller/job/session/authority realm
again and retire every unretained received capability on refusal. Resolve only
inside this explicit directory, authenticate the exact executable and manifest,
and call Loaderd's existing private PREPARE_REALM. Never imply a Posixd pathname,
Named route, root, cwd, TTY stream, ordinary job or public PreparedProcess input.

ABORT_REALM and READ_REALM are authority-free 24-byte requests: request ID,
operation and complete realm-record ID/generation. They require the same original
Running native owner. READ observes retained state only; ABORT must complete
independent source, invocation and exact-child retirement before its successful
acknowledgment. Parent terminality initiates the same retained cleanup internally.

All four operations have an exact 40-byte capability-free response: request ID,
operation, raw result and state (u32 each), record ID and generation (u64 each),
receipt slot and zero reserved word (u32 each). States are Unconfirmed=0,
Reserved=1, Preparing=2, Guarded=3, Retiring=4 and Retired=5. Success at BEGIN
requires Reserved, a nonzero complete handle and receipt slot. PREPARE success
requires Guarded; ABORT success requires Retired. READ returns an authenticated
nonzero state. Only successful BEGIN returns a receipt slot; every other result
has zero there. Failure always has Unconfirmed state; failed BEGIN has a zero
handle while other failures echo the original complete request handle. Unknown
nonzero result codes remain full-width. Unconfirmed proves no resource absence.
Correlate the complete response with the original request before using evidence.

Replace obsolete LCH1 v2 with exact 72-byte version3 startup policy. Preserve the
first 68-byte field order and append realm_capacity (u32 at offset68). Require an
explicit deployment value: zero disables new realm reservations, and nonzero
values allocate that many retained records and disjoint receipt slots. Validate
checked job-route + stream-route + realm-receipt arithmetic before leaving any
ordinary transaction receipt storage. No default or incidental fixed array sets
realm count. Coordinate shared startup codecs, Rootd payloads, Launchd arena and
Integration policy/packaging; old version/width must reject. Extend the native
capacity descriptor with the realm record's size/alignment and a new layout
version; do not assume ordinary reply records survive long enough for realms.

Keep original child, local scope/grant obligations and native invocation owners
independent. Actual scheduler progress must exclude ordinary and indirect blocking
peer calls while any native invocation needs progress. A permanently discharged
source slot is never revisited after reuse. Native release precedes ordinary
exact-child abort; preserve first errors and exhaust independent cleanup without
returning uncertain state to normal operation. Guarded staging remains private
and unstarted, without exported SEND or a Running job. This initial admission
interface does not define configuration, readiness, sealing or publication.

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

Original retained caller manual CI acceptance — 18 September 2026: Signed Docs 4dcbc10e32ebf257139bcbaf07bc1081b9589780 passes CI 963 and CI 964. This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements.

Actual runtime admission, coherent image consumers, mediated client I/O and both full guest builds remain open.

Original realm admission manual CI acceptance — 18 September 2026: Signed Docs 9868cf0e6f2c366b4a2c7992594a83c72789f1f0 passes CI 965 and CI 966. This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements.

Complete mediated execution and both full builds inside EriX remain required.

Original exact preparation manual CI acceptance — 18 September 2026: Signed Docs 880bdc59818b1eff9cf9929004680f354f8265a0 passes CI 967 and CI 968. This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements.

The manual describes public realm intake, independently held replies, original-parent cleanup and fair native progress before ordinary dispatch, while preserving separate consumer VM and guest-build acceptance.

Original public realm dispatch manual CI acceptance — 18 September 2026: Signed Docs 099f0c570414ca486bb2104c1510fbf3b84d59fb passes CI 969 and CI 970. This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements.

Coherent catalog adoption and actual consumer VMs remain required before image acceptance; no runnable realm or full guest build is claimed.

Original coherent realm source CI acceptance — 18 September 2026: Signed 33733ceba228669e27152aee32f997d6c72264ff passes CI 972 and CI 971. Coherent catalog publication, actual consumer VMs and full guest-build acceptance remain separate open requirements.

Native external-toolchain rebuild requirement — 19 September 2026: Signed b54d28e755dd415079100a19683ee1474edb4ed1 makes the native rebuild an explicit Phase 6 verification and acceptance gate. The first compiler may be cross-built for EriX against its libc/sysroot, Rust OS bindings and declared C/C++ runtime closure. The extended development image must then rebuild the selected upstream Rust/LLVM toolchain inside EriX using supplied offline recipes and an explicit bootstrap compiler. Require working guest-built tools and use in at least one full EriX build, with no unrecorded porting changes, downloads, Linux executables or host build delegation. Complete source, runtime, log and measured-resource evidence is required; compiler ownership remains distinct. All 45 documentation tests and the full 2,419-page manual pass, with 445,775 in-bounds word boxes, actual visual review of the changed page and zero final warnings. Shared API snapshots are unchanged. The phase master, toolchain issue and full-build issue contain the matching requirements. Original documentation CI is under observation; the native toolchain rebuild and both OS builds remain unproven.

Tracking and rollout

Local prerequisite acceptance — 29 September 2026: the receipt-preservation correction is complete in signed Integration d68a95870076c3435b1a5ab36440d0941b5ab45e, with matching producer adoption in Lib-cstd a76f6faa1eabe30d9a596d9e9650236ca6463d8c and Integration e4ffe2efcf4f06386ffc72d227c4d9c9646e86d1.

The caller-loss manual contract is signed and pushed as Docs e94d7c56dde026b407f85b75c9a2664b5f7756bf. All 45 documentation controls and the complete 2,657-page manual pass with zero final warnings. All 492,046 rendered word bounds pass; the changed contract and neighboring pages were visually checked. The helper's native behavior and whole lifecycle requirement remain pending. Remaining local Rust checks will run with compiler work serialized after a retained progress-deadline failure. No CI monitoring is being performed.

Caller-loss startup boundary — 29 September 2026: source audit found that the draft helper could not use the ordinary Exsh manifest as planned. Launchd derives fixed routes from the authenticated manifest: the ordinary entry supplies a redirection resolver even if the request omits its destination, and does not declare inherited launch. Host transport tests alone did not establish the helper's actual startup authority. The earlier full validation attempt was explicitly cancelled with owned-child cleanup before changing its frozen source; it is not native acceptance.

The implementation now packages a distinct /bin/realm-owner-loss-caller entry backed by the same Exsh artifact. Its manifest declares only cwd and inherited launch, with zero authority rows and no resolver or observation broker. The original Exsh graph root and ordinary startup inventory remain intact. In the selected diagnostic image, immutable LCS1 command-entry evidence selects the reduced inventory; argv cannot select it. Exact helper commands are required, with no environment or extra description records. Every architectural capability slot is checked, including absence of excess authority. The existing status-only parent wait and original VM gates are preserved.

Four focused startup controls, eight actual transport controls, strict native all-feature Clippy, five graph/manifest/installer controls, seven existing generic-manifest controls and six scenario controls pass. Installer controls exercise the actual validation and generated alias/sidecar commands; they do not claim an ext4 mount or native execution. The updated manual passes 45 controls; its complete render remains pending. A corrected full Exsh matrix is running. Coordinated signed source adoption, full Integration validation, native execution and original CI are still required. No lifecycle checkbox or completion credit is added.

Matched native performance evidence — 28 September 2026: both original startup captures pass the unchanged 120/45-second gates without warnings. The matched old/new Kernel comparison uses identical tools, firmware, normalized VM configuration and all 66 other runtime ELF/shared-object artifacts. Translated-instruction upper bounds fall from 38,281,446,500 to 37,372,677,139 (2.37%); the reported mapping-batch candidate groups fall from 11,178,003,410 to 10,355,082,032 (7.36%). These bounded counters indicate less work, not completed-instruction counts or an elapsed-time speedup: the instrumented runs take 55.36 and 55.75 seconds respectively. The rejected earlier comparison remains retained because its producer graph differed.

This completes the borrowed-mapping dependency's matched performance validation and the fourteen-snapshot numerical nonexecution witness already recorded here. Signed roadmap-only updates (kernel 1363f0c5, docs d72f0a57, integration 324cc4da, lib-cstd 50b9d289) record the results; selected runtime, helper, catalog and manual source bytes are unchanged and retain their exact prior evidence. Fresh documentation/policy/diff and applicable formatting checks pass. New original CI is registered independently. Whole lifecycle acceptance remains open through supervisor-loss and remaining partial-cleanup/exhaustion checks; complete guest EriX and external Rust/LLVM rebuilds remain required and unproved. No new checklist credit is claimed.

Docs original CI1103/1104 fails, with one fully validated manual job and three failed job logs returning HTTP 500. Docs bug 11 records exact jobs and unknown cause. Kernel CI706/707 and Lib-cstd CI13/14 pass; original Integration runs remain monitored. Integration receipt bug 99 has coordinated host/native evidence but remains open pending original CI. No unchanged failing CI was rerun for acceptance.

Prioritize completing each checklist item fully in one sustained pass: implementation, security/reliability audit, required validation, documentation, signed publication and complete CI review before unrelated work. Keep genuine blockers explicit and do not substitute intermediate checkpoints for full acceptance. The active remaining realm-lifecycle item includes positive numerical NeverExecuted accounting, abort/retire and partial-cleanup paths, supervisor loss and resource-ceiling validation. Already accepted native disposal/reuse and pool refusals remain prerequisites. Unrelated optimizations and regressions stay tracked unless evidence makes them dependencies. This execution priority does not change the phase scope, original gates or completion arithmetic.

Exact Launchd 2-realm/4-client/576-byte, Procd 38-record and Pagerd 102-binding budgets require reclamation. All six actual successful client exits, realm/client/plan refusals and original capability routes remain intact.

The client VM and older preparation/startup VMs pass every original marker, exit and 120/45-second gate. Retained client evidence binds 109 artifacts, 57,045 serial bytes, empty QEMU stderr and zero warnings. This accepts the native disposal/reuse sub-item. Separate positive NeverExecuted CPU accounting remains required: the first capture was rejected before boot because the host GDB package changed; after RPM identity/API verification and fresh two-positive/twenty-negative verifier controls, a separate capture reached the original 120-second limit after five Measured commits, before either NeverExecuted snapshot. Its failed result and cleanup are retained. No deadline, guest byte, authority or oracle was weakened; no numeric completion or speedup is claimed.

All fourteen Exsh development/release selections pass 988 tests each, strict host/native builds, Clippy, rustdoc and 355 checker controls pass without warnings, while native frame proof issue 4 stays open. Docs CI1099/1100 passes 45 document controls and the complete 2,657-page manual with zero final warnings. Integration passes its 187 host commands. Original CI1824 passes all 492 scenarios and subsequent image/input gates. CI1823 instead stops in the known physical utility host fixture, before catalog VMs. The companion pass does not resolve that intermittent failure.

All 22 original Integration runs 1803–1824 now have complete reviewed logs: 66 logs, 264,989,379 bytes, zero warning candidates. The smoke-policy defect is closed on its source correction and matching full-CI evidence. Remaining observations are retained under pipeline, ext4 quota, physical consent, interrupt reuse, canonical release, and the new canonical-template reports for release COM1 editor and canonical development. Their causes are not inferred from wrapper failures, and no unchanged CI job was rerun.

The phase checklist now records 419/879 completed sub-items, 17/460 accepted parents, and 15.45% weighted progress. Numerical NeverExecuted accounting, remaining authority/lifecycle cleanup, complete CI/frame acceptance, external Rust/LLVM/toolchain rebuilding and both complete EriX builds inside EriX remain required and unproved.

Both stale-client generations must remain absent. All six actual successful client exits, realm/client/plan capacity refusals, original capability routes and the 120/45-second guest gates remain mandatory. Independent native accounting must positively capture two zero-CPU NeverExecuted clients, six Measured clients and six Measured mediators. Local cancellation or absence cannot substitute for those records.

The preceding shell fails at call 88 in the independent 141-call transcript; all eight focused controls pass on the new source. All fourteen ordinary development/release selections pass 988 tests each under unchanged limits, with strict host/native builds, Clippy, doctests, private rustdoc and 355 frame-checker controls passing without warnings. All six separate local optimized frame observations produce incomplete reports and retain exit 1: runtime 271/97, all-features 298/63 and configured clients 323/100 reached/unresolved in both deployment profiles. These are not accepted frame proofs.

Original Exsh CI 291 and 292 each pass 988 unit tests and 355 checker controls, then fail the still-open native frame proof. Their own artifacts report runtime 256/101 and all-features 288/68 in both profiles. All four complete logs, totaling 323,674 bytes, are reviewed with zero warnings and no additional compiler or test failure. Native frame counts belong to their exact build configurations; different observations are not combined into a proof or speedup claim.

All 45 document controls, Markdown/template/link/reference checks, the complete 2,657-page manual and all 491,759 word bounds pass; three affected/adjacent pages are visually reviewed. Original Docs CI 1099 and 1100 pass, with all four complete logs reviewed and zero final warnings. Integration passes all 187 host commands: 174 helper controls, six profiler commands, strict orchestration Clippy, both unit selections, formatting, dependency policy, Markdown and diff checks. All 76 original source signatures and transitive dependency closure pass. The fresh structural audit finds all 3,196 code files below 1,000 lines and missing_docs gates at all 98 detected crate roots; this does not replace semantic authority review.

Original Integration CI 1823 and 1824 are queued. The isolated coordinated image build and configured-client VM are running. Its native result, older preparation/startup regressions and the separate positive NeverExecuted accounting capture remain pending. The observer's two positive host transcripts and twenty negative cases establish verifier behavior only. No new checklist acceptance or progress credit is claimed. Remaining authority/lifecycle work, full CI, native frame proofs, external Rust/LLVM/toolchain rebuilding and both complete EriX builds inside EriX remain required.

Native nonexecution contract checkpoint — 25 September 2026: signed Docs 47e68b07 specifies retirement of two fully provisioned clients before either START, followed by another generation of record reuse while the original peer stays sealed. Six actual successful client exits, capacity refusals, exact budgets and the existing 120/45-second VM gates remain mandatory. Independent native accounting must positively capture two zero-CPU NeverExecuted clients, six Measured clients and six Measured mediators, with original successful commits and final protected backing. Local cancellation or absence cannot substitute for that evidence.

All 45 document controls and Markdown/template/link/reference checks pass. The complete 2,657-page manual builds without final warnings; all 491,759 word bounds pass and three affected/adjacent pages are visually reviewed. Original CI 1099 and CI 1100 are running. The local shell extension passes eight controls across an independent 141-call transcript; the preceding probe fails at the missing retirement operation. The host accounting observer passes two positive transcripts and twenty negative cases. Complete shell validation is running; signed shell publication, catalog adoption, native execution and native accounting remain pending. No checklist acceptance or additional progress credit is claimed. The distinct compiler regression is resolved in Exsh issue 9; native frame proof, remaining authority/lifecycle work, external toolchain rebuilding and both complete EriX builds inside EriX remain required.

Documentation status now records the accepted native client/plan ceilings in signed Docs a1444c6b. Only ROADMAP changes; 45 fresh document tests, Markdown/template and dependency checks pass without warnings. Manual, tooling and reference bytes retain the earlier fully validated identity. No new manual build is claimed.

Valid counts independently exhaust each free pool, require exact RESOURCE_EXHAUSTED and unchanged Guarded/Sealed peers, then allow normal configuration.

The client VM and older preparation/startup VMs pass with every original marker, native exit and 120/45-second gate. Retained client evidence contains 109 artifacts and 57,045 serial bytes, with empty QEMU stderr and zero image warnings. Independent BootConfig decoding verifies 2 realm records, 4 client records and 576 plan bytes; packaged Procd/Pagerd layouts retain 38 records and 102 bindings. Requests add no capability or guest inspection route.

The phase checklist now has 417/877 completed sub-items, 17/460 accepted parents and 15.43% weighted progress after exact recalculation. This accepts the two configuration-storage ceilings. Existing compiler/frame gates, supervisor loss, partial cleanup, NeverExecuted accounting, complete CI review, external Rust/LLVM/toolchain rebuilding and both full EriX builds inside EriX remain required. All earlier failures are retained, and no unchanged CI job was rerun.

Original CI1799 and CI1800 are fully reviewed: 372/492 and 371/492 scenarios pass, with six complete logs and zero warning candidates. Both retain 119 obsolete policy refusals and the known configuration-carrier stall on their older graph. The pipeline descriptor scenario passes in 1799 and fails in 1800 on the same source graph, reproducing open Integration issue 91. Its cause remains unproved; a companion pass does not resolve it.

Exact RESOURCE_EXHAUSTED replies must preserve the original Guarded mediator and Sealed peer, then allow normal configuration. Requests transfer no capabilities; every existing byte-I/O, actual exit, retirement and reuse gate remains required.

The preceding probe fails at call 22 in an independent 111-call transcript. Eight focused controls and seven development selections of 988 tests pass. Fourteen strict host/native build, Clippy and rustdoc configurations and 355 frame controls pass without warnings. Seven release compilations retain their output-silence failure. Four native frame reports are incomplete; two further runs exit 1 without reports near the checker's 60-second bound. Those observations overlapped the host matrix; the outer owner did not time out. Original Exsh CI287/288 passes 988 unit tests and 355 checker controls, then emits all four incomplete reports per run: runtime 256 reached/101 unresolved and all-feature 287/68. All four complete logs are reviewed with zero warnings. None accepts the compiler or frame gates tracked in Exsh issue 9 and issue 4.

A separate built-in timing diagnostic completes in 250.623833 seconds without warnings and its exact executable passes 507 optimized library tests. Rust reports 115.623711 seconds in LLVM optimization and 108.817139 seconds in fat LTO. The complete LLVM trace attributes 76.09% of inclusive function-pass time and 65.88% of machine-function optimization time to Parser specializations, with 166 run specializations before LTO and 158 in the machine-function trace. These classes are nested and not additive. Instrumented library-only timings identify a refactoring candidate; they do not establish an ordinary-build speedup or accept the release gate. The exact installed compiler uses explicitly selected diagnostic switches only; maintained configuration is unchanged.

All 187 Integration host commands, 76 original signatures and complete catalog closure pass without warnings. The full 2,657-page manual and all 45 document tests pass; all 491,619 word bounds and three viewed pages pass with no final warnings. Original Docs CI1095/1096 also passes; all four complete logs are reviewed through the final warning-free TeX pass. Fresh native execution with the original markers and 120/45-second limits remains required. This checkpoint adds no checklist credit. Supervisor loss, partial cleanup, NeverExecuted observation, complete CI review, external toolchain rebuilding and both full EriX builds inside EriX remain open in the phase tracker.

Native full-table realm refusal accepted — 25 September 2026: signed Integration bdd04a62 runs the new Exsh bc5cc8ac probe. The added requests transfer no capability and use the original authenticated Launchd route.

All original client markers, native exit and 120/45-second limits pass. The 109 retained artifacts include 57,045 serial bytes and empty QEMU stderr, with zero image warnings. Independent BootConfig decoding follows the actual Launchd filesystem role to its 2-realm/4-client/576-plan-byte policy; packaged Procd and Pagerd layouts retain 38 records and 102 bindings. The original preparation-only and startup VMs also pass, with 108 retained artifacts each, 56,131/56,165 serial bytes and zero warnings. No guest inspection endpoint, grant or deadline change is introduced.

All 187 Integration host commands, seven 987-test Exsh development selections, fourteen strict host/native build/Clippy/rustdoc configurations and 355 checker controls pass. Docs CI1091/1092 passes the complete manual and 45 tests without final warnings. Exsh CI283/284 passes 987 unit tests and 355 checker controls, then fails the existing native frame proof: runtime 256 reached/101 unresolved and all-feature 286/68 in both profiles. All four complete logs contain zero warning candidates. Seven local release unit compilations and the native frame gaps remain open under compiler issue 9 and frame issue 4.

Documentation status is signed and pushed as Exsh 232e6849, Docs e2131e57, Integration c5958f12. Only ROADMAP changes in those follow-ups; code, catalog, helper and manual inputs retain their original validation identity. The phase tracker now records 416/876 completed sub-items, 17/460 whole parents, and 15.43% weighted progress after recalculation. This accepts the realm-record ceiling only. Client/plan exhaustion, supervisor loss, partial cleanup, NeverExecuted accounting, complete original CI review, external toolchain rebuilding and both full EriX builds inside EriX remain required.

Realm-capacity witness checkpoint — 25 September 2026: signed Exsh bc5cc8ac requires a third BEGIN to return canonical RESOURCE_EXHAUSTED while both selected realm records are occupied. The reply must be Unconfirmed with zero identity and receiver fields, and both original generations must still read as sealed. Every original byte-I/O, native exit, independent retirement, stale-selector and record-reuse check remains required. The three additional requests use the existing Launchd route and transfer no capability. The independent 99-call transcript rejects the preceding probe at its missing request; seven focused controls cover exact refusal, malformed replies, transport loss and unwanted receipts.

Seven development selections pass 987 tests each. All fourteen host/native build, strict Clippy and private-rustdoc configurations and 355 frame-checker controls pass without warnings. Seven release unit compilations retain the original silence failure, and six current native frame observations return incomplete reports with exit 1. Compiler issue 9 and frame issue 4 stay open. One bounded read-only compiler stack sample finds active LLVM inlining; it does not establish time attribution or a speedup. Original red-selector and Markdown-wrapping failures remain preserved.

Signed Docs e2d4ffc1 records the contract and reconciles resolved grant regressions. All 45 document controls pass; the complete 2,655-page manual builds without final warnings, all 491,488 word bounds pass and three affected/adjacent pages are visually reviewed. Original CI1091/1092 passes, with four complete logs reviewed through the final warning-free TeX pass.

Signed Integration bdd04a62 selects both original sources. All 174 helper and six profiler commands, strict orchestration Clippy and both unit selections, formatting, dependencies and Markdown pass: 187 commands, zero warnings. Both catalog policies, all 76 original signatures and complete transitive closure pass. The fresh structural audit covers 3,194 code files below 1,000 lines and 98 crate roots enforcing missing_docs; semantic authority closure remains separate. Fresh native capacity execution is pending with the original 120/45-second limits. No completion credit is added before that evidence.

Earlier guarded-fixture CI1797/1798 each passes 372/492 scenarios, including admission, preparation, startup and ext4 quota. All 120 failures are classified: 119 obsolete policy refusals tracked in Integration issue 96, and the original counted grant refusal resolved in Loaderd issue 5. Six complete logs total 25,636,311 bytes with zero warning candidates. No unchanged job was rerun; the later fixes still need their own full CI. Remaining supervisor loss, exhaustion/cleanup, external toolchain rebuilding and both complete EriX builds inside EriX remain required by the phase tracker.

Native configured-client acceptance — 25 September 2026: the exact signed Integration 7a42fa26 graph passes the configured-client, preparation and startup VMs with all original markers, deadlines and cleanup gates. The configured witness seals two isolated realms, observes six successful byte-client exits across three realm instances, checks independent retirement, rejects stale client selectors and reuses a Launchd realm record with a new generation. This proves the native configure/seal/publish/mediated-I/O criterion; full Procd managed-row/final CPU reclamation, supervisor loss and resource ceilings remain separate requirements.

Launchd 372ab70e retains only the required result-carrier GRANT and preserves RECV-only client copies plus complete setup retirement. All six strict 497-test configurations and original CI179/180 pass. Loaderd 5bcf522c retains the counted grant destination; four strict 145-test configurations and original CI107/108 pass. The original red tests, failed native runs and admitted host TCG diagnostic remain preserved. Docs 6a1a9686 passes the full 2,655-page manual and 45 tests locally and in original CI1085/1086; four complete CI logs total 824,660 bytes and final warnings are zero.

The configuration carrier defect, counted grant defect and configured-client stall are resolved by this component and native evidence. The Exsh fixture report retains its pending release compiler/frame validation despite the three native passes. Complete Integration CI1801/1802 is still queued. Whole-fleet authority/source/effect/frame acceptance, final accounting/profiler observation, rebuilding the external Rust/LLVM/runtime toolchain inside EriX and both full EriX guest-build generations remain open.

Original prerequisite Integration CI1793/1794 each passes 490/491 scenarios; Rust and Markdown pass, and six complete logs total 27,432,406 bytes with zero warnings. CI1794 retains the ext4 quota timeout. CI1793 instead exposes a distinct one-shot replay QMP connection loss, recorded using the canonical bug template and phase label. No original workflow was rerun, and no deadline or authority check was relaxed.

Only the existing native-witness sub-item gains credit: 15.42% weighted progress, 413/873 sub-items. Whole acceptance remains 3.86%, 17/460 parents.

Signed configuration carrier correction — 25 September 2026: Launchd 372ab70e retains exactly RECV | GRANT only for counted-client result delivery. Readiness-only RECV, mediator SEND-only routes, RECV-only client copies, original authentication and complete setup disposal before seal/retirement remain required.

Docs 6a1a9686 documents the carrier/source distinction and its temporary setup lifetime. All 45 document tests, Markdown, template, link and unchanged-reference checks pass. The complete 2,655-page manual builds without final warnings, all 491,315 word bounds pass and three affected/adjacent pages are visually reviewed. Original CI1085/1086 is under observation.

Integration 7a42fa26 selects the two signed image sources. Both catalog policies, all 76 original signatures and complete dynamic closure pass. Helper, Rust, profiler and CI inputs remain byte-identical to their recorded validation; fresh formatting, source policy and Markdown pass. The corrected client VM is running from a fresh source-bound runner, followed by the older preparation/startup regressions. Original CI1801/1802 is queued. Launchd issue 10 and Integration issue 92 remain open pending native closure. Earlier failures and host counter evidence are preserved. No deadline or authority gate was relaxed, and these repairs add no canonical checklist credit.

Legacy destinations, exact source/rights/caller/relation checks, native empty-slot and capacity enforcement, and acknowledged disposal remain required.

Signed Docs ee08bab6 documents the contract. All 45 document tests pass, the full 2,653-page manual builds without final warnings, all 491,233 word bounds pass and three affected/adjacent pages are visually reviewed. Its original CI1083/1084 is under observation.

Signed Integration 04bff04f adopts those two original image sources. Both catalog policies, all 76 original signatures and complete transitive closure pass. The Cargo catalog contains neither changed component and remains unchanged. All helper, Rust, profiler and CI source bytes retain their previous validation; fresh formatting, source policy and Markdown pass. Original CI1799/1800 is queued. Fresh configured-client and older preparation/startup VM execution on this successor remains required by Loaderd issue 5; the previous two prerequisite passes and subsequent client failure remain retained.

Original Exsh CI281/282 now have complete failure logs: unit suites pass 507/478/1 and all 355 frame-checker controls pass, but both runtime profiles reach 256 functions with 101 unresolved observations and both all-feature profiles reach 286 with 68 unresolved observations. All four logs total 322,830 bytes with zero warning candidates. Exsh frame issue 4 and compiler issue 9 remain open. No unchanged CI was restarted and no acceptance bound was relaxed. These repairs add no checklist credit; native configured-client acceptance, managed-row reuse, profiling, complete authority closure and both full guest-build requirements remain open.

Configured-client manual contract — 25 September 2026: signed Docs 4226a7c0 corrects operational documentation to LCH1 V4/88 and arena layout V7 and specifies private byte-client packaging, actual terminal outcomes, independent retirement and replacement clients. All 45 document controls, Markdown, template, link and unchanged-reference checks pass. The complete 2,653-page manual builds without final warnings; all 491,103 word bounds pass and nine affected/adjacent pages were visually inspected.

Original CI1081 and CI1082 pass. Four complete logs verify 824,206 bytes; normal early-pass cross-reference warnings converge, and both final passes are warning-free. No unchanged CI was rerun. The manual describes the required native evidence and does not establish configured-client execution or either complete build inside EriX.

Docs PR4 remains unfinished for the remaining phase requirements.

The seal component is now exposed as an accepted substep. Completion is 15.41% weighted checklist progress, 410 of 871 sub-items complete across 156 decomposed parents. Whole acceptance remains 3.86%, 17 of 460 parents, with all 22 original section weights unchanged. The fresh structural audit checks 76 repositories, 3,181 authored code files under the expanded suffix scope below 1,000 lines, 264 unchanged full Git pins and 98 original crate roots with missing-docs gates. This is not whole-fleet semantic authority acceptance.

Launchd PR2 remains unfinished. Next work must retain actual client Start and terminal outcomes, route authenticated client events before ordinary job lookup, consume final CPU once, and prove coherent native configuration/seal/byte I/O plus failure/reuse. The complete EriX build inside EriX and external Rust/LLVM/toolchain rebuild inside EriX remain unproved. Original Integration CI1792 also passes all 491 VM scenarios and interactive dev/release gates, with all three complete logs reviewed (13,516,777 bytes, zero warnings). This validates its older source graph only; Launchd issue 8 preserves CI164's original failure and inaccessible diagnostics.

Native configuration, seal, four-client byte I/O, failure/reuse and both rebuilds inside EriX remain open.

Native failure/reuse and both guest rebuilds remain separate acceptance gates.

This closes the earlier CI-pending observation for Docs PR4, without adding runtime or guest-build acceptance.

Configuration endpoint COPY and accepted private startup documentation.
Signed Docs 69840bd8
clarifies that native endpoint COPY preserves Launchd's configuration SEND
source. After the correlated Provision result and original caller retirement,
Launchd drops that source and independently observes absence before Start.
Unique InstallGrant MOVE retains its separate native source-consumption proof.
The manual and component documentation now also reflect the accepted
two-mediator startup witness
with Launchd 3d39c741:
each actual mediator reaches authenticated PrivateReady and independently
acknowledged positive Retire. Configuration, seal, real client byte I/O,
complete failure retirement and full guest builds remain open.

The Lib-IPC reference is regenerated from exact signed
d4d32115,
including the corrected opcode rustdoc. All 45 unchanged document controls
are reused with byte-identical test implementations. Fresh Markdown, source
binding and syntax checks pass; the full 2,499-page manual has zero final
warnings. All 464,692 word bounds and ten affected process/API pages are
reviewed. Both original CI runs for this exact checkpoint pass: run 1069, run 1070. All four complete terminal job logs (789,498 bytes) are retained and hash-verified. Each manual job passes 45 tests and builds the 2,499-page manual with zero final warnings; earlier reference-convergence warnings resolve before the final pass. No workflow was rerun.

Updated the process-service contracts in signed Docs commit
eade076a4cb30b3932776d8808b6c1203fb7533e.
The manual distinguishes an empty registered receiver from route absence, limits
first-Challenge registration waiting to the original unaccepted submission, and
retains every accepted or erroneous nonzero owner. Explicit Retire consumes only
its exact queued terminal event after proven child and capability disposal;
ordinary spontaneous terminal observation remains available. These contracts
correspond to Launchd #6,
Procd #7 and
Procd #8.

All 45 unchanged document tests remain applicable by byte-identical control
implementations. The complete 2,499-page manual passes without warnings; all
464,516 rendered word bounds pass and changed process pages are visually
reviewed. README, ARCHITECTURE and ROADMAP retain their existing formats.
Generated API selections are unchanged. Native startup acceptance remains
pending; this documentation checkpoint does not establish mediator execution.
Both original CI runs for this exact checkpoint pass: run 1067, run 1068. All four complete terminal job logs (789,510 bytes) are retained and hash-verified. Each manual job passes 45 tests and builds the 2,499-page manual with zero final warnings; earlier reference-convergence warnings resolve before the final pass. No workflow was rerun.

Updated the process and native-launch manual contracts in signed Docs commit
95921234c64d7cc11f9f9ed19d49a5d73c95357c.
Private mediator preparation resolves only its explicitly scoped executable;
Loaderd still checks the configured runtime graph and exact bytes. Ordinary
launch sidecar admission remains separate. The manual also describes both
Launchd-owned terminal-event classes and the current four-column realm geometry,
corresponding to Launchd #3 and
Launchd #4.

All 45 document tests and the complete 2,497-page manual pass without warnings.
All 464,159 rendered word bounds pass; changed process and launch-authority pages
are visually reviewed. README, ARCHITECTURE and ROADMAP retain their existing
formats. Docs has no generated Launchd API reference, so no reference selection
was added. Native startup acceptance remains pending; this documentation result
does not establish mediator execution. Both original CI runs for this exact checkpoint pass: run 1065, run 1066. All four complete terminal job logs (789,078 bytes) are retained and hash-verified. Each manual job passes 45 tests and builds the 2,497-page manual with zero final warnings; earlier reference-convergence warnings resolve before the final pass. No workflow was rerun.

Signed source 32ac049587ba7174d44109a3b179e5a2b69738e5 updates the technical manual and generated API reference for counted realm bootstrap messages, the native mediator entry and exact-generation running retirement while preserving the pending producer and VM acceptance boundaries.

All 45 documentation tests pass. The manual contains 2,469 pages and 459,127 extracted words; 32 selected rendered pages were visually reviewed. Final warnings and page-bound violations are zero.

Coordinated producer provisioning, operation 58 supervisor-lifetime-binding adoption, actual Posixd start and native readiness/retirement VM acceptance remain pending. These source and host/build results do not establish a running realm or a full guest build.

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

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

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

Detailed scope and contracts

Native caller admission checkpoint — 15 September 2026

Forwarded SEND aliases, request-body identities, other lifecycle roles, reused generations and unavailable identity cannot acquire this dispatch permission. Other receivers retain their policy; rejected delivered transfers still undergo local disposal, and uncertain disposal stops ordinary continuation.

Five new producer controls exercise accepted event dispatch and refusals without consuming the private event.

Product runtime-image validation still requires a coherent original-commit dependency graph; this checkpoint does not claim a new Procd VM. Actual returned-grant custody, guarded bootstrap, readiness/configuration/seal, mediated client byte I/O, fair retirement and both complete guest build generations remain open.

Mediator constructor adoption manual — 15 September 2026

The manual now records Procd's mediator-only use of operation 54 without a parent VSpace receipt, independent native TCB backing, unchanged ordinary construction, refusal without fallback and closed start gates.

Authenticated grant return, guarded private execution, readiness, configuration/seal, client I/O, fair retirement and both full guest build generations remain open.

Construction without child root capabilities — 15 September 2026

The first render was rejected because an operation-registry correction followed its source snapshot; accepted evidence uses frozen final text.

Procd adoption, authenticated grant return, guarded bootstrap authority, private mediator execution, readiness, configuration/seal, client I/O, fair retirement and both complete guest build generations remain open.

Staged endpoint attenuation checkpoint — 15 September 2026

Authenticated grant return, independently minimal bootstrap/root authority, retained native and nested guards, private mediator execution, configuration/seal, client I/O, fair retirement and both complete guest build generations remain open.

Signed Docs 87942ea7675e2a25fe3bf19f3cac19f9c5d8b1e2 specifies native IPC platform selection and hosted transport refusal, with both IPC API references generated from signed Lib-ipc 805717680d9dfb902216550a111d910807f30d23. Compile-target selection, local refusal, native observations and retirement evidence remain distinct.

Realm adoption, separate operation-completion contracts, the whole-codebase audit and both full EriX-in-EriX builds remain open.

Kernel 03e13a78 passes CI 528/529 and Bootloader e7fa3935 passes CI 135/136; the coordinated Integration 4b65755f native VM passes the required exit and ordered unique markers. Realm adoption, provider/pending-operation completion, the full audit and both complete builds inside EriX remain open.

This closes renderer issue #7 only; native VM, realm producer, full audits and guest self-hosting remain open.

Native VM, realm producer, complete audits and both full build generations inside EriX remain open.

Dependencies identify required contracts and closure gates; preparatory inventory/design can proceed in parallel under one owner per edited file. Link bounded implementation issues and their PRs here before claiming acceptance.

Close criteria only with their own reviewed deliverables and validation evidence.

Native external Rust/LLVM rebuilding and both full EriX build generations remain required.

Complete mediator execution, native toolchain rebuilding and both full guest builds remain required.

Procd uses the actual returned grant to attenuate the initial endpoint to RECV before execution, removes bypass sources, and retains nested custody beneath Kernel lifetime custody. A later mediator disposal report cannot prove absence of bypass senders.

Native upstream Rust/LLVM rebuilding and both complete EriX builds remain required.

A supervisor binds and starts a child; that child binds a staged grandchild and kills its supervisor through its own explicit Process SEND route. Read-only witnesses require terminal caller storage to survive dispatch, then exact child/grandchild absence before the independent observer reads child-before-supervisor events. All four additional lifetimes and twenty-two mapped pages must be disposed for ERIX_KERNEL:CHILD_EXECUTION_OK.

Signed Integration c14c5a61 requires the additional marker while preserving every earlier marker and the original 60-second limit.

The original install-grant constructor still gives GRANT | MINT while binding needs only GRANT; move-only transfer preserves exact rights. Full source/effect/frame proof, the Pagerd gate, native external Rust/LLVM/runtime rebuilding and both full EriX-in-EriX generations remain mandatory. No whole acceptance leaf is added: 15/460, 3.48% weighted.

The child kills that supervisor through its own explicit Process SEND route. Immediate faulting sentinels forbid either terminal payload from resuming.

A diagnostic-only read-only witness then requires empty CPU accounting, only terminal retained records, no bound cleanup duties or event reservations, exact child identity/CSpace/mapping absence and both unconsumed child-before-supervisor events.

Signed Integration 4d6f4fe8 requires the additional marker while preserving all earlier assertions and both 60-second scenario limits.

The static audit passes 3,140 authored code files below 1,000 lines, 74 manifests, 259 full Git selections, 171 direct missing_docs gates and 92 conventional crate roots; semantic authority and complete private-rustdoc closure remain open.

Further native failure controls, grant-rights minimization, terminal accounting, Procd adoption and complete service lifecycle acceptance remain open. Existing install-grant creation still supplies GRANT | MINT while binding needs GRANT, so minimum authority is not claimed. Full source/effect/frame proof, the 128-page Pagerd gate, profiler attribution, native external Rust/LLVM/runtime rebuilding and both full EriX-in-EriX generations remain mandatory. No whole acceptance leaf is added: 15/460, 3.48% weighted.

Native terminal-event allocation refusal — 19 September 2026: signed Kernel ba03995f extends the actual executing-child sequence with one deliberately refused heap allocation.

Read-only witnesses require complete reservation rollback, an empty event queue, unchanged exact records and capabilities, and preserved code/stack/message mapping ranges. Actual CPL3 instructions validate the refusal reply before the next ordinary ancestor kill succeeds with allocation available. Every earlier terminal, descendant-disposal, independent-process and no-successor idle assertion remains required. ERIX_KERNEL:TERMINAL_EVENT_RESERVATION_OK requires one consumed allocator refusal and no remaining armed fault. No witness supplies a syscall result, cleanup effect or scheduler choice.

Signed Integration cf5b2f5f requires the new marker without changing either 60-second limit.

Complete semantic authority and private-rustdoc closure remain open.

Its separate private-mediator branch does not take the same query path; adoption must state which lifetimes require retained metrics and preserve their original generation without fabricated zero/wall-clock values. Independent release-failure coverage, grant-rights minimization, accounting, Procd adoption and full mediator lifecycle remain open. Full source/effect/frame proof, the 128-page Pagerd gate, profiler attribution, native Rust/LLVM/runtime rebuilding and both full EriX-in-EriX generations remain mandatory. No whole acceptance leaf is added: 15/460, 3.48% weighted.

Independent native child release recovery — 19 September 2026: signed Kernel 82d88b60 extends actual supervisor-exit coverage with two deliberate refusals at the original staged child's final VSpace-release callback, after capability disposal and unlinking. Read-only observations around two ordinary CPL3 observer yields require the original full record, generation, abort custody and first error retained, an empty original CSpace and retained mapped backing. The independent running child must already be absent from native TCB, CSpace and VSpace directories.

The third callback must perform normal VSpace release before all original terminal-event, generation and resource-absence checks pass. ERIX_KERNEL:CHILD_RELEASE_ISOLATION_OK requires exactly two refusals and complete eventual disposal. This establishes injected callback-refusal coverage, not an observed hardware or allocator malfunction. All earlier nested-child, allocation-refusal and no-successor pre-halt assertions remain required.

Signed Integration 294a467a requires the added marker with both original 60-second limits unchanged.

Static audit passes 3,143 authored code files below 1,000 lines, 74 manifests, 259 original Git pins, 171 direct missing_docs gates and 92 conventional roots; complete semantic authority/private-rustdoc closure remains open.

The grant-rights audit confirms actual Procd derivation callers and exact GRANT | MINT receipt checks in Procd and Launchd. Grant authority minimization must coordinate those consumers and distinguish the grant's own rights from its installation ceiling. Original generation-bound terminal accounting, Procd adoption, provider completion, hardware halt/wakeup and complete mediator lifecycle remain open. Full source/effect/frame proof, the 128-page Pagerd gate, profiler attribution, native external Rust/LLVM/runtime rebuilding and both full EriX-in-EriX generations remain mandatory. No whole acceptance leaf is added: 15/460, 3.48% weighted.

The process and launch chapters require GRANT-only final receipts, explicit derivation/source disposal, and original-generation rollback.

Canonical acceptance remains 15/460 leaves, 3.48% weighted. Full service lifecycle, terminal accounting, source/effect/frame proof, the 128-page Pagerd gate, profiler attribution, native external Rust/LLVM/runtime rebuilding and both full EriX-in-EriX generations remain required. Static audit currently passes 3,150 authored code files below 1,000 lines, 74 manifests, 259 explicit Git pins, 172 direct missing_docs gates and 92 conventional Rust roots; full semantic authority and documentation review remain open.

Procd derives exactly GRANT into disposed VSpace scratch, drops its delegating source and uniquely relocates the result into the now-empty managed grant slot before handoff. Four 291/296-unit configurations, four native builds, formatting, strict Clippy and private rustdoc pass without warnings; relocation refusal and occupied-destination controls retain original-stage cleanup.

Canonical acceptance remains 15/460 leaves, 3.48% weighted. Original-generation terminal accounting, provider/lifetime completion, source/effect/frame proof, the 128-page Pagerd gate, profiler attribution, native external Rust/LLVM/runtime rebuilding and both full EriX-in-EriX build generations remain required.

Mediators retain only scalar counters and the original authenticated supervisor identity after disposing all capability columns; supervisor death discharges the pending scalar observation and a replacement cannot inherit it. Bug 5 remains open for actual service acceptance.

These are pending full regressions, not successful runtime acceptance.

No new canonical acceptance leaf is closed: 15/460 and 3.48% weighted. Ordinary Launchd metric-consumer restart/disposal semantics, coherent service CPU/profiler VMs, complete realm/provider authority and I/O, source/effect/frame proof, Pagerd, native external Rust/LLVM/runtime rebuilding and both full EriX-in-EriX build generations remain required.

Full native Rust/LLVM/runtime rebuilding and both EriX guest build generations remain required in Phase 6 completion.

Original frame-manual CI acceptance — 21 September 2026: signed f8a40d45fbbd631660f3adca9152fbb398a4ee6d passes both original 999/1000, including 45 tests and the complete 2,431-page manual. The native external toolchain rebuild and both full guest build requirements remain open.

Integration fd8a5cf0dbcf9a9cd3ddb6038370295e6ec2c8fa requires the complete runtime transition in both Rootd and its orchestration policy. Contract v2 requires the Kernel revision/tree and actual artifact/metadata binding; old receipts, synthetic wrappers and modified source cannot acquire this declaration.

Native external Rust/LLVM/runtime rebuilding and both complete EriX guest build generations remain mandatory.

Five actual service VMs pass: shell CPU accounting, exec successor replacement, two-CPU read-only inspection, out-of-session denial and guarded realm preparation.

Remaining lifecycle control/event ownership, complete native fault/cleanup acceptance and the measured startup timing failures remain open. No whole acceptance leaf closes: 15/460, weighted 3.48%. Rebuilding the external Rust/LLVM toolchain inside EriX and using it in the required full EriX guest-build generations remain mandatory and unproven.

The operator guide distinguishes complete counters from VM acceptance.

Neither proves startup acceptance, whole-transcript instrumentation overhead or a speedup. Profiler acceptance and startup performance remain open. The next optimization must preserve complete validation, live backing checks, page permissions, invalidation ordering and cleanup on errors.

No whole acceptance leaf closes: 15/460, weighted 3.48%. Rebuilding the external Rust/LLVM toolchain inside EriX and completing the required full guest-build generations remain mandatory and unproven.

Related records and contracts
Repository Links
docs issue 10, issue 9
exsh issue 8
integration issue 37, issue 50, issue 67, issue 69, issue 71, PR 12
kernel issue 11, issue 13, issue 19, PR 3
lib-dynlink PR 3
lib-ipc PR 2, child-lifetime-binding.md
meta issue 2
posixd PR 5
procd issue 4, PR 2
rootd issue 7, PR 2
## Problem and motivation Auditable Rust APIs need documented ownership, authority, failure and unsafe invariants across every target. Existing prose and a public-item lint alone cannot demonstrate that private code, build scripts, examples and manual outputs are adequately documented. ## Proposed behavior and scope Inventory every crate target, enforce missing_docs without blanket escape hatches, document public and private contracts, and run warning-denied rustdoc with private items. Reconcile canonical component documents, headers, API references, manual pages and the technical manual. This issue records planned work; its unchecked criteria are not implementation proof. The normative basis is [Phase 6 and AC1–AC24](https://git.erikinkinen.fi/erix/docs/src/branch/main/phases/6.md). ## Authority, security and reliability Documentation must state real capability sources, lifetimes, denial and cleanup behavior rather than infer authority from names. Shared governance remains byte-identical to meta. Non-Rust code uses the language’s own comment format, and security-sensitive details stay in restricted reporting channels. Apply the priority order: security, reliability, then performance. Keep suspected vulnerabilities in the repository’s restricted SECURITY.md reporting channel. ## Acceptance criteria <details> <summary>Checklist</summary> - [ ] Inventory every crate root and target, including binary-only, build-script, test/example and nested crates; identify existing missing_docs enforcement and every local allow/expect/doc-hidden escape. - [ ] Document crate/module purpose, trust boundary, owned/borrowed state, lifecycle, authority and error contracts using `//!`/`///` rustdoc comments. - [ ] Document every public item, field, variant, constant, associated item, macro and FFI export with semantics, units, ranges and failure behavior. - [ ] Document private functions, structures, fields and non-obvious algorithms as well; explain concurrency, mutation order, cleanup, complexity and invariants. `missing_docs` alone is not a private-code completeness audit. - [ ] Give unsafe APIs `# Safety`, and fallible/panicking APIs accurate `# Errors`/`# Panics` sections where applicable. Document each unsafe block's concrete invariant and why safe alternatives do not cover the operation. - [ ] Enforce `#![deny(missing_docs)]` or an equally non-bypassable shared lint policy in every EriX-authored crate/target; reject weakening attributes. Do not use blanket allowances, dummy comments or doc-hidden to pass the gate. - [ ] Add private-item documentation review/check coverage and run Rustdoc with `--document-private-items`; validate broken links and examples with `RUSTDOCFLAGS="-D warnings"` across supported target/feature profiles. - [ ] Ensure CI actually checks missing_docs in default and alternate feature builds, not only one public-library configuration; add a negative fixture proving undocumented public API fails the shared policy check. - [ ] Document non-Rust authored code inline in its language's supported comment format, including shell/Python tools and assembly boundary contracts. Do not pretend rustdoc parses unrelated languages. - [ ] Update `meta` standards/templates and propagate necessary policy changes deliberately. Repair stale canonical GenAI policy links to `docs/policies/generative-ai-contributions.md`; keep attribution optional. - [ ] Update README/ARCHITECTURE/ROADMAP and relevant manual chapters for each implemented ABI, realm, POSIX service, toolchain, profiler and build step; keep historical measurements separate from current guarantees. - [ ] Regenerate API references, test examples, build the whole manual, check final warnings/overflow/links and visually inspect changed rendered pages. Record toolchain/source provenance for the generated documentation. - [ ] Update canonical templates and every repository README to remove current-status/progress/checkpoint sections; put concise current state in ROADMAP/ARCHITECTURE and detailed historical evidence in linked issue/reports. - [ ] Refactor long README/ARCHITECTURE/ROADMAP paragraphs and exhaustive lists into short summaries plus focused design/API/operator documents. Preserve canonical headings, discoverability and normative invariants; do not hide important authority limitations or move status into another README section. - [ ] Keep help text, man pages, rustdoc, C headers, IPC specifications and technical manual consistent through shared semantic metadata where useful; validate coverage and examples, not merely that generated files exist. For each implementation slice, retain actual formatting, strict Clippy, unit/doctest and warning-denied build results for all altered Rust repositories and valid configurations. Add relevant runtime VM coverage, monitor older unit/VM regressions in exact-head CI, and update canonical component documents and affected technical-manual/API material. Every authored code file must remain below 1,000 physical lines, with meaningful inline documentation and missing_docs enforcement in Rust crates. </details> ## Alternatives and tradeoffs Dummy comments, hidden APIs and lint allowances make checks green without helping a reviewer. Keep useful inline invariants, concise canonical navigation and detailed contracts in their owning API/manual documents. Validation checkpoint — 14 September 2026: Signed Posixd `52ef820d33399490c121aad3af1409139e4a8f44` selects the proposed realm custody owner: Procd deposits an ancestor SEND-lineage revoker into its exact native generation before export and retains a nested guard for earlier realm retirement. Exported aliases descend from the nested guard; ancestor-only bypass and setup aliases must be removed before publication. Runtime producer adoption, realm byte I/O and both complete guest build generations remain open. Its private records cannot survive userspace scheduling and own no retained source authority. Reachable backend disposal-failure coverage, sustained invocation-workload profiling, realm producer adoption, whole-codebase authority/private-rustdoc closure and both complete EriX-in-EriX build generations remain open. No new syscall number or wire record is assigned; the existing CALL/RECV/REPLY ABI is unchanged. Sustained invocation-workload profiling, syscall wire and fresh-buffer/fault/overlap validation, actual owned CPL3 peers, reachable backend disposal-failure coverage, realm producer adoption, whole authority/private-rustdoc closure and both complete EriX-in-EriX build generations remain open. Every sample checks exact bytes and SEND capability bindings, authenticated origin, foreign selection, duplicate completion refusal, FIFO position reuse, one-time collection and final invocation disposal. Native syscall adapters, actual owned CPL3 peers, reachable backend disposal-failure coverage, realm adoption, full authority/private-documentation closure and both complete EriX-in-EriX build generations remain open. Measured native invocation lookup refinement — 15 September 2026: Signed Kernel `8349d68636382cc7e25a3347f5f1df216554203a` retains only numeric carrier-search positions. No successful authorization, capability or reference is cached. These are host operation wall times, not guest startup/build acceptance or a statistical guarantee. Current full-suite CI remains required; stopped cohorts are not polled again. Owned syscall wire adapters, actual owned CPL3 peers, fresh-buffer validation, reachable backend disposal-failure coverage, realm adoption, full authority/private-documentation closure and both complete EriX-in-EriX build generations remain open. Owned invocation wire and native acceptance — 15 September 2026: Signed Kernel `5f497adaefa526108a0439e0e071717dddb85334`, shared IPC `de968da19898bef532ddb3b5974bb9562f51dee5`, capability ABI `a001a26f0eb3aebec3f5fd02a28d98f1bc23f8a0` and Integration `9030b217c490db6ad3ec60a799cb025eccbfcdb1` implement and exercise the immediate owned invocation boundary. Destination capacity and descriptive receipt capacity are independent; spare capacity acquires no authority and repeated collection cannot duplicate transfers. The real three-process CPL3 scenario passes all eight operations, full-span pointer/rights/overflow/reserved-field rejection, actual returned selectors, payload/capability/origin checks, collection after server exit and repeated receipts. A second request rejects premature relinquishment, enters draining on caller release and retires only after the exact server acknowledgment. All 162 maintained Integration helper commands pass; three prior correct concurrent-run lock refusals are retained and their sequential checks pass on unchanged executable inputs. Current full-suite acceptance remains open, as does the intermittent quota cause in Integration issue 18. Reachable backend disposal-failure coverage, broader revocation/generation-reuse scenarios, producer adoption, realm runtime, complete authority/inline-documentation audits and both full EriX-in-EriX build generations remain open. Process-bound native acceptance — 15 September 2026: Signed Kernel `60da5858d7198185efd103f0e91e5ac2e0b63e67` implements control operation 52, checking the actual moved install grant against expected process/generation with exact rights, including zero, under existing endpoint policies. Signed Procd `f1105706cc19ed024a6cca79a29abc57c90c6661` uses this operation in its actual ordinary launch-description producer while retaining the narrow SEND receipt, pending state and exact failure cleanup. All 162 Integration helpers pass after updating the exact policy assertion to require the new marker; its initial mismatch remains recorded. Typed realm bootstrap, mediator startup/readiness/configuration/seal, complete consumer image adoption, fair terminal/provider retirement, broader native disposal failures and both full EriX-in-EriX build generations remain open. The new inventory covers 76 repositories, 2,950 code files below 1,000 lines and 158 direct missing_docs crate-root gates; complete inline documentation and whole-codebase authority closure remain open. Actual grant-return provisioning, authenticated receiver readiness, configuration/seal, client I/O, fair retirement, whole-codebase authority/documentation closure and both complete guest build generations remain required. No runnable Posixd realm or guest-build acceptance is claimed. Descriptor startup rejects short or dirty cleanup storage before metadata effects; transactions exclusively reborrow the complete slice and erase it after emergency cleanup. All 961 Rust tests pass in each default/all-feature/production development/release configuration, with formatting, strict host/native Clippy, private rustdoc and eight native builds without warnings. Four added tests cover workspace disjointness, malformed backing, complete caller extent and consecutive cleanup reuse; existing cleanup controls now also check buffer canaries and erasure. All 73 warning-denied checker tests pass. Both actual optimized native fallbacks measure 48 local bytes, compared with the retained prior 32,816-byte frames. Their full checker reports remain INCOMPLETE: runtime/all graphs contain 691/604 unresolved observations, and the old 32 KiB initial stack-reservation requirement still needs a workspace-specific evidence contract. Ordinary-source membership and direct-versus-nested early-drop bounds remain open. The 8/33/56 KiB upper limits and 64 KiB stack are unchanged; this measurement is not an all-path stack-safety claim. Matching producer `38424571b76b36c1e631d99fd2c859fb32311eea` exports/consumes 96 capacity words plus 72 target layout words, reserves both transport arrays first and rejects old/mixed layouts. Packaging both actual optimized shell configurations under canonical dev/release policies derives 4,300,800 workspace bytes, with unchanged executable bytes and a separate 64 KiB stack. All 162 Integration helper commands and its strict 320/321-test Rust matrix pass, including four native builds. These are private artifact and host checks, not guest execution. The product catalog still selects the earlier shell; coordinated catalog adoption and matching runtime VMs remain required. Documentation `79cdd4c3694e800091b55c737fca04c7bdd3d071` describes the ownership and compatibility contract. Its 45 tests and canonical checks pass. The full manual renders 2,375 pages without final warnings; all 433,713 word boxes are in bounds and changed page 2280 passes visual review. API snapshots are unchanged. Exsh CI 225/226 fails only the incomplete frame gate after 961 Rust and 73 checker tests; all four logs total 311,820 bytes with zero warnings. CI runtime/all graph observations are 662/587 and both fallbacks measure 48 bytes; these artifacts remain distinct from local images. Docs CI 883/884 passes with all four complete logs (762,212 bytes); reference passes converge with 35/1/0 warnings and zero final warnings. These component cohorts are fully classified. Integration CI 1637/1638 remains queued at its first observation. No full build within EriX or whole-codebase authority closure is claimed. Complete native companion checkpoint — 15 September 2026: Signed Integration `db80a2c1dfc669bd724762d476f5f5c0da005ff6` centralizes the complete eight assembly input roles plus the original producer script. Source selection and support-manifest validation share those roles; both outer artifact keys bind the contract module. The catalog changes only native lib-cstd to original `bdcbbea43550e8b99cd9a8221e4bc5a645637990`. Exact path/byte, tool, waited status, cleanup and output checks remain required. Actual hidden/public production and missing/extra/altered receipt controls pass, as do both outer cache-key controls. All 162 helper commands are covered: 160 pass in the full run, and the two corrected test-only fixtures pass separately. The original missing-module and unclosed-fixture-stream failures are retained. The strict 320/321-test Rust matrix, Clippy, formatting, private rustdoc and four native builds pass without warnings. A host-built diagnostic native image contains 38 executables and 27 shared objects, passes closure checks and builds without warnings. Its SHA-256 is `ff5d774308cdf236c860a2423adab6e2594bf3c0991b26eb37cb3c64af96ddfe`. It uses 73 original component selections with 72 coherent Cargo manifests and the five explicitly recorded helper corrections whose bytes match this signed checkpoint. It is not an unmodified product catalog. The unchanged editor/history, inherited-stream timing and runtime-error VM probes all pass with their original 120/15/10-second budgets and exact output checks; each leaves the source image unchanged. Signed Docs `31bd9524c31c9d8d6a8f00248f702e6b7d428106` explains the complete source contract. All 45 tests and canonical checks pass. The complete manual renders 2,375 pages without final warnings; all 433,817 word boxes are in bounds and changed page 2281 passes visual review. Original API snapshots are unchanged. Docs CI 885/886 passes with all four complete logs (762,204 bytes); reference passes converge with 35/1/0 warnings and zero final warnings. Integration CI 1639/1640 remains queued at its first observation; the build compatibility issue stays open pending its complete CI. Full Exsh frame proof, coherent product adoption and both complete EriX-in-EriX build generations remain open. Paired workspace and literal command evidence — 15 September 2026: Signed Docs `5d77dc2b82bf5439e58234d901e30f4565aaa81a` documents the independent pristine/packaged ELF workspace mapping domain, its native-loader assumption and the separate source borrowing, erasure and all-path frame obligations. It also fixes 24 existing inline long options and argument delimiters whose ASCII double hyphens previously became an en dash (issue #8). Numeric ranges, prose punctuation, verbatim command blocks and original signed API snapshots remain unchanged. All 45 documentation tests, canonical and Markdown checks pass. The complete manual has 2,375 pages, 433,924 in-bounds word boxes and zero final warnings. Text extraction confirms literal option bytes, including embedded `set --` and standalone delimiters; nine affected pages pass visual review. PDF SHA-256: `fd33102422cc80697ead3f5c939b39d1e9c6bf69ce06475be4ce8767cafb2f23`. The first render's punctuation failure remains recorded separately; the accepted PDF comes from the final corrected source. Docs CI 887/888 passes with all four complete classified logs (762,236 bytes). Both manual jobs pass 45 tests and converge with 35/1/0 reference warnings, leaving zero final warnings; both Markdown jobs pass. Rust and VM checks do not apply to these documentation-only edits. This checkpoint does not establish complete runtime permission, frame, authority, realm or guest-build acceptance. Separate one-CPU and two-CPU diagnostic VMs pass the unchanged native command sequence. A read-only hardware observer matches all 233,755 selected coreutils executable bytes, verifies CPL3 and enabled paging/execute-disable state, and confirms both observed RELRO pages are user-readable, read-only and non-executable; the current stack is user-writable and non-executable. Both processors report execute-disable enabled. This is an exact process-entry/table observation, not an injected instruction-fault test or whole-system permission proof. The diagnostic image SHA-256 is `8c3c24639e8e1ca8c4f2ad4e485323abf32ec07408241c3e4fa9713f6e07e812`. Signed Docs `d221e725c2543316680e63fc5e8314ce0fe3bdf1` documents the mapping and processor contracts. All 45 documentation tests and canonical checks pass; the 2,375-page manual has 434,308 in-bounds word boxes and zero final warnings, with three changed pages visually reviewed. Exported API snapshots are unchanged. Kernel CI 574/575 passes with four complete warning-free logs (708,112 bytes), including existing optimized workload examples. Docs CI 891/892 passes all four complete logs (762,176 bytes), with 45 tests per manual job and zero final warnings. The later maintained permission regression is recorded below. Full frame proof, whole-codebase authority/documentation review, runnable realms and both complete guest build generations remain open. Actual one-CPU and two-CPU runs on the repaired diagnostic image pass the original native-time command sequence and the expanded hardware checks: all 58 selected code pages are user-readable, read-only and executable; both RELRO pages are read-only/non-executable; the current stack is writable/non-executable. Complete executable bytes match and NX interpretation is enabled on every selected processor. An earlier image is rejected by the maintained observer. Both child outcomes, exact original input bytes and temporary cleanup are retained, with empty debugger stderr in both positive runs. The final cleanup code also preserves reaping when a direct child exits between poll and termination. The command's image CI gate awaits adoption of a coherent product catalog containing both required component fixes. Its explicit diagnostic invocations do not silently replace the older maintained image graph. Signed Docs `3fb0b12ff55d044cc4bbe142418ab7a5b07bb42d` documents the maintained operator contract. All 45 tests and canonical checks pass; the 2,377-page manual has 434,563 in-bounds word boxes with zero final warnings, and the changed subsection passes visual review. Exported API snapshots are unchanged. The preceding Docs CI result is recorded below; current Integration CI, complete frame proof, whole-codebase authority/documentation closure, runnable realms and both guest-build generations remain open. It shares the relocation inventory with guarded tables and rejects overlapping or executable-byte writes. Replaying both unique original pristine/packaged artifact pairs preserves their hashes and all original stack/resource budgets. Runtime/all-feature reports retain 641/591 new call/tail proofs and reach 266/240 functions; unresolved observations fall from 691/604 to 271/232. Workspace mapping passes. Both full reports remain incomplete: unknown indirect control flow, non-returning semantics and source/direct-versus-nested boundaries remain separate obligations. These are partial static admission results, not a complete frame or authority proof. Signed Docs `83b2d4a2dfc473bb8a99719f86fa1c3c33effa53` explains the proof contract and its limits. All 45 documentation tests and canonical checks pass; the 2,377-page manual has 434,680 in-bounds word boxes, zero final warnings and a visually reviewed changed page. API snapshots are unchanged. The preceding Docs permission-observer checkpoint passes CI 893/894 with four complete logs (762,616 bytes) and zero final warnings. Exsh CI 231/232 is fully classified: all 961 Rust tests, 102 checker tests and all four workspace domains pass, with four complete logs totaling 314,760 bytes and zero warnings. Only the complete frame gate fails. Its separately selected CI artifacts report 273/230 unresolved observations; these do not replace the retained local artifact identities/counts. The preceding Docs CI result is recorded below. All 2,997 inventoried authored code files remain below 1,000 lines; semantic authority/documentation closure, product catalog adoption, runnable realms and both complete guest builds remain open. Unknown calls, unsupported instructions, malformed boundaries and unproved tail cycles cannot establish facts. All 114 checker tests pass, including twelve new literal controls and a 1,200-function chain requiring at most two body visits per function. All six strict Rust feature/profile configurations pass 961 tests each, with six native builds, host/native Clippy, formatting and private rustdoc. Runtime Rust, linker scripts and Cargo selections are unchanged. The physical inventory now covers 2,999 authored code files, all below 1,000 lines. The same retained original artifact pairs yield thirteen grounded facts each. Runtime/all-feature unresolved observations fall from 271/232 to 181/150; every function-end boundary error disappears under the stated ordinary-call model. The work queue performs 347/313 body evaluations for 266/240 discovered functions and retains 263/237 in the final reachable graph. This is an analysis-work count, not a claimed runtime speedup. Remaining observations are 140/111 unknown calls, 40/38 unknown branches and one unsupported instruction per mode. Both workspace mappings pass; whole frame and source domains remain incomplete with unchanged budgets. A separate proof audit verifies earlier dependencies and retained terminal callees. Signed Docs `97ce65dcb8cef7232b50d53af90ff8673d623e05` documents the refinement. All 45 tests and canonical checks pass, and the 2,377-page manual has 434,800 in-bounds word boxes, zero final warnings and a visually reviewed changed page. Exported API snapshots are unchanged. Exsh CI 233/234 is fully classified: 961 Rust tests, all 114 checker tests and four workspace mappings pass, while the full frame gate remains incomplete. All four logs total 314,776 bytes with zero warnings. Those separately selected CI artifacts retain 183/145 unresolved observations, distinct from the retained local pair counts. Matching Docs CI 897/898 passes with all four complete logs across the two terminal observations (762,600 bytes), 45 tests per manual job and zero final warnings. The preceding Docs target-contract checkpoint passes CI 895/896 with four complete logs totaling 762,636 bytes and zero final warnings. Full indirect/source proof, coherent catalog adoption, whole-codebase authority/documentation closure, runnable realms and both full guest-build generations remain open. No guest authority, acceptance oracle, error precedence or 120/15/10-second limit changes. All 172 host cases in eleven suites pass, including 28 diagnostic cases and eight new independent producer, malformed-prefix, private-receipt and actual-wrapper controls. The strict default/all-feature development/release matrix passes 320/321 tests per mode, host/native Clippy, four native builds, formatting and private rustdoc without warnings. A documentation line wrap is the only source change after the Rust matrix. One initial negative fixture had identical transport bytes when both exits were unknown; a distinct contradiction replaces it. An initially over-isolated console-suite invocation is corrected to its maintained CI invocation, without changing that suite or the watchdog. Signed Docs `c4bfc12245036f069d178a10183bb1ed15b4aab5` updates the operator manual. All 45 tests, canonical checks and full rendering pass: 2,377 pages, 435,037 in-bounds word boxes, zero final warnings and both changed pages visually reviewed. API snapshots are unchanged. Matching CI is pending. [Release interrupt reuse #54](https://git.erikinkinen.fi/erix/integration/issues/54) and [release COM1 shell lines #55](https://git.erikinkinen.fi/erix/integration/issues/55) remain open: missing original inner artifacts are not recovered, no shared cause is proved, and this checkpoint adds no successful guest run or full guest build. Integration diagnostic CI 1645/1646 remains queued at its signed head; original release-input bugs 54/55 remain open. All 138 checker tests, formatting, canonical document checks and an independent original-byte/load/relocation and earlier no-return dependency audit pass. Retained runtime/all artifact pairs gain 16/18 register edges; the all-feature graph reaches one additional function. Remaining unresolved sites are 164/132, with thirteen grounded no-return facts per mode. Both workspace mappings pass. Full frame/source gates remain incomplete with actual exit 1 and unchanged 60/15-second and 64 MiB budgets. Every Rust/Cargo/linker/build/workflow byte is unchanged from six strict 961-test configurations and six native builds; no new Rust build or guest execution is claimed. Profiling identified unnecessary effect parsing when all registers were unknown. Skipping those identity transfers and compiling fixed effect patterns once preserves every report decision, reducing runtime effect-parser calls from 34,901 to 1,334 and all-feature calls from 33,398 to 1,348. One before/after observation per identical pair measures 5.089 to 4.385 seconds and 4.997 to 4.358 seconds respectively, including observer overhead. These are bounded host work measurements, not a statistical timing guarantee or guest speedup. Signed Docs `4f770bee4c6a4784b4fcce6ae606d1fc10b328da` documents register provenance and limits. All 45 tests and the 2,377-page manual render pass, with 435,231 word boxes inside page bounds, no final warnings and visual review of the changed page. All 3,001 authored code files remain below 1,000 physical lines. Matching Exsh/Docs CI is pending. Complete source domains, authority closure, executable realms and both complete guest-build generations remain open. Register checkpoint CI — 16 September 2026: Exsh `da8b75c9063c52de2149f2a6c7ed170f720a6c62` is terminal in CI 239/240. Both runs pass 961 Rust tests, all 138 checker tests, strict warning-denied Rust checks and Markdown. All four paired workspace domains pass in each run. The required full-frame gate remains incomplete, with 168/131 unresolved observations on these CI artifacts, so both runs correctly fail overall. Four complete logs total 314,840 bytes and contain no compiler/lint warnings. These CI artifact observations remain distinct from the retained local pairs. Docs `4f770bee4c6a4784b4fcce6ae606d1fc10b328da` passes CI 901/902. Four complete logs total 762,604 bytes; each manual job passes 45 tests and renders 2,377 pages. Initial reference-resolution warnings clear during the normal three LaTeX passes; final renders have zero warnings. The full source/frame proof, coherent catalog adoption, authority closure and both complete confined guest-build generations remain open. Every selected immutable table byte, matching base addition and candidate instruction boundary must be proved before retaining any successor or branch evidence. Numeric/table values cannot authorize function calls. All 157 checker tests pass, including complete 256/65,536-entry domains, nonzero and signed read windows, extended register fields, joins, bypasses, loops, width controls and immutable/boundary refusals. Original-byte function/table/base/index/addition audits, formatting, Markdown and canonical checks pass. Final original runtime/all pairs admit two table branches each and retain 164/132 unresolved obligations: two entry branches resolve, while two newly exposed guard-interior conflicts remain. Both workspace mappings and thirteen grounded no-return facts per mode are retained. Full frame/source status remains incomplete with actual exit 1 and unchanged budgets. Initial partial-set exploration is diagnostic negative evidence, not accepted coverage. Profiling identified repeated compilation of fixed stack patterns. Compiling sixteen unchanged patterns once and sharing the existing padding pattern preserves all report decisions and matching operations. One baseline/optimized observation per original pair reduces runtime/all regex-cache lookups from 651,254/627,530 to 135,274/131,391. Profiled times are 5.994 to 5.445 and 5.756 to 5.179 seconds, including overhead and waiting. These measurements establish reduced host work, not a timing guarantee or guest speedup. The final source has a clarified module docstring and separately reconciled complete replay decisions. Every Rust/Cargo/linker/build/workflow byte retains the existing strict matrix; no new Rust build or guest execution is claimed. Signed Docs `242b78c8f35aeaef879f819c670574a4c1d95c3f` explains complete read windows and target-set admission. All 45 tests and the 2,379-page render pass, with 435,421 word boxes inside page bounds, zero final warnings and visual review of both changed pages. All 3,003 authored code files remain below 1,000 physical lines. Matching CI is pending. Explicit flag/guard refinement, full source/frame proof, coherent catalog adoption, authority closure and both complete confined guest-build generations remain required. The required full-frame gate remains incomplete with 168/131 unresolved observations on the CI artifacts, so both runs fail overall. No incomplete proof is treated as acceptance. Signed Docs `242b78c8f35aeaef879f819c670574a4c1d95c3f` passes CI 903/904. All four logs are complete (763,044 bytes); each manual job passes 45 tests and renders 2,379 pages. Initial reference warnings clear in the normal LaTeX passes; final renders have zero warnings. An expanded local source/config inventory additionally checks 685 files, bringing the combined physical ceiling audit to 3,688 files, all below 1,000 lines. Flag/guard refinement, source/frame closure, coherent catalog adoption, complete authority review and both full confined guest-build generations remain required. A 32-bit comparison never zeroes upper bits. Every complete immutable target set remains mandatory, and numeric/table values cannot authorize function calls. All 176 checker tests pass, including an independent exhaustive interval oracle, high-register dispatch, sign extension, bypasses, conflicting/unknown joins, stale proofs, complete table arms and large arithmetic loops. Independent original-byte audits check 354/321 comparison edges, eleven table branches per mode, protected function loads and thirteen earlier grounded no-return facts per mode. Original runtime/all pairs reach 271/246 functions and retain 158/126 unresolved observations, down from 164/132. Workspace domains pass; full frame/source status remains incomplete with actual exit 1 and unchanged budgets. The audit also reproduces and fixes [terminal-call discovery loss](https://git.erikinkinen.fi/erix/exsh/issues/6). A prior successor diagnostic no longer suppresses recomputation of a revisited call. Three independent controls retain grounded no-return, returning and unknown-target behavior. Original byte/range inspection corrects earlier descriptions of two guard-interior conflicts: these were fallthrough exactly at declared function ends. Padding remains outside those functions; callee names never supply no-return proof. Matching CI remains required before closing the defect. Profiling identified repeated decoder-effect work. Sharing immutable effects only within one function-body analysis reduces runtime/all effect decoding from 72,668/69,784 to 34,499/32,576 and operand parsing from 75,637/72,547 to 37,468/35,339. Complete paired decisions remain identical. Final single paired profiled observations are 6.633 to 6.425 and 6.416 to 6.269 seconds, including overhead and waiting. The final baseline overlaps host test execution, and earlier pairs show timing variability; these diagnostic durations do not isolate a speedup. This establishes reduced host work, not a timing guarantee or guest speedup. Every Rust/Cargo/linker/build/workflow byte retains the existing strict six-configuration 961-test matrix and six native builds. Formatting, Markdown and canonical checks pass. Signed Docs `d8fbc3a1f3696e02954b81f23511cee513ddfa8c` passes all 45 tests and complete 2,379-page rendering: 435,637 in-bounds word boxes, zero final warnings and two visually reviewed pages. The physical audit covers 3,005 authored code files below 1,000 lines. Matching CI is pending. Remaining indirect calls/branches, full source/direct-versus-nested proof, coherent catalog adoption, complete realm authority and both full confined guest-build generations remain required. Comparison checkpoint CI — 16 September 2026: [Exsh CI 243](https://git.erikinkinen.fi/erix/exsh/actions/runs/243) and [244](https://git.erikinkinen.fi/erix/exsh/actions/runs/244) are terminal. All four complete logs total 314,904 bytes with no compiler/lint warnings. Strict Rust checks, 961 Rust tests, 176 checker tests, Markdown and all four workspace domains per run pass. The required full-frame gate remains failed with 163/126 unresolved observations on these CI artifacts; their identities are distinct from the original static replay pairs. No full frame or guest-build acceptance is claimed. [Docs CI 905](https://git.erikinkinen.fi/erix/docs/actions/runs/905) and [906](https://git.erikinkinen.fi/erix/docs/actions/runs/906) pass with all four complete logs (763,056 bytes), 45 tests and 2,379-page manuals. Both final renders have zero warnings after ordinary reference convergence. The terminal-call discovery controls pass in both Exsh runs, resolving the scoped defect in [Exsh #6](https://git.erikinkinen.fi/erix/exsh/issues/6) while the complete emitted-proof defect stays open. The current physical audit covers 3,690 authored source/config files below 1,000 lines; semantic authority and complete private documentation closure remain required. Original unfinished Integration jobs continue under their existing handles. Full 64-bit comparisons may use the architectural numeric domain while keeping protected typed identities separate; narrow comparisons still require independent upper-bit proof. All 191 checker tests pass, including independent exhaustive concrete arithmetic and modular-interval oracles, wraparound and authority-negative controls. Original runtime/all artifact pairs admit fifteen table branches each and reach 271/246 functions, with 156/124 unresolved observations. Both workspace mappings pass; actual full-frame exits remain 1 and full source/direct domains remain incomplete. Independent original-byte audits check arithmetic/conditional/table premises, 16/18 protected register edges and thirteen grounded no-return facts per pair. Profiling identified repeated stack-neutral grammar evaluation. A cache scoped to one function reduces those evaluations from 95,643 to 43,169 for runtime and 92,608 to 41,053 for all features, with complete paired report decisions equal. Cached values include refusals and contain no path facts. Timing observations include observer overhead and do not isolate a statistical speedup or guest performance. Formatting, Markdown, whitespace and all 45 Docs tests pass. The 2,379-page manual has 435,808 in-bounds word boxes, zero final warnings and visual review of the changed pages. The physical inventory covers 3,691 authored source/configuration files, all below 1,000 lines. Semantic authority and complete private rustdoc closure remain open. Rust/Cargo/linker/build/workflow bytes are unchanged from the retained strict matrix and classified CI 243/244; new [Exsh CI 245](https://git.erikinkinen.fi/erix/exsh/actions/runs/245)/[246](https://git.erikinkinen.fi/erix/exsh/actions/runs/246) independently reruns those checks. [Docs CI 907](https://git.erikinkinen.fi/erix/docs/actions/runs/907)/[908](https://git.erikinkinen.fi/erix/docs/actions/runs/908) also runs. Matching CI is pending, and no full confined guest build or coherent product-catalog adoption is claimed. Test-import correction and CI classification — 16 September 2026: original Exsh CI 245/246 failed before the frame gate because the arithmetic test could not import its checker module. They attempted 177 tests: 176 passed and one module import failed. The preceding 961 Rust tests and strict build stages passed; all four complete logs total 309,708 bytes with zero compiler/lint warnings. The earlier local 191-test pass used an explicitly supplied PYTHONPATH and did not prove equivalence to the clean workflow. This regression is retained in [Exsh #7](https://git.erikinkinen.fi/erix/exsh/issues/7). Signed correction `12331e26f3bb7a25c0146c8b314eef46dd451099` loads the repository's literal fixture setup before implementation imports in both affected modules. A new regression imports every checker test module in a fresh isolated interpreter; it reproduces both failures before correction and passes afterward. The exact clean workflow command now passes all 192 tests without PYTHONPATH. Formatting, Markdown and whitespace pass. Checker/runtime/Cargo/workflow bytes are unchanged, so the prior original-artifact and profiler evidence retains its exact scope. New [CI 247](https://git.erikinkinen.fi/erix/exsh/actions/runs/247)/[248](https://git.erikinkinen.fi/erix/exsh/actions/runs/248) runs against the corrected source; issue #7 remains open pending matching CI. Docs CI 907/908 now passes with four complete logs totaling 763,024 bytes, all 45 tests and 2,379-page manuals. Both final renders have zero warnings after ordinary reference convergence. Full frame/source proof, coherent catalog adoption and complete confined guest builds remain outstanding. Both runs reach and fail the required full-frame gate. All four workspace mappings per run pass, while the emitted CI pairs retain unresolved counts [161, 161, 124, 124]; these artifacts are distinct from the original static pairs' 156/124 observations. Full source/direct domains remain incomplete, and [Exsh #4](https://git.erikinkinen.fi/erix/exsh/issues/4) remains open. The original import-failed runs 245/246 stay classified and are not relabeled as passing. Docs CI 907/908 passes all 45 tests and 2,379-page manuals with zero final warnings; four complete logs total 763,024 bytes. Signed trees are clean, canonical issue/PR metadata remains applied, and the 3,691-file physical inventory remains below 1,000 lines per authored source/configuration file. Semantic authority and private documentation closure, coherent catalog adoption, runnable realms and both full confined guest build generations remain outstanding. Original unfinished Integration runs continue under their existing handles and budgets. Complete original bodies and earlier callee facts now prove never-written register families. All 213 clean-environment checker tests pass, including 21 new controls, eleven isolated module imports and a 1,200-function grounded dependency chain. All six strict Rust feature/profile configurations pass 961 tests each, with host/native Clippy, private rustdoc and six native builds; no warnings. Original runtime/all artifact pairs retain 65/72 protected register edges and 70/77 load origins, reducing unresolved observations from 156/124 to 107/70. Both workspace mappings pass; full source/frame/direct gates retain actual exit 1. Independent audits bind 7,795/7,503 used-contract instructions and complete earlier-proof closure to the original captured bytes. Profiling identified unnecessary empty-state scans and rejected-body suffix work. Removing them preserves every paired report decision and reduces total profiled Python calls from 32,160,478 to 26,673,252 and from 30,880,221 to 25,402,446. Single paired timings include observer overhead; they do not establish statistical or guest performance. Original timer, byte and stack budgets remain unchanged. All 45 Docs tests, formatting, Markdown and canonical checks pass. The 2,379-page manual has 436,058 in-bounds word boxes, zero final warnings and visual review of both changed pages. The physical audit covers 3,693 source/configuration files, all below 1,000 lines. Semantic authority/private-documentation closure, product adoption, complete source/frame admission, runnable realms and both full in-EriX build generations remain open. Automatic CI for both exact signed heads is being followed; local passes are not reported as CI acceptance. Matching preservation CI — 16 September 2026: [Exsh 249](https://git.erikinkinen.fi/erix/exsh/actions/runs/249) and [250](https://git.erikinkinen.fi/erix/exsh/actions/runs/250) are fully classified at `641ac2fc7c3fba3ab351f2863df7e35117b2732a`. Both pass all 213 checker tests, including eleven isolated imports and the stale-frame controls, all 961 Rust tests and preceding strict host/native Clippy, rustdoc and native build stages. Markdown and all four workspace mappings per run pass. The remaining full frame gate fails as required; original CI artifact observations are [[111, 111, 74, 74], [111, 111, 74, 74]]. All four complete logs total 314,995 bytes without warnings. The independently retained local pairs remain 107/70, with their own original identities. [Docs 909](https://git.erikinkinen.fi/erix/docs/actions/runs/909) and [910](https://git.erikinkinen.fi/erix/docs/actions/runs/910) pass at `7a7c3ff0095de8f008c9b534fd993554df37f976`. All four complete logs total 763,088 bytes; both manual jobs pass 45 tests and render 2,379 pages with zero final warnings after ordinary reference convergence. The corrected frame-pointer issue is closed on this matching evidence; the full source/frame issue remains open. No full confined build, runnable realm or coherent product-catalog adoption is established. Checked symbolic relocations contribute write footprints, never local targets or library-discovery authority. Code/dynamic metadata mutation, unknown streams, malformed names/links, resolver symbols and invalid relative prefixes refuse intake. All 231 checker controls (18 new) and 12 isolated test modules pass in a clean environment. All six strict Rust configurations pass 961 tests each, host/native Clippy, private rustdoc and six native builds without warnings; formatting and canonical checks pass. Both retained standalone pairs have exactly unchanged proof decisions (107/70 unresolved). The original native pair inventories 1,345 functions, reaches 220, proves workspace mapping and retains 299 unresolved observations, including 102 symbolic-target refusals. The shell entry has 6,864 partially accounted bytes; its incomplete paths do not establish an upper bound. Independent original-byte audit checks all 1,086,955 executable bytes, exactly 154 changed capacity bytes and 627 relative call-load proofs. Full source/frame/direct gates remain incomplete, actual checker exit 1. Native original SHA-256 `879579542895f2f3fbda38972ebaaaf55e05857ffc456342117624a9bc8d24a9` and packaged SHA-256 `183a1a2f1f4192ffd0b9c123ca50d33af6c584940ca51b156198f8822b718feb` retain their original Exsh runtime selection `b12e172e7b266842a8659104894f6821166165fb`. The native producer already retains the original; no duplicate artifact or producer mutation was required. Profiling all three original pairs takes 16.60/16.47/17.02 seconds including observer work under unchanged 60/15-second and 64 MiB budgets. These are individual static observations, not guest performance claims. Signed Docs `12c6d0a91e5e9c5f170d6d0aa7f050dd60e883ef` documents the contract. All 45 tests and a complete 2,381-page manual pass, with 436,247 in-bounds word boxes, zero final warnings and changed-page visual review. The physical inventory covers 3,695 source/configuration files, all below 1,000 lines; semantic authority/private documentation closure remains open. New Exsh CI 251/252 and Docs CI 911/912 are running at their exact signed heads. Complete source membership, native dependency closure, coherent catalog adoption, runnable realms and both full guest builds remain required. Matching native intake CI — 16 September 2026: [Exsh 251](https://git.erikinkinen.fi/erix/exsh/actions/runs/251) and [252](https://git.erikinkinen.fi/erix/exsh/actions/runs/252) are fully classified at `d67dcb963f1aa265b13dd0609a5f8488784b5822`. Both pass 231 checker tests, twelve isolated imports, 961 Rust tests and the strict preceding Clippy/rustdoc/native build stages. All four workspace mappings per run and Markdown pass. The required full frame gate remains incomplete; the CI artifact counts are 111/111/74/74 unresolved observations in each run. Four complete logs total 315,371 bytes, with zero warnings. Retained local standalone and native artifacts keep their own separate identities and 107/70/299 counts. [Docs 911](https://git.erikinkinen.fi/erix/docs/actions/runs/911) and [912](https://git.erikinkinen.fi/erix/docs/actions/runs/912) pass at `12c6d0a91e5e9c5f170d6d0aa7f050dd60e883ef`. Four complete logs total 763,452 bytes; each manual job passes 45 tests and renders 2,381 pages, with ordinary reference convergence followed by zero final warnings. No full source/frame proof, native dependency closure, runnable confined realm or full EriX-in-EriX build is established. A separate original-source relocation calculation defect is now reproduced and tracked with the canonical bug template in [lib-dynlink #2](https://git.erikinkinen.fi/erix/lib-dynlink/issues/2). Its two host failures do not imply a guest regression. All 107 symbol-only relocations in the seven retained native artifacts have zero addends; the supported nonzero-field case still requires correction before broader native binding admission. Original dynlinkd, loaderd and bootloader source candidates, each changing only the library's full commit selector in an isolated exact-commit worktree, pass four strict configurations: 13/105/41 tests respectively, with twelve native builds and private rustdoc, zero warnings. Published consumer commits remain unchanged pending coherent adoption. The retained Exsh executable and six explicit libraries yield 1,608 independently expected relocation writes under caller-selected hypothetical load biases. Both original and corrected planners match those original zero-addend inputs. All 107 symbol-only writes remain identical under positive, negative and extreme unused-addend variants with the fix; the original planner fails the addend-16 control (actual Cargo exit 101). The original/packaged dynamic tables are byte-identical and all artifact/manifest hashes are retained. This host metadata replay performs no target mapping or execution and does not admit native frame paths. Signed Docs `214b08666b8b36ad4270bcfee3b3379d8dc08a79` documents the expressions and regenerates only the library's 103-route API reference from exact signed-source rustdoc JSON. All 45 documentation tests, Markdown and canonical checks pass. The full manual has 2,383 pages, 436,424 in-bounds word boxes, zero final warnings and four visually reviewed changed pages. All 3,696 inventoried code/configuration files remain below 1,000 lines; complete semantic authority and private documentation closure remains open. Matching library CI [30](https://git.erikinkinen.fi/erix/lib-dynlink/actions/runs/30)/[31](https://git.erikinkinen.fi/erix/lib-dynlink/actions/runs/31) passes with four complete logs (36,856 bytes), 47 tests per run, strict builds/rustdoc and zero warnings. Docs CI [913](https://git.erikinkinen.fi/erix/docs/actions/runs/913)/[914](https://git.erikinkinen.fi/erix/docs/actions/runs/914) passes with four complete logs (763,872 bytes), 45 tests and 2,383-page renders, zero final warnings. Coherent catalog adoption, complete native source/frame evidence, runnable realms and both full guest build generations remain open. Complete file hashes, manifest records, package/feature identities and both needed-name inventories must agree. Library stripping permits only independently checked administrative header selectors, never executable-byte changes. The retained native closure binds seven objects, 2,373 ordinary functions and 1,608 relocation records. Intake does not yet resolve symbolic providers or compose cross-library frames. All 259 checker controls (28 new) and 16 isolated modules pass; six strict Rust configurations pass 961 tests each, host/native Clippy, private rustdoc and six native builds with zero warnings. Formatting, Markdown and canonical checks pass. All three retained artifact replays preserve their previous frame decisions: 107/70/299 unresolved observations for standalone runtime/all/native. Full frame/source gates retain actual exit 1. Profiling records 0.181 seconds in native dependency intake and 23.17/25.51/24.59 seconds for the three complete profiled runs, within unchanged 60/15-second and 64 MiB budgets. Concurrent Rust validation changes host contention, so elapsed differences from earlier runs are not a speedup or regression claim. Signed Docs `88537b23e1def210eeff40b7ef90fce92fe2009e` documents this contract. All 45 tests and the complete 2,383-page manual pass, with 436,642 in-bounds word boxes, zero final warnings and visual review of the changed page. An initial double-hyphen ligature was corrected and the full render revalidated. The physical census covers 3,704 source/configuration files, all below 1,000 lines; complete semantic authority and private documentation closure remain open. Exact-head Exsh CI 253/254 and Docs CI 915/916 are running. Symbol providers, ordered runtime binding, cross-object frame paths, source membership, coherent catalog adoption, runnable realms and both complete guest builds remain required. Matching closed dependency intake CI — 16 September 2026: [Exsh 253](https://git.erikinkinen.fi/erix/exsh/actions/runs/253) and [254](https://git.erikinkinen.fi/erix/exsh/actions/runs/254), exact `9827896d1cb5ad834589045ee03390aec650df84`, pass 259 checker controls, 16 isolated imports, 961 Rust tests and the strict preceding build/Clippy/rustdoc stages. All four workspace domains per run and Markdown pass. The required full frame gate remains incomplete, with 111/111/74/74 unresolved observations in each CI artifact set. Four complete logs total 315,052 bytes and contain zero warnings. Original local runtime/all/native replays retain separate input identities and 107/70/299 counts. [Docs 915](https://git.erikinkinen.fi/erix/docs/actions/runs/915) and [916](https://git.erikinkinen.fi/erix/docs/actions/runs/916), exact `88537b23e1def210eeff40b7ef90fce92fe2009e`, pass 45 tests and complete 2,383-page renders. Four complete logs total 763,918 bytes. Reference convergence is 35/1/0 warnings across the three TeX passes, with zero final warnings. Both cohorts are classified without rerunning jobs or changing their budgets. The seven-object native dependency inventory is now checked; symbolic providers, ordered runtime binding, cross-object frames and source membership remain incomplete. No runnable realm, coherent product adoption or complete in-EriX build is established. S-only relocations ignore addends, while S+A must retain an exact original executable entry. All 276 checker tests, 17 isolated modules and six strict Rust configurations (961 tests each) pass, including host/native Clippy, rustdoc and six warning-free native builds. Independent original-byte inventory matches all 117 symbolic records: 112 exact function identities and five refused data targets. Provider indexing/reporting takes approximately 16 ms in the captured native profile. Original standalone runtime/all/native replays preserve 107/70/299 unresolved observations and actual exit 1 under unchanged budgets. This is conditional relative identity evidence only: load-base arithmetic, protected slots, cross-object calls/frames and source membership remain incomplete. Signed Docs `24cefeb2dc6d3f163140d32f5fed5a7e1a768ebd` updates the manual contract. All 45 documentation tests pass; the complete 2,383-page render has 436,737 in-bounds word boxes, zero final warnings and visual review of pages 2284–2285. The physical audit covers 3,706 source/configuration files, all below 1,000 lines. No runtime Rust, dependency, linker or workflow inputs changed. New host/CLI controls cover the analyzer behavior; no new guest feature is asserted. Exsh CI 255/256 is terminal: unit/strict/workspace stages pass, and the required full-frame gate remains incomplete. Docs CI 917/918 passes. Acceptance remains 15/459 leaves, 3.48% weighted. Both full in-EriX builds and the complete semantic authority audit remain open. Ordered-provider automatic CI classification — 17 September 2026: Exsh 255/256 at `469bf1f1b9d8301cf98a79d16c7c27660ecda2a1` passes 961 Rust tests, the combined 276-test checker suite, strict preceding stages and all four workspace domains per run. The required full-frame gate fails with 111/111/74/74 unresolved observations per run. Four complete logs total 315,035 bytes with zero warnings. The 17 separate module executions are local evidence; CI uses combined test discovery. Docs 917/918 at `24cefeb2dc6d3f163140d32f5fed5a7e1a768ebd` passes 45 tests and the complete 2,383-page manual. Four complete logs total 763,878 bytes. Reference-resolution passes produce 35/1/0 warnings; final output has zero warnings and no layout overflow. Original API snapshots remain unchanged. Both cohorts are fully classified, without restarting workflows or changing thresholds. Original Integration layout, quota and FAT32 failures remain open, including #58 in Integration. Acceptance remains 15/459 leaves, 3.48% weighted. Complete native source/frame proof, a runnable realm, the full semantic authority audit and both full in-EriX builds remain required. Local control-flow offsets cannot alias a foreign function or transfer the root fallback role. Every captured decode shares the original output/time budgets; a late failure rejects the invocation. All 299 checker tests and 20 separately executed module suites pass. Six strict Rust configurations pass 961 tests each, host/native Clippy, rustdoc and six warning-free native builds; formatting and Markdown checks pass. Original runtime/all replays retain 107/70 unresolved observations. The composed native graph reaches 275 functions with 111 unresolved observations; all three actual checker exits remain 1. Native slots assume successful checked linking and unchanged disjoint mappings. Actual load bases, complete source/frame acceptance and coherent runtime adoption remain open. Profiling identified redundant root-only analysis in native mode. Removing it preserved every composed decision while one profile changed from 41.52 to 25.81 seconds and 64.37M to 39.61M calls. This host profile pair includes observer overhead and gives no general or guest timing guarantee. The final source replay also preserves every decision; three register-proof records now correctly identify symbolic load provenance. Signed Docs `44cd6c4aa95bebfa08c99804fab0f1551f537ae1` specifies the contract. All 45 documentation tests pass; the complete 2,383-page manual has 436,894 in-bounds word boxes, zero final warnings and visual review of the changed page. All 3,713 inventoried source/configuration files are below 1,000 lines. The broader documentation audit retains 108 unchanged older test definitions needing inline docstrings; current production and all new/modified definitions are documented. Runtime Rust, dependency, linker and workflow inputs are unchanged; added behavior has host and real CLI regressions, with no new guest runtime feature asserted. Original Exsh CI 257/258 passes unit/strict/workspace stages and retains the required full-frame failure; Docs CI 919/920 passes. Both cohorts are fully classified. Both full builds inside EriX and complete semantic authority acceptance remain open. Cross-object checkpoint CI classification — 17 September 2026: Exsh 257/258 at `ac9646c84e432129a872737789a9be08f984b881` passes 961 Rust tests, the combined 299-test checker suite, strict preceding stages and four workspace domains per run. Combined discovery also checks isolated module imports; the 20 separate module-suite executions are additional local evidence. The required full-frame gate fails with 111/111/74/74 unresolved observations on the four original CI artifact selections. Four complete logs total 315,180 bytes with zero warnings. Those CI selections remain distinct from the retained seven-object native replay. Docs 919/920 at `44cd6c4aa95bebfa08c99804fab0f1551f537ae1` passes 45 tests and the complete 2,383-page manual. Four complete logs total 763,906 bytes; reference-resolution passes have 35/1/0 warnings, with zero final warnings or layout overflow. Both automatic cohorts are fully classified without workflow restarts or threshold changes. Existing Integration layout, quota and FAT32 regressions remain open. Full native source/frame acceptance, coherent runtime adoption, the semantic authority audit and both full builds inside EriX remain required. Entry tokens carry equality only; they never supply a pointer or call target. A separate earlier callee contract must prove private stack writes before caller slots survive a call. All 329 checker tests and 22 separately executed module suites pass. Six strict Rust configurations pass 961 tests each, host/native Clippy, rustdoc and six warning-free native builds; formatting and Markdown checks pass. Independent eager scheduling controls agree with both filtered worklist orders. Original runtime/all/native replays retain 107/70/111 unresolved observations and actual checker exit 1. The native graph still reaches 275 functions. The startup iterator's unknown pointer writes remain a refusal; complete source/frame and runtime acceptance remain open. Two initial native profiles exhausted the original 60-second budget and produced empty reports; both failures are retained. Immutable decode caches, retirement of exhausted equality state, fact-sensitive wakeups and dependency-first scheduling brought the final native replay within the unchanged budget: 57.45 seconds wall time, 53.94 profiled seconds and 72.27M calls. All 2,373 bodies are inspected once. This bounds one retained host replay and makes no general speedup or guest timing claim. Report schemas and original source, stack, byte and time gates are unchanged. Signed Docs `c3401e5f6bbc19a0ba695219ed551e29a29677ed` specifies the contract. All 45 documentation tests pass; the complete 2,383-page manual has 436,968 in-bounds word boxes, zero final warnings and visual review of both changed continuation pages. All 3,717 inventoried source/configuration files are below 1,000 lines. The touched preservation tests now document 21 older methods; 87 unchanged older test definitions remain in the inline documentation audit. Current production and all new/modified definitions are documented. Runtime Rust, dependency, linker and workflow inputs are unchanged; no new guest runtime feature is asserted. Original Exsh CI 259/260 passes unit/strict/workspace stages and retains the required full-frame failure; Docs CI 921/922 passes. Both cohorts are fully classified. Both full builds inside EriX and complete semantic authority acceptance remain open. Saved-value checkpoint CI classification — 17 September 2026: Exsh 259/260 at `8b6b93a329757ae7f106e235761912b58a67deff` passes 961 Rust tests, the combined 329-test checker suite, strict preceding stages and four workspace domains per run. Combined discovery checks isolated module imports; the 22 separate module-suite executions are additional local evidence. The required full-frame gate fails with 111/111/74/74 unresolved observations on its four original CI artifact selections. Four complete logs total 315,234 bytes with zero warnings. These CI selections remain distinct from the retained seven-object native replay. Docs 921/922 at `c3401e5f6bbc19a0ba695219ed551e29a29677ed` passes 45 tests and the complete 2,383-page manual. Four complete logs total 763,958 bytes; reference-resolution passes have 35/1/0 warnings, with zero final warnings or layout overflow. Both automatic cohorts are fully classified without workflow restarts or threshold changes. Existing Integration layout, quota and FAT32 regressions remain open. Full native source/frame acceptance, coherent runtime adoption, the semantic authority audit and both full builds inside EriX remain required. Scoped masks never enter the unconditional function index; loaded words, unknown contents, released storage and recursive assumptions supply no binding. All 355 checker tests and 23 separately executed module suites pass. Six strict Rust configurations pass 961 tests each, host/native Clippy, private rustdoc and six warning-free native builds. Formatting, templates and Markdown pass. Original runtime/all/native replays retain 97/60/97 unresolved observations and actual exit 1. The native graph reaches 275 functions; the startup iterator now has caller-bound preservation for its exact live buffers. Complete source/frame and runtime acceptance remain open. Profiling exposed repeated failed argument specializations. Mandatory opaque-prefix refusals, conservative GP demand and rejection-only control candidates avoid unnecessary interpretations without changing the original 60-second limit. Candidate records cannot become proofs, and incompatible fact kinds defer to actual interpretation: losing pointer identity can enable numeric refinement. Positive and negative controls compare filtered and eager behavior. Each CFG site has at most one pending visit and later changes still enqueue it without an iteration cap; every native proof decision agrees with the prior queue. The final ordinary native replay takes 39.80 seconds. Complete tracing still exhausted the original deadline; failures and empty reports are retained. A separately identified selective profile measures only caller-context analysis: the complete invocation takes 56.59 seconds, with 26.92 profiled seconds in that scope. Instrumentation preserves the complete proof result. Different profiling scopes are not timing comparisons, and no guest performance claim is made. The replay selects 367 instances, evaluates 587 bodies, proves 190 and defers 51 candidate bodies for incompatible domains. Signed Docs `fc3ee44748c20a3aa6f55bd85ac1913c707e5d4e` specifies these contracts. All 45 documentation tests pass. The complete 2,385-page manual has 437,275 in-bounds word boxes, zero final warnings and visual review of the changed pages. All 3,721 inventoried source/configuration files are below 1,000 lines. All new/modified definitions are documented; 87 unchanged older test definitions remain in the audit. Runtime Rust, dependencies, linker and workflow inputs are unchanged. Original Exsh CI 261/262 passes unit/strict/workspace stages and retains the required full-frame failure; Docs CI 923/924 passes. Both cohorts are fully classified. Complete semantic authority acceptance, coherent runtime adoption and both full builds inside EriX remain required. Caller-bound checkpoint CI classification — 17 September 2026: Exsh 261/262 at `e7ba974e96ee77a41c6a861150da843d4c84c7d6` passes 961 Rust tests, the combined 355-test checker suite, strict preceding stages and four workspace domains per run. Combined discovery checks isolated module imports; the 23 separate module-suite executions are additional local evidence. The required full-frame gate fails with 101/101/64/64 unresolved observations on its four original CI artifact selections. Four complete logs total 315,210 bytes with zero warnings. These CI selections remain distinct from the retained seven-object native replay. Docs 923/924 at `fc3ee44748c20a3aa6f55bd85ac1913c707e5d4e` passes 45 tests and the complete 2,385-page manual. Four complete logs total 764,350 bytes; reference-resolution passes have 35/1/0 warnings, with zero final warnings or layout overflow. Both automatic cohorts are fully classified without workflow restarts or threshold changes. Existing Integration layout, quota and FAT32 regressions remain open. Full native source/frame acceptance, coherent runtime adoption, the semantic authority audit and both full builds inside EriX remain required. Removed selector 0x70 remains explicitly rejected; runtime ABI and generated API snapshots are unchanged. All 45 documentation tests, Markdown and template checks pass. The complete 2,385-page manual has 437,463 in-bounds word boxes, no final warnings, and visual review of pages 142 and 163. Rust and VM checks are inapplicable to these two prose-only changes. Original automatic [CI 927](https://git.erikinkinen.fi/erix/docs/actions/runs/927) and [CI 928](https://git.erikinkinen.fi/erix/docs/actions/runs/928) both pass. All four complete terminal logs total 764,750 bytes; reference passes resolve with 36/1/0 warnings and the final manual is warning-free. Issue 9 is repaired and closed. No full self-hosting acceptance is claimed. All 45 documentation tests and Markdown/template checks pass. The complete 2,387-page manual has 437,732 in-bounds word boxes and no final warnings; pages 146, 166, 168 and 169 were visually reviewed. Runtime tests are inapplicable to this documentation-only change. Original [CI 929](https://git.erikinkinen.fi/erix/docs/actions/runs/929) and [CI 930](https://git.erikinkinen.fi/erix/docs/actions/runs/930) both pass. All four complete terminal logs are classified; both full 2,387-page manual builds have zero final warnings. Issue 10 is closed for the corrected documentation drift. No complete guest build is established. Both complete guest builds and dependent runtime/source proof remain open. Borrowed syscall capture reference — 17 September 2026: signed `2435bf5ed105fbe2af0349088b2ae600d4b598fd` documents the complete entry prefix and refusal before operation dispatch. This documentation checkpoint does not imply runtime or complete guest-build acceptance. Runtime and full guest-build acceptance remain separate. Complete compiler-source admission, ordinary runtime adoption and both full guest builds remain open. Complete compiler-source admission, ordinary runtime adoption and both full guest builds remain open. Typed mediator bootstrap, ordinary service-image adoption and both complete EriX builds inside EriX remain open. Complete builds inside EriX and ordinary service-image adoption remain open. Corrected original manual CI — 18 September 2026: Docs `10ea454ebab2cb0ca465cedf52ff619c1fc7efd4` passes original [CI 947](https://git.erikinkinen.fi/erix/docs/actions/runs/947) and [CI 948](https://git.erikinkinen.fi/erix/docs/actions/runs/948). All four logs are complete (765,634 bytes), all 45 tests pass, and the complete 2,389-page manual has zero final warnings after reference passes of 36/1/0 warnings. The later generation-bound cleanup manual update is still under local validation. Generation-bound cleanup consumer acceptance — 18 September 2026: Signed revision `323da983653e6d6d25d012c2354f97afaaaa0699` is pushed. Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain open. Original cleanup manual CI acceptance — 18 September 2026: Signed Docs `323da983653e6d6d25d012c2354f97afaaaa0699` passes [CI 949](https://git.erikinkinen.fi/erix/docs/actions/runs/949) and [CI 950](https://git.erikinkinen.fi/erix/docs/actions/runs/950). This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements. Returned-grant bootstrap custody design — 18 September 2026: Add distinct Procd PREPARE_REALM_BOOTSTRAP (0x432) on the existing private Launchd route. The native pending caller must match a retained running Launchd generation. Its exact 32-byte request carries u32 request ID, opcode, original process/generation, source and original destination install-grant slots, then two zero words. The actual sole receipt must be INSTALL_GRANT with exactly GRANT|MINT. Slots are full-width descriptions; receipt, live inventory and native matching-grant checks establish custody. Previously guarded, started, stale, ordinary-role and malformed stages refuse before new effects. Reserve exact rollback ownership first. Use the real returned grant and native operation 53 to narrow the Created child's primary endpoint to RECV. Establish an ancestor SEND branch under Kernel lifetime custody and a distinct nested explicit revoker before any export. Retain the nested sender privately; dispose the original master, unguarded sender and ancestor-only bypass aliases. The returned install grant stays exclusively owned for later typed installation. No new endpoint factory or expanded Process endpoint policy is implied. The exact 32-byte capability-free reply echoes request/opcode/result/process/ generation, followed by a u32 custody state and two zero words. State 1 occurs exactly with OK and confirms only guarded unstarted-stage custody; failure state 0 is not absence proof. Lost reply, rollback, abort, supervisor loss and terminal cleanup must account for every reused scratch column, actual guard and exact child identity. Uncertain disposal prevents reuse and ordinary continuation. Keep ordinary mediator starts denied. Counted final receivers/configuration, owned fair intake/provider/retirement progress, private execution, authenticated readiness, initial receiver disposal, seal/publication, real two-realm client I/O and both complete builds inside EriX remain required. Host models or this guarded stage acknowledgment cannot substitute for those acceptance gates. Runtime realm orchestration, actual consumer VM execution, fair progress and both complete builds inside EriX remain open requirements. Runtime consumer VM, complete realm fairness and full guest-build acceptance remain open. Caller-local grant relocation design — 18 September 2026: Add immediate x86_64 syscall `0x54`, `RELOCATE_LOCAL_GRANT`, taking source slot in argument 0 and destination slot in argument 1. Both fit u32, are nonzero and distinct; arguments 2–5 are zero. The return is the exact result in rax with zero auxiliary value. Admission uses the actual current Running native process and nonzero generation, checks both slots against its syscall window, and accepts only an actual held INSTALL_GRANT or REVOCATION_GRANT with its matching native record. Movement uses the existing unique-record rebinding within that same native CSpace; rights, child/generation installation scope and revocation lineage are preserved. No grant is constructed, copied, attenuated or retargeted. Malformed register shape rejects before context lookup; caller/window checks precede source lookup, then type/binding checks precede empty-destination admission. Ordinary validation refusal leaves inventory unchanged. The transition is serialized with process-terminal and reply-authority lifecycle changes. Owned CLAIM already selects receiving destinations before exposing request bytes; this operation lets a producer validate the received grant and then relocate it into an existing per-process custody slot. The operation itself does not validate a bootstrap request, install child authority or acknowledge application retirement. It adds no Process endpoint selector or general CNode route. Literal register, foreign/terminal caller, missing/fake binding, occupied destination, exact-rights/scope and actual CPL3 controls are required, followed by coordinated producer/consumer adoption and the remaining realm VM gates. Original deferred-cleanup manual CI acceptance — 18 September 2026: Signed Docs `da66c0efd61fc05be023210e1c0c58196b51b878` passes [CI 953](https://git.erikinkinen.fi/erix/docs/actions/runs/953) and [CI 954](https://git.erikinkinen.fi/erix/docs/actions/runs/954). This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements. Actual owned service adoption, consumer VMs, complete realm fairness and both full builds inside EriX remain open. Owned receiver request-budget contract — 18 September 2026: Extend register-only REGISTER (0x4C) to take the actual local RECV slot, maximum request payload bytes and maximum request capability count in arguments 0–2; arguments 3–5 remain zero and successful RDX is zero. Both budget values are explicit receiver declarations. Zero/zero admits only empty requests. The byte/slot/receipt receive layout must be addressable and capability capacity must fit native private CSpace storage. The actual Running generation and held generic RECV endpoint remain the registration authority. Exact repeated registration is idempotent only with the same budget; a different budget or owner conflicts without modifying the original registration. Replacement follows the existing actual receiver-binding removal and exact native retirement rules. SUBMIT compares actual payload length and capability count against that exact registration before request allocation, private-space reservation, native transfer or invocation serial acceptance. Oversized requests return ordinary INVALID_ARGUMENT with zero owner ID and unchanged source custody. The packet decoder passes its checked capability iterator directly to native preparation, removing its redundant temporary vector. Accepted invocation, result-budget, delivery, draining and retirement contracts remain explicit. Migrate every producer and fixture to the new signature without a deprecated unbounded fallback. These budgets describe service-owned receiving storage; they add no global CALL-size ceiling, user-pointer retention, foreign selector or capability grant. Literal malformed/zero/exact registration controls, rejected-inventory checks, actual CPL3 calls and existing VM oracles are required. Then connect the owned Procd/Launchd bootstrap path through its held private route, actual claimed caller identity, server-chosen grant receipt and local relocation, retaining each committed/draining owner through exhaustive cleanup. Actual consumer VMs, complete fair realm progress and both full guest builds remain open acceptance requirements. Original local grant relocation manual CI acceptance — 18 September 2026: Signed Docs `623609ee627a4afba1340ee06c53678c4a562a88` passes [CI 955](https://git.erikinkinen.fi/erix/docs/actions/runs/955) and [CI 956](https://git.erikinkinen.fi/erix/docs/actions/runs/956). This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements. Explicit owned receiver admission acceptance — 18 September 2026: Signed `8361618f3f047479a9e52ffaba7f2607be99413c`. The manual documents explicit receiver request limits, complete layout addressability, immutable registration and pre-custody refusal, with accurate allocation-observation scope. Actual owned Procd/Launchd service adoption, consumer VM execution, complete realm fairness/readiness/sealing and both full builds inside EriX remain open. Owned guarded-bootstrap service contract — 18 September 2026: Migrate PREPARE_REALM_BOOTSTRAP to native owned request/result custody on the already held private Launchd-to-Procd endpoint. Its exact 16-byte body contains request/opcode/process/generation only; remove obsolete source and destination slot descriptions. The canonical capability-free response remains 32 bytes. No legacy bootstrap transport fallback is retained. Procd registers explicit 16-byte/one-capability request limits, supplies an actually empty local receiving slot, validates the committed receipt type and rights and matches the native claimed origin to the retained Running Launchd generation. It validates the exact staged mediator row and actual grant scope before adopting the grant into that row through caller-local relocation. Existing launch-description staging may be reused only with explicit exclusive ownership and proved completion of its former cleanup; add no broad Process authority or per-realm scratch column. Numeric identity or receipt metadata never replaces actual possession or scope validation. The running service loop must give native retirement a turn before owned bootstrap and ordinary intake. Retain nonzero delivery/invocation owners, received authority, exact child rollback and first cleanup failure through committed/draining outcomes. Complete every independent local and child retirement action before relinquishing bookkeeping; uncertain cleanup cannot return a service to ordinary work. Authenticate actual native origin and revalidate the original supervisor before effects; do not manufacture legacy pending-caller or source-slot receipts. Replace Launchd synchronous bootstrap exchange with retained progress driven by its actual runtime orchestration. Success requires a canonical correlated result, actual source-grant absence and complete invocation retirement. Connect this to authenticated staged realm preparation, with no public numeric shortcut into a prepared process. Preserve ordinary start refusal until realm configuration, readiness and sealing are complete. Acceptance requires adversarial ownership/cancellation/partial-cleanup host controls, strict coordinated builds and real producer/consumer VM execution. Native primitives alone do not establish service adoption, complete fairness or a full guest build. Existing ordinary source/effect/frame and two complete EriX-in-EriX build gates remain unchanged. Original receiver admission manual CI acceptance — 18 September 2026: Signed Docs `8361618f3f047479a9e52ffaba7f2607be99413c` passes [CI 957](https://git.erikinkinen.fi/erix/docs/actions/runs/957) and [CI 958](https://git.erikinkinen.fi/erix/docs/actions/runs/958). This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements. Actual Launchd runtime orchestration, consumer VM execution and both complete guest builds remain open. Original owned bootstrap manual CI acceptance — 18 September 2026: Signed Docs `5c1cf6da319787738fa03f3cc6f526e49604aa09` passes [CI 959](https://git.erikinkinen.fi/erix/docs/actions/runs/959) and [CI 960](https://git.erikinkinen.fi/erix/docs/actions/runs/960). This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements. Original realm supervisor and producer cancellation contract — 18 September 2026: Extend BEGIN_MATERIALIZATION to an exact 64-byte body. Its existing 56-byte semantic image description is followed by two full-width u32 fields: original supervisor process ID and generation. Both are nonzero only for the realm mediator role; both must be zero for every other role. Reject the obsolete 56-byte shape. Coordinate the shared codec, Loaderd and Procd through one original pinned dependency graph. On PREPARE_REALM, Loaderd obtains the supervisor pair from the actual native pending caller on its private Launchd receiver. Procd authenticates the actual Loaderd caller on its materialization receiver and matches the forwarded supervisor to its retained Running Launchd generation before any child effect. The pair describes delegated lifecycle responsibility; numbers alone never confer creation, installation or rollback authority. Retain that original owner before materialization and through grant handoff, native submit/claim and guarded staging. Supervisor terminality retires active preparation and every corresponding stage before unrelated provider cleanup. Guard admission must match the original supervisor, never replace it with a later claimant. Launchd retains child rollback and native invocation ownership separately. Caller RELEASE initiates cancellation and must precede any ordinary abort request that could wait behind Procd delivery retirement. RELEASE is not an application rollback acknowledgment: preserve the exact child obligation until its separate cleanup proof. Procd exhausts independent local and child cleanup before server RELINQUISH. Both parties retain nonzero native IDs and the first cleanup failure through draining; no uncertain state returns to ordinary work. Actual Launchd runtime preparation and scheduler adoption, deployment-sized ownership storage, adversarial host controls and real producer/consumer VM execution remain required. Guarded staging does not authorize ordinary start or establish configuration, readiness, sealing, complete fairness or either full EriX build inside EriX. Existing source, effect and frame gates remain. Actual Launchd owned runtime adoption, consumer VM execution and both full guest builds remain open. Original supervisor manual CI acceptance — 18 September 2026: Signed Docs `a410759e5515b18107f25efb0319ad7c85871a64` passes [CI 961](https://git.erikinkinen.fi/erix/docs/actions/runs/961) and [CI 962](https://git.erikinkinen.fi/erix/docs/actions/runs/962). This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements. Caller-bound realm admission and retained storage contract — 18 September 2026 Use distinct Launchd operations BEGIN_REALM 0x6D0, PREPARE_REALM 0x6D1, ABORT_REALM 0x6D2 and READ_REALM 0x6D3. The existing 0x6B0–0x6BF range belongs to filesystem providers and is not reused. Little-endian bodies are exact, with nonzero request correlation and no fallback to ordinary launch transactions. BEGIN_REALM is an authority-free 8-byte request (request ID, operation). Derive session, authority realm, original process/generation and Running job from the actual native pending caller. Reserve an independently budgeted realm record, a nonwrapping generation and one disjoint executable-scope receipt slot before replying. Client numeric identities or a bearer sender cannot select ownership. PREPARE_REALM has a 32-byte prefix: request ID and operation (u32), realm record ID and generation (u64 each), and selector byte length (u64), followed by exactly that nonempty UTF-8 selector without NUL. Parsing adds no pathname or packet-size ceiling. The request carries exactly one actual SEND-only directory endpoint to the reserved receipt slot. Verify the original caller/job/session/authority realm again and retire every unretained received capability on refusal. Resolve only inside this explicit directory, authenticate the exact executable and manifest, and call Loaderd's existing private PREPARE_REALM. Never imply a Posixd pathname, Named route, root, cwd, TTY stream, ordinary job or public PreparedProcess input. ABORT_REALM and READ_REALM are authority-free 24-byte requests: request ID, operation and complete realm-record ID/generation. They require the same original Running native owner. READ observes retained state only; ABORT must complete independent source, invocation and exact-child retirement before its successful acknowledgment. Parent terminality initiates the same retained cleanup internally. All four operations have an exact 40-byte capability-free response: request ID, operation, raw result and state (u32 each), record ID and generation (u64 each), receipt slot and zero reserved word (u32 each). States are Unconfirmed=0, Reserved=1, Preparing=2, Guarded=3, Retiring=4 and Retired=5. Success at BEGIN requires Reserved, a nonzero complete handle and receipt slot. PREPARE success requires Guarded; ABORT success requires Retired. READ returns an authenticated nonzero state. Only successful BEGIN returns a receipt slot; every other result has zero there. Failure always has Unconfirmed state; failed BEGIN has a zero handle while other failures echo the original complete request handle. Unknown nonzero result codes remain full-width. Unconfirmed proves no resource absence. Correlate the complete response with the original request before using evidence. Replace obsolete LCH1 v2 with exact 72-byte version3 startup policy. Preserve the first 68-byte field order and append realm_capacity (u32 at offset68). Require an explicit deployment value: zero disables new realm reservations, and nonzero values allocate that many retained records and disjoint receipt slots. Validate checked job-route + stream-route + realm-receipt arithmetic before leaving any ordinary transaction receipt storage. No default or incidental fixed array sets realm count. Coordinate shared startup codecs, Rootd payloads, Launchd arena and Integration policy/packaging; old version/width must reject. Extend the native capacity descriptor with the realm record's size/alignment and a new layout version; do not assume ordinary reply records survive long enough for realms. Keep original child, local scope/grant obligations and native invocation owners independent. Actual scheduler progress must exclude ordinary and indirect blocking peer calls while any native invocation needs progress. A permanently discharged source slot is never revisited after reuse. Native release precedes ordinary exact-child abort; preserve first errors and exhaust independent cleanup without returning uncertain state to normal operation. Guarded staging remains private and unstarted, without exported SEND or a Running job. This initial admission interface does not define configuration, readiness, sealing or publication. Coordinated host negatives, strict source-bound build matrices and real consumer VM execution are required. Two mediator processes, two clients per realm with actual mediated I/O, complete fair progress, source/effect/frame admission and both full builds inside EriX remain separate open acceptance requirements. Original retained caller manual CI acceptance — 18 September 2026: Signed Docs `4dcbc10e32ebf257139bcbaf07bc1081b9589780` passes [CI 963](https://git.erikinkinen.fi/erix/docs/actions/runs/963) and [CI 964](https://git.erikinkinen.fi/erix/docs/actions/runs/964). This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements. Actual runtime admission, coherent image consumers, mediated client I/O and both full guest builds remain open. Original realm admission manual CI acceptance — 18 September 2026: Signed Docs `9868cf0e6f2c366b4a2c7992594a83c72789f1f0` passes [CI 965](https://git.erikinkinen.fi/erix/docs/actions/runs/965) and [CI 966](https://git.erikinkinen.fi/erix/docs/actions/runs/966). This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements. Complete mediated execution and both full builds inside EriX remain required. Original exact preparation manual CI acceptance — 18 September 2026: Signed Docs `880bdc59818b1eff9cf9929004680f354f8265a0` passes [CI 967](https://git.erikinkinen.fi/erix/docs/actions/runs/967) and [CI 968](https://git.erikinkinen.fi/erix/docs/actions/runs/968). This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements. The manual describes public realm intake, independently held replies, original-parent cleanup and fair native progress before ordinary dispatch, while preserving separate consumer VM and guest-build acceptance. Original public realm dispatch manual CI acceptance — 18 September 2026: Signed Docs `099f0c570414ca486bb2104c1510fbf3b84d59fb` passes [CI 969](https://git.erikinkinen.fi/erix/docs/actions/runs/969) and [CI 970](https://git.erikinkinen.fi/erix/docs/actions/runs/970). This closes the manual CI observation recorded above; complete Integration catalog, runnable realm and guest-build acceptance remain separate open requirements. Coherent catalog adoption and actual consumer VMs remain required before image acceptance; no runnable realm or full guest build is claimed. Original coherent realm source CI acceptance — 18 September 2026: Signed `33733ceba228669e27152aee32f997d6c72264ff` passes [CI 972](https://git.erikinkinen.fi/erix/docs/actions/runs/972) and [CI 971](https://git.erikinkinen.fi/erix/docs/actions/runs/971). Coherent catalog publication, actual consumer VMs and full guest-build acceptance remain separate open requirements. Native external-toolchain rebuild requirement — 19 September 2026: Signed `b54d28e755dd415079100a19683ee1474edb4ed1` makes the native rebuild an explicit Phase 6 verification and acceptance gate. The first compiler may be cross-built for EriX against its libc/sysroot, Rust OS bindings and declared C/C++ runtime closure. The extended development image must then rebuild the selected upstream Rust/LLVM toolchain inside EriX using supplied offline recipes and an explicit bootstrap compiler. Require working guest-built tools and use in at least one full EriX build, with no unrecorded porting changes, downloads, Linux executables or host build delegation. Complete source, runtime, log and measured-resource evidence is required; compiler ownership remains distinct. All 45 documentation tests and the full 2,419-page manual pass, with 445,775 in-bounds word boxes, actual visual review of the changed page and zero final warnings. Shared API snapshots are unchanged. [The phase master](https://git.erikinkinen.fi/erix/integration/issues/65), [toolchain issue](https://git.erikinkinen.fi/erix/integration/issues/7) and [full-build issue](https://git.erikinkinen.fi/erix/integration/issues/9) contain the matching requirements. Original documentation CI is under observation; the native toolchain rebuild and both OS builds remain unproven. ## Tracking and rollout Local prerequisite acceptance — 29 September 2026: the receipt-preservation correction is complete in signed Integration `d68a95870076c3435b1a5ab36440d0941b5ab45e`, with matching producer adoption in Lib-cstd `a76f6faa1eabe30d9a596d9e9650236ca6463d8c` and Integration `e4ffe2efcf4f06386ffc72d227c4d9c9646e86d1`. The caller-loss manual contract is signed and pushed as Docs `e94d7c56dde026b407f85b75c9a2664b5f7756bf`. All 45 documentation controls and the complete 2,657-page manual pass with zero final warnings. All 492,046 rendered word bounds pass; the changed contract and neighboring pages were visually checked. The helper's native behavior and whole lifecycle requirement remain pending. Remaining local Rust checks will run with compiler work serialized after a retained progress-deadline failure. No CI monitoring is being performed. Caller-loss startup boundary — 29 September 2026: source audit found that the draft helper could not use the ordinary Exsh manifest as planned. Launchd derives fixed routes from the authenticated manifest: the ordinary entry supplies a redirection resolver even if the request omits its destination, and does not declare inherited launch. Host transport tests alone did not establish the helper's actual startup authority. The earlier full validation attempt was explicitly cancelled with owned-child cleanup before changing its frozen source; it is not native acceptance. The implementation now packages a distinct `/bin/realm-owner-loss-caller` entry backed by the same Exsh artifact. Its manifest declares only cwd and inherited launch, with zero authority rows and no resolver or observation broker. The original Exsh graph root and ordinary startup inventory remain intact. In the selected diagnostic image, immutable LCS1 command-entry evidence selects the reduced inventory; argv cannot select it. Exact helper commands are required, with no environment or extra description records. Every architectural capability slot is checked, including absence of excess authority. The existing status-only parent wait and original VM gates are preserved. Four focused startup controls, eight actual transport controls, strict native all-feature Clippy, five graph/manifest/installer controls, seven existing generic-manifest controls and six scenario controls pass. Installer controls exercise the actual validation and generated alias/sidecar commands; they do not claim an ext4 mount or native execution. The updated manual passes 45 controls; its complete render remains pending. A corrected full Exsh matrix is running. Coordinated signed source adoption, full Integration validation, native execution and original CI are still required. No lifecycle checkbox or completion credit is added. Matched native performance evidence — 28 September 2026: both original startup captures pass the unchanged 120/45-second gates without warnings. The matched old/new Kernel comparison uses identical tools, firmware, normalized VM configuration and all 66 other runtime ELF/shared-object artifacts. Translated-instruction upper bounds fall from 38,281,446,500 to 37,372,677,139 (2.37%); the reported mapping-batch candidate groups fall from 11,178,003,410 to 10,355,082,032 (7.36%). These bounded counters indicate less work, not completed-instruction counts or an elapsed-time speedup: the instrumented runs take 55.36 and 55.75 seconds respectively. The rejected earlier comparison remains retained because its producer graph differed. This completes the borrowed-mapping dependency's matched performance validation and the fourteen-snapshot numerical nonexecution witness already recorded here. Signed roadmap-only updates ([kernel 1363f0c5](https://git.erikinkinen.fi/erix/kernel/commit/1363f0c5f3d09d8e8e3388c388137663312c28fd), [docs d72f0a57](https://git.erikinkinen.fi/erix/docs/commit/d72f0a572854bb33e98cbabcd8299593da375dff), [integration 324cc4da](https://git.erikinkinen.fi/erix/integration/commit/324cc4dad331fe53ab2bb0a4b7cb3f49b822cccd), [lib-cstd 50b9d289](https://git.erikinkinen.fi/erix/lib-cstd/commit/50b9d28919a0dd64a31ccd05671f9c75a57da83b)) record the results; selected runtime, helper, catalog and manual source bytes are unchanged and retain their exact prior evidence. Fresh documentation/policy/diff and applicable formatting checks pass. New original CI is registered independently. Whole lifecycle acceptance remains open through supervisor-loss and remaining partial-cleanup/exhaustion checks; complete guest EriX and external Rust/LLVM rebuilds remain required and unproved. No new checklist credit is claimed. Docs original CI1103/1104 fails, with one fully validated manual job and three failed job logs returning HTTP 500. [Docs bug 11](https://git.erikinkinen.fi/erix/docs/issues/11) records exact jobs and unknown cause. Kernel CI706/707 and Lib-cstd CI13/14 pass; original Integration runs remain monitored. [Integration receipt bug 99](https://git.erikinkinen.fi/erix/integration/issues/99) has coordinated host/native evidence but remains open pending original CI. No unchanged failing CI was rerun for acceptance. Prioritize completing each checklist item fully in one sustained pass: implementation, security/reliability audit, required validation, documentation, signed publication and complete CI review before unrelated work. Keep genuine blockers explicit and do not substitute intermediate checkpoints for full acceptance. The active remaining realm-lifecycle item includes positive numerical NeverExecuted accounting, abort/retire and partial-cleanup paths, supervisor loss and resource-ceiling validation. Already accepted native disposal/reuse and pool refusals remain prerequisites. Unrelated optimizations and regressions stay tracked unless evidence makes them dependencies. This execution priority does not change the phase scope, original gates or completion arithmetic. Exact Launchd 2-realm/4-client/576-byte, Procd 38-record and Pagerd 102-binding budgets require reclamation. All six actual successful client exits, realm/client/plan refusals and original capability routes remain intact. The client VM and older preparation/startup VMs pass every original marker, exit and 120/45-second gate. Retained client evidence binds 109 artifacts, 57,045 serial bytes, empty QEMU stderr and zero warnings. This accepts the native disposal/reuse sub-item. Separate positive NeverExecuted CPU accounting remains required: the first capture was rejected before boot because the host GDB package changed; after RPM identity/API verification and fresh two-positive/twenty-negative verifier controls, a separate capture reached the original 120-second limit after five Measured commits, before either NeverExecuted snapshot. Its failed result and cleanup are retained. No deadline, guest byte, authority or oracle was weakened; no numeric completion or speedup is claimed. All fourteen Exsh development/release selections pass 988 tests each, strict host/native builds, Clippy, rustdoc and 355 checker controls pass without warnings, while [native frame proof issue 4](https://git.erikinkinen.fi/erix/exsh/issues/4) stays open. Docs CI1099/1100 passes 45 document controls and the complete 2,657-page manual with zero final warnings. Integration passes its 187 host commands. Original [CI1824](https://git.erikinkinen.fi/erix/integration/actions/runs/1824) passes all 492 scenarios and subsequent image/input gates. [CI1823](https://git.erikinkinen.fi/erix/integration/actions/runs/1823) instead stops in the known [physical utility host fixture](https://git.erikinkinen.fi/erix/integration/issues/74), before catalog VMs. The companion pass does not resolve that intermittent failure. All 22 original Integration runs 1803–1824 now have complete reviewed logs: 66 logs, 264,989,379 bytes, zero warning candidates. The [smoke-policy defect](https://git.erikinkinen.fi/erix/integration/issues/96) is closed on its source correction and matching full-CI evidence. Remaining observations are retained under [pipeline](https://git.erikinkinen.fi/erix/integration/issues/91), [ext4 quota](https://git.erikinkinen.fi/erix/integration/issues/73), [physical consent](https://git.erikinkinen.fi/erix/integration/issues/78), [interrupt reuse](https://git.erikinkinen.fi/erix/integration/issues/54), [canonical release](https://git.erikinkinen.fi/erix/integration/issues/47), and the new canonical-template reports for [release COM1 editor](https://git.erikinkinen.fi/erix/integration/issues/97) and [canonical development](https://git.erikinkinen.fi/erix/integration/issues/98). Their causes are not inferred from wrapper failures, and no unchanged CI job was rerun. The phase checklist now records **419/879 completed sub-items**, **17/460 accepted parents**, and **15.45% weighted progress**. Numerical NeverExecuted accounting, remaining authority/lifecycle cleanup, complete CI/frame acceptance, external Rust/LLVM/toolchain rebuilding and both complete EriX builds inside EriX remain required and unproved. Both stale-client generations must remain absent. All six actual successful client exits, realm/client/plan capacity refusals, original capability routes and the 120/45-second guest gates remain mandatory. Independent native accounting must positively capture two zero-CPU NeverExecuted clients, six Measured clients and six Measured mediators. Local cancellation or absence cannot substitute for those records. The preceding shell fails at call 88 in the independent 141-call transcript; all eight focused controls pass on the new source. All fourteen ordinary development/release selections pass 988 tests each under unchanged limits, with strict host/native builds, Clippy, doctests, private rustdoc and 355 frame-checker controls passing without warnings. All six separate local optimized frame observations produce incomplete reports and retain exit 1: runtime 271/97, all-features 298/63 and configured clients 323/100 reached/unresolved in both deployment profiles. These are not accepted frame proofs. Original [Exsh CI 291](https://git.erikinkinen.fi/erix/exsh/actions/runs/291) and [292](https://git.erikinkinen.fi/erix/exsh/actions/runs/292) each pass 988 unit tests and 355 checker controls, then fail the still-open [native frame proof](https://git.erikinkinen.fi/erix/exsh/issues/4). Their own artifacts report runtime 256/101 and all-features 288/68 in both profiles. All four complete logs, totaling 323,674 bytes, are reviewed with zero warnings and no additional compiler or test failure. Native frame counts belong to their exact build configurations; different observations are not combined into a proof or speedup claim. All 45 document controls, Markdown/template/link/reference checks, the complete 2,657-page manual and all 491,759 word bounds pass; three affected/adjacent pages are visually reviewed. Original [Docs CI 1099](https://git.erikinkinen.fi/erix/docs/actions/runs/1099) and [1100](https://git.erikinkinen.fi/erix/docs/actions/runs/1100) pass, with all four complete logs reviewed and zero final warnings. Integration passes all 187 host commands: 174 helper controls, six profiler commands, strict orchestration Clippy, both unit selections, formatting, dependency policy, Markdown and diff checks. All 76 original source signatures and transitive dependency closure pass. The fresh structural audit finds all 3,196 code files below 1,000 lines and missing_docs gates at all 98 detected crate roots; this does not replace semantic authority review. Original [Integration CI 1823](https://git.erikinkinen.fi/erix/integration/actions/runs/1823) and [1824](https://git.erikinkinen.fi/erix/integration/actions/runs/1824) are queued. The isolated coordinated image build and configured-client VM are running. Its native result, older preparation/startup regressions and the separate positive NeverExecuted accounting capture remain pending. The observer's two positive host transcripts and twenty negative cases establish verifier behavior only. No new checklist acceptance or progress credit is claimed. Remaining authority/lifecycle work, full CI, native frame proofs, external Rust/LLVM/toolchain rebuilding and both complete EriX builds inside EriX remain required. Native nonexecution contract checkpoint — 25 September 2026: signed [Docs 47e68b07](https://git.erikinkinen.fi/erix/docs/commit/47e68b079bf36d8a42c8bc5a330b72a352e56075) specifies retirement of two fully provisioned clients before either START, followed by another generation of record reuse while the original peer stays sealed. Six actual successful client exits, capacity refusals, exact budgets and the existing 120/45-second VM gates remain mandatory. Independent native accounting must positively capture two zero-CPU NeverExecuted clients, six Measured clients and six Measured mediators, with original successful commits and final protected backing. Local cancellation or absence cannot substitute for that evidence. All 45 document controls and Markdown/template/link/reference checks pass. The complete 2,657-page manual builds without final warnings; all 491,759 word bounds pass and three affected/adjacent pages are visually reviewed. Original [CI 1099](https://git.erikinkinen.fi/erix/docs/actions/runs/1099) and [CI 1100](https://git.erikinkinen.fi/erix/docs/actions/runs/1100) are running. The local shell extension passes eight controls across an independent 141-call transcript; the preceding probe fails at the missing retirement operation. The host accounting observer passes two positive transcripts and twenty negative cases. Complete shell validation is running; signed shell publication, catalog adoption, native execution and native accounting remain pending. No checklist acceptance or additional progress credit is claimed. The distinct compiler regression is resolved in [Exsh issue 9](https://git.erikinkinen.fi/erix/exsh/issues/9); [native frame proof](https://git.erikinkinen.fi/erix/exsh/issues/4), remaining authority/lifecycle work, external toolchain rebuilding and both complete EriX builds inside EriX remain required. Documentation status now records the accepted native client/plan ceilings in signed [Docs a1444c6b](https://git.erikinkinen.fi/erix/docs/commit/a1444c6b8d207286370339f989232ba746bb2a12). Only ROADMAP changes; 45 fresh document tests, Markdown/template and dependency checks pass without warnings. Manual, tooling and reference bytes retain the earlier fully validated identity. No new manual build is claimed. Valid counts independently exhaust each free pool, require exact RESOURCE_EXHAUSTED and unchanged Guarded/Sealed peers, then allow normal configuration. The client VM and older preparation/startup VMs pass with every original marker, native exit and 120/45-second gate. Retained client evidence contains 109 artifacts and 57,045 serial bytes, with empty QEMU stderr and zero image warnings. Independent BootConfig decoding verifies 2 realm records, 4 client records and 576 plan bytes; packaged Procd/Pagerd layouts retain 38 records and 102 bindings. Requests add no capability or guest inspection route. The phase checklist now has **417/877 completed sub-items**, **17/460 accepted parents** and **15.43% weighted progress** after exact recalculation. This accepts the two configuration-storage ceilings. Existing compiler/frame gates, supervisor loss, partial cleanup, NeverExecuted accounting, complete CI review, external Rust/LLVM/toolchain rebuilding and both full EriX builds inside EriX remain required. All earlier failures are retained, and no unchanged CI job was rerun. Original [CI1799](https://git.erikinkinen.fi/erix/integration/actions/runs/1799) and [CI1800](https://git.erikinkinen.fi/erix/integration/actions/runs/1800) are fully reviewed: 372/492 and 371/492 scenarios pass, with six complete logs and zero warning candidates. Both retain 119 obsolete policy refusals and the known configuration-carrier stall on their older graph. The pipeline descriptor scenario passes in 1799 and fails in 1800 on the same source graph, reproducing open [Integration issue 91](https://git.erikinkinen.fi/erix/integration/issues/91). Its cause remains unproved; a companion pass does not resolve it. Exact RESOURCE_EXHAUSTED replies must preserve the original Guarded mediator and Sealed peer, then allow normal configuration. Requests transfer no capabilities; every existing byte-I/O, actual exit, retirement and reuse gate remains required. The preceding probe fails at call 22 in an independent 111-call transcript. Eight focused controls and seven development selections of 988 tests pass. Fourteen strict host/native build, Clippy and rustdoc configurations and 355 frame controls pass without warnings. Seven release compilations retain their output-silence failure. Four native frame reports are incomplete; two further runs exit 1 without reports near the checker's 60-second bound. Those observations overlapped the host matrix; the outer owner did not time out. Original Exsh CI287/288 passes 988 unit tests and 355 checker controls, then emits all four incomplete reports per run: runtime 256 reached/101 unresolved and all-feature 287/68. All four complete logs are reviewed with zero warnings. None accepts the compiler or frame gates tracked in [Exsh issue 9](https://git.erikinkinen.fi/erix/exsh/issues/9) and [issue 4](https://git.erikinkinen.fi/erix/exsh/issues/4). A separate built-in timing diagnostic completes in 250.623833 seconds without warnings and its exact executable passes 507 optimized library tests. Rust reports 115.623711 seconds in LLVM optimization and 108.817139 seconds in fat LTO. The complete LLVM trace attributes 76.09% of inclusive function-pass time and 65.88% of machine-function optimization time to Parser specializations, with 166 run specializations before LTO and 158 in the machine-function trace. These classes are nested and not additive. Instrumented library-only timings identify a refactoring candidate; they do not establish an ordinary-build speedup or accept the release gate. The exact installed compiler uses explicitly selected diagnostic switches only; maintained configuration is unchanged. All 187 Integration host commands, 76 original signatures and complete catalog closure pass without warnings. The full 2,657-page manual and all 45 document tests pass; all 491,619 word bounds and three viewed pages pass with no final warnings. Original Docs CI1095/1096 also passes; all four complete logs are reviewed through the final warning-free TeX pass. Fresh native execution with the original markers and 120/45-second limits remains required. This checkpoint adds no checklist credit. Supervisor loss, partial cleanup, NeverExecuted observation, complete CI review, external toolchain rebuilding and both full EriX builds inside EriX remain open in the [phase tracker](https://git.erikinkinen.fi/erix/integration/issues/65). Native full-table realm refusal accepted — 25 September 2026: signed [Integration bdd04a62](https://git.erikinkinen.fi/erix/integration/commit/bdd04a62e0419061f33f850cabca0b6216994545) runs the new [Exsh bc5cc8ac](https://git.erikinkinen.fi/erix/exsh/commit/bc5cc8ac420e86a8632445fe7d7da47785e5ae0f) probe. The added requests transfer no capability and use the original authenticated Launchd route. All original client markers, native exit and 120/45-second limits pass. The 109 retained artifacts include 57,045 serial bytes and empty QEMU stderr, with zero image warnings. Independent BootConfig decoding follows the actual Launchd filesystem role to its 2-realm/4-client/576-plan-byte policy; packaged Procd and Pagerd layouts retain 38 records and 102 bindings. The original preparation-only and startup VMs also pass, with 108 retained artifacts each, 56,131/56,165 serial bytes and zero warnings. No guest inspection endpoint, grant or deadline change is introduced. All 187 Integration host commands, seven 987-test Exsh development selections, fourteen strict host/native build/Clippy/rustdoc configurations and 355 checker controls pass. Docs CI1091/1092 passes the complete manual and 45 tests without final warnings. Exsh CI283/284 passes 987 unit tests and 355 checker controls, then fails the existing native frame proof: runtime 256 reached/101 unresolved and all-feature 286/68 in both profiles. All four complete logs contain zero warning candidates. Seven local release unit compilations and the native frame gaps remain open under [compiler issue 9](https://git.erikinkinen.fi/erix/exsh/issues/9) and [frame issue 4](https://git.erikinkinen.fi/erix/exsh/issues/4). Documentation status is signed and pushed as [Exsh 232e6849](https://git.erikinkinen.fi/erix/exsh/commit/232e68490bffea9d7c57bde7d6384403cb6469c4), [Docs e2131e57](https://git.erikinkinen.fi/erix/docs/commit/e2131e5757c5f08939d6678ae763339aa989dbec), [Integration c5958f12](https://git.erikinkinen.fi/erix/integration/commit/c5958f12daf35ef8c53d8caabaa7429340770179). Only ROADMAP changes in those follow-ups; code, catalog, helper and manual inputs retain their original validation identity. The [phase tracker](https://git.erikinkinen.fi/erix/integration/issues/65) now records **416/876 completed sub-items**, **17/460 whole parents**, and **15.43% weighted progress** after recalculation. This accepts the realm-record ceiling only. Client/plan exhaustion, supervisor loss, partial cleanup, NeverExecuted accounting, complete original CI review, external toolchain rebuilding and both full EriX builds inside EriX remain required. Realm-capacity witness checkpoint — 25 September 2026: signed [Exsh bc5cc8ac](https://git.erikinkinen.fi/erix/exsh/commit/bc5cc8ac420e86a8632445fe7d7da47785e5ae0f) requires a third BEGIN to return canonical RESOURCE_EXHAUSTED while both selected realm records are occupied. The reply must be Unconfirmed with zero identity and receiver fields, and both original generations must still read as sealed. Every original byte-I/O, native exit, independent retirement, stale-selector and record-reuse check remains required. The three additional requests use the existing Launchd route and transfer no capability. The independent 99-call transcript rejects the preceding probe at its missing request; seven focused controls cover exact refusal, malformed replies, transport loss and unwanted receipts. Seven development selections pass 987 tests each. All fourteen host/native build, strict Clippy and private-rustdoc configurations and 355 frame-checker controls pass without warnings. Seven release unit compilations retain the original silence failure, and six current native frame observations return incomplete reports with exit 1. [Compiler issue 9](https://git.erikinkinen.fi/erix/exsh/issues/9) and [frame issue 4](https://git.erikinkinen.fi/erix/exsh/issues/4) stay open. One bounded read-only compiler stack sample finds active LLVM inlining; it does not establish time attribution or a speedup. Original red-selector and Markdown-wrapping failures remain preserved. Signed [Docs e2d4ffc1](https://git.erikinkinen.fi/erix/docs/commit/e2d4ffc1a1737ad21e682fef0ee622883e0c9536) records the contract and reconciles resolved grant regressions. All 45 document controls pass; the complete 2,655-page manual builds without final warnings, all 491,488 word bounds pass and three affected/adjacent pages are visually reviewed. Original CI1091/1092 passes, with four complete logs reviewed through the final warning-free TeX pass. Signed [Integration bdd04a62](https://git.erikinkinen.fi/erix/integration/commit/bdd04a62e0419061f33f850cabca0b6216994545) selects both original sources. All 174 helper and six profiler commands, strict orchestration Clippy and both unit selections, formatting, dependencies and Markdown pass: 187 commands, zero warnings. Both catalog policies, all 76 original signatures and complete transitive closure pass. The fresh structural audit covers 3,194 code files below 1,000 lines and 98 crate roots enforcing missing_docs; semantic authority closure remains separate. Fresh native capacity execution is pending with the original 120/45-second limits. No completion credit is added before that evidence. Earlier guarded-fixture CI1797/1798 each passes 372/492 scenarios, including admission, preparation, startup and ext4 quota. All 120 failures are classified: 119 obsolete policy refusals tracked in [Integration issue 96](https://git.erikinkinen.fi/erix/integration/issues/96), and the original counted grant refusal resolved in [Loaderd issue 5](https://git.erikinkinen.fi/erix/loaderd/issues/5). Six complete logs total 25,636,311 bytes with zero warning candidates. No unchanged job was rerun; the later fixes still need their own full CI. Remaining supervisor loss, exhaustion/cleanup, external toolchain rebuilding and both complete EriX builds inside EriX remain required by the [phase tracker](https://git.erikinkinen.fi/erix/integration/issues/65). Native configured-client acceptance — 25 September 2026: the exact signed [Integration 7a42fa26](https://git.erikinkinen.fi/erix/integration/commit/7a42fa2663bda878edcf59de01d972dd20c58ec7) graph passes the configured-client, preparation and startup VMs with all original markers, deadlines and cleanup gates. The configured witness seals two isolated realms, observes six successful byte-client exits across three realm instances, checks independent retirement, rejects stale client selectors and reuses a Launchd realm record with a new generation. This proves the native configure/seal/publish/mediated-I/O criterion; full Procd managed-row/final CPU reclamation, supervisor loss and resource ceilings remain separate requirements. [Launchd 372ab70e](https://git.erikinkinen.fi/erix/launchd/commit/372ab70ea2ea1133a9bc3edb2cb621f9679b075d) retains only the required result-carrier GRANT and preserves RECV-only client copies plus complete setup retirement. All six strict 497-test configurations and original CI179/180 pass. [Loaderd 5bcf522c](https://git.erikinkinen.fi/erix/loaderd/commit/5bcf522cfec873fa29ffe1b91bde1bf67e9f5ba2) retains the counted grant destination; four strict 145-test configurations and original CI107/108 pass. The original red tests, failed native runs and admitted host TCG diagnostic remain preserved. [Docs 6a1a9686](https://git.erikinkinen.fi/erix/docs/commit/6a1a96869736030727d0366c3e7622993dded7ff) passes the full 2,655-page manual and 45 tests locally and in original CI1085/1086; four complete CI logs total 824,660 bytes and final warnings are zero. The [configuration carrier defect](https://git.erikinkinen.fi/erix/launchd/issues/10), [counted grant defect](https://git.erikinkinen.fi/erix/loaderd/issues/5) and [configured-client stall](https://git.erikinkinen.fi/erix/integration/issues/92) are resolved by this component and native evidence. The [Exsh fixture report](https://git.erikinkinen.fi/erix/exsh/issues/10) retains its pending release compiler/frame validation despite the three native passes. Complete Integration CI1801/1802 is still queued. Whole-fleet authority/source/effect/frame acceptance, final accounting/profiler observation, rebuilding the external Rust/LLVM/runtime toolchain inside EriX and both full EriX guest-build generations remain open. Original prerequisite Integration CI1793/1794 each passes 490/491 scenarios; Rust and Markdown pass, and six complete logs total 27,432,406 bytes with zero warnings. CI1794 retains the [ext4 quota timeout](https://git.erikinkinen.fi/erix/integration/issues/18). CI1793 instead exposes a distinct [one-shot replay QMP connection loss](https://git.erikinkinen.fi/erix/integration/issues/93), recorded using the canonical bug template and phase label. No original workflow was rerun, and no deadline or authority check was relaxed. Only the existing native-witness sub-item gains credit: **15.42% weighted progress**, 413/873 sub-items. Whole acceptance remains **3.86%, 17/460 parents**. Signed configuration carrier correction — 25 September 2026: [Launchd 372ab70e](https://git.erikinkinen.fi/erix/launchd/commit/372ab70ea2ea1133a9bc3edb2cb621f9679b075d) retains exactly RECV | GRANT only for counted-client result delivery. Readiness-only RECV, mediator SEND-only routes, RECV-only client copies, original authentication and complete setup disposal before seal/retirement remain required. [Docs 6a1a9686](https://git.erikinkinen.fi/erix/docs/commit/6a1a96869736030727d0366c3e7622993dded7ff) documents the carrier/source distinction and its temporary setup lifetime. All 45 document tests, Markdown, template, link and unchanged-reference checks pass. The complete 2,655-page manual builds without final warnings, all 491,315 word bounds pass and three affected/adjacent pages are visually reviewed. Original CI1085/1086 is under observation. [Integration 7a42fa26](https://git.erikinkinen.fi/erix/integration/commit/7a42fa2663bda878edcf59de01d972dd20c58ec7) selects the two signed image sources. Both catalog policies, all 76 original signatures and complete dynamic closure pass. Helper, Rust, profiler and CI inputs remain byte-identical to their recorded validation; fresh formatting, source policy and Markdown pass. The corrected client VM is running from a fresh source-bound runner, followed by the older preparation/startup regressions. Original CI1801/1802 is queued. [Launchd issue 10](https://git.erikinkinen.fi/erix/launchd/issues/10) and [Integration issue 92](https://git.erikinkinen.fi/erix/integration/issues/92) remain open pending native closure. Earlier failures and host counter evidence are preserved. No deadline or authority gate was relaxed, and these repairs add no canonical checklist credit. Legacy destinations, exact source/rights/caller/relation checks, native empty-slot and capacity enforcement, and acknowledged disposal remain required. Signed [Docs ee08bab6](https://git.erikinkinen.fi/erix/docs/commit/ee08bab65e29dd6c3c3781f1b361070a99d7325b) documents the contract. All 45 document tests pass, the full 2,653-page manual builds without final warnings, all 491,233 word bounds pass and three affected/adjacent pages are visually reviewed. Its original CI1083/1084 is under observation. Signed [Integration 04bff04f](https://git.erikinkinen.fi/erix/integration/commit/04bff04f4328676ba8205f7ac2b0df64213698a0) adopts those two original image sources. Both catalog policies, all 76 original signatures and complete transitive closure pass. The Cargo catalog contains neither changed component and remains unchanged. All helper, Rust, profiler and CI source bytes retain their previous validation; fresh formatting, source policy and Markdown pass. Original CI1799/1800 is queued. Fresh configured-client and older preparation/startup VM execution on this successor remains required by [Loaderd issue 5](https://git.erikinkinen.fi/erix/loaderd/issues/5); the previous two prerequisite passes and subsequent client failure remain retained. Original Exsh CI281/282 now have complete failure logs: unit suites pass 507/478/1 and all 355 frame-checker controls pass, but both runtime profiles reach 256 functions with 101 unresolved observations and both all-feature profiles reach 286 with 68 unresolved observations. All four logs total 322,830 bytes with zero warning candidates. [Exsh frame issue 4](https://git.erikinkinen.fi/erix/exsh/issues/4) and [compiler issue 9](https://git.erikinkinen.fi/erix/exsh/issues/9) remain open. No unchanged CI was restarted and no acceptance bound was relaxed. These repairs add no checklist credit; native configured-client acceptance, managed-row reuse, profiling, complete authority closure and both full guest-build requirements remain open. Configured-client manual contract — 25 September 2026: signed [Docs 4226a7c0](https://git.erikinkinen.fi/erix/docs/commit/4226a7c02f58b3de98d45bcf35f031484a136f6d) corrects operational documentation to LCH1 V4/88 and arena layout V7 and specifies private byte-client packaging, actual terminal outcomes, independent retirement and replacement clients. All 45 document controls, Markdown, template, link and unchanged-reference checks pass. The complete 2,653-page manual builds without final warnings; all 491,103 word bounds pass and nine affected/adjacent pages were visually inspected. Original [CI1081](https://git.erikinkinen.fi/erix/docs/actions/runs/1081) and [CI1082](https://git.erikinkinen.fi/erix/docs/actions/runs/1082) pass. Four complete logs verify 824,206 bytes; normal early-pass cross-reference warnings converge, and both final passes are warning-free. No unchanged CI was rerun. The manual describes the required native evidence and does not establish configured-client execution or either complete build inside EriX. [Docs PR4](https://git.erikinkinen.fi/erix/docs/pulls/4) remains unfinished for the remaining phase requirements. The seal component is now exposed as an accepted substep. Completion is 15.41% weighted checklist progress, 410 of 871 sub-items complete across 156 decomposed parents. Whole acceptance remains 3.86%, 17 of 460 parents, with all 22 original section weights unchanged. The fresh structural audit checks 76 repositories, 3,181 authored code files under the expanded suffix scope below 1,000 lines, 264 unchanged full Git pins and 98 original crate roots with missing-docs gates. This is not whole-fleet semantic authority acceptance. [Launchd PR2](https://git.erikinkinen.fi/erix/launchd/pulls/2) remains unfinished. Next work must retain actual client Start and terminal outcomes, route authenticated client events before ordinary job lookup, consume final CPU once, and prove coherent native configuration/seal/byte I/O plus failure/reuse. The complete EriX build inside EriX and external Rust/LLVM/toolchain rebuild inside EriX remain unproved. Original [Integration CI1792](https://git.erikinkinen.fi/erix/integration/actions/runs/1792) also passes all 491 VM scenarios and interactive dev/release gates, with all three complete logs reviewed (13,516,777 bytes, zero warnings). This validates its older source graph only; Launchd issue 8 preserves CI164's original failure and inaccessible diagnostics. Native configuration, seal, four-client byte I/O, failure/reuse and both rebuilds inside EriX remain open. Native failure/reuse and both guest rebuilds remain separate acceptance gates. This closes the earlier CI-pending observation for [Docs PR4](https://git.erikinkinen.fi/erix/docs/pulls/4), without adding runtime or guest-build acceptance. **Configuration endpoint COPY and accepted private startup documentation.** Signed [Docs `69840bd8`](https://git.erikinkinen.fi/erix/docs/commit/69840bd8ca4aaea2a098d5d85cbea2d5614f7067) clarifies that native endpoint COPY preserves Launchd's configuration SEND source. After the correlated Provision result and original caller retirement, Launchd drops that source and independently observes absence before Start. Unique InstallGrant MOVE retains its separate native source-consumption proof. The manual and component documentation now also reflect the accepted [two-mediator startup witness](https://git.erikinkinen.fi/erix/integration/commit/66ddc78da31dd03dd554d0677cdc2af86588d525) with [Launchd `3d39c741`](https://git.erikinkinen.fi/erix/launchd/commit/3d39c7413a9c35a051323fceb7f895f0b18402e0): each actual mediator reaches authenticated PrivateReady and independently acknowledged positive Retire. Configuration, seal, real client byte I/O, complete failure retirement and full guest builds remain open. The Lib-IPC reference is regenerated from exact signed [`d4d32115`](https://git.erikinkinen.fi/erix/lib-ipc/commit/d4d32115b8cc446a337de3f12d31016df6ad624d), including the corrected opcode rustdoc. All 45 unchanged document controls are reused with byte-identical test implementations. Fresh Markdown, source binding and syntax checks pass; the full 2,499-page manual has zero final warnings. All 464,692 word bounds and ten affected process/API pages are reviewed. Both original CI runs for this exact checkpoint pass: [run 1069](https://git.erikinkinen.fi/erix/docs/actions/runs/1069), [run 1070](https://git.erikinkinen.fi/erix/docs/actions/runs/1070). All four complete terminal job logs (789,498 bytes) are retained and hash-verified. Each manual job passes 45 tests and builds the 2,499-page manual with zero final warnings; earlier reference-convergence warnings resolve before the final pass. No workflow was rerun. Updated the process-service contracts in signed Docs commit [`eade076a4cb30b3932776d8808b6c1203fb7533e`](https://git.erikinkinen.fi/erix/docs/commit/eade076a4cb30b3932776d8808b6c1203fb7533e). The manual distinguishes an empty registered receiver from route absence, limits first-Challenge registration waiting to the original unaccepted submission, and retains every accepted or erroneous nonzero owner. Explicit Retire consumes only its exact queued terminal event after proven child and capability disposal; ordinary spontaneous terminal observation remains available. These contracts correspond to [Launchd #6](https://git.erikinkinen.fi/erix/launchd/issues/6), [Procd #7](https://git.erikinkinen.fi/erix/procd/issues/7) and [Procd #8](https://git.erikinkinen.fi/erix/procd/issues/8). All 45 unchanged document tests remain applicable by byte-identical control implementations. The complete 2,499-page manual passes without warnings; all 464,516 rendered word bounds pass and changed process pages are visually reviewed. README, ARCHITECTURE and ROADMAP retain their existing formats. Generated API selections are unchanged. Native startup acceptance remains pending; this documentation checkpoint does not establish mediator execution. Both original CI runs for this exact checkpoint pass: [run 1067](https://git.erikinkinen.fi/erix/docs/actions/runs/1067), [run 1068](https://git.erikinkinen.fi/erix/docs/actions/runs/1068). All four complete terminal job logs (789,510 bytes) are retained and hash-verified. Each manual job passes 45 tests and builds the 2,499-page manual with zero final warnings; earlier reference-convergence warnings resolve before the final pass. No workflow was rerun. Updated the process and native-launch manual contracts in signed Docs commit [`95921234c64d7cc11f9f9ed19d49a5d73c95357c`](https://git.erikinkinen.fi/erix/docs/commit/95921234c64d7cc11f9f9ed19d49a5d73c95357c). Private mediator preparation resolves only its explicitly scoped executable; Loaderd still checks the configured runtime graph and exact bytes. Ordinary launch sidecar admission remains separate. The manual also describes both Launchd-owned terminal-event classes and the current four-column realm geometry, corresponding to [Launchd #3](https://git.erikinkinen.fi/erix/launchd/issues/3) and [Launchd #4](https://git.erikinkinen.fi/erix/launchd/issues/4). All 45 document tests and the complete 2,497-page manual pass without warnings. All 464,159 rendered word bounds pass; changed process and launch-authority pages are visually reviewed. README, ARCHITECTURE and ROADMAP retain their existing formats. Docs has no generated Launchd API reference, so no reference selection was added. Native startup acceptance remains pending; this documentation result does not establish mediator execution. Both original CI runs for this exact checkpoint pass: [run 1065](https://git.erikinkinen.fi/erix/docs/actions/runs/1065), [run 1066](https://git.erikinkinen.fi/erix/docs/actions/runs/1066). All four complete terminal job logs (789,078 bytes) are retained and hash-verified. Each manual job passes 45 tests and builds the 2,497-page manual with zero final warnings; earlier reference-convergence warnings resolve before the final pass. No workflow was rerun. Signed source [`32ac049587ba7174d44109a3b179e5a2b69738e5`](https://git.erikinkinen.fi/erix/docs/commit/32ac049587ba7174d44109a3b179e5a2b69738e5) updates the technical manual and generated API reference for counted realm bootstrap messages, the native mediator entry and exact-generation running retirement while preserving the pending producer and VM acceptance boundaries. All 45 documentation tests pass. The manual contains 2,469 pages and 459,127 extracted words; 32 selected rendered pages were visually reviewed. Final warnings and page-bound violations are zero. Coordinated producer provisioning, operation 58 supervisor-lifetime-binding adoption, actual Posixd start and native readiness/retirement VM acceptance remain pending. These source and host/build results do not establish a running realm or a full guest build. The matching signed [Docs PR 4](https://git.erikinkinen.fi/erix/docs/pulls/4), `54557713f4afad380c1166f6aa1c1622d3959744`, updates the TeX chapter and both IPC API views from original signed source. All 45 tests, independent API regeneration, the complete 2,423-page manual, all 446,749 word bounds and nine visually reviewed contract pages pass, with zero final warnings. Original [Docs CI 979](https://git.erikinkinen.fi/erix/docs/actions/runs/979) and [980](https://git.erikinkinen.fi/erix/docs/actions/runs/980) pass from four complete hashed logs, 773,034 bytes. Both runs pass 45 tests and the complete 2,423-page manual; successive TeX passes retain 36/1/0 warning observations, with zero final-pass warnings. No workflow rerun or cancellation supplies this result. Native upstream Rust/LLVM rebuilding and both complete EriX build generations inside EriX remain required. All reserved bits are rejected; replies carry zero result values and preserve uninterpreted codes. Seven new controls pass all eight strict library/shim configurations: 419 wire tests and 20 shim tests per configuration, eight freestanding builds, formatting, strict host/native Clippy and private rustdoc, with no warnings. The original kernel-only shim test remains ignored. Original [lib-ipc CI 365](https://git.erikinkinen.fi/erix/lib-ipc/actions/runs/365) and [366](https://git.erikinkinen.fi/erix/lib-ipc/actions/runs/366) pass from four complete hashed logs, 494,246 bytes, without warnings. Kernel admission, descendant stopping, safe native reclamation progress, coherent consumer adoption and actual CPL3 failure coverage remain open. The shared codec does not enable private mediator execution or alter the current complete image's source graph. <details> <summary>Detailed scope and contracts</summary> ### Native caller admission checkpoint — 15 September 2026 Forwarded SEND aliases, request-body identities, other lifecycle roles, reused generations and unavailable identity cannot acquire this dispatch permission. Other receivers retain their policy; rejected delivered transfers still undergo local disposal, and uncertain disposal stops ordinary continuation. Five new producer controls exercise accepted event dispatch and refusals without consuming the private event. Product runtime-image validation still requires a coherent original-commit dependency graph; this checkpoint does not claim a new Procd VM. Actual returned-grant custody, guarded bootstrap, readiness/configuration/seal, mediated client byte I/O, fair retirement and both complete guest build generations remain open. ### Mediator constructor adoption manual — 15 September 2026 The manual now records Procd's mediator-only use of operation 54 without a parent VSpace receipt, independent native TCB backing, unchanged ordinary construction, refusal without fallback and closed start gates. Authenticated grant return, guarded private execution, readiness, configuration/seal, client I/O, fair retirement and both full guest build generations remain open. ### Construction without child root capabilities — 15 September 2026 The first render was rejected because an operation-registry correction followed its source snapshot; accepted evidence uses frozen final text. Procd adoption, authenticated grant return, guarded bootstrap authority, private mediator execution, readiness, configuration/seal, client I/O, fair retirement and both complete guest build generations remain open. ### Staged endpoint attenuation checkpoint — 15 September 2026 Authenticated grant return, independently minimal bootstrap/root authority, retained native and nested guards, private mediator execution, configuration/seal, client I/O, fair retirement and both complete guest build generations remain open. Signed Docs `87942ea7675e2a25fe3bf19f3cac19f9c5d8b1e2` specifies native IPC platform selection and hosted transport refusal, with both IPC API references generated from signed Lib-ipc `805717680d9dfb902216550a111d910807f30d23`. Compile-target selection, local refusal, native observations and retirement evidence remain distinct. Realm adoption, separate operation-completion contracts, the whole-codebase audit and both full EriX-in-EriX builds remain open. Kernel `03e13a78` passes CI 528/529 and Bootloader `e7fa3935` passes CI 135/136; the coordinated Integration `4b65755f` native VM passes the required exit and ordered unique markers. Realm adoption, provider/pending-operation completion, the full audit and both complete builds inside EriX remain open. This closes renderer issue #7 only; native VM, realm producer, full audits and guest self-hosting remain open. Native VM, realm producer, complete audits and both full build generations inside EriX remain open. Dependencies identify required contracts and closure gates; preparatory inventory/design can proceed in parallel under one owner per edited file. Link bounded implementation issues and their PRs here before claiming acceptance. Close criteria only with their own reviewed deliverables and validation evidence. Native external Rust/LLVM rebuilding and both full EriX build generations remain required. Complete mediator execution, native toolchain rebuilding and both full guest builds remain required. Procd uses the actual returned grant to attenuate the initial endpoint to RECV before execution, removes bypass sources, and retains nested custody beneath Kernel lifetime custody. A later mediator disposal report cannot prove absence of bypass senders. Native upstream Rust/LLVM rebuilding and both complete EriX builds remain required. A supervisor binds and starts a child; that child binds a staged grandchild and kills its supervisor through its own explicit Process SEND route. Read-only witnesses require terminal caller storage to survive dispatch, then exact child/grandchild absence before the independent observer reads child-before-supervisor events. All four additional lifetimes and twenty-two mapped pages must be disposed for `ERIX_KERNEL:CHILD_EXECUTION_OK`. Signed [Integration c14c5a61](https://git.erikinkinen.fi/erix/integration/commit/c14c5a617196a9b135b479601ca47a21371a9482) requires the additional marker while preserving every earlier marker and the original 60-second limit. The original install-grant constructor still gives `GRANT | MINT` while binding needs only `GRANT`; move-only transfer preserves exact rights. Full source/effect/frame proof, the Pagerd gate, native external Rust/LLVM/runtime rebuilding and both full EriX-in-EriX generations remain mandatory. No whole acceptance leaf is added: 15/460, 3.48% weighted. The child kills that supervisor through its own explicit Process SEND route. Immediate faulting sentinels forbid either terminal payload from resuming. A diagnostic-only read-only witness then requires empty CPU accounting, only terminal retained records, no bound cleanup duties or event reservations, exact child identity/CSpace/mapping absence and both unconsumed child-before-supervisor events. Signed [Integration 4d6f4fe8](https://git.erikinkinen.fi/erix/integration/commit/4d6f4fe8b383603b225b04a7771a11f32886e0a9) requires the additional marker while preserving all earlier assertions and both 60-second scenario limits. The static audit passes 3,140 authored code files below 1,000 lines, 74 manifests, 259 full Git selections, 171 direct missing_docs gates and 92 conventional crate roots; semantic authority and complete private-rustdoc closure remain open. Further native failure controls, grant-rights minimization, terminal accounting, Procd adoption and complete service lifecycle acceptance remain open. Existing install-grant creation still supplies GRANT | MINT while binding needs GRANT, so minimum authority is not claimed. Full source/effect/frame proof, the 128-page Pagerd gate, profiler attribution, native external Rust/LLVM/runtime rebuilding and both full EriX-in-EriX generations remain mandatory. No whole acceptance leaf is added: 15/460, 3.48% weighted. Native terminal-event allocation refusal — 19 September 2026: signed [Kernel ba03995f](https://git.erikinkinen.fi/erix/kernel/commit/ba03995fe0dcfc3d4a1f72eb000e0c7698bbcbaa) extends the actual executing-child sequence with one deliberately refused heap allocation. Read-only witnesses require complete reservation rollback, an empty event queue, unchanged exact records and capabilities, and preserved code/stack/message mapping ranges. Actual CPL3 instructions validate the refusal reply before the next ordinary ancestor kill succeeds with allocation available. Every earlier terminal, descendant-disposal, independent-process and no-successor idle assertion remains required. `ERIX_KERNEL:TERMINAL_EVENT_RESERVATION_OK` requires one consumed allocator refusal and no remaining armed fault. No witness supplies a syscall result, cleanup effect or scheduler choice. Signed [Integration cf5b2f5f](https://git.erikinkinen.fi/erix/integration/commit/cf5b2f5f1d63631e69df3074d7c1c0b9b4921480) requires the new marker without changing either 60-second limit. Complete semantic authority and private-rustdoc closure remain open. Its separate private-mediator branch does not take the same query path; adoption must state which lifetimes require retained metrics and preserve their original generation without fabricated zero/wall-clock values. Independent release-failure coverage, grant-rights minimization, accounting, Procd adoption and full mediator lifecycle remain open. Full source/effect/frame proof, the 128-page Pagerd gate, profiler attribution, native Rust/LLVM/runtime rebuilding and both full EriX-in-EriX generations remain mandatory. No whole acceptance leaf is added: 15/460, 3.48% weighted. Independent native child release recovery — 19 September 2026: signed [Kernel 82d88b60](https://git.erikinkinen.fi/erix/kernel/commit/82d88b609bd808a840780993da315230dd14399a) extends actual supervisor-exit coverage with two deliberate refusals at the original staged child's final VSpace-release callback, after capability disposal and unlinking. Read-only observations around two ordinary CPL3 observer yields require the original full record, generation, abort custody and first error retained, an empty original CSpace and retained mapped backing. The independent running child must already be absent from native TCB, CSpace and VSpace directories. The third callback must perform normal VSpace release before all original terminal-event, generation and resource-absence checks pass. `ERIX_KERNEL:CHILD_RELEASE_ISOLATION_OK` requires exactly two refusals and complete eventual disposal. This establishes injected callback-refusal coverage, not an observed hardware or allocator malfunction. All earlier nested-child, allocation-refusal and no-successor pre-halt assertions remain required. Signed [Integration 294a467a](https://git.erikinkinen.fi/erix/integration/commit/294a467a3bcd9464ea55c32dbce98acf19d0e400) requires the added marker with both original 60-second limits unchanged. Static audit passes 3,143 authored code files below 1,000 lines, 74 manifests, 259 original Git pins, 171 direct missing_docs gates and 92 conventional roots; complete semantic authority/private-rustdoc closure remains open. The grant-rights audit confirms actual Procd derivation callers and exact GRANT | MINT receipt checks in Procd and Launchd. Grant authority minimization must coordinate those consumers and distinguish the grant's own rights from its installation ceiling. Original generation-bound terminal accounting, Procd adoption, provider completion, hardware halt/wakeup and complete mediator lifecycle remain open. Full source/effect/frame proof, the 128-page Pagerd gate, profiler attribution, native external Rust/LLVM/runtime rebuilding and both full EriX-in-EriX generations remain mandatory. No whole acceptance leaf is added: 15/460, 3.48% weighted. The process and launch chapters require GRANT-only final receipts, explicit derivation/source disposal, and original-generation rollback. Canonical acceptance remains 15/460 leaves, 3.48% weighted. Full service lifecycle, terminal accounting, source/effect/frame proof, the 128-page Pagerd gate, profiler attribution, native external Rust/LLVM/runtime rebuilding and both full EriX-in-EriX generations remain required. Static audit currently passes 3,150 authored code files below 1,000 lines, 74 manifests, 259 explicit Git pins, 172 direct missing_docs gates and 92 conventional Rust roots; full semantic authority and documentation review remain open. Procd derives exactly GRANT into disposed VSpace scratch, drops its delegating source and uniquely relocates the result into the now-empty managed grant slot before handoff. Four 291/296-unit configurations, four native builds, formatting, strict Clippy and private rustdoc pass without warnings; relocation refusal and occupied-destination controls retain original-stage cleanup. Canonical acceptance remains 15/460 leaves, 3.48% weighted. Original-generation terminal accounting, provider/lifetime completion, source/effect/frame proof, the 128-page Pagerd gate, profiler attribution, native external Rust/LLVM/runtime rebuilding and both full EriX-in-EriX build generations remain required. Mediators retain only scalar counters and the original authenticated supervisor identity after disposing all capability columns; supervisor death discharges the pending scalar observation and a replacement cannot inherit it. [Bug 5](https://git.erikinkinen.fi/erix/procd/issues/5) remains open for actual service acceptance. These are pending full regressions, not successful runtime acceptance. No new canonical acceptance leaf is closed: 15/460 and 3.48% weighted. Ordinary Launchd metric-consumer restart/disposal semantics, coherent service CPU/profiler VMs, complete realm/provider authority and I/O, source/effect/frame proof, Pagerd, native external Rust/LLVM/runtime rebuilding and both full EriX-in-EriX build generations remain required. Full native Rust/LLVM/runtime rebuilding and both EriX guest build generations remain required in [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). Original frame-manual CI acceptance — 21 September 2026: signed `f8a40d45fbbd631660f3adca9152fbb398a4ee6d` passes both original [999](https://git.erikinkinen.fi/erix/docs/actions/runs/999)/[1000](https://git.erikinkinen.fi/erix/docs/actions/runs/1000), including 45 tests and the complete 2,431-page manual. The native external toolchain rebuild and both full guest build requirements remain open. Integration [fd8a5cf0dbcf9a9cd3ddb6038370295e6ec2c8fa](https://git.erikinkinen.fi/erix/integration/commit/fd8a5cf0dbcf9a9cd3ddb6038370295e6ec2c8fa) requires the complete runtime transition in both Rootd and its orchestration policy. Contract v2 requires the Kernel revision/tree and actual artifact/metadata binding; old receipts, synthetic wrappers and modified source cannot acquire this declaration. Native external Rust/LLVM/runtime rebuilding and both complete EriX guest build generations remain mandatory. Five actual service VMs pass: shell CPU accounting, exec successor replacement, two-CPU read-only inspection, out-of-session denial and guarded realm preparation. Remaining lifecycle control/event ownership, complete native fault/cleanup acceptance and the measured startup timing failures remain open. No whole acceptance leaf closes: 15/460, weighted 3.48%. Rebuilding the external Rust/LLVM toolchain inside EriX and using it in the required full EriX guest-build generations remain mandatory and unproven. The [operator guide](https://git.erikinkinen.fi/erix/integration/src/commit/4fa27f942bc2c6511eedceb5b20b8212f2bc94b0/docs/tcg-profiling.md) distinguishes complete counters from VM acceptance. Neither proves startup acceptance, whole-transcript instrumentation overhead or a speedup. [Profiler acceptance](https://git.erikinkinen.fi/erix/integration/issues/3) and [startup performance](https://git.erikinkinen.fi/erix/integration/issues/72) remain open. The next optimization must preserve complete validation, live backing checks, page permissions, invalidation ordering and cleanup on errors. No whole acceptance leaf closes: 15/460, weighted 3.48%. Rebuilding the external Rust/LLVM toolchain inside EriX and completing the required full guest-build generations remain mandatory and unproven. </details> <details> <summary>Related records and contracts</summary> | Repository | Links | | --- | --- | | docs | [issue 10](https://git.erikinkinen.fi/erix/docs/issues/10), [issue 9](https://git.erikinkinen.fi/erix/docs/issues/9) | | exsh | [issue 8](https://git.erikinkinen.fi/erix/exsh/issues/8) | | integration | [issue 37](https://git.erikinkinen.fi/erix/integration/issues/37), [issue 50](https://git.erikinkinen.fi/erix/integration/issues/50), [issue 67](https://git.erikinkinen.fi/erix/integration/issues/67), [issue 69](https://git.erikinkinen.fi/erix/integration/issues/69), [issue 71](https://git.erikinkinen.fi/erix/integration/issues/71), [PR 12](https://git.erikinkinen.fi/erix/integration/pulls/12) | | kernel | [issue 11](https://git.erikinkinen.fi/erix/kernel/issues/11), [issue 13](https://git.erikinkinen.fi/erix/kernel/issues/13), [issue 19](https://git.erikinkinen.fi/erix/kernel/issues/19), [PR 3](https://git.erikinkinen.fi/erix/kernel/pulls/3) | | lib-dynlink | [PR 3](https://git.erikinkinen.fi/erix/lib-dynlink/pulls/3) | | lib-ipc | [PR 2](https://git.erikinkinen.fi/erix/lib-ipc/pulls/2), [child-lifetime-binding.md](https://git.erikinkinen.fi/erix/lib-ipc/src/commit/aaf2df39700b43507b23ff2007bc0d573c4eea30/docs/child-lifetime-binding.md) | | meta | [issue 2](https://git.erikinkinen.fi/erix/meta/issues/2) | | posixd | [PR 5](https://git.erikinkinen.fi/erix/posixd/pulls/5) | | procd | [issue 4](https://git.erikinkinen.fi/erix/procd/issues/4), [PR 2](https://git.erikinkinen.fi/erix/procd/pulls/2) | | rootd | [issue 7](https://git.erikinkinen.fi/erix/rootd/issues/7), [PR 2](https://git.erikinkinen.fi/erix/rootd/pulls/2) | </details>
erikinkinen changed title from [FEATURE] [P03] Enforce complete inline documentation and warning-free documentation builds to [FEATURE] Enforce complete inline documentation and warning-free documentation builds 2026-09-12 08:02:01 +02:00
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:33:37 +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/docs#1
No description provided.