diff --git a/README.md b/README.md
index dde935a9897d09c4dafc8bd4cfb7fd70c692bd2a..c57225edce1822e5444b136d1421e2349aac65c0 100644
--- a/README.md
+++ b/README.md
@@ -16,6 +16,7 @@ Check the here the [TODO list](TODO).
 
 - **Modularity:**  Each module is self-contained, adhering to the [Open-Closed Principle](https://en.wikipedia.org/wiki/Open%E2%80%93closed_principle). `hotwheels` consists of C libraries wrapped in Python for high-level processing, following the successful paradigm of machine learning frameworks ([reference](https://www.mdpi.com/2078-2489/11/4/193)). Developers can focus solely on their module’s files without altering other parts of the code.
 - **Mini-Apps:**  From over 10 years of experience collaborating with HPC engineers and GPU vendors, I found it crucial to deploy the code as minimal, standalone applications. This approach allows engineers to focus on improving code quality and porting it to different architectures without being distracted by unrelated components.
+See [Cavelan et al.](https://dl.acm.org/doi/10.1145/3394277.3401855)  (2020, [SPH-EXA](https://github.com/sphexa-org/sphexa?tab=readme-ov-file)) for external interesting past cases of Mini-App usages.
 - **Testability:**  A robust testing framework is a priority in `hotwheels`. Each module is isolated and can be independently tested, leveraging the modular structure to facilitate efficient debugging and verification.
 - **Parallelism:**   Recognizing the dominance of **GPUs** in HPC, especially driven by AI advancements, `hotwheels` is designed from scratch to run efficiently on GPUs, multi-core CPUs, and MPI-parallel systems.
 - **Documentation:**  Navigation through a large codebase can be challenging. `hotwheels` prioritizes comprehensive documentation, including high-level overviews and detailed API references for each component. Documentation is generated automatically, and commits to the `main` branch are rejected if they fail the indentation and documentation pipelines.