architecture: specialized-JS executor is emission-only — unsafe-eval out, as invariant - #28
Merged
Merged
Conversation
…is out, as invariant Operator decision (2026-08-10), rescoping #8: no code path may require CSP beyond wasm-unsafe-eval. The v2 host-boundary executor becomes a descriptor->JS-module generator with an AOT-shaped contract (explicit linking context, no closure capture of live runtime state), delivered by deploy-time emission or a server-host first-load cache import — never eval/new Function. Browsers running dynamically-loaded components stay on the interpreter. Kills the CSP feature-detection/fallback machinery and a third executor mode in the test matrix; the differential oracle survives via imported emitted modules (the production delivery mechanism itself). Deploy-time unbundling moves to the caching track (#7) — packaging, independent of executor choice. All still gated on #17 measuring a gap. §3 CSP bullet, §8 v2 + future-options bullets, §11 diff-testing note, §12 risk row; issues #8 (rewritten) and #7 (scope comment) updated alongside.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pins the operator decision before anyone spends the budget: the runtime never requires CSP beyond
wasm-unsafe-eval(§3, now an invariant). #8's v2 executor is rescoped to an emission-only generator — deploy-time AOT or server-host first-load cacheimport(), one AOT-shaped artifact, noeval/new Function, no CSP-detection/fallback machinery, two-mode (not three-mode) differential matrix via imported emitted modules. Unbundled deploy layout moved to #7 (packaging, executor-independent). Everything remains gated on #17 measuring a real gap.Docs-only; issues #8/#7 already updated to match.