Independent render-artifact review, 2026-10-23

Historical source last updated, 2026-10-23. Runtime and implementation claims below describe that dated source; see current app notes and source for subsequent changes.

Verdict: REJECT the candidate's unrestricted executable-identity/cache contract; do not integrate. Candidate fd5e3fc9329711d3190bbd5c7046976c21d0b9a1, exact base/unchanged remote main 7f7358c160ae7185fc38f9a15447a6d20c00f97e. This is an independent source and small-fixture protocol review, not native acceptance. No renderer/WAT, D3D fixture 09dc88de, production helper, or main change is published by this review.

Concrete executable-identity failures

  1. prepareArtifact checks only require.cache[watx.js]. Importing the actual test/compile-src.js also imports the actual closure adapter, but does not load WATX until compilation. Import that adapter, replace its disk file with throw Error("CHANGED adapter must reject"), then prepare. Preparation succeeds using the previous cached function; the receipt seals the new, throw-only adapter and consumption accepts it. The before/after hashes are identical because the replacement is complete before preparation starts. This is a deterministic stale-code binding, without any concurrent writer during hashing or compilation. Checking the loader cache alone does not establish that the sealed adapters are the evaluated adapters.
  2. Default mode hashes a changed compiler loader into a different cache key, but compile-src and watx-closure retain Node's previously loaded loader. First boot with the tiny loader, replace that loader with a throw-only file, verify that identity() changed, then boot again. The second boot succeeds using the old loader. Fresh disk identity invalidates the Wasm map entry, not the executable compiler cache. This control uses the real closure and compile adapter, with an eight-byte loader double and instantiation double.

The replay asserts both defects, rather than accepting any thrown exception as evidence. See independent.js (historical artifact: d3d-render-artifact-independent-review-20261023/independent.js), checks.log (historical artifact: d3d-render-artifact-independent-review-20261023/checks.log), and execution receipts (historical artifact: d3d-render-artifact-independent-review-20261023/execution.jsonl).

Scope qualification: both failures require disk changes after a relevant module has been loaded. A wholly immutable tree for the entire Node process, started fresh, avoids these reproductions. The producer explicitly documents immutable inputs during an admitted command, which is a useful operating restriction; these findings do not allege failure under that narrower condition. However, the feature also expressly offers fresh identities and invalidation between default calls, and its prepare freshness guard does not enforce adapter freshness. The broad source/compiler identity claim therefore needs a narrower, enforced lifetime contract or an executable-cache correction before acceptance. The immutable-source requirement cannot by itself prove the requested behavior when exercising input invalidation between calls.

No speculative compiler input omission was found. The concrete omission is the relationship between hashed disk adapters/compiler and their cached evaluated versions. Merely deleting all require-cache entries is not a reviewed fix: other callers can retain exports from the same compiler, and default/prebuilt users currently share this process. A safe correction must explicitly settle that lifetime/compatibility behavior and retain the two reproductions as rejecting controls. This bounded review leaves production code untouched rather than claiming such a lifecycle change is qualified by loader doubles alone.

Independently examined successful properties and limits

Evidence, resource bounds, publication, and remaining gates

Replay from this report's directory in its checkout:

timeout 60s python3 docs/re-notes/d3d-render-artifact-independent-review-20261023/run.py \
  node --max-old-space-size=256 \
  docs/re-notes/d3d-render-artifact-independent-review-20261023/independent.js

The adjacent sealed reviewed-inputs contains small exact candidate/main input copies for replay after rejection; no executable was copied. Fixtures create tiny temporary input files and always remove them. Node executes installed in place. The full compiler is neither copied into fixtures nor evaluated. input-seals.json records copied inputs. The original independent harness had a generated-regexp quoting error; its failed log/receipt remains, followed by the corrected passing run. No guard failure was retried unchanged.