Foundation
How Tekku operates, what it refuses to compromise on, and the seven principles that every decision passes through before it ships. This is the page that tells you what the company will still be about once the thesis has been proven.
Tekku was not started in a whiteboard session. It was started the night the founder watched his 8-year-old son close Claude in frustration because the AI had made broken code worse. The son wanted a clicker game. Claude wrote something that compiled, then something that did not. The son asked, "why is it red?" There was no good answer. The AI had no idea the user was eight. It used adult vocabulary for errors. It pasted entire files instead of fixing the one line. It assumed the user would recover. The user did not. He quit.
That night the founder wrote the first Tekku spec. A kid-first AI-native platform where every reasoning step is visible, every error is translated into language an 8-year-old can act on, every checkpoint is a binary choice, and every build ends with a real URL the kid can text to a grandparent. Not a coding tutor. A place where kids build and ship real apps. The product followed the spec. The company is the structure around the product.
The founding instinct has not changed in the months since. Kids need a tool that treats them as builders, not learners. Parents need a surface that gives them back the screen-time conversation. Schools need something COPPA-safe by construction. We built outward from the kitchen-table incident, not inward from a category survey. The company is the continuation of that first night.
The seven principles below are the rubric every Tekku decision passes through. They are not a culture deck. They resolve arguments. When we have to choose between a curriculum alignment a district wants and a kid experience that works, the principles pick. When we have to choose between shipping a feature fast and holding to parent trust, the principles pick. They are listed in descending order of how often we have to invoke them.
Each principle is paired with one concrete example of how it shows up in the actual work. That is the only way to know a principle is load-bearing. If no decision in the last month has had to lean on the principle, the principle is decoration.