Skip to content

Bind inventory mutation kills to oracle provenance - #785

Merged
d6g8k5htny-coder merged 1 commit into
mainfrom
codex/cbz-inventory-origin-20261109
Nov 9, 2026
Merged

d6g8k5htny-coder merged 1 commit into
mainfrom
codex/cbz-inventory-origin-20261109

Conversation

@d6g8k5htny-coder

@d6g8k5htny-coder d6g8k5htny-coder commented Nov 9, 2026 •

Copy link
Copy Markdown
Owner

Inventory mutation controllers could count a subject or helper AssertionError as a kill because they trusted formatted unittest failure text. This change records actual traceback code identities before unittest cleanup and requires the selected synchronous test body or finite unittest assertion helpers to be the origin. It retains the original ten source mutations and adds the previously surviving post-status and fsmonitor mutations; no inventory implementation, mathematical statement, bound, axiom, kernel outcome, authorship or scientific disposition changes.

Native commit 2b93a6d2279e5f3edff0eb991e4fdb25d64a6b8f and hosted head 9c21bdfabed78477f7ef7e6ef4fb28bad1b31214 have identical tree 9c036c987ca439135a1784bb5e79711782df8a79. The native composition preserves Main #783's six canonical/decision files before this documented follow-up. Its prior source commit and prerequisite-bound Git delta are retained in the evidence; published Main history remains the normal parent.

Observed local validation on the exact test and recorder bytes in that tree:

  • 83 inventory contract tests passed in each Python mode, no top-level skips, with 11 passing original-source baselines and 12 authorized source-mutant kills per mode. The two full-suite mutant paths each account for exactly four named inner recursion skips.
  • A real subject-assertion contamination of the full-suite path produced 83 failures and four declared skips per mode and was rejected. The eight original selected mutation paths also rejected real subject-assertion contamination in both modes. Historical false kills are retained, not rebound.
  • Four recorder self-mutations were killed in each child mode using the previously qualified node-freshness origin checker. An adverse driver experiment refused a no-op and a subject assertion in both parent modes. The initial missed post-status and forged-target mutants and an initial driver JSON parsing error are preserved.
  • Four origin-control tests and 104 navigation/reader tests passed in each mode without skips. The exact native committed tree then passed the bounded G11 census in both modes: 1,365 files, 70 tools, zero failing findings or tools and zero skips. Both reports are byte-identical, SHA-256 02536f852c5cf69a5d3125d50cd485f26d77fa8459ccad82447a766a4dfe50a4; the existing invalid-escape SyntaxWarning is retained. This is not the final federation G11 gate. Hosted checks completed successfully for tested merge cc78eb354e2e65705bc76bd23ad9e28ccfd31175, whose tree matches this head: navigation run 42692397895, workspace-landing 42692398125, G11 component 42692398310, federation drift 42692397871 and public shop 42692397843. The hosted normal regression ran 2,576 tests with 25 skips; it does not establish the no-skips federation criterion. The focused component checks passed in both modes as described above.

Main #783 and Workspace #56 are separately observed at 7738e4c2... and 5dcb544c...; Workspace pins that Main. Both Workspace post-merge jobs succeeded. A later Main merge requires a fresh guarded Workspace pin comparison. The separate #784 Node repair is active; its earlier success is scoped to its tested base, and the original failed Node run remains preserved.

This is a bounded synchronous unittest component, not a hostile-code sandbox, proof checker, whole Layer A audit, final G0/G6, scientific review, CBZ-0 or terminal Partial. Source-bound evidence is libfile_fde3_f-a1d4cb841f208191aafdc61057043076_59a0f9f234e48191bc19fddcc0f80648, SHA-256 bea63fdd7dc5e53174e2af4e08f3db91973546a45392def6763446f097f026d3; prior adverse probes are retained separately. A fresh head and default comparison remains necessary before normal integration.

@d6g8k5htny-coder
d6g8k5htny-coder marked this pull request as ready for review November 9, 2026 20:37
@d6g8k5htny-coder
d6g8k5htny-coder merged commit c81b757 into main Nov 9, 2026
15 checks passed
@d6g8k5htny-coder
d6g8k5htny-coder deleted the codex/cbz-inventory-origin-20261109 branch November 9, 2026 20:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant