Evolution Notes

This project evolved in two dimensions at the same time: the kernels became more structured, and the public narrative became more explicit.

Code evolution

The kernel ladder moved from a readable FP32 baseline toward higher-throughput strategies while preserving a comparable launcher contract. That matters because comparability is part of the teaching value.

Documentation evolution

The public site moved from “good documentation” toward a more opinionated whitepaper:

1. first, architecture and methodology were separated clearly
2. then validation boundaries and references were made first-class
3. now the site is reorganized into overview, architecture, academy, validation, and research

Why the new shape is better

• Reviewers get a faster orientation surface.
• Candidates get a better storytelling path.
• Advanced readers get explicit lineage and comparative context.
• The site can become deeper without becoming messier.