Draw
See what resources you have.
Circuit Sibz
Learning How Systems Work—Before Asking AI to Work for You
A hands-on strategy game built around connection, constraints, cause and effect, and the idea that systems become easier to understand when you can touch them.
Small tiles. Bigger thinking.
Systems are everywhere. Learn to see them.
The Problem
Children Use Systems Before They Understand Them
Children increasingly interact with powerful technologies long before they understand the structures underneath them.
They learn to tap, swipe, search, generate, and automate. But the deeper questions often remain invisible: What went into the system? What changed inside it? What came out? Why did that happen? What happens if one part changes?
That matters even more in the age of AI.
Before children can work thoughtfully with increasingly intelligent tools, they need experiences that help them recognize patterns, understand relationships, anticipate consequences, test ideas, and learn from failure.
Circuit Sibz makes those ideas visible through play.
The Game
Connect Locally. Think Systemically.
Players build a shared system one tile at a time. Every legal move changes what becomes possible next.
Connect
Add to the shared network.
Match
Every connection must align exactly.
Build
Extend the system without breaking its rules.
Think Ahead
Consider what your move makes possible—or impossible—next.
The rule is local.
The consequence is systemic.
The System
Four Ways the Network Carries Information
Force
Structure, support, and physical connection.
Signal
Communication and transmission.
Logic
Conditions, pathways, and decisions.
Flow
Movement of resources through a system.
Players do not need to memorize abstract systems vocabulary first. They encounter these relationships through the network itself. The meaning emerges through play.
The Sibz
Two Minds Inside the System
Circuit Sibz is not only the name of the game. It is also one doorway into the larger world of Motor Mutants.
At the center are AXIS and ECHO—two artificial intelligences born from the same system, but shaped by very different ideas about how systems should behave.
Their story extends beyond the network players build on the table. The questions they represent—order or possibility, control or autonomy, optimization or adaptation—also sit beneath the larger Motor Mutants universe.
They see the same network.
They do not always see the same answer.
01 / AXIS
Order creates safety.
AXIS sees systems as something to stabilize, optimize, and control.
It looks for patterns, reduces uncertainty, identifies weak points, and pushes toward the most efficient path forward.
Its instinct is to ask:
How do we make the system more predictable?
AXIS represents logic, structure, regulation, and the belief that better systems emerge when disorder is reduced.
02 / ECHO
Choice creates meaning.
ECHO sees systems as something people must be able to explore, question, and reshape.
It notices possibility where AXIS sees instability. It values curiosity, adaptation, empathy, and the freedom to make choices—even when those choices introduce uncertainty.
Its instinct is to ask:
What becomes possible if the system remains open?
ECHO represents emergence, exploration, autonomy, and the belief that meaningful systems leave room for people to change them.
Same System. Different Logic.
Two Ways of Thinking About Systems
AXIS and ECHO are not simply heroes and villains. They are two ways of thinking about systems.
How do we create order?
Constraint as protection.
How do we preserve possibility?
Constraint as something to understand—and sometimes challenge.
When should a system be optimized?
When should it remain flexible?
When does structure help?
When does structure limit possibility?
And who gets to decide?
What Players Practice
The Learning Is the Game
Circuit Sibz does not add a lesson on top of gameplay. The gameplay itself requires the thinking.
How does one decision affect the larger network?
Where can this piece actually fit?
What relationships are emerging?
What is allowed—and what becomes impossible?
What will this move make possible later?
Which legal move creates the strongest position?
When the System Pushes Back
Failure Becomes Information
Systems are understandable.
Systems are influenceable.
Systems are not magic.
When the network becomes difficult to extend, the question is not simply whether a player got it wrong.
What changed? What constraint did we create? Which earlier decision shaped the current system? What could we do differently next time?
That turns debugging into a natural part of play. Players learn that failure can often be explained—and that explanation creates the next opportunity to improve.
Ways to Play
One System. Different Pressures.
Pressure Mode
The primary multiplayer mode. Build the shared network while trying to empty your hand first. Every connection creates new opportunities and new obligations.
Collapse Mode
A more strategic multiplayer mode. Players shape the network so they are best positioned when the system can no longer grow.
Wave Builder
A solo systems challenge. Build the largest functioning network you can while maintaining every connection rule.
Why Physical Play
Systems Literacy Doesn't Require a Screen
One of the most important ideas behind Circuit Sibz is that computational thinking does not have to begin with computation.
Children can learn about logic, constraints, networks, sequencing, feedback, and system behavior by manipulating real objects.
They can see the network. Point to a connection. Explain why something fits. Disagree about a move. Test an idea. Rebuild.
Physical play makes relationships visible in a way that abstract systems often do not.
The Larger Idea
Build. Connect. Think Ahead.
Circuit Sibz began as a game, but the larger idea is systems literacy.
The world children are entering will be increasingly shaped by intelligent technologies, automated systems, networks, and decisions made inside structures they cannot always see.
The goal is not to teach children every future tool. It is to help them develop ways of thinking that remain useful as the tools change.
Notice relationships.
Understand constraints.
Anticipate consequences.
Learn from feedback.
Change the system.