Apple-Silicon MLX-Swift support for microsoft/Mage-Flow-Turbo (t2i, defaults: 4 steps / cfg 1.0). One of six checkpoints of the Mage-Flow family, all sharing one architecture — this repo carries the port's support artifact; the component weights come from the upstream microsoft repo (MIT) and are not re-hosted (multi-component diffusion pipeline → xocialize namespace per mlx-community conventions).

Code, parity gates, and full porting notes: github.com/xocialize/mage-flow-swift. The DiT/VAE/Gaussian-Shading watermark/scheduler are parity-locked against the PyTorch oracle; T2I and CFG paths are gated per-step and validated with renders at the real defaults (sample_512.png is this checkpoint's).

Notes: the mandatory upstream RAI content filter is wired in (fail-closed); the Gaussian-Shading provenance watermark is reproduced bit-exactly; the DiT runs bf16 with one GEMM row-chunked around mlx-swift's NAX split-K JIT bug (mlx#3797) until a release ships #3810.

Modulation/io/norm layers and the trailing block 11 stay bf16 (the final norm amplifies last-block quant error ~1.6× into proj_out). Files are self-describing (metadata carries bits / group size / kept blocks) and load directly with no bf16 peak — int8 gate: quant-vs-bf16 per-pass, family threshold ≥ 0.9998; int4 gate: quant-vs-bf16 per-pass, family threshold ≥ 0.99. Quantization is weight-only: the mandatory content filter and the bit-exact Gaussian-Shading watermark are unaffected. Measured t2i peak GPU @1024²: bf16 19.6 → int8 17.2 → int4 16.1 GB.

MLXEngine: MLXMageFlow (same repo) wraps the family as MageFlowT2IPackage / MageFlowEditPackage — quant tiers auto-materialize these files via WeightSourcing.