Research Desk
The research desk is where this project stops speaking only in its own voice. It points outward — to the papers, repositories, and historical decisions that make the whitepaper stronger and more honest.
Why a research desk exists
An optimization project without external references is an isolated claim. The research desk answers four questions that no internal page can answer alone:
- Which official sources justify the architectural claims made in the architecture section?
- Which public SGEMM or GEMM projects show what a stronger or different approach looks like?
- Which papers improve the mental model behind the ladder, especially for Tensor Core and memory hierarchy reasoning?
- How did this project's current narrative shape emerge from an earlier, weaker form?
Research desk map
| Surface | Primary job |
|---|---|
| Reference Map | Structured index connecting each whitepaper claim to its external source |
| Curated References | Full annotated reference list with reading notes |
| Related Projects | Comparative context — what this repository is and is not |
| Evolution Notes | Why the public narrative and route map changed over time |
| Papers | Focused academic reading list for theory and optimization history |
| Further Reading | Recommended next routes after each section |
| Performance Casebook | How to interpret representative outcomes without over-claiming |
Suggested research path
For a first pass through the research desk:
- Start with Reference Map — understand which claims have external backing
- Continue to Related Projects — calibrate where this project sits relative to the field
- Read Evolution Notes — understand why the current presentation shape was chosen
- Use Papers or Further Reading for depth on specific topics
Using the research desk as a reviewer
If you are auditing the whitepaper's claims, the research desk gives you the tools to check them:
- Find the claim in the architecture or validation section.
- Find its supporting source in the Reference Map.
- Check whether the source supports the claim at the stated scope.
A claim that cannot be traced to an external source, an internal implementation, or an explicit open-question label is a claim that should be challenged.
What the research desk is not
The research desk is not a literature survey that pre-justifies the project. It is a live index that keeps the whitepaper honest by making its external dependencies visible and checkable.
It is also not a competitive analysis. The Related Projects page explicitly acknowledges what this repository does not do — because knowing the limits of a project is part of understanding it.