v0.1 · open-source · MITBuilt with Coach Lamont · Brooklyn

The kid was already doing the thinking.

We just give them the tools to see it, and build something real for the people they belong to.

About this page

An open-source teaching method being developed by Reemy (Kareem Adedeji Richard Akabashorun) and Coach Lamont Kirton in Brooklyn, alongside BeyondChess and an inclusive adaptive basketball program. The method is the body. The use cases below are reflections of it into specific contexts. MIT-licensed. Forks welcome. Working name is The Method until Lamont and Reemy lock in the real one — see the open items section.

What this is for

Write-access to your own attention.

We teach young people to notice which beliefs and habits got installed in them without their choosing, and the skill to deliberately build new ones. Success is measured by what each kid builds from their own real problem.

Chess is the surface. Attention is the actual subject. A kid who finishes can sustain attention, see structure others miss, and turn a problem they care about into something real.

That skill transfers — to school, to work, to whatever they do next. We aren't teaching coding. We aren't teaching chess. We are teaching kids to see their own world as a system they can change, and giving them the tools to ship a first version of that change.

The method — six steps

From a kid's own observation to a community-deployed build

01

Identify

Start with the kid's own observation — a problem they actually see in their own life, family, or block. Not a topic assigned. Not a tutorial. Their thing.

02

Research

The kid interviews family, classmates, teachers, anyone living with the same concern. Listening is the first discipline. The build hasn't started; the kid is becoming a researcher of their own world.

03

Connect

Together we map the concern to the people it will affect, to what they already have, to what's missing. This is where cross-domain pattern recognition kicks in — what concept from class is actually structuring this real problem?

04

Brainstorm

The kid leads on intent; the teacher guides on what's buildable. The kid stays in the driver's seat of their own concern. The build is real, small, shippable.

05

Build

The teacher drives the AI build process; the kid shadows. They watch, ask, redirect when the build drifts from their intent. They are not consuming AI content; they are stewarding the build of their own idea.

06

Ship

We deploy the build — a website, a system, a community tool — in a form their family, classmates, and community can actually use. Their name is on it. Their reasoning is on it. They wrote it.

The three moves underneath

How the method actually changes a kid

The six steps above are the surface. Underneath, every session is teaching one of three moves. They are taught in order because each depends on the one before it.

Move 1

See the thread

Catch a belief or habit and recognize it as something that was built, not something that's simply true. A kid who thinks “I'm just bad at this”feels like they're reporting a fact. Move 1 is learning to see it as a thread that got walked into them — which means it can be re-walked.

Move 2

Walk the new thread under load

The old habit reps itself without permission. Move 2 is deliberately practicing the better pattern while the old one is still pulling. The hard middle. The guitar principle: you don't stop the rhythm to fix a mistake — you keep the strum going until the mistake becomes texture.

Move 3

Build something that rests on it

A new skill stays fragile until something real depends on it. Move 3 is making the kid build an actual thing from their own problem, so the skill becomes load-bearing. Care alone doesn't hold a skill in place. Care plus a structure resting on it does.

See it. Walk it under load. Build on it.Every session in a cohort is one of these three moves. The six-step method above is just the three moves spelled out as a workflow. The cohort isn't learning a curriculum — they're practicing a skill, in three stages, until each stage holds.

Why this works

The Derivative Principle

Coach Lamont named the philosophy that powers this work, and named it well. BeyondChess is analog coding: the kid was already doing CS on the chess board — we just helped them see it. This method runs the same move with the kid's life: their concerns and observations are already the early stages of product thinking. We help them see it and ship it.

The kid was already doing the thinking. The method just makes the thread visible, and gives them the tools to walk it.

That framing has a practical consequence: this isn't a new curriculum to bolt on, and it isn't two unrelated programs. BeyondChess and this work are one philosophy in two mediums. The funder story is the same. The theory of change is the same. The kid walking through one is being prepared for the other.

The discipline underneath

Why this resists the AI shortcut

Most schools incentivize the wrong thing. Schools specify an outcome — a test score, a finished assignment, a grade — and the kid becomes an optimizer. The optimizer correctly delivers the specified outcome by the cheapest available path. In the 2000s, SparkNotes. In the 2010s, paying for essays. Today, ChatGPT. The kid isn't broken. The kid is aligned — to the reward we set, not the one we meant.

This method fixes that by rewarding the trajectoryinstead of the endpoint. There is no SparkNotes for noticing a real problem in your own neighborhood. There is no shortcut to interviewing six families about water access. The shipped thing isn't the rewarded target — it's the natural consequence of having actually walked the process. What the method rewards is the walk. The AI shortcut has nowhere to land.

How the room runs

Anchor and orbit · floor-raising

The teacher is the anchor — they hold a steady rhythm the whole room runs on. Kids orbitat different distances based on where they currently are. A new kid orbits close, matching the basic pattern. An advanced kid orbits further out, adding variation, while staying in the teacher's rhythm.

Floor-raising is the core move. The anchor always plays at a level the lowest kid can join. The advanced kids add their substance on top. Everyone stays in the same wave. Over the weeks, as the beginners develop, the whole wave rises together. Nobody is left out, nobody is held back.

The most damaged kids are the priority.Not because they're easiest — they aren't. Because the change in them is the most visible and the most transferable. When the kid everyone gave up on starts holding attention, the whole room sees that the method is real.

Ratio

Roughly 4 kids to 1 instructor at the youngest ages. Non-negotiable. Anything higher and some kids stop building and start watching. The method depends on each kid being seen.

How a cohort proves it worked

One page per kid · one Demo Day per cohort

