[FEATURE] Freeze the complete source, build, ABI and self-hosting inventory #1
Open
opened 2026-09-12 07:56:21 +02:00 by erikinkinen
·
0 comments
No Branch/Tag specified
main
fix/bounded-source-path-diagnostics
fix/configured-boot-tool-revision
fix/propagate-image-manifest-failures
feature/service-cargo-dependency-aliases
feature/consistent-dynlink-compiler-metadata
feature/configured-image-cargo-routing-merge-ready-5583860a
fix/trusted-frame-snapshot-identity
feature/native-startup-compiler-selections-merge-ready-0761fd75
feature/exact-kernel-runtime-exports-merge-ready-f1cdc8b6
feature/native-startup-compiler-selections-72ec5647
feature/exact-kernel-runtime-exports-merge-ready-39827352
fix/configured-image-cargo-routing
feature/shared-development-source-selection
feature/native-input-owner-cohort
feature/retained-source-range-comparison-merge-ready-012d1dc4
feature/completed-python-syntax-progress-merge-ready-45097d26
feature/retained-fixture-metadata-merge-ready-eb7dfbea
feature/retained-fixture-source-paths-merge-ready-fc961955
feature/retained-image-failed-queue-merge-ready-52c5cdb3
feature/retained-native-companion-source-merge-ready-36ba241f
feature/retained-image-metadata-python-merge-ready-2331d9b0
feature/vfsd-conditional-resize-provider
feature/vfsd-directory-access-provider
feature/retained-source-range-comparison-merge-ready-dfb8c6e7
feature/retained-fixture-metadata-merge-ready-37b4dc99
feature/retained-fixture-source-paths-merge-ready-c823d028
feature/retained-image-failed-queue-merge-ready-8c4c37ba
feature/retained-native-companion-source-merge-ready-60f7cf9e
feature/vfsd-permission-evidence-provider
feature/completed-python-syntax-progress-merge-ready-3d8d5288
feature/retained-image-metadata-python-merge-ready-38f1c74e
feature/vfs-three-region-capacity-merge-ready-bb59d3b6
feature/vfsd-directory-root-companions
feature/retained-source-range-comparison-merge-ready-bbaf8a9e
feature/retained-source-range-comparison-merge-ready-9b231c76
feature/retained-image-failed-queue-merge-ready-51d5cd03
feature/retained-native-companion-source-merge-ready-0b4be9dc
feature/retained-fixture-source-paths-merge-ready-c01cc992
feature/retained-fixture-metadata-merge-ready-e476d0d7
feature/retained-image-metadata-python-merge-ready-847d3fac
feature/completed-python-syntax-progress-merge-ready-3b81e619
feature/retained-fixture-metadata-merge-ready-f55a380e
feature/retained-image-metadata-python-merge-ready-e2524564
feature/cargo-bundle-stage-observations-merge-ready-9e5f66f9
feature/cargo-bundle-stage-observations
feature/interactive-probe-diagnostics
feature/complete-firmware-fixture-inputs-merge-ready-9022dca4
feature/portable-git-error-fixture-merge-ready-9a9424b8
feature/catalog-fixture-policy-controls
perf/generic-caller-native-owner
feature/root-runtime-main-dependencies
feature/retained-bootstrap-progress
feature/explicit-kernel-runtime-exports
fix/bootstrap-ci-companion-profile
feature/main-ci-provider-policy
feature/retained-host-executable-birth
fix/artifact-upload-stage-diagnostics
fix/image-grant-retirement-registration
feature/local-catalog-source-ownership
fix/explicit-companion-branch-policy
fix/native-diagnostic-fixture-startup-budget
fix/generated-source-retirement-proof
fix/native-c-helper-source-cohort
feature/clean-standalone-library-variants
fix/shared-service-symbol-restoration
feature/legacy-sdk-tool-custody
feature/retained-runtime-disk-formatter
fix/kernel-dynamic-dependency-order
feature/current-api-reference-scope
feature/retained-ext4-population-budget
feature/explicit-exsh-lifecycle-catalog
feature/retained-vfs-capacity-assembly
feature/native-boot-offline-sources
fix/source-descriptor-acquisition-custody
feature/retained-ext4-image-readback
feature/retained-image-library-variants
feature/retained-helper-import-edges
feature/retained-git-validation-duties
feature/native-graph-terminal-retirement
feature/retained-vm-python-selection
feature/native-c-process-contract
feature/extended-release-payload-policy
feature/retained-source-range-comparison
feature/owned-vm-command-lifetimes
feature/owned-git-acquisition-progress
feature/completed-python-syntax-progress
feature/retained-fixture-metadata
feature/owned-source-directory-persistence
feature/native-graph-held-guard-checks
feature/native-c-owner-input-cohort
feature/retained-image-metadata-python
feature/retained-signing-key-consumption
feature/retained-boot-tool-image-build
feature/retained-host-data-use
feature/retained-efi-development-link-staging
feature/retained-image-manifest-inputs
feature/native-extended-profile-inputs
fix/source-closure-entry-diagnostics
feature/owned-offline-catalog-preparation
feature/native-c-artifact-matrix
fix/raw-live-scope-freshness
feature/native-c-pure-owner-cohort
perf/source-bookend-ancestry-boundary
fix/preparation-profile-custody
perf/source-descriptor-admission
feature/native-scripted-build-cli
feature/native-scripted-root-build
feature/native-live-output-custody
fix/catalog-graph-prepared-profile
fix/root-source-bytecode-producer
fix/shared-source-diagnostic-expectations
fix/source-closure-diagnostics
fix/source-root-admission
perf/target-history-comparison
perf/catalog-helper-parent-boundary
perf/target-output-completion-boundary
perf/census-directory-borrows
refactor/native-custody-core
refactor/constructor-owned-binding
perf/constructor-dependency-source-boundary
fix/historical-output-capture-interval
perf/retained-input-hash-streams
fix/caller-controller-signal-admission
perf/recipe-runtime-binding-projection
test/efi-offline-original-inputs
test/efi-source-bundle-selection
fix/input-control-fixture-storage
perf/unit-query-binding-projection
perf/constructor-dependency-projection
fix/compiler-input-consumer-enrollment
perf/offline-context-output-batch
perf/target-cfi-source-bookends
perf/target-input-source-proof
perf/target-profile-query-boundary
perf/constructor-query-boundary
fix/input-diagnostics-ci-storage
fix/settled-recipe-lease-failure
fix/efi-fixture-source-entries
fix/catalog-helper-descriptor-lifetime
perf/source-tool-proof-projection
perf/owned-input-module-compilation
perf/recipe-unit-output-validation
perf/catalog-helper-borrow-pairs
perf/owned-input-root-imports
perf/owned-code-parse-reuse
test/original-output-capture-faults
perf/recipe-capture-completion-continuation
perf/recipe-selected-runtime-proof
perf/efi-completion-proof-projections
test/connected-efi-current-producers
perf/target-completion-output-return
fix/linked-image-runtime-registration
fix/offline-forest-negative-retirement
perf/recipe-output-capture-batch
fix/runtime-link-retirement-order
fix/cargo-free-offline-inputs
fix/vm-fixture-timeout-evidence
perf/recipe-unit-output-proofs
perf/target-prepared-producer-binding
perf/recipe-unit-input-proofs
fix/scripted-artifact-stage-diagnostics
perf/helper-chunk-descriptor-use
perf/recipe-fixed-effect-source-proofs
test/connected-recipe-efi-publication
fix/recipe-owned-dependency-bindings
perf/helper-proof-row-index
fix/shared-helper-selection-controls
perf/source-history-projection
perf/native-target-query-proofs
feature/native-scripted-root-driver
fix/native-target-control-runner
fix/compiler-tool-fixture-portability
fix/recipe-source-loan-doc-wrap
perf/catalog-helper-verification
fix/native-helper-runner-syntax
feature/recipe-efi-artifact-adoption
feature/native-recipe-target-compiler
feature/native-recipe-target-closure
feature/native-build-script-producers
feature/native-recipe-external-inputs
fix/recipe-executable-source-checks
feature/observed-unit-origins
feature/native-recipe-root-units
feature/external-source-scope-withdrawal
fix/native-profile-trim-paths
feature/owned-native-build-pipeline
feature/native-build-script-call
feature/source-input-offline-execution
feature/recipe-executable-inputs
fix/runtime-input-original-registration
feature/native-recipe-source-leases
feature/native-recipe-product-files
perf/source-consumer-selection-proofs
feature/native-build-script-environment
fix/source-input-entry-guard
fix/source-input-fixture-tool-selection
perf/catalog-source-postcheck-proofs
fix/shared-shallow-fetch-prefix
fix/compiler-input-receiver-birth
perf/passive-helper-verification
fix/cargo-shallow-fetch-prefix
perf/offline-retained-space-checks
perf/source-consumer-adjacent-proofs
perf/source-archive-member-lookup
feature/production-source-bundle-publications
perf/immutable-source-export-selection
fix/native-fixture-retirement-order
feature/complete-source-input-catalog
feature/prepared-source-production-join
fix/qualified-source-fixture-python
fix/gateway-source-failure-diagnostics
fix/source-bundle-original-custody
feature/native-release-output-publications
feature/production-cargo-publications
feature/source-input-production-join
fix/owned-region-source-baseline
feature/archive-byte-codec
feature/owned-release-file-writer
fix/diagnostic-fixture-startup-budget
fix/native-wrapper-fixture-ordering
fix/production-export-initialization
fix/shared-helper-source-closure
feature/owned-original-git-packs
perf/runtime-artifact-tls-lifetime
feature/production-source-object-inputs
feature/native-production-offline-sources
feature/native-production-contract
feature/native-link-history-selection
perf/native-signal-mask-observations
feature/native-graph-preparation-profiling
fix/native-rust-ci-contract
fix/self-contained-native-metadata
fix/native-graph-fixture-toolchain
fix/catalog-source-work-owner
feature/rust-rlib-metadata-revision
fix/rlib-long-name-diagnostics
feature/gptfdisk-runtime-inputs
fix/host-ci-fixture-contracts
fix/input-owner-bootstrap-cohort
feature/cabal-metadata-revision-selection
feature/git-portable-string-configuration
feature/locale-byte-string-producers
feature/owned-vm-input-code
feature/memory-string-family-producers
fix/retained-census-progress
feature/toolchain-cxx-runtime-inputs
fix/catalog-metadata-planning-borrow
feature/native-current-locale-scenario
feature/current-locale-multibyte
feature/source-history-depth
feature/catalog-compilation-input-lifetime
fix/retained-helper-read-directories
feature/owned-coreutils-scenario
feature/scenario-owned-directory-build
feature/build-scope-toolchain-ownership
feature/native-build-source-contract
feature/clean-native-image-closure
feature/readonly-ext4-population-selection
feature/gpt-layout-readback
feature/ext4-format-readback-contract
feature/retained-partition-readback
feature/explicit-inventory-source-revisions
feature/retained-image-driver
feature/retained-image-failed-queue
feature/retained-native-companion-source
feature/retained-fixture-source-paths
feature/retained-image-gpt-inputs
feature/retained-efi-image-build
feature/native-graph-retirement-diagnostics
feature/retained-image-artifact-inputs
feature/native-graph-input-materialization
feature/native-graph-kernel-allocation-contract
feature/retained-image-kernel
feature/native-graph-allocation-runtime
feature/native-artifact-graph-execution
feature/retained-native-runtime-links
feature/compiler-runtime-input-binding
feature/native-boot-linked-artifact-owners
feature/native-compiler-environment-identity
feature/native-graph-object-symbols
feature/native-boot-runtime-link
feature/selected-native-runtime-inputs
feature/graph-compiler-retained-accounting
feature/native-boot-compiler-stages
feature/native-boot-artifact-graph
feature/native-graph-product-integrity
feature/owned-stream-directory-image
feature/directory-stream-workload
feature/native-allocation-error-contract
feature/native-graph-allocation-marker
feature/native-boot-profile-matrix
feature/native-alloc-runtime-input
feature/native-allocation-marker
feature/native-package-version-input
feature/sha2-owned-stream-vm
feature/owned-shell-frame-inventory
feature/posix-compat
feature/exfat-final-upcase-literal
feature/realm-counted-file-resize-fixture
feature/rustdoc-ci-helper-provider
feature/counted-realm-binding-fixture
feature/realm-credential-fixtures
feature/counted-realm-authority-deployment
feature/native-realm-caller-loss-fixture
feature/native-realm-capacity-reuse-controls
feature/configured-private-byte-client-fixture
feature/guarded-private-mediator-fixtures
feature/native-realm-admission-fixture
feature/disabled-realm-startup-controls
feature/explicit-realm-startup-storage
feature/selected-exfat-large-cluster-media
feature/selected-fat-detached-recovery
feature/orchestration-rustdoc-contracts
feature/offline-toolchain-bootstrap-graph
feature/ram-entry-capacity-lifetimes
feature/imported-payload-contracts
feature/offline-payload-source-store
feature/native-gitlink-source-roles
feature/selected-exfat-catalog-growth
feature/dependency-policy-source-custody
feature/selected-fat-undo-catalog-fixtures
feature/process-local-output-observers
feature/live-ci-output-source-closure
feature/plain-ext-undo-fixtures
feature/charged-ci-input-extents
feature/exact-public-ci-source-graph
feature/ci-preparation-progress
feature/explicit-ci-output-custody
feature/python-test-failure-retention
feature/retained-cargo-ci-consumers
feature/source-bound-python-test-shards
feature/isolated-python-host-tests
feature/strict-non-cargo-source-roots
feature/explicit-offline-preparation-command
feature/original-acquisition-integrity
feature/owned-preparation-progress
feature/snapshot-persistence-profiler
feature/original-object-transport
feature/portable-cargo-graphs
feature/generated-cargo-lock-inputs
feature/inventory-bound-source-delivery
feature/original-git-object-custody
feature/original-main-source-pipeline
feature/declared-build-scope
feature/joined-scenario-catalog-lifetime
feature/complete-tracked-source-size
feature/source-preserving-syntax
feature/bounded-startup-profiler
feature/correlated-vm-failure-status
feature/original-native-c-memory-linking
feature/explicit-offline-vm-networking
feature/orchestration-module-contracts
feature/owned-host-command-lifetimes
feature/selected-compiler-cache-inputs
feature/dynamic-compiler-coordinates
feature/watchdog-fixture-writers
feature/dynamic-image-serialization
feature/dynlink-fixture-readers
feature/ci-source-acquisition
feature/cross-repository-policy-checks
feature/native-cli-media-module-controls
feature/explicit-original-ci-source-graph
feature/balanced-python-host-shards
feature/kernel-return-helper-cohort
feature/rootd-fixture-source-selection
feature/enclosing-cargo-work-budget
feature/dynamic-cache-helper-inputs
feature/realm-readiness-workload-group
feature/dynamic-symbol-export-visibility
feature/retained-native-byte-inspection
feature/explicit-shared-library-variants
feature/object-symbol-syntax-coverage
feature/object-symbol-inspection
feature/compiler-bound-shared-identities
feature/scenario-harness-policy-closure
feature/block-fixture-source-cleanliness
feature/cargo-rlib-native-objects
feature/generated-cargo-regression-fixtures
feature/compiler-observation-retirement
feature/cargo-native-compiler-observations
feature/host-tool-admission-checks
feature/ci-scenario-heap-policy-inputs
feature/retained-host-tool-artifacts
feature/retained-source-only-boot-inputs
feature/generated-cargo-lock-refresh-order
feature/retained-native-library-artifacts
feature/retained-efi-artifact
feature/native-boot-command-profiles
feature/native-profile-fixture-storage
feature/retained-service-builder-inputs
feature/native-boot-required-target-features
feature/native-boot-build-profiles
feature/retained-primary-native-artifacts
feature/native-build-fixture-prerequisites
feature/ci-component-fixture-inputs
feature/native-object-fixture-toolchain
feature/coherent-native-boot-source-graph
feature/native-build-validation-inputs
feature/workspace-feature-source-helper-cohort
feature/precheck-owned-live-output
feature/detached-syntax-fixture-storage
feature/workspace-feature-preparation
feature/native-input-progress-diagnostics
feature/native-end-copy-source-controls
feature/current-rootd-fixture-policy
feature/host-cancellation-retained-evidence
feature/clock-ci-tool-components
feature/coreutils-provider-validation-source-graph
feature/coreutils-nested-ci-environment
feature/explicit-console-font-inputs
feature/selector-validation-source-graph
feature/rustdoc-authored-input-controls
feature/readonly-storage-verifier
feature/direct-exsh-default-controls
feature/integration-native-fixture-source
feature/physical-selector-reviews
feature/runtime-root-porting-wave-coverage
feature/four-way-host-validation
feature/physical-command-echo
feature/caller-loss-readiness-controls
feature/offline-command-fixture-lifetimes
feature/cargo-catalog-membership
feature/python-test-phase-profile
feature/block-durability-workloads
feature/timed-clock-contract
feature/component-catalog-source-cleanliness
feature/selected-compiler-target-preflight
feature/shared-cargo-capture
feature/native-c-error-catalog-consumers
feature/native-conversion-consumers
feature/bounded-source-read-cleanup
feature/owned-fetch-capture
feature/readonly-configuration-clis
feature/portable-generated-symbols
feature/gpt-formatter-route-controls
feature/coherent-host-validation
feature/retained-source-blob-layout
feature/external-descriptor-diagnostic-output
feature/inert-cleanup-diagnostics
feature/native-descriptor-query-diagnostic
feature/native-signal-policy-controls
feature/native-binary-output-controls
feature/native-cleanup-diagnostic-controls
feature/complete-file-identity-layout
feature/ordinary-service-read-accounting
feature/retained-compilation-inputs
feature/retained-service-source-comparison
feature/ordinary-service-shared-libraries
feature/kernel-fixture-parser-source-closure
feature/native-descriptor-inheritance
feature/original-source-rustdoc-json
feature/standalone-vm-worker-custody
feature/input-helper-completion-custody
feature/failed-vm-metadata-retention
feature/ci-runtime-profile-contracts
feature/source-signal-disposition-query
feature/source-directory-identity-comparison
feature/native-test-runtime-source-cohort
feature/registry-fixture-source-closure
feature/owned-service-artifact-route
feature/compiled-terminal-provider-inputs
feature/service-source-scenario-cleanliness
feature/coreutils-provider-ci-context
feature/native-vm-process-custody
feature/ci-rustdoc-source-policy
feature/native-runtime-service-source-cohort
feature/ci-native-worker-completion
feature/complete-worker-source-verification
feature/rust-documentation-policy
feature/rootd-complete-policy-api
feature/native-binary-printf-workflows
feature/native-cmp-workflows
feature/runtime-fixture-policy-consistency
feature/vfs-namespace-cancellation
feature/vfs-three-region-capacity
feature/sha2-host-command-fixture
feature/native-sha2-verification-workflows
feature/coreutils-catalog-provider-selection
feature/ext-special-inode-contract
feature/borrowed-product-launch-records
feature/rootd-bootstrap-policy
feature/conventional-terminal-speed-symbols
feature/held-directory-filesystem-workload
feature/terminal-contract-markdown
feature/owned-runtime-fingerprint-inputs
feature/native-c-terminal-runtime
feature/native-runtime-counted-capacity
feature/terminal-control-storage
feature/native-c-time-runtime
feature/scoped-filesystem-source-record
feature/native-c-scoped-filesystem-client
feature/gpt-typed-formatter-oracle
feature/realm-description-policy-oracles
feature/process-root-private-symbol-checks
feature/counted-original-description-pools
feature/scenario-source-read-only
feature/native-c-termios-parameters
feature/process-root-active-dependency-closure
feature/native-c-pipe-creation-probe
feature/native-c-readiness-probe
feature/native-c-multibyte-runtime
feature/native-c-descriptor-io
feature/typed-realm-fixture-prerequisites
feature/native-cpu-local-execution-fixture
feature/caller-loss-fixture-readiness
feature/native-default-acl-inheritance
feature/native-persistent-acl-metadata
feature/catalog-service-build-lifetimes
feature/foundation-fixture-contracts
feature/acquired-catalog-provider-objects
feature/native-ext4-product-population
feature/explicit-ext4-image-initialization
feature/ordinary-c-process-startup
feature/owner-driven-manual-fixture
feature/native-input-failure-diagnostics
feature/native-process-heap-runtime
feature/owned-vm-input-helpers
feature/composed-component-manuals
feature/native-offline-manual-store
feature/pathname-and-shell-help-workflows
feature/dynamic-metadata-page-permissions
feature/native-fat32-esp-construction
feature/owned-gpt-payload-assembly
feature/owned-gpt-image-construction
feature/native-capture-stream-progress
feature/shared-compiler-coordinates
feature/catalog-terminal-waiter-fixture
feature/timed-deadline-adapter-inventory
feature/catalog-cargo-provider-graph
feature/retained-command-retirement-allowance
feature/scoped-boot-image-workflows
feature/lexical-continuation-storage
feature/native-runtime-record-contract
feature/shell-transport-target-layout
feature/recipient-stream-view-packaging
feature/native-runtime-fixture-catalog-controls
feature/counted-job-runtime-policy-storage
feature/native-boot-command-inventory
feature/native-runtime-consumer-cohorts
feature/native-runtime-source-cohorts
feature/native-c-source-owner-cohort
feature/owned-source-cache-identity
feature/native-sha-plan-controls
feature/terminal-packaging-waiter-controls
feature/retained-boot-tool-operation
feature/declared-dependency-feature-selection
feature/shared-object-builder-modules
feature/command-workspace-harness-inputs
feature/native-c-memory-producer
feature/authenticated-publication-policy
feature/command-catalog-packaging
feature/descendant-termination-grace
feature/fixture-socket-io
feature/fixture-startup-ownership
feature/packaging-catalog-layout-controls
feature/owned-boot-tool-producer
feature/native-duplex-socket-workloads
feature/wide-device-fixture-encoding
feature/exsh-packaging-catalog-fixture
feature/caller-loss-helper-source-closure
feature/persisted-filesystem-timestamps
feature/filesystem-time-contract-wording
feature/native-cli-fat-catalog
feature/truthful-filesystem-timestamps
feature/guarded-native-thread-fixture
feature/native-caller-loss-command-custody
feature/elf-original-byte-inspection
feature/native-thread-factory-intake
feature/realm-client-dynamic-registration
feature/externally-clocked-owned-commands
feature/loader-tls-storage-capacity
feature/runtime-heap-policy-coherence
feature/procd-tls-packet-capacity
feature/three-column-client-framing
feature/recipient-readiness-capacity
feature/standard-readiness-storage-policy
feature/ci-component-source-layout-controls
feature/live-realm-filesystem-lifetimes
feature/pty-readiness-capacity
feature/package-assembly-source-snapshot
feature/public-deadline-capacity
feature/counted-job-program-storage
feature/counted-ram-name-storage
feature/realm-fifo-storage-fixture
feature/kernel-fixture-harness-inputs
feature/realm-pipe-clock-policy
feature/retire-legacy-git-transport-overrides
feature/selected-component-catalog-binding
feature/filesystem-compliance-source-evidence
feature/detached-fixture-output-custody
feature/native-default-sigpipe-fixture
feature/realm-directory-relative-open-fixture
feature/realm-linked-parent-mount-fixture
feature/realm-retained-link-image-fixtures
feature/realm-acquisition-scope-fixture
feature/realm-descriptor-alias-fixture
feature/native-fixture-ci-source-graph
feature/portable-git-error-fixture
feature/complete-firmware-fixture-inputs
feature/integration-rust-source-graph
feature/native-cli
feature/phase-4-audit
feature/dynlink
feature/program-loader
feature/e2fs-fat
feature/block-devices
feature/vfs
feature/centralized-process-authority
ci-feature-interactive-probe-diagnostics
ci-feature-ci-source-acquisition
ci-feature-posix-compat
nightly
ci-feature-native-cli
ci-feature-phase-4-audit
ci-feature-dynlink
ci-feature-program-loader
ci-feature-e2fs-fat
ci-feature-block-devices
ci-feature-vfs
ci-feature-centralized-process-authority
Labels
Clear labels
alpha-1
EriX Alpha 1 release acceptance
bug
Something is not working
ci
docs
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
performance
Measured performance profiling, bottleneck analysis, and regression budgets.
phase-6
Phase 6: POSIX compatibility, full EriX self-hosting, and its required audits and validation.
question
More information is needed
refactor
Code cleanup, removal of obsolete paths, and structural improvements preserving behavior.
security
wontfix
This won't be fixed
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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/integration#1
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem and motivation
A full in-EriX build needs an explicit inventory of every product, generator and runtime dependency. POSIX and toolchain work otherwise risks targeting a small demonstration while leaving image assembly or documentation dependent on an external host.
Proposed behavior and scope
Actual mediator startup witness — 24 September 2026 (implementation pending): retain the existing unstarted
bin/truepreparation fixture and add a separate opt-in shell diagnostic that prepares the actual packagedbin/posixd, requests private START with explicit 256-byte request/result budgets, and requires PrivateReady. Keep two original realms simultaneously running, retire the first, require the second still PrivateReady, then retire the second and require stale reads to fail. The caller borrows only its existing explicit cwd scope and launch route, accepts no returned capability, and emits success only after both complete retirement acknowledgments. The image includes the actual Posixd artifact only when this fixture is explicitly selected. Preserve the existing authority refusals, cleanup checks and VM deadline; no full realm/client-I/O or self-hosting claim follows from this startup witness.Private start admission refinement — 24 September 2026 (implementation pending): add Launchd START_REALM operation
0x6D4with an exact 40-byte authority-free request: request/op at offsets 0/4, original realm/generation at 8/16, and explicit request/result byte budgets at 24/32. The actual pending native caller must still own that retained realm. Validate packet arithmetic and both minimum 96-byte budgets before effects. Preserve all existing BEGIN/PREPARE/READ/ABORT selectors and the ordinary process-start gate.Extend descriptive realm state with Starting (6) and PrivateReady (7), retaining values 0–5. Reuse the existing 40-byte admission response; a successful START acknowledgment requires PrivateReady. The service retains the original response obligation while its immediate private caller and configuration-server owners progress. READ may describe Starting; a lost public response or cancellation retains exact cleanup. PrivateReady proves the observed native-child Ready and confirmed independent controller challenge plus retirement of Launchd-owned transport handles. It does not claim that server COMPLETE observes Posixd's later caller RELEASE, nor does it seal, publish or grant client access.
Private provisioning transport refinement — 24 September 2026 (implementation pending): the guarded preparation request remains non-starting. Add separate typed Procd operations for Provision (
0x433), private Start (0x434) and exact Retire (0x435), all admitted only from the original Launchd generation on its held private receiver. Provision carries a 48-byte request with exact child and realm identity plus explicit request/result byte budgets, and exactly one moved Generic SEND configuration receipt. Procd derives the actual child capability extent from its retained creation geometry, installs configuration at child slot 5, and computes page-rounded startup/workspace mappings beyond the recorded executable extent. Its successful 224-byte response returns the canonical 208-byte startup record after a 16-byte correlation/result/state prefix; failure carries no startup bytes. Start and Retire each carry 64 bytes with the original child/realm and canonical startup digest, preventing cross-stage substitution. These bytes constrain actual held routes and never confer authority.Procd has no existing own-process identity in its startup payload. Reuse native caller attribution through a separate 64-byte configuration ContextProbe/Ack before RBS1 construction. The probe carries correlation, realm/child and original Launchd identity, with zero controller fields; Launchd obtains the Procd pair from actual CLAIM, retains that original pair and echoes it in the correlated acknowledgment. Procd retains the accepted invocation through retirement before committing the resulting context. This adds no kernel identity query, process endpoint or permission to trust an arbitrary first challenge. Posixd still requires its supplied controller to match the challenge's actual native caller.
Launchd explicitly reserves four capability columns per admitted realm in its authenticated deployment geometry. It creates the configuration receiver before exporting SEND, binds an ancestor revoker to its own native lifetime, keeps a separate nested revoker for early retirement, and removes all bypass source aliases. Original executable-scope storage may be reused for temporary construction only after its absence is acknowledged. Procd retains the received configuration sender in an already empty role-owned scratch column, accounts for every mapped frame and setup alias, consumes the actual GRANT through operation 58 only after provisioning, and records uncertain start disposition before the native start effect. No grant-derived MINT capability or ordinary-start fallback is added.
Private Start completes only after native start and the independent control challenge have completed their owned caller cleanup; readiness uses Launchd's separate actual-child CLAIM and full startup digest. Invocation handles and application owners remain retained on cancellation, malformed response, lost reply, supervisor loss and partial disposal. Retire selects running termination after any possibly committed start and waits for exact terminal observation/destruction before acknowledging final retirement. Frame allocation and each handshake must preserve explicit ownership and bounded progress; ordinary staging and all existing refusal/cleanup witnesses remain required. Provision, Start, readiness, seal, publication and client I/O remain distinct acceptance steps.
Private mediator execution design — 24 September 2026 (implementation pending): the next native witness executes the actual Posixd binary using the existing serialized process mapping path. Private address-space-root routing remains separate work; source review found no dependency that requires it before this witness.
The shared contract will add a distinct counted RBS1 startup image: exact version/byte extent; original realm and generation; native child, Launchd supervisor and Procd controller identity pairs; ordered endpoint and writable-workspace records; explicit capability-window and request/result/receipt storage budgets. The initial schema admits exactly a control RECV endpoint and a configuration SEND endpoint, with no root object, Process route or factory. Reject unknown roles, surplus records, duplicate slots, reserved bits, arithmetic overflow and overlapping storage. Counts describe the supported bootstrap roles, while deployment inputs set storage budgets. Startup bytes are child-read-only/NX; Procd verifies installed inventory and separate private RW/NX workspace before execution. The consumer checks actual local capability types/rights. The complete canonical bytes are SHA-256 correlated in readiness and the independent control challenge; parsing and digests grant no authority.
Provisioning finishes by consuming the existing GRANT-only installer through native child-lifetime binding (operation 58), without adding MINT or another installer. Record uncertain binding/start effects before replying. Native start independently requires an empty installer census. Adopt generation-bound native running termination through a new Process operation 61: original child/generation and kill reason, zero reserved fields, no extra route or rights. The generation comparison and terminal transition share native lifecycle serialization; stale requests must never select a replacement. Its acknowledgment is distinct from terminal observation, invocation retirement and native destruction.
Posixd will register only its declared control receiver and use immediate owned operations to submit readiness through its declared configuration SEND while continuing bounded control progress. Launchd authenticates readiness from actual CLAIM origin. Procd independently challenges its retained control endpoint; COLLECT payloads do not attest a server identity. Both exchanges carry exact original identities and startup digest, admit no capabilities at this bootstrap stage, and retain every accepted native handle even on unusual immediate status. Configuration, sealing and client publication remain later separate gates.
Required evidence includes strict codecs and actual inventory denial; committed-effect/lost-reply ownership; wrong/stale caller and generation denial; running-child retirement; supervisor loss; and a maintained VM executing Posixd with native readiness and challenge. Existing unstarted staging regressions remain required. Subsequent acceptance still requires two mediators, two clients each, mediated byte I/O, cross-realm refusal and full retirement, followed by the external toolchain rebuild and both complete guest OS build generations.
Build-host and emitted-target matrix reviewed — 24 September 2026:
x86_64-unknown-erix; includes EriX libc/sysroot, Rust OS bindings and the selected C/C++ runtime closure. These ports and their execution remain unproven.x86_64-unknown-noneand existing native ABI/link contracts.x86_64-unknown-uefi; building the OS inside EriX still requires this cross-target output.Reviewed original sources: native kernel builder, native service builder, UEFI build recipe, compatibility toolchain scope, and build/output contract. Commit signatures and exact local file equality were verified. Recording this matrix closes its specification item only. Complete output/recipe inventory, compiler porting, rebuilding Rust/LLVM/runtime inside EriX, and both full EriX guest-build generations remain required and unproven.
Detailed scope and contracts
Caller-owned transport scratch — 15 September 2026
Move both full-capacity shell transport buffers into the authenticated caller-owned workspace: ordinary message I/O and the descriptor transaction's emergency cleanup. The current descriptor state is exclusively borrowed while a transaction lives, so the transaction can borrow its cleanup slice directly. No global scratch lookup, shared mutable cell, runtime lock or new capability is needed. Remove the unsafe static message accessor and the 32 KiB automatic cleanup array. Preserve the 64 KiB process stack and all current upper stack ceilings.
Group descriptor backing storage explicitly at startup, validate cleanup capacity and clean bytes before constructing effectful state, and keep the cleanup slice disjoint from ordinary transport, history and other arenas. A transaction temporarily borrows that slice, retires providers in the existing order, erases the full borrowed extent and returns the borrow; explicit restore and already-retired resolver paths retain their existing behavior. Failure and uncertain ownership must retain their existing fail-stop rules. Do not introduce shared aliases or fallback storage.
Coordinate target and image-builder layout version 22. Export the target transport-array size/alignment in the layout description, allocate both buffers in identical typed carve order, and reject old or mixed descriptors. Preserve caller resource policy and complete transport capacity; this is an ownership/layout change, not a smaller-message workaround. The frame inspector must eventually bind the full workspace reservation instead of requiring a now-removed stack array, while still rejecting unproved ordinary-source and direct/nested bounds.
Required evidence includes clean/short/dirty scratch, canary/erasure/reuse, early error, explicit restore, handoff, uncertain cleanup and existing shell regressions; exact target/producer layout agreement and old-version refusals; strict warning-denied Rust/helper matrices; actual optimized frame inspection; and relevant bounded runtime VMs before product acceptance. Keep the complete frame gate and full self-hosting criteria open until their own evidence exists.
Staged construction without root capabilities — 15 September 2026
Add kernel-control operation 54, CREATE_STAGED_PROCESS_WITHOUT_ROOT_CAPS, and checked StagedProcessWithoutRootCapsV1 scalar framing. Successful creation returns a live Created process and nonzero generation whose CSpace contains exactly its requested primary endpoint, with no CNode, VSpace or TCB capabilities. Native CSpace/TCB/VSpace objects and the process's VSpace lifetime reference still exist. No child code executes during construction. The endpoint initially retains its ordinary full endpoint rights; operation 53 independently narrows it before bootstrap execution.
Keep the existing creation operation 32 and its producer behavior unchanged. The new selector is independently recognized: an older kernel refuses it, and callers must not fall back to old ignored flags or a child self-report. Admit it only on the existing Process endpoint family, without adding a capability type, endpoint factory or ChildPopulate creation authority.
Use the existing fixed request envelope. arg0 contains the caller-local install-grant destination in its low 32 bits; its upper half is zero. arg1 low/high halves contain child-local primary endpoint and caller-local endpoint-master destinations. arg2 low/high halves contain the child window base and optional caller-local VSpace destination. arg3 contains the 32-bit window length, with a zero upper half. Flag bit 0 means that the VSpace receipt is requested; all other flag bits are zero. When the bit is clear, arg2's upper half must be zero. This explicit presence bit distinguishes an omitted receipt from a real receipt in slot zero. All slot fields retain their full unsigned width; slot zero and otherwise vacant former root positions are ordinary requested slots, subject to native bounds, actual caller-window visibility and occupancy. The checked codec validates framing, not native capacity or authority. The native constructor requires a valid child window containing the primary endpoint.
The caller receives only its actual unique stage-bound install grant, endpoint master and optional MAP-only VSpace receipt. The grant is bound to the returned process/generation and exact child window. Existing capability ceilings, actual object identity and explicit disposal rules remain in force. Temporary native setup bindings must be gone before constructing the final primary endpoint and publishing the grant; otherwise former root positions would remain an unnecessary destination restriction. The TCB's independently held VSpace reference must keep backing alive even without any child or parent VSpace capability.
On failure, destroy the partial child and dispose only successfully created parent receipts. Preserve pre-existing or overlapping destinations and the original failure; uncertain cleanup fail-stops. Never treat a requested slot as evidence that its capability was created. The new contract supplies an initial inventory, not a permanent prohibition on later explicitly authorized installations or a sealed realm. The returned grant remains a real pre-start population authority that its owner must account for and retire.
Required checks include full-width codec/reserved-field cases, omitted versus slot-zero VSpace receipts, zero/former-root/last-slot endpoint destinations, invalid or inaccessible windows, occupied/overlapping outputs, exact parent and child inventories, no residual native objects, mapping/startup backing retention, attenuation through the actual grant and abort/terminal cleanup. Actual CPL3 creation/refusal/disposal must complement host tests. Procd adoption must select this operation only for the mediator role and preserve all ordinary start gates until authenticated grant return, minimum typed startup, retained native/nested guards, readiness, configuration/seal and fair retirement are independently implemented. No runnable realm or guest build is established by this constructor alone.
Inventory the repository and target graph, create the required components from meta, freeze the tool/API workload and authority model, and define the complete two-generation acceptance contract. Include firmware, signing, manuals, console/input behavior and all four image profiles.
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
Define trusted owners and capability ceilings before implementation. POSIX metadata and ABI identifiers remain descriptive, resource budgets come from workload evidence, and immutable source selection uses full commit hashes. The inventory cannot authorize release promotion.
Apply the priority order: security, reliability, then performance. Keep suspected vulnerabilities in the repository’s restricted SECURITY.md reporting channel.
Acceptance criteria
Checklist
profiles, feature combinations, scripts and maintained tests. Record repository paths,
remotes, exact heads, dirty state and build ownership.
feature/posix-compatbefore each repository's first edit; verifyexact dependency pins and signed ancestry from the accepted base.
creating absent repositories in Forgejo from meta, then cloning. Record the
existence/template/clone result for each of these three required components.
boundaries, rustdoc, strict CI, tests and specialized canonical docs. Keep import
recipes/profiler in Integration; do not invent extra daemons/repos without a concrete
ownership need and recorded design review.
policy; validate the exact transitive source graph.
crate/library/binary, kernel, EFI bootloader, native build tools, boot image, dynamic/launch
metadata, four image profiles and release manifests.
checksums/compression/signing steps and their host executables. Include these in the in-EriX
build closure; distinguish external test execution from building.
compatibility libraries for
x86_64-unknown-erix, plus the existing bare-metal and UEFItargets needed to rebuild the OS. Do not rewrite native target ABIs merely to make imported
tools run.
Git, shell, image and documentation recipes; map every required call/ELF feature to an owner,
implementation item and independent test.
and optional extensions. Mark unsupported optional surfaces explicitly; never claim full POSIX
certification from a selected build workload.
standard descriptor inheritance expectations. Preserve native authority ceilings; specify any
compatibility deviation before implementation.
posixdisolation, process mediation,TLS, fork snapshotting, signal delivery and build realms. Enumerate trusted components and
keep POSIX policy out of the kernel/rootd.
workloads; distinguish ABI/hardware bounds, authorized quotas and accidental hard-coded
limitations.
implementation: source-only inputs, no host build delegation, two clean in-EriX builds,
deterministic artifacts, boot result and authority-negative tests.
enrollment, native build-tool targets, man/help coverage and console/input interfaces; assign
each an owning public issue and acceptance test.
v1.0.0-alpha.1as the intended manually reviewed release baseline,coordinating platform/component version policy without premature version bumps, tags, PR
readiness or release publication.
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
A target-triple-only port or single-crate smoke test leaves compiler-host APIs and packaging helpers unresolved. Freeze the actual required graph, while explicitly recording optional POSIX surfaces and later-phase non-goals.
The 62-capability allocation-rejection controls execute against actual kernel objects on the host; these VMs validate the existing IPC/lifetime paths. The existing intermittent quota timeout remains open in Integration issue 18; later successful runs do not establish its cause or a causal fix. Current transfer-preparation workflows 1611/1612 are running; their full-suite acceptance is pending.
The existing intermittent quota timeout in Integration issue 18 remains open with unknown cause; later passes do not establish a causal fix. 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.
This is existing-path regression coverage; new owned-invocation CPL3 peer acceptance still requires a wire adapter. 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. The next bounded change will retain only non-authoritative numeric search positions: every fast path must still check current capability type/rights, endpoint identity/in-use state and exact CSpace/slot binding, with complete lookup on a stale hint. Original workload bytes and sample policy must remain unchanged for comparison. 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
8349d68636382cc7e25a3347f5f1df216554203aretains 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 IPCde968da19898bef532ddb3b5974bb9562f51dee5, capability ABIa001a26f0eb3aebec3f5fd02a28d98f1bc23f8a0and Integration9030b217c490db6ad3ec60a799cb025eccbfcdb1implement 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
60da5858d7198185efd103f0e91e5ac2e0b63e67implements control operation 52, checking the actual moved install grant against expected process/generation with exact rights, including zero, under existing endpoint policies. Signed Procdf1105706cc19ed024a6cca79a29abc57c90c6661uses 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.Pin the corrected native graph and require ordered, unique constructor/cleanup evidence while preserving the owned-invocation and ordinary scenario oracles. Actual grant-return provisioning, authenticated receiver readiness, configuration/seal, client I/O, fair retirement, whole-codebase authority/documentation closure and both complete guest build generations remain required. No runnable Posixd realm or guest-build acceptance is claimed.
Native creation rollback acceptance — 15 September 2026: Staged construction now retains a receipt for each successful parent copy until commit. On later failure it destroys the child and disposes only those new endpoint/VSpace copies, preserving pre-existing or overlapping output bindings. The transaction has a separate documented module. Eight actual constructor refusal cases check complete parent inventory and native VSpace counts. Kernel b853d51cfb36c2fbc81eb565b7d2fc3ab731de2b passes 649/673 default/all tests, strict host/native development/release Clippy, private rustdoc, formatting and ten native builds, with three existing ignores. Matching CI 566/567 passes with four complete warning-free logs. Integration
3c4e260256passes both actual native VMs with empty QEMU stderr and clean teardown. The lifetime fixture now includes seven creation/refusal/disposal calls alongside the thirteen installation calls; the existing owned-invocation oracle is preserved. Integration Rust/helper sources are unchanged and retain their completed 320/321-test strict matrix and all 162 helper results; changed native catalog inputs have fresh policy and VM checks. Full Integration CI 1627/1628 remains pending. Typed grant-return provisioning, independently constrained bootstrap authority before mediator execution, readiness, configuration/seal, client I/O, fair retirement and both complete guest build generations remain open. The code inventory covers 76 repositories and 2959 files below 1000 lines; all 158 scanned Rust roots enforce missing_docs. Whole-codebase semantic authority and private-item documentation audits remain incomplete.Signed helper
cdf15c52f24bd463dcabdddb945f779fff4ab367excludes shallow local caches before an exact dependency fetch. It preserves the cache, selects the canonical catalog URL without following cache remotes, and requires original complete history. Three new real-Git controls and all 162 helper commands pass, along with 320/321 Rust tests per development/release configuration, strict host/native Clippy, four native builds, formatting, private rustdoc and Markdown with no warnings. Actual Rootd standalone preparation also passes using a shallow helper fixture and complete original Cargo metadata. Runtime library2a16b1a7ac5514a43582025e5b9ba0a2f2ce2a29and product catalogs remain unchanged. Full Integration CI for this helper commit is pending; no new VM or guest build 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
38424571b76b36c1e631d99fd2c859fb32311eeaexports/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
79cdd4c3694e800091b55c737fca04c7bdd3d071describes 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.Native companion correction design — 15 September 2026: centralize the complete eight assembly body/export inputs and original producer script as one reviewed native support contract shared by selection and support-manifest validation. Compare the full producer input set without dropping unknown, missing, altered or misidentified records; retain exact waited tool, cleanup and output checks. Coordinate the native lib-cstd catalog pin with original
bdcbbea43550e8b99cd9a8221e4bc5a645637990. Include the contract module in both outer artifact fingerprints, update independent fixture inventories, and exercise actual hidden/public output against that original source. The existing shell workspace/catalog and complete frame/VM acceptance requirements remain separate. Tracks #52.Complete native companion checkpoint — 15 September 2026:
Signed Integration
db80a2c1dfc669bd724762d476f5f5c0da005ff6centralizes 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 originalbdcbbea43550e8b99cd9a8221e4bc5a645637990. 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
31bd9524c31c9d8d6a8f00248f702e6b7d428106explains 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.Packaged workspace evidence design — 15 September 2026: Replace the obsolete automatic-stack-scratch requirement with a separate mandatory workspace mapping domain. The checker will accept an explicitly selected pristine ELF and optional corresponding packaged ELF, capture both under its existing owner/budgets, and require the packaged artifact to retain the pristine entry and executable bytes. Missing packaged input remains incomplete. A complete mapping domain requires the unique version-22 read-only descriptor, unchanged target type layout and full transport capacity, exact descriptor/arena extent, two disjoint complete transport spans, unique writable/non-executable zero-fill arena ownership, and the unchanged separate 64 KiB stack. Overlapping section/load/page claims, stale or mixed layouts, executable changes and relocation writes into the descriptor must fail. No cache receipt or caller-supplied success flag substitutes for actual artifact bytes.
Local fallback stack accounting remains independent and retains its existing upper bound; register pushes or an old 32 KiB stack reservation cannot certify workspace storage. This mapping domain does not prove source-level borrowing/erasure, complete typed arena carving or every machine call path. Existing source tests and exact build identity retain those separate contracts. Ordinary-source membership, direct-versus-nested bounds and unproved indirect targets remain incomplete, and the full gate remains nonzero until every required domain is established. Add original positive/malformed/overlap/mismatch fixtures and replay the unchanged actual runtime/all artifacts and their existing dev/release packaging. No runtime code or stack budgets change in this checker slice.
Paired workspace mapping checkpoint — 15 September 2026:
Signed Exsh
f17670c7f0c3b6da4458deac534ba6210921550dadds paired pristine/packaged ELF workspace evidence under report schema 2. The checker captures both regular-file snapshots under its existing budgets and retains them when pair admission fails. It verifies the version-22 target descriptor, complete transport spans, exact arena extent, unique zero-fill arena/stack ownership and the unchanged separate 64 KiB stack. All mapped file bytes and permissions must match except tunable capacity words and the workspace owner's extent. Stale/mixed layouts, changed code/data, overlapping claims and relocation writes into descriptor/arena/stack bytes fail before the disassembler runs.The obsolete automatic-stack-scratch requirement and redundant prologue-reservation scan are removed. Local frame ceilings remain 8/33/56 KiB in their existing domains; a local stack frame cannot supply workspace evidence. Mapping success assumes the native loader preserves the declared mappings and does not prove source borrowing, erasure, complete typed carving, ordinary-source membership or direct-versus-nested bounds. Unproved indirect targets remain unresolved.
All 90 warning-denied checker tests pass, including 17 new independent mapping/CLI controls. Formatting, Markdown and canonical checks pass. Four exact retained runtime/all-feature artifacts with canonical dev/release packaging establish the mapping domain: workspace 4,300,800 bytes, two complete 32 KiB buffers, separate 64 KiB stack. Both local fallback frames are complete at 48 bytes. Full reports remain INCOMPLETE with 691/604 unresolved observations and the original source/direct-path gaps; no full frame pass is claimed.
Rust, Cargo and linker source bytes are unchanged from workspace checkpoint
b12e172e7b266842a8659104894f6821166165fb. Its 961-test strict matrices and eight native builds retain that source scope; the paired replays retain their original ELF hashes. The earlier three diagnostic guest probes also retain their original image/source identities and are not new runtime execution at this checker head. Exsh CI 227/228 fails the remaining full frame gate after all 961 Rust and 90 checker tests pass. All four logs are complete (311,713 bytes) with zero warnings. Both fallbacks are complete at 48 bytes; CI runtime/all graphs retain 662/587 unresolved observations. CI supplies no packaged counterpart, so its workspace mapping domain remains incomplete; the four local paired-artifact results retain their separate scope. The cohort is fully classified without accepting any missing proof. Matching Docs5d77dc2b82bf5439e58234d901e30f4565aaa81ais signed and pushed: all 45 tests, the complete warning-free 2,375-page render, 433,924 in-bounds word boxes, literal-option extraction and nine-page visual review pass. 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. Its issue erix/docs#8 records the 24 repaired inline-option/delimiter cases and is closed after complete CI classification. Full frame proof, coherent product admission, realm work and both complete guest build generations remain open.CI packaged-input checkpoint — 15 September 2026:
Signed Exsh
453641cd19eaa7c85a8f6693363f8660c792ed73supplies packaged counterparts in CI. Its helper is pinned to original Integrationdb80a2c1dfc669bd724762d476f5f5c0da005ff6. The actual producer packages separate copies of each optimized runtime/all-feature ELF using both canonical dev/release policies. Packaging has a 60-second deadline, refuses existing outputs and stops the job on failure. Each pristine/packaged pair gets its own complete checker invocation; any unresolved required domain keeps a nonzero status.The exact changed workflow block was replayed against both retained native binaries. All four produced ELF hashes equal the previously independently validated production bytes, workspace mapping is complete, and pristine inputs remain unchanged. The full reports remain incomplete with 691/604 unresolved observations and unproved source/direct-path domains. YAML and shell syntax, 90 checker tests, formatting, Markdown, canonical and pinned dependency checks pass without warnings. Rust, linker and checker source bytes are unchanged, so their earlier strict validation retains its original source scope. Current Exsh CI 229/230 is fully classified: both runs pass 961 Rust and 90 checker tests and all four workspace-mapping domains, but fail the remaining full frame gate. All four complete logs total 314,746 bytes with zero warnings. Runtime/all graph observations remain 662/587 and fallback local frames remain 48 bytes. This resolves the missing packaged-input domain; source membership, non-returning/indirect targets and direct-versus-nested path proof remain open. No full frame proof, product admission or guest build is claimed.
Native final mapping design — 15 September 2026:
Implement validated RELRO final permissions within the existing native materialization protocol. Loaderd retains authenticated original ELF bytes and original PT_LOAD relocation ranges for Dynlinkd. It separately derives page-bounded final materialization fragments, clearing WRITE on the complete declared protected region. Procd's existing transaction remains the sole owner of privileged construction writes and final mappings; no new control endpoint, capability, lookup root or wire operation is introduced. The child remains unstarted until all bytes and authoritative relocation writes succeed.
Validate range arithmetic, mapped coverage and every writable byte sharing a protected hardware page before starting a transaction. Rounded protection must neither leave a declared byte writable nor silently remove write permission from unrelated mutable data. Permit multiple checked regions without a fixed region-count cap and preserve normal images that declare none. Preserve exact file/BSS coverage, load bias, initial writable stack selection, relocation authorization, abort precedence and uncertain-cleanup behavior. Final fragment counting uses checked arithmetic and caller-owned source bytes, without an additional persistent table.
Independent tests will cover partial and complete segments, page sharing, adjacent/multiple regions, missing mappings, overflow and mutable-page conflicts. Transaction tests must preserve original relocation ranges while emitting final read-only permissions, apply construction relocations successfully and retain failure/abort behavior. Run strict host/native Rust matrices, the complete existing tests, relevant native VM checks and warning-free manual/CI validation. This establishes final mapping permissions only; typed grant custody, whole-codebase authority closure, exact native frame proof and both complete guest builds remain separate requirements.
Specification provenance: the LSB program-header definition and GNU linker options describe the relocation-protected region and hardware page-size constraint. The implementation and fixtures will be original; no external implementation is copied.
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
d221e725c2543316680e63fc5e8314ce0fe3bdf1documents 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.Four independently selected wrong refresh, exact-expiry, marker and status decisions are rejected. The real subprocess refusal cases and production watchdog code/deadlines are unchanged. Bug #53 remains open pending matching CI.
Maintained native permission regression design — 16 September 2026: add an explicit-input host runner and read-only hardware observer for a selected native image/ELF. Require selected QEMU, GDB, firmware, acceleration, CPU count, private temporary/evidence roots and recorded byte identities. Use a private Unix debugger endpoint, disable debugger auto-loading, match complete executable bytes at CPL3, and accumulate effective user/write/execute restrictions across the live four-level tables. Verify protected RELRO pages and the writable non-executable stack, plus execute-disable setup on every selected CPU. Continue the unchanged native inherited-stream commands and budgets after observation. Keep both process statuses, bounded cleanup and unchanged source-image checks mandatory. Extract pure ELF/page-table validation for independent malformed/permission-negative controls. Existing failed diagnostic images remain negative evidence. This adds no guest capability or lookup authority and does not replace instruction-fault, full frame, realm or guest-build acceptance. CI activation must use a coherent catalog containing the required Loaderd and Kernel revisions; the older maintained catalog must not be silently replaced or labeled accepted.
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
3fb0b12ff55d044cc4bbe142418ab7a5b07bb42ddocuments 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
83b2d4a2dfc473bb8a99719f86fa1c3c33effa53explains 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
97ce65dcb8cef7232b50d53af90ff8673d623e05documents 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.Mismatched bytes, operands and prefixes refuse.
Replaying the same exact artifact pairs now admits each
memmoveframe at eight local bytes and removes its one unsupported-instruction observation. Runtime/all-feature reports retain 180/149 unresolved observations, all unknown indirect calls or branches, with thirteen grounded no-return facts each. Original input hashes and budgets are unchanged; workspace mappings pass and full frame/source domains remain incomplete.Every Rust, Cargo, linker, build and workflow input is byte-identical to the preceding checkpoint's six strict 961-test configurations and six native builds. Those results are retained at their original identity; this checker-only follow-up claims no new Rust or guest execution. Matching Exsh CI 235/236 is fully classified: all 961 Rust tests, 117 checker tests and four workspace domains pass, while the full frame gate remains incomplete. All four complete logs total 314,740 bytes with zero warnings. Those CI artifact identities retain 182/144 unresolved observations, distinct from the local retained pairs. No whole authority, realm or full guest-build acceptance is added.
Release-input diagnostic design — 16 September 2026: foreground interrupt reuse #54 and COM1 shell lines #55 have complete terminal CI logs but unavailable inner artifacts. The original 486 scenario suites pass; the separate release input failures have no demonstrated shared cause.
Extend the existing bounded native-input progress formatter for the maintained three-line and physical interrupt/reuse profiles. Render only allowlisted event names and command indices from a complete sequential log prefix. Correlate the original private runner receipt and independently observed wrapper status; for physical VM stall/timeout, retain unknown input status and cleanup-request information rather than claiming injector failure or cleanup success. Read only existing fixed-name files through the retained private directory descriptor, keep current byte/record limits and mutation checks, and print no raw command, guest text, token, path or exception. Diagnostic output cannot change probe success, failure precedence or any original timer.
Add original literal positive/malformed/privacy controls, producer-contract checks and real wrapper status tests. Validate the complete changed Integration tree and document the operator interpretation before a signed checkpoint. This improves subsequent evidence; it neither recovers the missing original receipts nor fixes or closes the two underlying regressions.
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
c4bfc12245036f069d178a10183bb1ed15b4aab5updates 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.Measured parser checkpoint — 16 September 2026: signed Exsh
ffbe846cbcd0ab6ea12a476c2c84339f635ee50acompiles the three unchanged disassembly regexes once per input.All eight runtime/all-feature observations preserve their original nonzero checker exits and identical complete decision reports. Only checker-source identity and private snapshot path metadata differ. Workspace mappings pass and the same 180/149 unknown indirect observations keep full frame/source admission incomplete. All 117 checker tests, formatting, canonical documentation checks and the 2,999-file physical ceiling audit pass. Every Rust, Cargo, linker, build and workflow input remains byte-identical to the existing six strict 961-test configurations and six native builds; no new Rust or guest execution is claimed. The focused contract documents the measurement and limits; the unchanged manual's stack model remains applicable. Matching Exsh CI 237/238 is fully classified: all 961 Rust tests, 117 checker tests, Markdown and four workspace domains pass; both runs fail the still-incomplete full frame gate. All four complete logs total 314,754 bytes with zero warnings. These CI artifacts retain 182/144 unresolved observations, the same counts as preceding CI and distinct from the local retained artifact pairs. Whole authority, realms and both full guest-build generations remain open.
Integration diagnostic CI 1645/1646 remains queued at its signed head; original release-input bugs 54/55 remain open.
Register-target proof design — 16 September 2026: the current runtime/all-feature artifacts retain 180/149 unresolved indirect observations. Six/seven immediately adjacent protected-slot loads are only candidates: textual proximity does not prove every incoming path. Extend the existing finite stack CFG with register facts for all sixteen baseline x86-64 general registers. Entry values are unknown. Exact byte-checked 64-bit RIP-relative loads can acquire a target only from the existing complete immutable relocation/RELRO proof; exact 64-bit register copies carry that evidence. Immediate integers, names, mutable data and stored pointer words supply no target.
Join facts only when every incoming path has the same target value, retaining all contributing load sites and protected-slot proofs. Explicit and implicit writes invalidate each affected full-register family, including partial aliases. Unknown effects, system calls and ordinary calls clear facts; no callee-saved convention, returned function pointer or stack spill becomes an unproved preservation premise. Existing probe/dispatch macros conservatively discard register facts until their complete effects are represented. Unsupported instruction/control-flow cases remain incomplete under the existing trusted-decoder and ordinary-call model.
Revisit weakened joins and replace stale call/branch evidence; an earlier strong path cannot survive as the only proof after another predecessor loses its value. Exact register-call/tail bytes must agree with the selected register. Preserve call depth, tail restoration, grounded return dependencies, unknown branches and the full source/domain gates. The finite worklist and provenance sets use the caller's original deadlines with no invented iteration or origin-count ceiling.
Add independently authored positive, alias/implicit-clobber, bypass, disagreeing/equal-join, loop, stale-edge, call/syscall and source-receipt controls. Replay both original artifact pairs, measure analysis work, update the focused/manual contracts, and validate/sign/push before any adoption. This is original code derived from the Intel instruction reference; it imports no implementation code. Complete guest-image identity, source membership, authority and both full guest-build generations remain separate required work.
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
4f770bee4c6a4784b4fcce6ae606d1fc10b328dadocuments 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.Continued original CI failures — 16 September 2026: Integration 1636 at
cdf15c52f24bd463dcabdddb945f779fff4ab367passes all 486 catalog scenarios and earlier native probes, then the development COM1 directory gate fails after command 5 injection. Three complete warning-free logs total 13,307,223 bytes; bug #56 preserves its exact status and remaining diagnosis. Paired CI 1635 retains the separate release shell-line failure in bug #55; both original runs are terminal, with all six logs retained.Integration 1637 at
38424571b76b36c1e631d99fd2c859fb32311eeapasses 408/486 catalog scenarios and fails 78 during version-22 producer/version-21 catalog-shell preparation. Three complete warning-free logs total 13,031,316 bytes and retain 78 layout refusals. Bug #57 tracks coherent adoption after the source/frame/runtime prerequisites. Mixed-layout rejection remains required. The same paired CI 1638 remains live; later queued runs retain their original handles and observation policies. No retry, timer relaxation or full Integration acceptance is claimed.Register checkpoint CI — 16 September 2026: Exsh
da8b75c9063c52de2149f2a6c7ed170f720a6c62is 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
4f770bee4c6a4784b4fcce6ae606d1fc10b328dapasses 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
242b78c8f35aeaef879f819c670574a4c1d95c3fexplains 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
242b78c8f35aeaef879f819c670574a4c1d95c3fpasses 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
d8fbc3a1f3696e02954b81f23511cee513ddfa8cpasses 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
12331e26f3bb7a25c0146c8b314eef46dd451099loads 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.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.
Release-baseline planning acceptance — 16 September 2026: the existing signed release policy identifies
1.0.0-alpha.1with OS self-hosting, defines the platform/component version relationship and retains all pre-alpha components at0.1.0. Runtime acceptance, two complete guest builds, release readiness, merging, tagging and publication remain separate requirements; no release action was performed.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.Remaining original CI results — 17 September 2026: permission CI 1644, exact
89d15e4536004c087dcebd63c87216c0fd58958d, finishes with 408 passing and 78 known layout refusals. Release-input CI 1645, exactdf8147dfa437194cd091747fd7147941bd2793c4, finishes with 405 passes and 81 failures: those 78 layout refusals, the original quota timeout, and new 120-second FAT32 mirrored/Unicode timeouts. Paired CI 1646, at the same source revision, records 408 passes and only the 78 layout refusals. The separate FAT32 observations are tracked with the canonical bug template in #58; a common cause with quota is not established.All nine terminal logs are complete, totaling 40,256,559 bytes with zero warning candidates; host/Rust/Markdown checks pass. Original artifact APIs expose no images or inner receipts. Both formerly pending cohorts are fully classified, with their original failures retained. No run was restarted, no limit was increased and no complete product or guest-build acceptance is asserted.
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
24cefeb2dc6d3f163140d32f5fed5a7e1a768ebdupdates 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
469bf1f1b9d8301cf98a79d16c7c27660ecda2a1passes 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
24cefeb2dc6d3f163140d32f5fed5a7e1a768ebdpasses 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
44cd6c4aa95bebfa08c99804fab0f1551f537ae1specifies 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
ac9646c84e432129a872737789a9be08f984b881passes 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
44cd6c4aa95bebfa08c99804fab0f1551f537ae1passes 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
c3401e5f6bbc19a0ba695219ed551e29a29677edspecifies 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
8b6b93a329757ae7f106e235761912b58a67deffpasses 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
c3401e5f6bbc19a0ba695219ed551e29a29677edpasses 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
fc3ee44748c20a3aa6f55bd85ac1913c707e5d4especifies 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
e7ba974e96ee77a41c6a861150da843d4c84c7d6passes 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
fc3ee44748c20a3aa6f55bd85ac1913c707e5d4epasses 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.The strict kernel matrix is complete; matching-image runtime evidence and automatic CI classification remain required.
Absent Exsh, Coreutils and Extop artifacts require no launch catalog; present artifacts retain capacity and missing-metadata checks.
All 165 helper commands pass. Four strict Rust matrices pass 320 default or 321 all-feature tests, formatting, Clippy, native builds and private rustdoc. Matching query/invocation and lifetime VMs pass under unchanged 60-second deadlines without warnings. The original packaging refusal is retained in integration issue 59 and the initial canary failure in kernel issue 16. Automatic Integration runs 1647/1648 are being monitored; no full-suite or full guest-build acceptance is claimed while their original outcomes are pending.
All 166 helper commands and four strict Rust matrices pass, with 320 default or 321 all-feature tests, formatting, Clippy, native builds and private rustdoc. The standard wrapper passes invocation, entry-direction and lifetime VMs without build warnings under their unchanged 60-second deadlines and exact marker/exit requirements.
Original automatic CI 1649 and CI 1650 are being monitored. Earlier runs 1647/1648 remain separately monitored; no complete-suite or full guest-build acceptance is claimed while those outcomes are pending.
Original Integration regression classification — 17 September 2026: Original runs 1647–1650 are fully classified. Runs 1648, 1649 and 1650 each pass 408 of 486 scenarios and fail the same 78 known shell-layout refusals in issue 57. Run 1647 passes 407 and additionally repeats the existing ext4 quota timeout in issue 18. All twelve complete terminal logs total 52,533,051 bytes and contain no warnings. Rust and Markdown jobs pass. No additional failed scenario is identified; the complete catalogs remain failed. The separate local automatic-KVM preboot observation is tracked in issue 60.
The separate KVM preboot observation in #60 and both full guest builds remain open.
Original CI reconciliation — 17 September 2026: CI 1651/1652 at
fa86d1b64f8e1299c0ee0c886e6f1b35d58ea15bretains full-catalog failure.All six logs are complete, 27,230,062 bytes, zero warnings; Rust/Markdown pass.
Both runs retain 78 layout refusals and the quota timeout. PR CI 1652 also
retains the named idle-time-resolution timeout in #61, while original
push CI 1651 passes that scenario. Totals are 407/79 and 406/80 of 486.
No unchanged retry, increased deadline or accepted full guest build is claimed.
Runtime archive checkpoint — 17 September 2026, signed
77921a7d97874e3f44aae66ae9bef6e6196af2f5: Eight selector controls pass, including four original refusal subcases that fail against the predecessor.Linker selection checkpoint — 17 September 2026, signed
bc0e67f927ded76dd3ff5790180a7bded0886885: Thirteen focused controls pass, including real bundled-LLD linking and warning refusal. 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.
Four strict Rust configurations and all 169 helper commands pass; the old marker assertion was corrected to require the added generation marker. Typed mediator bootstrap, ordinary service-image adoption and both complete EriX builds inside EriX remain open.
Original archive-head CI 1653/1654 is fully classified with 406/486 passing in each run; layout and filesystem timeout failures remain in #18, #20 and #57. The bounded archive-selection repair #62 is closed on its specific evidence. Current CI 1659/1660 remains under observation without restarts.
Generation-bound cleanup consumer acceptance — 18 September 2026: Signed revision
4d4628f565d7102e6ef2987e4085fd8d97d247d3is pushed. Both actual 60-second native scenarios pass, including nineteen new CPL3 cleanup calls and the mandatory GENERATION_CLEANUP_OK marker. All earlier lifetime oracles remain required, and normally stripped packaged Kernels match their original builds. The ordinary service catalog is unchanged; ordinary source/effect/frame admission remains open. Runnable mediator bootstrap, fair retirement and both complete builds inside EriX remain open.The lifetime scenario requires thirty-nine additional real CPL3 relocation controls before the original installation, revocation, terminal, inventory, queue and page oracles, with the original 60-second bound. Ordinary service source/effect and frame admission, actual owned consumer execution and both full guest builds remain separate open gates.
Explicit owned receiver admission acceptance — 18 September 2026: Signed
435e69a9840b37108529e5f9f9915937a12bafc9. The owned scenario requires the receiver-admission marker before its final ownership marker; all prior lifetime and ordinary source/effect/frame gates remain intact. Actual owned Procd/Launchd service adoption, consumer VM execution, complete realm fairness/readiness/sealing and both full builds inside EriX remain open.Original Integration catalog completion — 18 September 2026: At exact revision
0db8a679f5d1acb50d9ff92e003cec91f145dfc8, CI 1659 finishes with 396 passes and 90 failures out of 486; CI 1660 finishes with 393 passes and 93 failures. Each retains the 78 known Exsh layout refusals. The remaining 12 and 15 failures are original 120-second QEMU storage-scenario timeouts. All six terminal logs are complete (36,570,659 bytes), with zero warning candidates. Rust/unit and Markdown jobs pass. No workflow was restarted, no deadline was enlarged and no failed scenario is accepted. A shared guest or host cause is unestablished.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 generation-cleanup catalog completion — 18 September 2026: At exact revision
4d4628f565d7102e6ef2987e4085fd8d97d247d3, CI 1661 and CI 1662 each finish with 408 passes and 78 failures out of 486. The exact failed set is the 78 known Exsh layout refusals. There are no storage timeout failures in these two observations; earlier timeout failures remain unresolved. All six terminal logs are complete (26,074,278 bytes), with zero warning candidates. Rust/unit and Markdown jobs pass. No workflow was restarted, no deadline was enlarged and no failed scenario is accepted.Original realm contract library prerequisite — 18 September 2026: Signed
ad85421257b7d964845fd4b84931966ad36cc122selects the original bootstrap, capability and IPC revisions in Rootd orchestration. Only the Cargo dependency selection is published; Rust implementation and image policy remain unchanged in this commit. Four strict default/all development/release configurations pass 320/321 tests, host/native Clippy, native builds, formatting and private rustdoc without warnings. Compiler inputs contain no unpublished image-consumer changes. CI 1667 and CI 1668 are queued. Rootd can now pin this real original prerequisite before coordinated startup/image publication. Consumer VMs and both complete builds inside EriX remain required. Older CI 1663/1664 remains failed with 78 known layout refusals and one quota timeout per run; existing issues #57 and #18 retain the complete original evidence.Coherent startup consumer acceptance — 18 September 2026: Signed Integration
8b1c037aed2503e1f2a4b17c8a8be0666d62a305adopts exact 72-byte LCH1 version 3, explicit realm capacity and version-6 compiler-derived arena geometry across runtime profiles, wire/configuration boundaries and image packaging. Full source/effect/frame admission, complete realm operation and both full builds inside EriX remain required.Explicit zero-realm startup acceptance — 19 September 2026: Signed Integration
c479813423fb71c606fa30e5cf7d4dfb16f557d0adds the bounded startup scenario using the existing explicit standard CLI policy. This proves ordinary startup with admission disabled; complete realm execution, source/effect/frame admission and both full builds inside EriX remain required.Original coherent-graph CI classification — 19 September 2026: CI 1669 records 485 passes/1 failure; CI 1670 records 484 passes/2 failures, each across all 486 scenarios at
8b1c037aed2503e1f2a4b17c8a8be0666d62a305. Both retain the original 120-second ext4 quota timeout in bug 18; the latter also fails physical input observation in the exact-selector race scenario, now bug 64. That scenario explicitly passes in the paired run. All six terminal logs are complete (27,557,577 bytes), with no warning candidates; Rust and Markdown pass. No incompatible shell-layout refusal remains. The layout issue’s full source/frame prerequisites and later native-image gates remain unproved. Neither workflow was rerun, and no deadline or admission check was relaxed.Tracking and rollout
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 final CPU accounting — 25 September 2026: the original signed Integration 3bfa40a6 client image now has a complete host-debugger observation of all eleven final Measured snapshot additions.
The observation binds all executable bytes before and after, actual caller PCs, the original shared root and 137 active backing pages. At final exit, inactive virtual addresses deny user access; their restored mappings are not mistaken for the captured process storage. Hardware breakpoints and physical reads add no guest inspection endpoint, capability, memory/register mutation or success marker. All original required/forbidden/ordered markers, retirement/reuse checks, QEMU exit 33 and 120/45-second gates pass, with empty debugger/QEMU stderr and zero warning candidates. Two positive host transcripts and fifteen negative cases exercise the observer. These debugger-perturbed numbers are neither CPU utilization nor a speedup measurement.
Four rejected observer configurations remain preserved: two reached the original deadline; two completed the native scenario but failed host checks based on incorrect assumptions about inactive mappings. None earns acceptance. The final observer records each checked commit immediately, installs return/exit breakpoints only when needed, and separately checks captured storage and inactive protection.
Signed Integration 125bcbb5 records this status. Only ROADMAP changes; all maintained runtime, helper, profiler, catalog and CI bytes retain their validated identity. Fresh formatting, Markdown, dependency policy and diff checks pass without warnings. The phase tracker exposes this as one completed sub-item: 15.43%, 415/875 sub-items, 17/460 whole parents. Procd issue 5 remains open for its broader requirements. NeverExecuted native observation, remaining supervisor loss/exhaustion/cleanup, existing Exsh compiler/frame gates, full original CI review, external toolchain rebuilding and both complete EriX builds inside EriX remain required.
The current consumer remains strict; the changed source adds no guest route or capability. Issue 96 retains the original deterministic rejection and both original CI runs' 119 packaging failures each.
All 174 helper and six profiler commands, fresh strict Clippy and both orchestration unit selections, formatting, dependency policy and Markdown pass: 187 commands, zero warnings. The existing
subsystem-crash-reporting-positiveVM now passes on this signed source with its original native exit, required/forbidden markers and 120/45-second limits. Its retained 119 artifacts include 194,161 serial bytes, empty QEMU stderr and zero image warnings. This is an affected original VM, not a replacement success criterion. Full original regression CI remains under observation; the separate guarded-fixture failures and ext4 quota timeout are not attributed to this correction.The documentation status is signed as Integration 7db7aa53; only ROADMAP changes and all tested code/catalog bytes remain identical. Fresh formatting for both crates, Markdown, source policy and diff checks pass without warnings. Original corrected-source CI1811/1812 and status CI1813/1814 are queued.
The structural audit covers 76 repositories and 3,194 authored code files, all below 1,000 lines, with 264 full dependency pins and all 98 conventional/manifest crate roots enforcing missing_docs. This does not establish complete semantic authority closure. Completion remains 15.42%, 414/874 sub-items and 17/460 whole parents. Numeric CPU values, remaining loss/exhaustion, external toolchain rebuilding and both full EriX builds inside EriX remain required.
Complete logs identify 119 packaging refusals caused by an obsolete smoke-only Launchd policy tuple. The same producer remains defective at
4efc9d5d; the new host regression reproduces its status-1 rejection. Issue 96 tracks the correction and native regression acceptance.The other failures are three realm PREPARE refusals matching the older guarded-fixture mismatch in Exsh issue 10, plus the original 120-second ext4 quota timeout. Later targeted realm passes do not rewrite those original failures. The new smoke fix explicitly disables realm/client/plan storage in the current 16-field tuple and preserves strict input rejection; corrected host and native checks are in progress. Original CI1797/1798 is running and CI1799–1810 waits. Accepted progress stays 15.42%, 414/874 sub-items and 17/460 whole parents. Numeric CPU values, loss/exhaustion and both full EriX guest builds plus external toolchain rebuilding remain open.
The corrected five-test control rejects the old configuration with
39 != 38; all 174 helper and six profiler commands, formatting, source policy and Markdown pass without warnings.The actual configured-client VM passes every original marker, exit and cleanup check within the unchanged 120/45-second guest bounds. It retains 109 hashed artifacts, 57,045 serial bytes and empty QEMU stderr. Independently decoded packaged tables contain exactly 38 Procd records and 102 Pagerd bindings; runtime slices use the authenticated count, so page padding does not add records. Six clients execute across three realm instances, including replacement while the peer stays live and rejection of stale selectors. This resolves the RTC inventory defect.
Capture review corrected: issue 95 was an invalid report caused by reading the combined display of two separate stream-tail commands as stdout alone. All allegedly missing build progress is present in the original 35,691-byte stderr, where the build scripts explicitly emit it. The 106-byte stdout correctly contains the three final validators. Both original streams have zero warning candidates and intact start/end records; no capture or source fix is needed. Two separate build-only diagnostics ran no VM; the broader trace exceeded its declared output budget and is retained as failed diagnostic evidence. Neither diagnostic substitutes for the original native run.
Docs ef2f8ae0 passes 45 controls, the complete 2,655-page manual, 491,436 word bounds and three visual reviews. Original CI1089/1090 also passes; four complete logs total 824,668 bytes, with early reference warnings converging to zero on the final pass. Integration CI1807/1808 remains queued, and older Integration runs remain under observation.
The demonstrated native record-reuse slice is now exposed as one additional completed sub-item: 414/874 sub-items, with 17/460 whole parents. Fixed parent/section weights are unchanged; rounded completion remains 15.42%. Final numeric CPU/profiler observation, supervisor loss, remaining exhaustion/cleanup coverage, existing Exsh compiler/frame gates, external Rust/LLVM/toolchain rebuilding and both complete EriX guest builds remain required.
Passing-workload profile and signed execution record — 25 September 2026: Integration ad43a352 records the three native passes and remaining acceptance work.
A separate admitted host TCG run of the exact passing client disk also passes every original VM marker and the original 120/45-second guest bounds, without warnings or guest diagnostic authority. Its complete capture contains 112,801 translations and 78,579 unique code groups. The reporter checks all 68 exact packaged ELF inputs; the instruction upper bound is 65,020,956,536 and the top 100 groups cover 84.98%. Uniquely matching Kernel mapping-batch candidates account for 35.46% of that upper bound. These are executed-block/code candidates, not completed instructions, process ownership or elapsed-time attribution. No speedup follows from comparison with the earlier failed workload. Exact inputs, original failures and the complete captures remain retained.
The mapping preparation loop is the next source-review candidate, while complete managed-row/final CPU reclamation and supervisor-loss/resource-ceiling validation remain required. Profiling does not close those gates or the external Rust/LLVM/runtime and two complete EriX guest-build requirements. Completion remains 15.42%, with 413/873 sub-items and 17/460 whole parents.
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.
The configured-client VM stalls after the same three inherited markers and a private process exit with status 5. Its original failure retains 109 artifacts and 56,130 serial bytes, zero image-warning candidates and no process-owner cleanup failure. Integration issue 92 preserves that observation. An admitted host TCG counter run against the identical guest disk reproduces the stall under the original 120/45-second bounds. Its complete capture contains 100,639 translations and 74,009 code groups. The top 100 groups cover 85.32% of the 65,912,963,324 translated-instruction upper bound; uniquely matching Kernel mapping-batch code accounts for 38.67% of that total. This is a performance investigation candidate, without a measured speedup, timing attribution or accepted native result. Shared code, addresses and process identity remain separate evidence questions.
Exact retained executable-region comparison with original symbol-bearing artifacts narrows the failure to Posixd configuration progress and its native exit; the exit block uniquely matches Posixd across all 68 packaged executables/shared objects. The source mismatch is confirmed independently: Launchd retains only RECV on its configuration receiver, while native COMPLETE requires carrier GRANT for capability-bearing client replies. Enforcing that actual gate in the maintained complete-record pull fixture fails the original implementation. Launchd issue 10 tracks the correction and original red control. The local correction retains exactly RECV | GRANT only for counted-client replies, preserves readiness-only RECV, mediator SEND-only routes and RECV-only client copies, and retains complete receiver disposal before seal/cancellation. Full component validation is running; corrected native client execution remains required.
Both original Docs CI1083/1084 pass, with 45 document tests and the 2,653-page manual. All four complete logs total 824,211 bytes; normal early-pass references converge to zero final warnings. Original Integration runs remain running or queued, without unchanged reruns. No canonical checklist credit is added: configured native clients, managed-row reuse, complete authority/frame closure, profiling improvements and both full guest-build requirements remain open.
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.
Guarded preparation uses the actual Posixd root with its required immutable layout, and actual private mediators reach readiness and retire independently.
The configured-client VM now passes all three inherited markers, then its first PREPARE_REALM_CLIENT request 34 (opcode 0x6d7) returns INTERNAL (5). The original failed run retains 109 artifacts and 56,226 serial bytes, with zero build-warning candidates and no process-owner cleanup failure. Loaderd issue 5 records the separate defect: the counted Launchd client producer selects its own grant column, while Loaderd's intake, handler and reply retain legacy fixed destination 645. Two independent actual-code tests reproduce intake refusal and reply redirection. A correction must preserve the exact original client destination while retaining legacy destination, source receipt, actual caller, relation and cleanup gates.
The mediator-fixture correction is demonstrated in both prerequisite VMs; Exsh issue 10 remains linked to full configured-client validation. No client execution, configuration/seal/byte-I/O acceptance, managed-row reuse, profiler observation or full guest build is claimed. Original Exsh CI281/282 is running, and original Integration CI1797/1798 is queued; earlier original Integration cohorts remain under observation. Exsh compiler/frame gates remain open, and no unchanged CI was restarted. These repairs add no canonical checklist credit.
All 174 Integration helper commands and six strict profiler commands pass. Sixteen selector combinations include preparation-only packaging and admission-only exclusion; actual private filesystem aliases still require exact artifact and runtime-graph identities. Seven Exsh development selections pass 986 tests each, fourteen host/native builds, strict Clippy and private-rustdoc configurations pass, and all 355 frame-checker controls pass without warnings. The initial changed wire-test byte count and documentation wrapping failures are corrected with original receipts retained. The unchanged Integration orchestration retains four strict 320/321-test matrices. No Loaderd check, capability right, sidecar rule or guest deadline is relaxed.
Seven Exsh release unit-test compilations still reach the original silence limit and all six native frame observations remain incomplete; compiler issue 9 and frame issue 4 stay open. Fixture regression 10 preserves both original failed VMs. Fresh corrected preparation-only, older startup and configured-client VM execution remains required. These component checkpoints earn no new acceptance credit; complete authority closure, managed-row reuse, profiler observation, external toolchain rebuilding and both full EriX guest builds remain open.
Exsh regression 10 records the canonical bug report and correction criteria.
The guarded fixture selects
bin/true, but the actual packaged Coreutils root has no loaded immutable realm layout. The packaged Posixd root has exactly one read-only, non-executable layout descriptor. Loaderd correctly refuses the ordinary executable as a mediator. The correction selectsbin/posixdand includes explicit private packaging for preparation-only images; it must preserve the strict layout gate, borrowed cwd scope and original 120/45-second guest deadlines. Exsh endpoint 0x520 exits E5; that observation does not attribute this failure to Launchd's process-event path.Both original source graphs, command statuses, serial logs and image artifacts are retained. There are zero image-warning candidates and no process-owner cleanup failure. Fresh preparation, startup and configured-client VM validation is required. This failure earns no checklist credit; complete authority closure, managed-row reuse, profiler evidence, the external toolchain rebuild and both complete guest-build generations remain open.
The separate two-realm/four-client fixture retains the older admission/preparation/startup markers, actual terminal outcomes, independent retirement, stale-handle refusal and the original bounded guest deadline.
All 174 maintained helper commands pass after correcting the old filesystem fixture's 26-word layout to the actual 28-word version. The original closure refusal for the missing Lib-PosixABI image row and original stale-layout failure remain retained. Fresh profiler formatting, strict Clippy, both five-test profiles, release build and private rustdoc pass. The unchanged orchestration source retains four strict 320/321-test host/native matrices. All final checks are warning-free. README, ARCHITECTURE, ROADMAP and the manual contract are updated.
Original CI1795 and CI1796 are queued. Both exact-source local VMs have now failed guarded preparation as recorded above. Exsh's compiler gate and frame-proof gate, full authority closure, managed-row reuse, profiler observation, the external toolchain rebuild and both complete EriX guest-build generations remain open.
The separate image draft selects 76 original signed repository objects and passes both complete image/Cargo dependency policies. It adds the required Lib-PosixABI image source and regenerates 53 dynamic target records, including the private byte client. Explicit filesystem packaging, a separate two-realm/four-client/576-plan-byte fixture, selector rejection and preservation of the original deadline and markers pass focused controls. The full 174-command helper matrix now passes at the signed image checkpoint above. Actual configuration/seal/byte I/O, managed-row reuse and profiler observation remain unproved. No feature credit is assigned to dependency alignment.
Complete client admission/lifecycle design — 25 September 2026: the shared codec design now defines public Launchd operations6D5–6DD using only original owned realm/client handles; private Procd provisioning43D–441; distinct authenticated never-started client disposal messages; and LCH1v4 counted client-row/plan-byte storage. No public caller nominates a native process or capability identity. Freeze verifies the complete canonical plan before effects; private provisioning preserves grant MOVE, receiver COPY and independent source/caller retirement. Client Start follows the two-sided seal, and exact terminal outcomes remain in counted storage until realm retirement. The first immutable byte cohort is explicitly scoped; it is no permanent POSIX process ceiling. A dedicated rootless byte-client binary will use RCS1 and its own ingress only. Implementation, strict validation and the real four-client VM witness remain open.
Counted client configuration continuation — 24 September 2026:
Proposed coordinated continuation: configure each private Posixd instance with two actual staged clients and mediator-owned bounded byte channels. Preserve the existing startup/control handshake and native identity checks. Configuration is canonical, counted and digest-bound; labels select already held owners and never confer authority. This is a first nonblocking byte-I/O slice. Full filesystem/TTY configuration, complete POSIX semantics, libc, all resource-retirement criteria, rebuilding Rust/LLVM inside EriX and both complete EriX guest builds remain required later work.
Build a real capability-minimal native client fixture using ordinary owned IPC and the versioned client startup. Exsh orchestrates actual two-Posixd realms with two clients each; it does not simulate their requests. Each realm has two channels and four descriptor bindings for reciprocal distinct bytes, explicit small ring budgets and payloads that force short progress. Keep realm B exchanging fresh bytes after realm A retirement, then require exact terminal outcomes and stale-handle rejection.
Exercise wrong-origin/stale/refused-capability inputs without leaving foreign SEND in a normal client. Preserve controls for partial receipt installation, pending calls, lost replies, source-copy disposal, each seal boundary and no accepted-operation replay. Record native turns and committed byte counts through the integration profiler without granting clocks/log routes to ordinary clients. Actual frame/authority/image closure, warning-free construction, original scenario limits and all retained older failures remain gates. A source model or successful private Start is not configuration, byte-I/O or complete-retirement acceptance.
Authenticate target geometry through the existing selected-image path. Posixd exports one immutable 96-byte target-generated descriptor in read-only file-backed ELF load storage: magic16
ERIXPXSCAPLAY001, then ten little-endian u64 words for version1, total size96, ELF machine, pointer bits, and client/descriptor/channel row size/alignment pairs. Sizes are nonzero and alignments powers of two; target fields match the selected executable. Loaderd extracts exactly one complete descriptor from its already authenticated root ELF bytes, refusing missing, duplicate, malformed or writable records. No host-derived type size or reopened pathname supplies geometry.An exact 144-byte BindRealmLayout request uses the existing authenticated LoaderMaterialization route: request/op u32, original active transaction u64, root ELF SHA-25632 and descriptor96. Its response uses the existing 36-byte materialization shape with zero noncommit materialization/staged fields. Procd accepts it only from actual Loaderd for that original active mediator transaction, retains the description through staged commit/rollback, and requires it before mediator commit. The startup carries the descriptor SHA-256, which Posixd compares against its own compiled descriptor before any typed arena borrow. Canonical checked sizing partitions client rows, descriptor rows, channel rows, plan bytes, ring bytes, retained per-client results and immediate packet storage; every multiplication, alignment, address and page round must fit. This grants no additional endpoint or allocation authority.
Ordinary endpoint transfer copies authority. Every source and possible receive destination remains owned across submission, collection and native retirement, including ambiguous results. Reserve each prospective receive slot before COLLECT; validate its normalized receipt and actual Generic kind/rights, then independently reconcile its disposal before reuse. Unique InstallGrant and RevocationGrant transfers keep MOVE semantics. Do not infer source deletion from successful copy or use deletion to manufacture successful unique-grant movement.
Track this continuation with Posixd realm lifecycle, POSIX ABI and Phase 6 completion. This is a proposed contract; no runtime or implementation acceptance is claimed.
The maintained
appliance-disk-image-realm-startup-positivescenario passes unchanged: both actual Posixd processes reach authenticated PrivateReady; A retires while B stays ready; B then retires; both stale handles are rejected; the initial shell exits successfully. The original required, unique, ordered and forbidden markers, expected guest exit0x10, 120-second guest hard limit and 45-second serial-progress limit all pass.This exercises counted minimum startup, actual capability census, setup-grant consumption and copied SEND disposal before Start, followed by native child registration, exact-origin readiness and the controller challenge. The packaged Posixd alias selects the same authenticated executable; no ordinary sidecar, extra child endpoint or fallback is introduced. Source-bound exercised gates are the evidence; no separate global inventory dump is claimed. Posixd's Ready caller remains its separately owned obligation until retirement. The successful explicit-retirement path does not exercise Launchd's spontaneous WAIT decoder, final CPU/profiler handoff, repeated row reuse, loss paths or capacity exhaustion.
Launchd's six strict local configurations pass 329 library and 69 runtime tests each; all 48 required commands are warning-free. The corrected native-faithful 14-test group includes COPY source retention, post-Provision caller retirement, separate source disposal/absence verification and failure preservation. Original Launchd CI155/156 also passes: four complete logs, 148,673 bytes, zero warning/failure candidates. Original Integration CI1791/1792 remains queued; earlier failures and regression reports remain preserved. The copied-SEND defect and its native startup regression are resolved at this scoped boundary. Relevant implementation reviews remain Launchd PR2, Procd PR2, Posixd PR5 and Integration PR12.
Configuration/seal/publication, four real clients and mediated byte I/O, complete running retirement and profiler disposition, rebuilding the external Rust/LLVM toolchain inside EriX and both complete EriX guest builds remain required and unproved. The WIP reviews remain unfinished.
Docs
eade076a4cb30b3932776d8808b6c1203fb7533eis signed and pushed. It records empty registered intake, exact terminal-event disposition and the scoped first-Challenge registration wait. The full 2,499-page manual passes within the unchanged 600/90-second bounds, all 464,516 word bounds pass and five affected pages were visually reviewed; final warnings and overflow are zero. The 45 documentation test results remain bound to byte-identical implementations, with fresh prose/Markdown checks. Original Docs 1067/1068 CI is running, with Markdown passing.Older original Integration run 1778 passes 487 of 490 catalog scenarios, with three exFAT deadline failures tracked in issue 88. Run 1780's command-4 consent failure belongs to existing host-fixture issue 74. Six newly terminal logs total 14,921,510 bytes and contain zero warning candidates. The earlier 505 pass count included repeated log lines and is withdrawn; worker summaries establish 487. No failed run was retried or cancelled. Runs 1781/1782 continue; 1783–1790 await assignment. These observations and the separately instrumented startup diagnosis add no checklist credit.
No native acceptance or completion credit is awarded.
All three component strict matrices pass without warnings. Original Launchd 153/154, Posixd 25/26 and Procd 310/311 CI passes with twelve complete logs totaling 572,242 bytes and zero warning candidates. Integration's catalog-only adoption preserves the exact previously validated 173 helpers and Rust source; both full catalog policies and original source signatures verify. The final CPU observation that retains a retired mediator's managed row is separately required work under Procd issue 5; consuming its terminal event does not discharge that accounting obligation. Configuration/seal, client I/O, complete retirement and all required guest rebuilds remain open. Weighted progress remains 15.16%.
The first START, request
0x13/ operation0x6d4, returns a typed NOT_FOUND rejection before the startup marker. No startup acceptance or checklist increase is awarded.Source review and fail-before controls identify empty registered-CLAIM handling defects in Launchd issue 5 and Posixd issue 7: Kernel empty intake returns NOT_FOUND with no delivery owner. A separate Procd first-challenge registration race can also reject an unaccepted call before the new child registers. The public START code alone does not distinguish internal failure locations. Corrections retain nonzero owners, exact origins and accepted-call ownership; the next native attempt must adopt the reviewed fixes together.
The independently reviewed explicit retirement event gap, linked to Launchd issue 6, must transfer only the exact terminal observation into the retained Retire acknowledgment after actual child/capability disposal. Spontaneous WAIT and other generations stay independently visible. It is not attributed as this START failure's cause. Configuration/seal, four real clients, byte I/O and all toolchain/EriX guest builds remain open.
Docs
95921234c64d7cc11f9f9ed19d49a5d73c95357cpublishes the preceding private preparation/event-contract correction: 45 tests and the full 2,497-page manual pass, all 464,159 word bounds pass and six affected pages were visually reviewed. Original Docs CI 1065/1066 passes with zero final warnings; intermediate TeX reference convergence remains recorded. Further intake/retirement contract prose is a separate pending change. Launchd's original 151/152 CI passes with four complete warning-free logs; Integration 1787/1788 awaits runner assignment. Weighted progress remains 15.16%.Its first real Posixd PREPARE receives a valid typed NOT_FOUND rejection.
The original image, 107 evidence files and 56,013 serial bytes are retained. Rootd exits after the failed shell probe; the unchanged 45-second progress watchdog stops QEMU within its 120-second outer deadline. Exit E5 alone cannot identify Launchd: Exsh uses the same status, and the observed endpoint corresponds to the ordinary child range. Launchd issue 3 separately tracks a verified realm-event decoder gap; it is not established as the cause of this attempt. No unchanged failed input was rerun. Posixd startup, configuration/seal, client I/O and guest builds remain unaccepted; checklist progress stays 15.16%.
Older original Integration run 1779 passes all 490 catalog VMs and the unit suites, then fails a serial native-directory consent step. The distinct observation is recorded in existing regression 77, while regression 85 retains its earlier powerbox-input failure. Their root causes remain unresolved.
The filesystem link shares its validated executable inode, and the exact loader-graph source must match package identity and both manifest/content digests before filesystem effects. The ordinary launch-manifest generator emits no Posixd sidecar or authority row.
Six focused controls exercise the actual ext4 inode, link count, mode, bytes, installed graph, absent mediator and malformed evidence. Seven launch-flag tests and six existing packaging helpers pass; all complete validation logs have zero warnings. Both original regressions remain retained. The existing graph decoder is shared without changing its decoding behavior, and the maintained CI helper suite now contains 173 commands. All Rust and catalog inputs retain their prior validated bytes. This resolves the source mismatch in packaging regression 87; that issue stays open until the image and native path are exercised.
The first coherent actual startup VM is being prepared with the same requested path, existing scoped cwd and Launchd authority, earlier markers, ordinary shell exit and 120-second guest deadline. No actual Posixd guest execution, configuration/seal, client byte I/O or full guest build is accepted yet. Original Rootd CI 1043/1044 now passes, with all four complete logs and zero warnings/failures. New Integration CI is monitored separately; weighted checklist progress remains 15.16%, with 16/460 whole items accepted.
All 172 maintained Integration helpers and 28 focused intake/capacity controls pass. Profiling scenario intake regression 86 demonstrates 49 actual parser invocations reduced to one with identical output and unchanged deadlines. Original failures remain retained. Procd startup protection is corrected at signed
d04311abff67e7355bd92bb2e48fb6161e0ec674; original CI 308/309 passes without warnings. All 35 reviewed current consumer run pairs pass, with complete logs checked and zero warnings or failure candidates. Exsh's separate original 277/278 runs fail the existing frame proof; its release compilation gate remains open.The updated manual passes 45 tests and the complete 2,497-page build; all 464,103 text bounds and representative changed pages are reviewed. Original documentation CI 1063/1064 also passes. Each CI log retains 37 intermediate TeX reference warnings across early passes, then zero in its final pass; final warning gates pass. These raw logs are not described as warning-free.
Before the first actual startup VM, source review found that the requested
bin/posixdwas absent from both filesystem aliases and the exact loader graph. Packaging regression 87 tracks the correction and targeted original-failure control. The intended selector, existing cwd/Launchd authority, earlier markers, ordinary shell exit and 120-second guest deadline remain unchanged. No actual Posixd guest execution is accepted yet. Integration CI 1783/1784 is queued; Rootd 1043/1044 is being monitored. Two ready mediators with independent retirement, configuration/seal, two clients per realm, mediated byte I/O, cross-realm refusal, rebuilding external Rust/LLVM/runtime, and both complete EriX guest builds remain required.Private provisioning implementation checkpoint — 24 September 2026: Procd now implements counted memory provisioning, controller attribution through actual native CLAIM, minimal child capability installation, consumed lifetime GRANT, retained private start/challenge and exact retirement after uncertain start. Launchd implements four disjoint capability columns per realm, guarded configuration transport, authenticated Ready/Start progress and independent cleanup. Accepted native handles remain owned through final retirement; an unaccountable successful zero handle stops ordinary intake. The initial synchronous Memd backing operation precedes the context probe and all mediator execution; bounded progress for the entire provisioning operation remains separate work.
Procd passes four strict configurations with 327 default/333 all-feature main tests plus five probe tests, nine native build/Clippy profiles and private rustdoc. Launchd passes six strict configurations with 393 tests each, native builds/Clippy and private docs. The published Posixd consumer and fourteen shared libraries use the same original immutable dependency graph. All 34 original CI runs across these seventeen repositories pass; all 68 complete logs (1,883,783 bytes) have zero warnings or failure candidates. Procd runs 306/307 and Launchd 149/150 cover these exact published heads.
The two-mediator Exsh/Integration startup witness is implemented locally and awaits the coherent service image and actual guest execution. The maintained dynamic builder has produced a checked Posixd PIE and its five original shared objects with exact dependency records and zero warnings; this proves artifact construction only. PrivateReady, Posixd's own Ready RELEASE, configuration/seal, client publication and mediated I/O remain distinct. Existing Exsh release-test compilation and native frame gates remain open. The next runtime acceptance must start both actual mediators, retire the first while the second remains ready, retire the second and reject both stale handles under the existing authority and 120-second guest deadline. Two mediators/four clients, cross-realm refusal, full EriX guest builds and rebuilding the external toolchain inside EriX remain required.
One actual QEMU lifetime run passes the original 60-second deadline and all ordered/unique markers, including reused numeric identity with a new generation, stale-generation refusal preserving its replacement, route denial, exact terminal events and executing-child ancestor termination.
Signed Integration checkpoint adopts the exact Kernel/shared pins in the dedicated lifetime catalog. All 172 maintained helper tests pass freshly, plus formatting and source/document policy checks. Unchanged Rust inputs retain their prior strict validation. Procd uses exact-generation termination, and Posixd has a validated freestanding bootstrap, readiness and challenge loop. The manual documents these contracts; all 45 documentation tests and the complete 2,469-page build pass with zero final warnings.
Actual Posixd execution is still pending. Active work adds counted provisioning, authenticated controller discovery, retained private Start/Retire exchanges and the separate two-mediator native startup witness. Configuration/seal, client I/O, full in-guest EriX builds and rebuilding the external toolchain remain open.
Integration remains pending; existing regression reports remain open.
The original Clippy style refusal is retained and corrected without relaxing lints.
Current regression monitoring: original Integration run 1777 passes all 490 catalog VM scenarios and earlier image/input gates, then fails development serial trusted-consent input. Bug report 85 records the original failure, complete logs and unestablished cause using the bug-report contract. No failed input was retried. Current table-storage run 1779 is running and 1780 remains queued.
Weighted checklist progress remains 15.16% (394/858 sub-items); whole-item acceptance remains 16/460 and 3.67% weighted. The remaining provisioning, actual mediator execution, configuration/seal and client-I/O criteria have not been closed.
Current checklist progress — 24 September 2026: Phase 6 completion now exposes completed and remaining sub-items. Weighted checklist progress is 15.16%, with 394/858 sub-items complete beneath 156 partially completed parents. Whole-item acceptance remains 3.67% weighted, or 16/460 original parents. Sub-items divide each parent's existing share; the original section weights and acceptance requirements are unchanged. This recognizes verified intermediate work without treating the complete realm, compiler/runtime port or either full guest-build generation as accepted.
The Phase 6 master completion checklist tracks all 460 acceptance items, including supplementary requirements, section weights, current acceptance, owning issues and PRs. Update it alongside this record whenever scope, accepted evidence, regressions or CI disposition changes. Current accepted completion is 15 items, 3.48% weighted; both complete builds inside EriX remain required.
Detailed scope and contracts
Coordinated library dependency update — 15 September 2026
Full Integration CI is being monitored separately; earlier native-image serial-check failures remain open in issue #46.
Library dependency wave accepted — 15 September 2026
The product catalog and product VM acceptance remain pending.
Coherent runtime source adoption — 15 September 2026
Full commit selectors remain mandatory.
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.
Validated mediator constructor adoption — 15 September 2026
A refusal never falls back to operation 32.
Exact requests, omitted receipt/drop, materialization, refusal without fallback and unchanged ordinary behavior are covered.
Runtime-image adoption, authenticated grant return, guarded bootstrap routes, private execution, receiver readiness, configuration/seal, client I/O, fair retirement and both full guest build generations remain open.
Mediator constructor adoption — 15 September 2026
Scratch absence cleanup, complete failed-stage retirement, grant-only handoff, retained endpoint master and all ordinary mediator start gates remain required. A refusal of operation 54 must never fall back to operation 32.
Verify the exact constructor request, omitted receipt and drop, ordinary behavior, refused construction without fallback, materialization and final cleanup.
Authenticated grant return, guarded bootstrap routes, private execution, readiness, configuration/seal, fair retirement and both complete guest build generations remain open.
Construction without child root capabilities — 15 September 2026
Select the signed native construction graph and require actual root-capability-free construction and complete disposal in the existing lifetime VM oracle. All required markers occur once in order. Full Integration CI remains separate from local acceptance.
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
The new ordered, unique STAGED_ENDPOINT_ATTENUATION_OK marker requires actual returned identity, exact rights, refusal and complete cleanup.
Authenticated grant return, independently minimal root/bootstrap authority, retained native and nested guards, private execution, configuration/seal, client I/O, fair retirement and both complete guest build generations remain open.
Issue 50 tracks the observed shared-compiler regression: valid dependency-qualified Rootd selections are rejected as unknown local features. Earlier isolated native VM acceptance retains its separate exact source and artifact scope.
The actual native VM passes both ordered unique markers, expected exit and forbidden-marker checks using signed Kernel
03e13a784bde08914864267a4e2a6324a22d05c7and Bootloadere7fa39357a38c21529cccfd16cf3446eb07e8aa5. Integration CI 1603/1604 is running; older suite and complete current-head acceptance remain pending.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 diagnostic observation — 19 September 2026: the first actual caller VM fails before its required success marker.
No acceptance credit or complete realm execution is claimed.
The actual VM passes all eleven admission calls over the shell's existing private script route: reservation, reads, full-width stale-generation rejection, missing-scope refusal, acknowledged retirement, record reuse and stale-abort rejection.
Successful preparation, mediator configuration/readiness/sealing, client byte I/O, complete source/effect/frame proof, native Rust/LLVM rebuilding and both full EriX builds remain required. This partial lifecycle acceptance adds no whole checklist item.
The new diagnostic will reserve a record, transfer exactly one SEND-only copy of its explicitly supplied startup cwd to the BEGIN-reserved receipt slot, select
bin/truewithin that initial root scope, require PREPARE/Guarded and READ/Guarded, then require ABORT/Retired and a stale READ/NOT_FOUND.No ordinary start, new endpoint, root capability or implicit namespace is introduced. Launchd must retire its received directory copy after exact resolution; Loaderd must return the original staged child and grant, and Procd must retain the actual returned grant and guarded sender branch before acknowledging Guarded. Abort must retire that exact stage and retained custody. Error telemetry must preserve application refusal codes and stop ordinary output after uncertain receipt disposal. The new actual VM retains the 120-second hard and 45-second progress limits and requires its own unique marker before ordinary shell exit. Full source/effect/frame proof, configured/sealed mediator execution, real client byte I/O, native Rust/LLVM rebuilding and both full EriX builds remain required.
The actual VM passes the eleven existing admission calls followed by BEGIN/Reserved, PREPARE/Guarded, READ/Guarded, ABORT/Retired and stale READ/NOT_FOUND. It transfers exactly one SEND-only copy of the explicitly supplied initial cwd to the authenticated reservation and selects
bin/trueinside that scope. The existing private Launchd route is reused; no new endpoint, root grant or implicit namespace is introduced.Eight actual frame observations retain complete workspace mapping but incomplete 97/63/100/100 runtime/all/admission/preparation proof in both policies; the full frame gate remains required.
Complete typed mediator bootstrap, readiness/configuration/sealing, real client byte I/O, complete source/effect/frame proof, native upstream Rust/LLVM rebuilding and both full EriX build generations remain required.
Original guarded-preparation CI — 19 September 2026: Exsh run 271 and 272, for signed
ffe50612889dd58a45a40d04593a4aa3a3ffa512, both fail the required complete frame proof. No workflow was rerun or cancelled to obtain acceptance.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.
Process-start census correction — 19 September 2026: signed Kernel
b762e19d0c16acd605d0f6123994a586cc6fcde1requires a successful install-grant absence census before process start. An unavailable census returns the existing refusal and preserves the whole staged child and grant state.The static census covers 3,127 authored code files below 1,000 lines, 74 manifests, 259 original Git pins, 170 direct missing_docs gates and 92 conventional crate roots; complete semantic authority and private-documentation closure remain open.
Complete mediator execution, full source/effect/frame proof, upstream Rust/LLVM rebuilding and both full EriX build generations inside EriX remain required. No whole acceptance item is newly completed.
This completes the terminal-refactor prerequisite in child lifetime design #19; it introduces no lifetime binding, new opcode or additional authority.
Full semantic authority and private rustdoc closure remain open. Native child-lifetime custody, running mediator lifecycle, full frame proof, upstream Rust/LLVM rebuilding and both full EriX build generations inside EriX remain required. No whole phase acceptance item is added.
The private script-route admission defect is corrected and natively demonstrated, while full realm lifecycle, complete frame proof and guest builds remain open.
Fourteen new real-object controls cover refusals, rollback, nested stopping, a 257-descendant tree, late preflight failure, exact reuse and failed explicit abort after unlinking.
A real CPL3 supervisor proves ChildPopulate refusal, malformed/generation refusal, actual Process-route binding, start and exit.
Executing-child, no-successor native idle, allocation/partial-effect failure coverage, Procd adoption, running-mediator failure, provider completion, complete source/effect/frame proof, upstream Rust/LLVM rebuilding and both full EriX-in-EriX generations remain open. No whole phase acceptance leaf is added.
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 | MINTwhile binding needs onlyGRANT; 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.
Acceptance stays 15/460, 3.48% weighted; native toolchain rebuilding and both full EriX-in-EriX generations remain open.
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_OKrequires 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.
This does not establish a new current-source regression, full lifecycle acceptance or full guest builds. Current Integration 1689/1690 remains queued at its second observation; acceptance stays 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_OKrequires 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.
Derivation requires actual MINT and subsets of both own rights and installation scope. The new actual CPL3 derivation/disposal controls and GRANT-only relocation/installation compile; their matching VM execution remains pending.
Procd's move-only handoff cannot attenuate the original delegating grant: it now derives a GRANT-only final receipt into the already-disposed VSpace receipt slot and drops the source before returning that receipt. Nonderiving materialization and rootless mediator paths request GRANT directly. Procd, Launchd, Rootd, Loaderd and Deviced pass their default unit suites; their full strict matrices and coherent guest validation remain open.
This is partial implementation evidence, not completed lifecycle or self-hosting acceptance. Full terminal accounting, provider completion, consumer lifecycle, source/effect/frame proof, the 128-page Pagerd gate, profiler attribution, native external Rust/LLVM/runtime rebuilding and both complete EriX-in-EriX generations remain required.
Lifetime now exercises 27 ordinary CPL3 grant-right controls and requires INSTALL_GRANT_RIGHTS_OK before its existing cleanup assertions. These minimal native scenarios establish neither full service-image acceptance nor a guest build.
Those filesystem failures require separate analysis.
Canonical acceptance remains 15 of 460 leaves, 3.48% weighted. Complete lifecycle and terminal accounting, provider completion, 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.
The process and launch chapters require GRANT-only final receipts, explicit derivation/source disposal, and original-generation rollback.
Catalog regression 68 remains open until the remaining Exsh selection and complete original catalog are validated together. Individual repository success is not full service-image acceptance.
The complete source/effect/frame gate also remains open.
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.
Corrected-source original CI 1695/1696 is running; bug 68 remains open pending that observation and full consumer acceptance remains separate.
These local and CI artifacts are distinct; no frame or release-unit acceptance, relaxed deadline or unchanged retry is claimed.
Canonical acceptance remains 15/460 leaves, 3.48% weighted. Full consumer lifecycle, terminal accounting, source/effect/frame proof, the 128-page Pagerd gate and profiler attribution remain required; no canonical leaf closes at this checkpoint.
Catalog mismatch issue 68 is corrected; this does not establish full consumer acceptance.
The final installer was handed off from VSpace scratch slot 1056 while later TTY provisioning requires managed grant slot 1040. Signed Procd 10d972b652297fd656e9a6ac6dbdf197f362c7ce in WIP PR 2 derives the exact GRANT-only result, disposes its delegating source and uniquely relocates the result back to the empty managed grant slot. Refusals preserve original-stage rollback and remaining custody. Corrected full-service VM validation and original CI remain open; bug 4 remains open.
Acceptance remains 15/460 leaves, 3.48% weighted. Full consumer lifecycle, terminal accounting, source/effect/frame proof, Pagerd, profiler attribution, native external Rust/LLVM/runtime rebuilding and both full in-EriX build generations remain required.
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.
Host controls include nonzero final counters after actual reclamation and ID reuse, original observer death, pending-final-charge destruction refusal, malformed requests, wrong callers, immutable errors and lost-acknowledgement reply retry.
Actual guest instructions check repeat observations and CPU queries, exact acknowledgement and absent-acknowledgement retry; executing children require nonzero user and kernel counters after native reclamation.
Procd and Rootd consumer adoption, ordinary and mediator metric retention/consumer loss, manual updates, full service/profiler scenarios, complete authority/source/frame audits and full regression acceptance remain open under Kernel design 20. Canonical acceptance remains 3.48% weighted; 15 of 460 items. Native upstream Rust/LLVM/runtime rebuilding and both full EriX guest build generations remain mandatory and unproven.
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.
Exsh's release compiler and complete frame gates remain explicitly open in issue 9 and issue 4.
The original stale memory-source rejection, quiet storage-fixture timeout and overly long socket-fixture path remain retained.
The published runner and original full source graph are prepared for the maintained shell CPU-accounting, two-CPU inspection and out-of-session denial scenarios. Actual VM evidence remains pending and no full guest-build acceptance is awarded. Complete authority/source/effect/frame and Pagerd gates, native external Rust/LLVM/runtime rebuilding and both full EriX guest build generations remain mandatory in Phase 6 completion.
The published original Integration catalog
dff878dd3545c4751b3c05d37b2bdd5e21cce548passes the maintained shell times, two-CPU Extop and out-of-session denial VM scenarios under their unchanged 120-second guest limits. Each retains 106 hashed evidence files, warning-free image builds, empty QEMU stderr and every required, forbidden, ordered and unique marker check.The denial scenario confirms the existing out-of-session boundary. Complete mediator/lifecycle acceptance in Procd 5 remains open.
A separate ordinary development package also builds without warnings, but its required startup-contract preflight exits 1 before any VM or observer starts. Preserve the refused package and all admission controls; the 120/15/10 capture limits and performance thresholds are unchanged. No startup-profile acceptance is awarded. Complete source/effect/frame and Pagerd proof, native external Rust/LLVM/runtime rebuilding and both full EriX guest build generations remain required by Phase 6 completion.
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.
The VM and complete observer finish with all required stages, zero dropped records, empty QEMU stderr, successful cleanup and unchanged source image.
No startup-performance or full native toolchain/EriX guest-build acceptance is awarded.
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.
The next work in Kernel 22 must resolve the supervisor baseline, bootstrap/saved-frame overlays and inactive-space population before adding root ownership, residency and retirement. Startup timing acceptance, complete authority cleanup and the profiler's measured speedup remain open. Rebuilding the external Rust/LLVM toolchain and runtime inside EriX, then completing both full EriX guest-build generations, remains mandatory and unproven.
Bootstrap provenance, independent hardware roots, complete authority cleanup and measured startup improvement remain open. Canonical acceptance remains 15/460 leaves, weighted 3.48%. Rebuilding the external Rust/LLVM toolchain and runtime inside EriX and completing both full EriX guest-build generations remain mandatory and unproven.
Empty and MANAGE-only aliases are denied; MAP-only access remains valid.
Actual CPL3 calls preserve the authorized RW/NX page across restricted-alias refusals and drop all five temporary grants.
Integration 1721/1722 remains queued; it receives no CI acceptance credit.
Canonical acceptance remains 15/460 leaves, weighted 3.48%. Independent hardware roots, complete authority cleanup and measured startup improvement remain open. Rebuilding the external Rust/LLVM toolchain and runtime inside EriX, then completing both full EriX guest-build generations, remains mandatory and unproven.
Explicit READ now governs admission and hardware activation. No-access mappings retain backing with USER/WRITE clear and NX set; write-only and execute-only requests are rejected without adding READ.
Twenty-four actual CPL3 calls preserve earlier witnesses and cover no-access protection, write-only refusal, MAP-only frame derivation, denied READ and unmap after both frame grants are dropped.
Integration 1723/1724 remains queued; it receives no CI acceptance credit.
Canonical acceptance remains 15/460 leaves, weighted 3.48%. Authorized protection restoration, independent hardware roots, complete authority cleanup and measured startup improvement remain open. Rebuilding the external Rust/LLVM toolchain and runtime inside EriX and completing both full EriX guest-build generations remain mandatory and unproven.
Ordinary protection contract — 22 September 2026: the runtime memory design now specifies in-place no-access/R/RW/RX changes using current VSpace MAP and exact selected frame authority, including same-backing aliases and complete backing checks. Preserve W^X, explicit READ, object kind, reference custody, error ordering and all native witnesses. This earns no canonical acceptance credit; external toolchain rebuilding and both complete EriX guest-build generations remain mandatory.
Root cause, isolated reproduction and correction remain open; no rerun or relaxed limit supplies acceptance. External toolchain rebuilding and both complete EriX guest-build generations remain required.
The Kernel implementation permits representable no-access/R/RW/RX changes through current exact-backing grants and aliases while active or inactive. It removes historical access ceilings and original-slot equality while preserving current VSpace MAP, selected frame rights, kind/range/identity checks, W^X, explicit READ, backing custody and failure ordering.
Actual user instructions write, execute, rewrite and execute managed RAM, check narrow alias authority and final disposal, while a reused device slot cannot authorize unrelated backing. Every prior marker remains required.
Full semantic authority review remains open. Integration 1725/1726 remains queued and receives no completed CI acceptance. The separate older ext4 deadline report remains open.
Canonical acceptance remains 15/460 leaves, weighted 3.48%. Complete POSIX protection support, Process endpoint scope, independent hardware roots, complete authority cleanup and measured startup improvement remain open. Rebuilding the external Rust/LLVM toolchain and runtime inside EriX and completing both full EriX guest-build generations remain mandatory and unproven.
Original 60/120-second guest limits, existing markers, exact component signatures and retained packaged artifacts remain required; image warnings and QEMU stderr are absent. No startup speedup or independent hardware-root acceptance is inferred.
Integration 1727/1728 remains queued and has no completed acceptance; earlier ext4 deadlines remain tracked in Integration report 73. Complete authority cleanup, external toolchain rebuilding within EriX and both full guest build generations remain open. Canonical acceptance remains 15/460 leaves (3.48% weighted).
Full semantic authority and inline-documentation review remain open. Integration 1729/1730 remains queued and has no completed acceptance; earlier ext4 CI deadline failures remain unresolved. Canonical acceptance stays 15/460 leaves, weighted 3.48%. Rebuilding the external Rust/LLVM toolchain and runtime inside EriX and completing both full EriX guest-build generations remain mandatory and unproven.
The unreachable raw-VA fallback is removed, and complete preflight rejects missing or ambiguous backing metadata before any range effects. No new userspace operation or capability grant is introduced. This is preparatory work for owned address spaces; independent roots and their switching/reclamation proof remain open.
Both allocator scenarios require the new same-VA/different-backing byte-and-leaf proof after complete cleanup, retaining every preceding marker and the original 60/120-second deadlines.
Complete semantic authority and inline-documentation review remain open. Integration 1731/1732 remains queued and has no completed acceptance. Canonical acceptance remains 15/460 leaves, weighted 3.48%. Rebuilding the external Rust/LLVM toolchain and its runtime inside EriX and completing both full EriX guest-build generations remain mandatory and unproven.
User leaves, malformed geometry and invalid recursive identity are refused.
Both allocator scenarios require successful baseline capture before their original marker sequence, with capability grants and original 60/120-second deadlines preserved.
Integration 1733/1734 remains queued at the latest retained observation and has no completed acceptance. Per-VSpace population, CR3 activation, invalidation and live-root reclamation remain open, and no speedup is claimed. Full semantic authority and inline-documentation review also remain open. Canonical acceptance stays 15/460 leaves, weighted 3.48%. Rebuilding the external Rust/LLVM toolchain and runtime inside EriX and completing both full EriX guest-build generations remain mandatory and unproven.
No new userspace authority, original native exploit or universal boot failure is claimed.
Integration 1735/1736 remains queued and has no completed acceptance. Private root population, CR3 activation, live-root reclamation and full semantic authority/documentation review remain open; no speedup is claimed. Canonical acceptance stays 15/460 leaves, weighted 3.48%. Rebuilding the external Rust/LLVM toolchain and runtime inside EriX and both full EriX guest-build generations remain mandatory and unproven.
Ordinary anonymous stack materialization now rejects addresses outside the existing user domain, and direct bootstrap writes require retained writable registered backing.
Private root population, CR3 activation, CPU residency, live-root reclamation and complete semantic authority/documentation review remain open; no speedup is claimed. Canonical acceptance stays 15/460 leaves, weighted 3.48%. Rebuilding the external Rust/LLVM toolchain and runtime inside EriX and both full EriX guest-build generations remain mandatory and unproven.
Canonical phase acceptance remains 15/460, weighted 3.48%.
It adds no user grant or real TCB context mutation; original user-mode witnesses and deadlines remain.
Full semantic authority/documentation closure, private-root readiness/activation and live-root retirement remain open. Canonical acceptance remains 15/460 leaves, weighted 3.48%. Rebuilding the external Rust/LLVM toolchain and runtime inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
Every allocation is retained before parent/recursive rebasing; failed construction or capability publication releases unpublished storage, and final teardown disposes never-activated tables after mapping cleanup. Process mappings, readiness, actual CPU residency and live-root retirement remain open under the owned address-space design.
No temporary grants survive.
Seven host controls pass; a fresh 4 KiB allocation consumes 4 KiB instead of 8 KiB, and a bounded storage trace reduces refusals from 20 to 15 without establishing latency improvement. Both native allocator scenarios require actual global-allocation geometry and payload-reuse checks, then pass all prior service-readiness gates under the unchanged 80 MiB reservation and 60/120-second deadlines.
Complete semantic authority and inline-documentation closure remain open.
Integration regression acceptance remains open. Complete CI review remains required; earlier image/input failures remain separately tracked without unchanged retries. Canonical acceptance remains 15/460 leaves, weighted 3.48%. Rebuilding the external Rust/LLVM toolchain and runtime inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
Physical addresses never become pointers. This prepares the population boundary in the owned address-space design; process mapping population, readiness, activation, CPU residency and live-root retirement remain open.
Eight added host controls cover actual independent traversal, a peer's physical edge, malformed directory/parent metadata, path bounds, absent and huge paths, real Vec capacity refusal, independent disposal and a 72-table directory.
The lifetime witness rejects a peer's physical edge and restores the original before error propagation, while retaining all prior independent-copy, failed-publication and exact-disposal checks. It requires the ordered, unique index-byte metric before custody success.
Complete semantic authority and inline-documentation closure remain open.
Integration regression acceptance remains open. Complete CI review remains required. Canonical acceptance remains 15/460 leaves, weighted 3.48%. Rebuilding the external Rust/LLVM toolchain and runtime inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
Numeric leaf entries confer no authority; the exact caller and backing custody remain prerequisites.
UNPUBLISHED_LEAF_EDIT_OK requires actual retained backing and distinct private leaf entries at one VA, protection, withdrawal and peer survival.
Complete semantic authority and inline-documentation closure remain open.
Complete CI review remains required. Live mapping transactions must coordinate frame/registered/physical inventories and withdraw private references before releasing backing; process readiness, activation, CPU residency, invalidation and live-root retirement remain open under the owned address-space design. Canonical acceptance remains 15/460 leaves, weighted 3.48%. Rebuilding the external Rust/LLVM toolchain and runtime inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
Run any still-required shared-active effect after preparation; on failure discard the guard before releasing newly retained backing.
Unmap must restore the selected root's supervisor-template policy and withdraw its process-backing reference before release. Final teardown and subsystem reset must dispose never-activated table ownership before relinquishing mapped backing. Native coverage must inspect actual private leaves after ordinary admitted mapping/protection/unmap calls, including current rights, backing identity, peer independence and cleanup. Registered image/stack and physical/device range inventories still require their own coherent range transactions and per-leaf cache/permission policy.
Existing source, warning, authority and timing gates remain required. Canonical acceptance remains 15/460 leaves, weighted 3.48%; external Rust/LLVM/runtime rebuilding inside EriX and both full EriX guest-build generations remain mandatory and unproven.
Ordinary private mapping population — 23 September 2026: the signed Kernel now connects admitted ordinary managed/DeviceFrame and Kernel-anonymous mappings to exact never-activated private leaves. Refusal preserves its error and drops staging before backing rollback; success commits without allocation and then publishes the row or changed rights.
PRIVATE_MAPPING_POPULATION_OK follows actual CPL3 managed/DeviceFrame operations whose private leaves must match admitted backing, permissions and final supervisor restoration. All earlier witnesses, grants and deadlines remain required.
Complete semantic authority and inline-documentation closure remain open.
Integration regression acceptance remains open. Complete CI review remains required. Previous Kernel 664/665 and Docs 1029/1030 succeeded with eight reviewed complete logs and zero final warnings; their Integration runs and earlier separately tracked failures retain independent acceptance. Registered image/stack and physical/device range transactions, supervisor-backing reconciliation, readiness, activation, CPU residency, invalidation and live-root retirement remain open under the owned address-space design. Canonical acceptance remains 15/460 leaves, weighted 3.48%. Rebuilding external Rust/LLVM/runtime inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
All nineteen timeout transcripts lack VFS_IO readiness and contain no scenario-forbidden fault markers.
The ext4 report remains open. Complete corrected CI acceptance for Kernel #33 and Kernel #34 also remains open; passing selected allocator cases does not stand in for unreached workflow gates. Newer private mapping population checks and their CI remain separate, and full external-toolchain/runtime and EriX guest rebuilding are still required.
Integration #73 remains open: isolated success and TCG instruction counts do not explain the nineteen original CI deadlines. External toolchain/runtime rebuilding and both complete EriX guest-build generations remain mandatory and unproven. No phase acceptance checklist item is closed by this diagnostic.
All prior grants, deadlines and witnesses remain required.
Static checks cover 3,221 authored code files below 1,000 lines, 75 manifests, 259 exact Git pins, 174 direct missing_docs gates and 93 conventional crate roots; whole-code semantic authority and inline-documentation closure remain open.
Integration regression acceptance remains open. Complete corrected CI remains required before bug closure. Registered image/stack and physical/device range transactions, readiness, CR3 activation, residency, invalidation and live-root retirement remain open under the owned address-space design. Canonical acceptance remains 15/460 leaves, weighted 3.48%. Rebuilding external Rust/LLVM/runtime inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
Both new full runs pass the ext4 scenarios; the original timeout cause is still unproven, so Integration #73 remains open for attribution and timing review.
Later leaf/population/ancestor cohorts retain their own CI acceptance. Complete semantic authority review, root activation, external Rust/LLVM/runtime rebuilding and both complete EriX guest-build generations remain required. Canonical acceptance stays 15/460 leaves, weighted 3.48%.
Six new controls cover preparation refusal, ordering, geometry, outside leaves, explicit flags and GLOBAL invalidation. Exact source signatures and packaged artifacts verify with no image warnings or QEMU stderr, under unchanged grants and deadlines.
Complete semantic authority and inline documentation closure remain open.
Integration regression acceptance remains open. Complete corrected CI remains required before this bug closes. Later source cohorts retain their own acceptance, and original ext4 timeout attribution remains open in Integration #73. Private range transactions, complete multi-range activation, readiness, CR3 residency and live-root retirement remain open under the owned address-space design. Canonical acceptance remains 15/460 leaves, weighted 3.48%. Rebuilding external Rust/LLVM/runtime inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
Private physical-range population — 23 September 2026: the signed Kernel now mirrors admitted complete ranges in never-activated VSpace tables before inventory publication. An exclusive rollback guard copies each touched original table once, retains new child pages, and restores original entry bytes before dropping new storage on allocation/resolution failure, cancellation or shared-effect refusal. No activation handle, new capability or fixed page-count ceiling is added.
Native prepared-range refusal restores prior leaves and table count. All earlier markers, grants and 60/120-second deadlines remain required.
Static checks cover 3,228 authored code files below 1,000 lines, 75 manifests, 259 exact Git pins, 174 direct missing_docs gates and 93 conventional crate roots; complete semantic authority and inline-documentation closure remain open.
Integration regression acceptance remains open. Registered image/stack population and withdrawal, boot-backing retirement, whole multi-range activation, readiness, CPU residency, invalidation and live-root retirement remain open under the owned address-space design. Canonical acceptance remains 15/460 leaves, weighted 3.48%; external Rust/LLVM/runtime rebuilding inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
This closes CI review for this exact private-leaf construction graph; subsequent mapping/range implementations retain their own CI acceptance.
Registered image/stack population, readiness, actual root residency, invalidation, complete semantic authority review and external Rust/LLVM/runtime rebuilding plus both complete EriX guest-build generations remain required. Canonical acceptance stays 15/460 leaves, weighted 3.48%.
The new native marker requires real range API denial before table effects and complete original cleanup.
Complete semantic authority and private inline-documentation closure remain open. Integration regression acceptance remains open. Complete corrected CI is still required before this bug closes. Registered private image/stack population and withdrawal, baseline retirement, readiness, actual root residency, invalidation and live-root retirement remain open under the owned address-space design. Canonical acceptance remains 15/460 leaves, weighted 3.48%; rebuilding external Rust/LLVM/runtime inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
A later geometry, allocation, resolution or shared-effect refusal restores every prepared private edit before new table storage is released. Numeric geometry and leaf descriptions confer no authority, and these tables remain never activated.
The existing lifetime witness prepares three discontiguous private intervals and verifies their complete rollback after shared-effect refusal, preserving peer state and retained backing. Every prior grant, marker and 60/120-second deadline remains required. Complete semantic authority and inline-documentation closure remain open.
Integration regression acceptance remains open. Registered image/stack import, withdrawal, coherent baseline/source retirement, readiness, actual CR3 residency, invalidation and live-root retirement remain open under the owned address-space design. Canonical acceptance remains 15/460 leaves, weighted 3.48%; rebuilding external Rust/LLVM/runtime inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
No input selector, capability or backing lifetime is broadened.
Complete semantic authority and inline-documentation closure remain open.
Integration regression acceptance remains open. Complete corrected CI is required before the report closes. Registered image/stack import and withdrawal, coherent baseline/all-root retirement, readiness, actual CR3 residency and live-root retirement remain open under the owned address-space design. Canonical acceptance remains 15/460 leaves, weighted 3.48%; external Rust/LLVM/runtime rebuilding inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
Private user leaves clear GLOBAL and reject W+X.
Three added independent policy controls cover backing presence, cache preservation, effective permissions, metadata drift and W+X refusal.
The new lifetime witness verifies late W+X refusal with complete rollback, exact data/image backing and permissions, idempotent data registration, complete supervisor restoration, peer survival and backing cleanup. Every prior grant, marker and deadline remains required. These observations concern never-activated private tables; they do not establish CR3 residency or a performance improvement.
Complete semantic authority and inline-documentation closure remain open.
Coherent baseline/all-root boot-source retirement, readiness, both AP paths, actual CR3 residency and live-root retirement remain open under the owned address-space design. Canonical acceptance remains 15/460 leaves, weighted 3.48%; external Rust/LLVM/runtime rebuilding inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
This closes CI review for this exact ordinary private mapping graph; subsequent mapping/range implementations retain their own CI acceptance.
The latest registered data/image checkpoint has separate selected native acceptance and pending CI. Coherent baseline/all-root retirement, readiness, actual root residency, invalidation and complete semantic authority review and external Rust/LLVM/runtime rebuilding plus both complete EriX guest-build generations remain required. Canonical acceptance stays 15/460 leaves, weighted 3.48%.
Later-owner, allocation, source and effect refusal restore the prepared group.
Both mapping contracts require the new ordered unique retirement witness after the prior invalidation marker. It checks effect refusal, reader policy, independent backing, saved restoration, future copies and full scratch cleanup after actual shared retirement. Every earlier grant, witness and 60/120-second deadline remains required. These are never-activated private tables; no CR3 residency or performance improvement is inferred.
Complete semantic authority and inline-documentation closure remain open.
Integration regression acceptance remains open. Readiness, both AP paths, actual CR3 residency and live-root retirement remain open under the owned address-space design. Canonical acceptance remains 15/460 leaves, weighted 3.48%; external Rust/LLVM/runtime rebuilding inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
Missing, huge or drifted paths refuse before alias publication.
Twelve focused physical-access controls cover ordered malformed-path refusal, backing/policy drift, byte bounds, restoration and partial failures.
The lifetime contract requires the new ordered unique SUPERVISOR_WINDOW_CUSTODY_OK after range-geometry denial and before aggregate table-custody acceptance. Every earlier grant, witness and 60/120-second deadline remains required.
Complete semantic authority and inline-documentation closure remain open.
Integration regression acceptance remains open. Remaining late structural writers, readiness, both AP paths, actual CR3 residency and live-root retirement remain open under the owned address-space design. Canonical acceptance remains 15/460 leaves, weighted 3.48%; external Rust/LLVM/runtime rebuilding inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
Existing owner-isolation controls remain required. The initial strict Clippy refusal concerned a redundant test-fixture expression; the simplified and formatted changed source passes the complete matrix.
Both mapping contracts require ordered unique NONMUTATING_LEAF_OBSERVATION_OK after huge-leaf geometry. The witness observes every page of a real 2-MiB PAT mapping, repeats through an ordinary PT, refuses an absent parent without creating a child, and checks a readonly ancestor while CR0.WP is enabled. All earlier lifetime, retirement, range and service witnesses, grants and 60/120-second deadlines remain required.
Complete semantic authority and inline-documentation closure remain open.
Integration regression acceptance remains open. Remaining structural writers, root readiness, both AP paths, actual CR3 residency and live-root retirement remain open under the owned address-space design. Canonical acceptance remains 15/460 leaves, weighted 3.48%; external Rust/LLVM/runtime rebuilding inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
Reservation refusal leaves previous ownership, parent and root binding unchanged. Only successful publication binds the first observed active root; later mismatches refuse.
Both mapping contracts require ordered unique SHARED_TABLE_OWNERSHIP_OK after nonmutating leaf observation. All earlier lifetime, retirement, range and service witnesses, grants and 60/120-second deadlines remain required.
Complete semantic authority and inline-documentation closure remain open.
Integration regression acceptance remains open. Routing every structural mutation through its actual root owner, supervisor reachability, both AP paths, actual CR3 residency and live-root retirement remain open under the owned address-space design. Canonical acceptance remains 15/460 leaves, weighted 3.48%; external Rust/LLVM/runtime rebuilding inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
Each original observation error survives mandatory fixture cleanup. Earlier markers, grants and original 60/120-second deadlines remain required.
Complete semantic authority and inline-documentation closure remain open.
Integration regression acceptance remains open. Full structural-writer routing, supervisor reachability, both AP paths, actual CR3 residency and live-root retirement remain open under the owned address-space design. Canonical acceptance remains 15/460 leaves, weighted 3.48%; external Rust/LLVM/runtime rebuilding inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
Later borrowing refuses missing custody or a different root before recursive access, then rechecks that edge under table and local interrupt guards.
Operation-local hints cannot outlive this custody.
Seven new production binding controls cover one-time adoption, invalid identity and policy, absence, mismatch before callback, preserved state after refusal and independent hardware metadata.
Each requires ordered unique BOOTSTRAP_ROOT_CUSTODY_OK before its earlier witnesses and forbids adoption failure. Earlier markers, grants, cleanup and original 60/120-second deadlines remain required.
Complete semantic authority and inline-documentation closure remain open.
Integration regression acceptance remains open. Private-root writer routing, supervisor reachability, both AP paths, actual CR3 residency and live-root retirement remain open under the owned address-space design. Canonical acceptance remains 15/460 leaves, weighted 3.48%; external Rust/LLVM/runtime rebuilding inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
Retaining the table binding cannot preserve withdrawn source access, rebind the original tables or establish physical RAM reclamation.
Private-root readiness and activation remain open under Kernel #22, with Kernel review, manual review and Phase 6 completion. Acceptance remains 15/460 leaves, weighted 3.48%; external toolchain/runtime rebuilding inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
Every previous marker, grant, cleanup assertion and original 60/120-second deadline remains required.
The original pre-entry startup-silence failure remains open. No unchanged failed input was retried for acceptance. The three new reports use bug_report with applicable bug, security, ci, refactor and phase-6 labels; the two corrected defects remain open for publication CI review.
Owning Kernel review, Bootloader review, Integration review, manual review and Phase 6 completion remain unfinished. Owned address-space routing and residency, semantic authority and inline-documentation closure, and older CI regressions including release physical-directory input remain open. Canonical acceptance remains 15/460 leaves, weighted 3.48%; external Rust/LLVM/runtime rebuilding inside EriX and both complete EriX guest-build generations remain mandatory and unproven.
All previous grants, timing and cleanup requirements remain required.
The storage report remains open for complete CI review. The separately retained pre-entry startup stall, development COM1 directory failure and other older regressions remain open without unchanged-input acceptance retries. Kernel PR 3, Integration PR 12, manual PR 4, owned address-space routing and Phase 6 completion remain unfinished. Actual private-root routing, readiness, residency, invalidation, complete authority and inline-documentation closure, external Rust/LLVM/runtime rebuilding and both complete EriX guest-build generations remain mandatory and unproven. Acceptance remains 15/460 checklist items, weighted 3.48%.
Related records and contracts
erikinkinen referenced this issue from erix/lib-posixabi2026-09-12 07:56:23 +02:00
[FEATURE] [P01] Freeze the complete source, build, ABI and self-hosting inventoryto [FEATURE] Freeze the complete source, build, ABI and self-hosting inventoryerikinkinen referenced this issue from erix/lib-cstd2026-09-12 08:02:05 +02:00
erikinkinen referenced this issue2026-09-12 10:21:05 +02:00
erikinkinen referenced this issue from erix/lib-partition2026-09-15 15:13:51 +02:00
erikinkinen referenced this issue from erix/sha2-tool2026-09-15 15:13:54 +02:00
erikinkinen referenced this issue from erix/lib-stdio2026-09-15 15:29:32 +02:00
erikinkinen referenced this issue from erix/boot-tool2026-09-15 15:59:31 +02:00
erikinkinen referenced this issue from erix/coreutils2026-09-15 15:59:35 +02:00
erikinkinen referenced this issue from erix/extop2026-09-15 16:24:52 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-09-15 18:05:51 +02:00
erikinkinen referenced this issue from erix/ramfsd2026-09-15 18:22:30 +02:00
erikinkinen referenced this issue from erix/timed2026-09-15 18:22:44 +02:00
erikinkinen referenced this issue from erix/ttyd2026-09-15 18:22:52 +02:00