Developer Guide

These pages explain how to extend Diffulex internally to adapt new requirements. They focus on engine boundaries, extension points, test strategy, and debugging workflow rather than user-facing command examples.

• Research Engine

• The Design

• Extending the Engine

• Testing

• Developer Troubleshooting

• Profiling

Suggested Reading Order

Read Research Engine first when using Diffulex as a backend for a new dLLM algorithm. Read The Design before changing scheduler, cache, runner, or strategy code. Use Extending the Engine when adding a model, sampler, strategy, or kernel. Use Testing and Developer Troubleshooting while iterating on a change.

Run focused tests first. Expand to full-suite or GPU-heavy checks only after the smallest relevant verification passes.