Explanation

Explanation pages are for understanding. They do not teach by step-by-step success and they do not act as a reference dictionary; instead, they answer the why questions behind AIVI.

Read these when you want the bigger picture

Question	Page
Why does AIVI exist at all?	Why AIVI?
What changes if I come from imperative code?	If you are new to functional programming
How should I approach real AIVI code?	Thinking in AIVI

What explanation pages should give you

• the mental model behind values, signals, sources, and pipes
• the reasons AIVI chooses explicit types and closed data
• the design logic behind GTK-first native desktop work
• enough conceptual footing that the tutorials and reference pages make sense faster