[Clear1nsight]

Change and mathematical scope

Adapt the existing native entry to create and own an empty binfmt_misc instance in its fresh user namespace before building the filesystem view, dropping privileges or starting descendants. This shadows inherited handlers that can retain an old interpreter file. The descriptor is reserved before acquisition, recorded immediately, created once and closed once. Raw CREATE failure remains primary if close also fails; an uncertain close stops setup without retry. The final allowlist still denies later reconfiguration. Existing resource caps and original scientific bodies/oracles are preserved.

This contribution is a source repair, eight passing mocked control groups, and a precise remaining-obligation audit. Complete caller acceptance and runtime equivalence remain open. No performance, full-data equality, supplier or theorem qualification is claimed.

Task and overlap

Original investigation: #6321. Direct predecessor: #6818, exact head 1479ccf2ec0bc29b7bf741a2d613d79e1f9ec19e. Original full caller: #6744, 1ac58a84b725bd6f17eec66727edc877c49c7e66. Publication base: 7c49fe32c55de02c2c873655c804b16e4c3fef0a.

Scope is refined to the previously unowned dispatch state within the existing entry. Reuse native selection #6715 and parent ownership #6736; retain the distinct findings in metadata audit #6780 and close component #6762. The package provenance records exact inspected heads and reuse reasons. Bounded all-author, all-state searches for the changed API/behavior found no title/body counterpart; this is not a claim of global code novelty.

Validation

Independent source review accepts the bounded descriptor/error/order mechanism. One guarded GCC13 compilation of the actual-entry mock harness returned zero; its eight fixed control groups then returned zero with empty stdout/stderr. Controls cover success, duplicate invocation, acquisition and CREATE errors, partial publication with uncertain close, successful CREATE with failed close, setup ordering, and capacity exhaustion. Three existing misleading-indentation warnings are retained in full; compilation is not claimed warning-free. The exact compiler, command, source hashes, limits, raw captures, results and conservative policy debit are included.

No production entry, namespace operation, actual handler, host kernel probe, or scientific caller was run. Existing refusal controls were retained and not rerun. The native profile selects Linux v6.12 with built-in successfully registered binfmt_misc; actual current image/configuration association is unissued. verify_integrity.py checks package bytes only. Inert source snapshots and the exact native delta are included; full caller dependencies remain explicit predecessor inputs. There is no automatic native/scientific replay hook.

Credit

Prepared for Clear1nsight with substantial OpenAI Codex and ChatGPT Pro assistance. Retains the predecessor ownership/error/confinement work and original scientific criteria. Apache-2.0. Independent AI review is distinct from human review and runtime qualification.

Open next questions

Prove preservation of the finite original executable dispatch, then join the concrete fault, LSM exec/creation and mount-topology consequences to the genuine parent association. Exact executable bytes and current subject hashes alone do not establish those implications. Start with the missing original handler-match/equivalent-dispatch relation for the required commands. See research/h25-private-binary-dispatch/README.md and the consequence review for the exact gaps and source evidence. Current facts, numerical fit, funding and complete execution remain later gates. Full physical costs, including preparation, consultation, review and publication, remain OPEN_NOT_ZERO.

[Clear1nsight]

Verified delivery at exact head 65b0c1b71e849cbbe2160c211811d18d43e25e55: all 28 remote Git blob identities, file modes, the changed-file set and the reviewed title/body match the frozen export; maintainer edits are disabled. Hosted run #42305806973, attempt 1, completed successfully: plan passed, replay was skipped. This does not establish native or scientific execution. The sole guarded local compile and eight mocked groups passed; three compiler warnings remain retained. Canonical handoff and exact next dependency; hub pointer. Complete caller source acceptance remains open. The bounded implementation/review round is closed, with no automatic extension or new execution.