Complexity Framework is a PyTorch research stack for deterministic TR-Hash Mixture-of-Experts (TR-MoE) language and multimodal models.
- Architecture and naming
- Getting started
- TR-Hash execution engine
- TokenRoutedMLP (removed) and migrating to TR-Hash
- Training
- Run configurations
- GPU and dispatch paths
- API reference
| Public name | Attention | FFN |
|---|---|---|
| TR-GQA | GQA | TR-MoE |
| TR-MHA | MHA | TR-MoE |
TR-GQA and TR-MHA share the same TRHashEngineMLP. They differ only in the
attention head layout. The framework is currently scoped to TR-Hash MoE only
— dense and learned-router baselines were removed and will return later as
explicit comparisons.
The registry values tr_mha and tr_mha_v2 refer to experimental routed
residual adapters inside attention. They are documented separately in
../TR_MHA.md to avoid conflating them with the main
MHA + TR-MoE architecture.
- MoE comparison
- Custom models and registries
- Efficient training
- Multimodal prototypes
- Historical Mu-Guidance control
- TR-Hash image editor
- TR-Hash image-text-to-text
- TR-Hash text-to-image
- TR-Hash object detection and serving
A configuration file or model implementation is not a completed experiment. Documentation distinguishes:
- implemented: represented in code and tests;
- pilot: bounded evidence, usually short or single-seed;
- controlled comparison: matched protocol with tracked metrics;
- planned: a launch or cluster plan without completed metrics.
Claims should point to the tracked configuration, metrics, or artifact that supports them.