From Code Consumers to System Architects.
Most AI education for teenagers teaches prompting. We teach architecture. A student who learns a clever prompt has learned a trick. A student who learns to build a harness - memory, tools, permissions, sensors, observability - has learned how real systems are governed.
Built on two decades of building enterprise systems - not a weekend of AI enthusiasm. Part of the KETL pathway, Sydney, Australia.
Agent = Model + Harness. We treat students as near-adults capable of governing a system - not children being protected from one.
Explorer → Co-Creator → Architect.
A system to click into, not a syllabus to read. Each tier ends on what a student builds, not what they learn about.
Two weeks, one pathway.
A remote intensive across the Australian Spring holidays, running as two one-week blocks - Sep 28 - Oct 1 and Oct 6 - 9 - with a break between them, not back-to-back. Seats are capped at 12. Mentorship is live, from someone who has built these systems professionally for over two decades. Ages 12-18+
Explorer → Co-Creator → Architect pathway, delivered across both weeks. Not self-paced video - a mentor who has built these systems, live in the room throughout. * Friday - 2nd Oct - No class as it's a Public Holiday.
Small cohorts — 5 to 7 students — run by trained facilitators progressing through KETL's own pathway: observer → co-facilitator → solo delivery → senior facilitator. Every facilitator has been through the model themselves before running it. This isn't outsourced. It's built to hold up.
For families already part of the Coding Club, Python Boot Camp, and other technology-interested communities associates with KETL, and for families across Australia who value hands-on, independence-led learning meeting this pathway for the first time.
Twelve seats, and they'll go to the families who move first. This cohort shapes the pathway students in it end up building. Ask us anything about where things stand.
Whichever door you're coming through.
This fits the pedagogy you already trust.
Independence and the prepared environment don't stop at technology. A harness - permissions, guardrails, observability - is a prepared environment for AI. Your child sets the boundaries; they don't just work inside someone else's.
Your worry about screen time and dependency is the right worry.
Most AI tools train a child to depend on an answer they didn't build. This pathway trains the opposite: a student who understands the system well enough to govern it, not just query it.
Questions we get asked.
+Isn't this just prompt engineering with a fancier name?
No. Prompting is one skill inside Explorer. Architect is about the harness around the model - the tools it's permitted to call, the guardrails it must respect, and the observability that lets a student see what it actually did.
+Does my child need coding experience?
No. Explorer assumes none. By Architect, students are building small tools and APIs - the pathway builds toward that rather than requiring it upfront.
+Who's actually teaching this?
Live mentorship from someone who has built enterprise systems professionally for two decades - this pathway is that experience brought down to something a 12–18 year old can build and understand.
+What if we're not sure this is right for our child yet?
Start with the free session for parents and educators. No paid commitment - just a clear look at the pathway before you decide anything.
Learn to govern the system, not just talk to it.
Enquire about the Spring cohort, or start with a free session if you want to see the pathway first.