Epilogue

tq is ready. It accepts tasks, stores them, answers requests, shuts down cleanly, and checks itself. The path from an empty workshop to a working tool is complete.

This grimoire is deliberately limited in scope. It teaches you to build - it does not explain how the material you build with actually works. Things that stay offstage begin to matter once the first tool is running and you want to understand why it behaves the way it does.

There is an appetite to continue. Ideas for separate materials on:

• How Rust works inside: ownership and borrowing not as rules but as a mechanism; what the compiler does with your code; why zero-cost abstractions is not marketing
• Profiling and performance: how to find where time is spent, how to read a flamegraph, when to optimize and when not to

No timeline yet. If you want to be the first to know - thegrimoire.dev.