This public source tree implements Wan training only. External families may be provided by separately distributed plugins through the exact-name lazy program entry-point contract; they are not built-in products or release artifacts.
cli
└─> programs # sole composition root
├─> training # model/algorithm/engine-neutral lifecycle
├─> engines # FSDP and TeleTron distributed mechanisms
├─> models/wan # Wan model, sampling, attention, parallel math
├─> algorithms # pure math and structurally compatible hooks
├─> reward # registry, routing, execution, providers
├─> datasets # contracts and Wan preprocessing
└─> config
recipes # declarative only; never imported by teleboost
third_party # source mirrors; never bundled into root artifacts
A program is a typed binding of (family, algorithm, engine, policy). Most
programs are rows in programs/builtins.py assembled by common wiring; only a
topology that cannot be expressed by that assembler owns special composition
code.
programsis the only layer allowed to assemble concrete families, algorithms, engines, rewards, and training hooks.training/coreimports no concrete model family or family adapter.training/families/wanmay adapt Wan training semantics but does not import the composition root.models/wanowns model computation; distributed framework mechanics live inengines.engines/teletronreceives concrete model factories by injection and never imports models or training.rewardnever importsprograms.teleboostnever importsrecipes.- vendored
third_partycode never imports its TeleBoost host.
These rules are executable in tests/architecture/.
The Git branch is the release source of truth. Non-Wan family paths are not retained as hidden implementations, compatibility facades, inactive registry entries, recipes, dependency extras, or build-time rewrite inputs. The release builder fails if this contract regresses, so source, sdist, and wheel remain isomorphic at the product-family boundary.