Explanation

Understanding-oriented documentation: why Kokua is shaped the way it is. Read these when a rule elsewhere in the documentation looks arbitrary.

• Design principles: why Kokua exists, and the six principles that serve that goal, each with the code backing it and what it therefore rules out. Start here.
• Architecture: the whole map. Module layout, control flow, configuration layering, images, MCP, planning, and the web front end.

For task-oriented recipes see the how-to guides; for exhaustive settings see the reference.