| I have added two deeper "Behind the Scenes" pages for those interested in the linguistic philosophy or the specific agentic workflow: WHY SWALPA? (https://swalpa.org/behind_swalpa/why/) This section dives into the "Survival Kannada" philosophy. It explains why we prioritize high-frequency scenarios like negotiating auto fares or understanding local etymology (e.g., why tech hubs like Marathahalli still carry the "-halli" village suffix) over standard textbook grammar. AI ARCHITECTURE & WORKFLOWS (https://swalpa.org/behind_swalpa/architecture/) This page breaks down the "Local-First" stack and the agentic loop: * The Staging "Brain": I maintain a private repository where I use Gemini Deep Research to crunch raw linguistic data. This verified "Spec" is what I then feed to Antigravity (the coding agent) to build out the game engines and lessons. * Portability: The framework is designed to be "forkable." A sister project for Tamil (konjam.org) is already being built using these same architectural principles. I am happy to dive into the weeds on the prompt engineering, the TTS pipeline, or the Bangalore-specific nuances if anyone is interested! |