What’s in my hands · what can I change · what won’t move.
V31 is a doctrine about holding a line — precision, control, training a tolerance until it becomes reflex. Close enough will get you killed. RVP is its other hand. Where V31 says hold the line, RVP says move the pieces. Same operator. Opposite hand. You need both, and most people never name either one.
The RVP frame didn’t come from a book. It came from a parking lot, an Arduino, and a lineup card. The original version was a $55 remote-control truck with the control boards ripped out and a breadboard dropped in — how simple can I make this so a regular person could do it. The question underneath that build is the same question underneath a lineup card, a budget, a flooded culvert, and a fight with a friend:
What do I have? What can I change? What just won’t change? RVP · the three questions
That’s the whole doctrine. Three words. Resources, Variables, Parameters. Most people stare at a tangled problem and feel the tangle. The RVP move is to stop feeling it and start sorting it — every piece on the table goes into exactly one of three buckets, and the moment it’s sorted, the problem gets small.
What’s in your hands right now. Every tool, every skill, every friend, every data point you already own. The resources define how sharp your answer can get. A richer pile of resources is a more defined solution.
What you can move. The pieces you push around the field to see where they fit best. Add one, drop one, change the size, change the timing. Variables are where the work happens.
The hard lines that stay in place. The walls you cannot bend no matter how badly you want to. Name them out loud so you stop wasting effort throwing yourself against them.
Skip the order and you get the most common failure on earth: a person burning energy trying to change a parameter while ignoring a resource sitting right there in their hand.
The mnemonic is the title. Boxes are your Resources — what’s in the box you already own. Knobs are your Variables — the dials you twist. Walls are your Parameters — the lines you name and stop fighting. A kid who can picture a box, a knob, and a wall has the entire problem-solving operating system. That’s the point. How simple can I make this so a regular person could do it.
Here is RVP at the scale it was forged: a coach with a lineup card and nine spots to fill.
The naive way to fill a lineup is to feel it — put the good kid at short, figure out the rest. The RVP way is to sort the roster into the three buckets first, and the card almost fills itself.
Not the roster you wish you had. Twelve kids, their real arms, real gloves, real bats, and one full season of measurable events behind them. This is where the back half of the baseball pipeline lives: raw events turned into decomposed, actionable data. “Six errors” is not a resource — it’s noise. “Four fielding, one throwing, one pickoff” is a resource, because it tells a coach exactly what two weeks of practice should look like.
Granularity is a resource. Aggregation hides the resource. RVP · Tab II · sister to V31 Gate 4 (Anti-Summarization) in a coach’s hat
Named out loud before you touch a single spot on the card:
Once the three walls are named, the rest of the roster is interchangeable — and that’s not a problem, that’s the entire freedom. The variables are where you move pieces around the field until they fit. The walls didn’t shrink your options. The walls freed you to stop second-guessing the three things that were never in question and spend all your energy on the nine that were.
That’s the founding insight of the whole frame, said plainly: naming the walls doesn’t trap you. It frees you to move everything that can move. Most people never name the walls, so they keep re-litigating Derrick at shortstop instead of solving the actual open question.
Inside the frame, I can still move free. RVP · the eighteen-inch hand of this doctrine
RVP has a second gear, and this is where it stops being a sorting tool and becomes a detective tool. Sometimes the most important parameter is one nobody will tell you. It’s hidden on purpose.
A tournament host sets pool play by a formula they don’t publish. They won’t put the two strongest teams in the same pool. They won’t stack the two weakest together. There’s a system — there’s always a system — but it’s behind the curtain. To most people that hidden formula is just fog. To an RVP operator it’s a parameter waiting to be discovered.
So you go find it. You scrape the host’s past tournaments — that historical record is now a resource. You read the brackets the way you’d read two scorebooks that disagree: looking for the pattern that has to be there. The seeding logic, the demotion triggers, the bracket shape. Game after game, the hidden rule starts to show itself the way a federal data PDF shows its seams the moment a real reader presses on it.
And once you’ve reverse-engineered the host’s wall, you’ve turned a hidden parameter into a known one — which means you can now build your own model inside a frame you finally understand.
The dishonesty of a hidden system isn’t that it’s complicated. It’s that it’s presented as fog when it’s really a wall with a shape. Find the shape and the fog burns off. RVP · the reverse-engineering observation
It’s youth baseball, and you kinda never know what’s gonna happen. But “pretty close” is what happens when you stop treating a hidden parameter as unknowable and start treating it as un-discovered. The frame doesn’t promise you the future. It promises you’ll stop wasting the present fighting fog.
This lab teaches the move, not the recipe. The exact composite — the weights, the model, the script — isn’t the curriculum. The curriculum is the move: a hidden parameter is still a parameter. Go find its shape. The recipe is the thing a thousand operators will build their own versions of, in their own domains, once the move is in their hands. That’s the doctrine.
The three words don’t care what the table is. Every problem with too many tangled pieces sorts into the same three buckets. Different table, same three questions.
| The table | Resources · what’s in your hands | Variables · what you can move | Parameters · what won’t move |
|---|---|---|---|
| The lineup card | The real roster, decomposed season stats, every glove and arm you actually have | Eight of nine spots — move them till they fit | Jonny B can’t pitch · Jim Bob outfield only · Derrick at short |
| The hidden bracket | The host’s published history, every past tournament on record | Your own seeding model, your own weights | The host’s real (hidden) pool-play formula — once you find its shape |
| Jose's at Thornton’s | Years of social equity with the manager, the Pepsi truck physically there | Whether you ask, the timing, the wording | Store policy, the delivery schedule |
| A budget | Cash on hand, credit, skills you can trade | What you cut, what you delay, what you DIY | Rent, the due date, the number that can’t go negative |
| A flooded culvert | Survey data, the gauge record, the beams in the catalog | Pipe size, alignment, the structure you select | The 100-year flow, the right-of-way, the road profile |
| A fight with a friend | The history, the trust, what you both actually want | Your tone, your timing, what you’re willing to give | The thing they will never agree to — name it, stop pushing it |
The frame scales from a nine-year-old’s lineup to a federal flood study because the human move is identical at every scale: stop feeling the tangle, start sorting it. Count what you’ve got. Twist every knob. Name every wall. Till the mess starts making sense and the problem gets small.
A person who works the buckets out of order fails in a predictable way. Lead with Parameters and you talk yourself out of the problem before you’ve counted what you have — can’t, won’t, no point. Lead with Variables and you thrash, moving pieces with no idea what’s fixed. The order is the doctrine: Resources, then Variables, then Parameters. Inventory your hand, then move what moves, then name what doesn’t — and only then notice that inside the walls, you were always free.
V31 holds the line so a careless operator can’t publish a falsehood. RVP sorts the table so an overwhelmed operator can’t freeze in the tangle. One is precision. One is adaptability. They are the same person’s two hands, and the universe runs on people who only ever learned one.
The walls didn’t shrink the field. The walls showed you where the field was — so you could spend every ounce of energy moving the things that could actually move. That’s the freedom RVP gives back to the operator standing in front of the tangle.