[codex] Reorganize core contracts and source layers#9
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
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.
What changed
This PR continues the core-convergence work by tightening the repository around five layers:
core/logicalcore/executioncore/contractinteropexperimentalIt also keeps the Python ecosystem as a supported interop layer, removes the old dashboard path from the active runtime lane, and finishes the vector-search v0.1 contract tightening.
Concretely, this PR:
examples/andbenchmarks/areas[1 2 3]and[1,2,3]src/dataflow/core,src/dataflow/interop, andsrc/dataflow/experimentalWhy it changed
Velaria had already converged conceptually on a local runtime kernel plus supported Python ecosystem plus experimental same-host runtime lane, but the repository still mixed those concerns heavily in directory layout and target ownership.
This change makes the core boundary more explicit in both documentation and source layout so future work can expand from a clearer center instead of growing more parallel “fact cores”.
Impact
Validation
bazel test //:core_regressionVELARIA_PYTHON_BIN=/Users/bytedance/.local/share/uv/python/cpython-3.12.10-macos-aarch64-none/bin/python3.12 ./scripts/run_python_ecosystem_regression.sh./scripts/run_experimental_regression.sh./scripts/run_vector_search_benchmark.sh