n.V4-5.01| NOT SCHOOL
01| Every training method starts with an assumption about the student. Ours starts with an observation instead: most of the people we are about to train have already been through twelve years of education and came out the other side without the capabilities we need. That is the fact the method has to answer to.
02| The easy read is that they failed school. The more useful read is that school and these students failed each other, and that the failure was structural. School measured a narrow band of ability, on a schedule set elsewhere, with the results made public. For a student carrying the load described in V4-4.00, that combination is close to the worst possible design.
03| So the method begins by subtracting. No traditional classes. No exams. No grades. No cohort moving through a syllabus at one speed. This is not pedagogical fashion. Each of those things is removed because we can name the specific damage it does here.
04| The class fails because it puts the slowest and the fastest person in one room on one clock, and then requires the slowest to be visibly slow in front of the fastest. In a population where the biggest fear is being called dumb, that is not a scheduling inefficiency. It is the mechanism that produces the opt-out reflex.
05| The exam fails because it measures retention under artificial conditions and calls it capability. It also does something worse: it produces a number attached to a person's name. Once that number exists, it is a verdict, and the student who already suspects the verdict will avoid the test that confirms it.
06| The grade fails because it ranks people against each other on a single dimension. We do rank — the league tables in V4-4.05 are public and competitive — but we rank teams on delivered work, not persons on measured intelligence. The distinction is the whole design, and we come back to it in V4-5.03.
07| What replaces all of it is one principle: you learn the work by doing the work. Not a simulation of the work followed by the work. The work.
08| There is a fourth subtraction, and it is the one people find strangest. A Maveriq has the right to stop. Not to quit — to opt out for a period, without penalty, without a conversation in which she explains herself, and with the door open on the way back. Her project responsibilities transfer to the team; her place in the system does not disappear.
09| We built that in for a plain reason. Life in the barrio interrupts. A job changes shift, a parent gets sick, a household comes apart. The traditional response is an attendance policy, which converts an unavoidable event into a disciplinary one and loses the person permanently over something neither side controlled. We would rather lose four months of a good Maveriq than lose the Maveriq.
10| The cost of that clause is real and we should say it: it makes planning harder, it makes team composition unstable, and it means the Factory pipeline has to absorb absence as a normal condition rather than an exception. We accept that cost because the alternative filters out exactly the people the system exists for.
11| None of this is a lowering of the standard. Nothing here says the work is easier, the project bar is lower, or the impact buyer is more forgiving. What is removed is the ceremony around the learning, not the difficulty of it. The difficulty moves into the work, where it belongs, and where being wrong costs a project outcome rather than a piece of a person's self-image.
