reflow2

One project, start to finish.

The Gearheads are a made-up school robotics team. This season they need a climber: the part of the robot that pulls it up onto a bar at the end of a match. Here is that one design, from the first thing it has to do to the first competition, and what happens when the rules change.

Each step says who does it: You the people, AI their AI assistant, reflow2 the record.

1 Say what it has to do

Maya, the team captain, tells the AI what the climber is for: it has to lift the robot onto the bar in under 10 seconds, and it must never drop the robot, even if the battery runs low. The AI writes these down as one thing the climber must do and one limit it must never break, with Maya's name on both.

You say it · AI writes it down · reflow2 keeps it, with who said it

2 reflow2 asks what's missing

Nothing in the record yet says how the climber will meet either one. reflow2 points that out, and the AI turns it into plain questions for Maya: how heavy is the robot? What should happen if power cuts out halfway up?

Before asking, the AI searches what the team already knows, and finds last season's note: the old winch slipped when the battery was low. Maya's answers go into the record too, so nobody asks her again.

reflow2 finds the gap · AI searches, then asks · You answer

3 Weigh the options

The AI lays out three ways to build it: a winch, a telescoping arm, or hooks that grab the bar. It writes each one down as an idea, beside the strongest argument against it. A winch can slip, and theirs did last season. A telescoping arm is heavy. Hooks need the driver to line up perfectly. Leo, who writes the robot's code, adds a fourth: a winch with a ratchet that can't run backwards.

AI drafts the options and the case against each · You add your own · reflow2 keeps them all

4 Decide

Maya chooses Leo's ratchet winch, because the ratchet answers both the never-drop limit and last season's slip. The record keeps who decided, when, and why, and the three options that weren't chosen, with the reasons they lost. The AI could suggest a choice, but a decision only counts as made with a person's name on it.

You decide · reflow2 records who, when, why, and what lost

5 Build it

Leo and the AI write the winch code, and the team draws the bracket. Each file is linked to the part of the design it carries out, so anyone can point at a file and ask "why is this here?" and get the decision back.

You and the AI build · reflow2 links each file to the design

6 Keep the design and the work in agreement

Two weeks later Leo rewrites how the winch code stops at the top of the bar, and forgets to say so. The next time the team runs reflow2's check, it notices that the winch code no longer matches what the design last accepted, and asks: did the design change, or only the code? Leo answers, and the AI records which it was. Nothing drifts apart quietly.

reflow2 notices · You say which · AI records it

7 When the rules change, see what it touches first

Coach Rivera brings news: a new rule says the climb must take under 6 seconds. Before anyone edits anything, reflow2 shows what that touches: the gearing decision, the motor choice, the winch code and the climb test. The bracket and the wiring are untouched.

Maya records the new requirement and a new decision. The old ones are kept, marked as replaced, so next season "why did we change the gearing?" still has an answer.

You bring the change · reflow2 shows its reach · You decide · AI updates the work

8 Learn from how it turned out

At the first competition the climb takes 7 seconds, one too many. The result goes into the record marked as measured, with the date and the match, so nobody mistakes it for a guess. reflow2 points to the decisions that result calls into question, starting with the gearing.

When the team works out why (the battery sags under the new motor's load), the cause is written down before the fix. Next season, the AI starts from this, not from zero.

You and the AI record what happened · reflow2 points to the decisions it reaches

Five steps, over and over

Look back and every step above is one of five: notice a choice is needed, look into it, weigh the options, decide, and learn from how it turned out. The climber went round that loop several times in one season, and the record grew each time.

No code? A season plan has no code for step 6 to check. Every other step works the same: the questions, the options, the decisions and their reasons, what changed, and what was learned.

Why it works this way Set it up

The climber is one design. A team with many gives each its own and links them with a hub.