Every kid produces one project page, posted publicly with their consent and their name on it:

  • 01 The problem. A real problem the kid found in their own life or community.
  • 02 The brainstorm. How they thought it through. Their reasoning in their own voice.
  • 03 The plan. What they decided to make and why.
  • 04 The build.The actual thing. An app, a tool, a video, a paper artifact. It doesn't have to fully work. It has to be real and theirs.

At the end of each cohort, a Demo Day: kids present their individual builds and the cohort presents one shared group project. Family and community attend.

These pages, together, are the results. They are what a funder reads. Proof that arrives before the funding, not after a promise of it.

As cohorts run, the kid-built project pages will land here on this site, under /method/work. Their builds, their names, their reasoning. Live and visible.

Where it runs

One method, three rooms, more coming

The method is the body. Each context below is a specific reflection of that body into a specific room and a specific group of people.

Use case 01 · Brooklyn · live

BeyondChess + the youth-builder program

Built with Coach Lamont Kirton in Brooklyn. Chess is the surface, attention is the subject. A 50-week arc maps onto the three moves naturally — Read the Parts, Read the Connections, Read the Flow, Read the Whole, Read Anything. The youth-builder program is the same philosophy in the second medium: kids build apps from their own concerns. Entry age 7+, ratio 4:1.

Use case 02 · adult/young-adult · active

Phonix

The same method applied to adults building real projects. Partner: Jonti. Started from a real meeting at a diner; same engine, different person in the chair. Proof that the method isn't age-locked.

Use case 03 · rural Tanzania · conceptread the concept piece ↗

Tumaini Senior Secondary School (concept)

A concept piece written for Tanzania Education Corporation around a STEM/CS Teacher Fellowship at Tumaini in Makuyuni, Monduli District. NECTA-locked in-curriculum integration, Shadow → Interrogate → Drive AI staging mapped to Form level, worked example with a Form 5 student. Theoretical; would activate if the fellowship lands.

Use case N · your context · open

Wherever this lands next

The method is MIT-licensed and meant to be forked. If you're running a youth program, an NGO, a fellowship, or a tutoring practice and want to apply it in your context, take it. Contact is below.

The giants this work stands on

Prior art, named honestly

This isn't a novel method. The project-based pipeline shape — kid's problem to research to shipped artifact — has been validated by programs operating at global scale.

  • · Technovation Girls— 18+ years, 400,000+ girls, 120+ countries including Tanzania. Free. Mentor-driven. Longitudinal evidence: develops “durable identities as problem solvers,” which is the community-builder identity this method targets.
  • · Project SHINE— Two Maasai pastoralist boarding schools in Ngorongoro. Statistically significant behavior and community engagement gains (p<0.001). Same demographic as the Tumaini use case.
  • · Apps and Girls (Tanzania, since 2013), She Codes for Change, Buni Divaz, TechChix, the Buni hub — an active, Tanzanian-led youth-tech ecosystem.
  • · Achievement-goal theory— the decades-old education research showing outcome-rewarded environments increase shortcut-taking and cheating; process-rewarded environments reduce both. This method rides on that finding, doesn't invent it.

Where this method adds something is narrower: the deliberate AI-staging arc (Shadow → Interrogate → Drive, mapped to age/Form level), the observation pedagogy (pressure vs attention; self-observation as endpoint), and the in-curriculum integrationthat fits inside a school day rather than competing with it. Everything else, we're standing on the giants above.

What we're still figuring out

Open items · for Lamont and Reemy to lock down

This method is at v0.1. The shape is solid; the implementation details are deliberately open until the first cohort runs. Naming these in public so they're visible, not hidden.

  • Age tiers within 7+.Lamont's instinct: two tiers (7–9 with visual/drag-drop tools; 10–12 with no-code or AI-assisted builders). Confirm cutoff.
  • What “build an app” means in practice. Live on a phone, designed on paper with walkthroughs, somewhere between. Has to match what we promise.
  • Tech stack per tier. What specific tools the kids touch at each age.
  • Session length, frequency, and total program length.
  • Sister program to BeyondChess, or standalone brand? Lamont leans portfolio-unified. Worth one conversation.
  • The final name.Working name is “The Method.” Lamont's candidates: derivative-principle extension of BeyondChess; kid-as-builder identity (“Founder School”); Brooklyn / cultural anchor; method-named. The name locks in after the first cohort, not before.
  • What identity the kids claim out loud.The “I am a ___” line at the end of a cohort. Names the program from the kid's mouth.
What this is NOT

Guard rails

  • × Not a “kids learn to code” program. Kids don't necessarily learn to code. They learn to build.
  • × Not a pre-packaged curriculum.The student's observation IS the curriculum.
  • × Not an AI-tutoring product.Students don't have direct AI access in early cohorts. The teacher drives, the student shadows.
  • × Not a career-prep funnel out of the community. The intent is the inverse: graduates who build IN their community, not who leave it.
  • × Not monetized.MIT-licensed. Forks welcome. If you're using it, that's the point.
  • × Not a defensible tech product. The framework lens plus a consistent human at the center is what makes it work — and a chatbot cannot be the floor for a kid.
If this is useful

Take it. Adapt it. Tell us how it went.

If you're a teacher, NGO, fellow, school director, or parent and any of this fits your context, run it. Fork it. The method gets sharper through real applications.

  • Maintainer: Kareem Adedeji Richard Akabashorun (“Reemy”) — reemysdreams@gmail.com
  • Co-developer: Coach Lamont Kirton
  • Underlying framework: CHIMERA github.com/DrealR ↗
  • License: MIT — fork freely; link back if you publish your adaptation so the method can sharpen.

The kid was already doing the thinking. The method just makes it visible. The rest is just walking with them.

v0.1 · open-source, MIT · this page will keep updating as Coach Lamont and Reemy run the first cohort and learn what actually works in the room.

🍈
CHIMERA SUBSTRATE ACTIVE