Migrate flow-kernel to the Tiny Core Linux substrate - #4
Merged
Merged
Conversation
This was referenced Aug 21, 2026
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
1 participant
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.
Implements the canonical architecture described in #1 by replacing the bespoke Multiboot2 kernel with a pinned Tiny Core CorePure64 + Linux substrate.
The branch adds reproducible Tiny Core fetch/boot tooling, deterministic QEMU health diagnostics and regression baselines, the Flow/Linux ABI and syscall layer, a libc-free Flow userspace smoke test, initial eBPF target documentation/tooling, CI artifact capture, and the project Pages site. The retired
x86_64boot/kernel/linker path is removed so Linux owns commodity kernel infrastructure as intended by the master checklist.This also incorporates the current
maincitation metadata, so the migration branch is now zero commits behindmain.This PR corresponds to the Phase 0 “review and merge
codex/tiny-core-base” item in #1. It does not close #1; the later eBPF, packaging, hardening, DX and release phases remain tracked there.