Repository navigation
Syntakt core: OS 1.40/1.42 research and boot-probe core (from #684) - #702
Merged
Merged
Conversation
docs/VERIFICATION.md keeps both new entries, newest first. The Syntakt summary names only the 1.40A and 1.42 rebuilds as byte-identical, and the core README points at the research report's 1.40A survey. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SakBf5zGyZY61TAzvKCKHC
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
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.
This is @nrdsrfr's #684 with current
mainmerged in. Their commits are unchanged; the owner can't push to the contributor's fork from here, so it comes in through this branch. All of the research, code and docs are nrdsrfr's; see #684 for the full description.What the merge commit adds
docs/VERIFICATION.md: kept both new entries, newest first. The conflict was main's elekloader kit 0.6.0 entry (elekloader kit 0.6.0, with the catalog as it is #699) and this PR's Syntakt entry, both added at the top.sdk/machines/syntakt/machine.json: the summary now says only 1.40A and 1.42 were rebuilt byte-identical. No 1.40 rebuild is recorded; the research notes cover 1.40A and 1.42. The summary has to stay within 200 characters. The registry was regenerated withnpm run machines:generate.sdk/syntakt/core/README.md: open decision 4 no longer says the 1.40A image "was not available". It links to the report's §5.1, which surveys it at container level.Owner decision recorded at merge. The boot stub replays the two instructions its
jmpdisplaces at 0x400004b2:lea -16(%sp),%spandmovem.l %d4-%d7,(%sp). Their 8 encoded bytes are written intoboot.sandSYNTAKT_BOOT_STUB(src/engine/elektron/syntakt.ts), not read from the user's file. The owner reviewed this and accepted it for the research probe. Digi Utils'osc_glue.sis a precedent.What changes on the live site: only the Syntakt machine page.
There are no builds, downloads, beta UI or backend changes.
Checked:
npm run check -- --base origin/main(2,366 tests) andnpm run pr:ready(Ready) on the merged tree.Supersedes #684.
Generated by Claude Code