Repository navigation
docs: position FlowKernel as an OS-level trust substrate - #11
Merged
Merged
Conversation
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.
FlowKernel currently describes a C-first AI Execution OS, which can be read as a claim to replace a general-purpose OS or as an existing cross-platform implementation. This change separates the public category from the experimental vehicle: FlowKernel is an OS-level trust and execution substrate for untrusted agentic intelligence; the C-first target and Linux reference lab remain separate planned research lines.
It also records that future Windows/Linux/macOS mappings would require platform-specific enforcement adapters and that none exist today. No R0 state, implementation authority, roadmap gate, or runtime code changes.
Validation:
node scripts/verify-repository.mjsgit diff --check