Workflows
The workflows page translates “what should I do next?” into specific reading paths so you can move naturally from the whitepaper narrative into action-oriented material.
Choose the goal first, then choose the page
| Current goal | Recommended path |
|---|---|
| Decide whether it is worth trying | Why FastQTools → Whitepaper → Performance |
| Run commands quickly | Getting Started → CLI Reference |
| Integrate into an existing workflow | Configuration → Deployment |
| Enter development and maintenance | Developer Guide → Reference |
Typical reading paths
Adoption evaluation
Start with Why FastQTools to confirm the problem fit, then read Architecture and Performance to judge whether the claims hold together.
Execution path
If you are already ready to run commands, start with Getting Started and then fill in parameters and environment constraints through CLI Reference and Configuration.
Integration and maintenance
If your goal is to embed the capability into a C++ application or submit patches to the repository, enter through the Developer Guide and Reference, then return to Architecture to keep the boundaries aligned.
Relationship to the whitepaper
The whitepaper builds the decision framework. Workflows turns that framework into action. After reading this page, you should know whether to keep drilling into execution documents or step back into the evidence layer for more context.