feat(experimental): tier contract, boundary lint, private-package convention - #279
Merged
Conversation
…vention Writes down the experimental-tier rules converged in the #210 review and makes the mechanical ones lint-enforced: - experimental/README.md — the contract: two-way flow with core (official flows live in core; mainstream packages graduate up, ill-fitting core paths move down), package anatomy with mirror naming (models/ reward/ examples/ named after the core home content graduates into), locked single-stack policy, additive-only requirements with the differentiable⇒same-process⇒same-stack corollary, owner+verification table requirement. - scripts/check_experimental_boundaries.py (pre-commit): core never imports experimental; packages never import each other; recipe requirements may not re-declare core dependencies (same-process colocation cannot version-isolate). - experimental/private_*/ gitignored; the tier is not packaged into the wheel, so private code cannot leak into a build.
2 tasks
haonan3
force-pushed
the
feat/experimental-contract
branch
from
July 31, 2026 07:26
ed98f2a to
d701b06
Compare
haonan3
marked this pull request as ready for review
July 31, 2026 08:07
github-actions
Bot
added
need review
This was referenced Jul 31, 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.
Summary
Writes down the experimental-tier contract converged during the #210 review and makes the mechanical rules lint-enforced. Stacked on #210 — the diff collapses to the last commit once #210 merges.
experimental/README.md— the tier contract: official flows live in core; this tier is the incubation side of a two-way flow (mainstream packages graduate up, ill-fitting core paths move down; privateexperimental/private_*/packages stay uncommitted). Package anatomy with mirror naming (models//reward//examples/named after the core home their content graduates into, so promotion is a structural no-op), single locked-stack policy (no version-compat branches), additive-only requirements with the differentiable ⇒ same-process ⇒ same-stack corollary, owner + verification-table requirement.scripts/check_experimental_boundaries.py(wired into pre-commit): core never importsexperimental; experimental packages never import each other; reciperequirements.txtmay not re-declare core dependencies..gitignore:experimental/private_*/; the tier is deliberately not packaged into the wheel, so private code cannot leak into a build.Test Plan
python scripts/check_experimental_boundaries.py— ok on the clean tree.transformers==4.45.2re-pin) — all three reported, exit 1.pre-commit run --all-files— green, including the new hook.Compatibility / Risk
Docs + additive lint only; no runtime code paths change. The new hook fails closed on future violations by design.
AI-assisted; reviewed and directed by the maintainer.