Post-Match: Reyes-Montoya

POST-MATCH: REYES-MONTOYA Approximately fourteen hours after the bell. Hotel room. Alone. ———————————————— The body, first. The right elbow is the priority. Hyperextended at the joint capsule, not at the ligament — I felt the structural give-point during the application and tapped at the moment it became a choice between releasing the arm and breaking it. He held the position cleanly for the additional second the protocol permits between tap and release, which is the correct interval. There is no malice in it. He was being precise. The joint is swollen but the swelling is consistent with capsular strain rather than tear. Range of motion will be reduced for approximately eleven days. Pain at rest, a six. Pain at extension, a nine. Within tolerance. The left shoulder absorbed the impact when I came down off the second buckle in the third exchange. Within tolerance. The right knee — there was a moment during the corner sequence when I thought I had compromised the medial structure, but the joint is reporting a normal envelope this morning. False alarm. The body was loud during the match in ways it has not been before, and I was reading every signal as more significant than it turned out to be. This is a thing to note. The internal volume of the data does not always correspond to the actual structural significance. I have been sitting on the edge of the bed for thirty-eight minutes. The body has nothing more to say to me. I have heard it. ———————————————— The Quiet. A separate note, longer than usual. The Quiet did not ask for anything during the match. I have already documented this in the morning piece — He was first-column. The Quiet was uninterested. I expected the absence of appetite and the absence was, as I noted, a relief. What I did not anticipate was the Quiet's behavior after. I lost. I tapped clean. The match was decided cleanly in his favor. There was, by my own standards, no failure of the discipline, no failure of the Code, no failure of any element I had prepared for. The result was honest. The result was his to take and he took it. The Quiet did not protest. The Quiet did not surge. The Quiet did not appear, in any register I am familiar with reading, to register the loss as a problem. It registered the loss as data. I am writing this down because I have not, in any prior moment of my arrangement with it, experienced the Quiet processing information in the way it processed last night. There is a distinction between the Quiet being silent because it has nothing to say and the Quiet being silent because it is busy. Last night was the second. It is still busy. I can feel it filing. What it is filing, I do not yet know. I am going to wait. The Quiet has rules — I wrote them — and one of the rules is that I do not pull on the filing process when it is happening. I let it complete and then I read what it produced. This may take a week. It may take longer. I am noting it now because I want a record of the moment the data began to be filed differently from how it has been filed before, and because if the filing produces something I have not previously encountered, I would like to have the timestamp. ———————————————— The opponent. He fought the match I expected him to fight, with one exception. The exception was the moment, late in the sequence, when he could have transitioned from the position he had me in to a different position from which the answer would have been faster. He did not transition. He stayed with the joint. He stayed with the joint because the joint was the answer he had been building toward for the entire match, and because changing the answer in its final phase would have been a different kind of competition than the one he had been engaged in. I want to be precise about what this means. It means he was, in that moment, not optimizing for the result. He was completing the match he had decided to fight. He could have made me lose faster by changing tools. He did not change tools. He let the work he had done produce the result the work was going to produce. This is the marker of a particular kind of fighter. It is not common. It is the kind of fighter who is more interested in the integrity of the process than the efficiency of the outcome. I have met three of them across my life. He is the fourth. I observed this with attention. The Code does not require me to admire opponents, but it does not prohibit it, and there is, I think, no useful word other than admiration for what I felt when I noticed what he was doing and why. I will note it without elaboration. The note is the thing. He is the inaugural champion of this federation. He is the correct inaugural champion of this federation. The Code has registered him as first-column and will keep him there. I would prefer not to fight him again, not because I think I cannot, but because I think the next match would teach me less than I would want it to. ———————————————— The data the loss produced. I want to be specific about this because the Quiet is busy with it. For the duration of my work in this federation, I have operated under the assumption that the categorization — first column, second column — was complete. An opponent was either a subject of study or an earner. The Code permitted exactly two responses, and I had refined them across enough years that the choice between them, when an opponent arrived, was nearly instant. Last night produced a third category that I had not previously needed to define. There exists a class of opponent who is first-column, who is honest, who has earned his place — and who is better than I am in the specific dimensions on which the match was contested. Not in every dimension. Not in most dimensions. But in the dimension that determined the result. He was better than me at finding the right joint at the right time in the right corner. The Code has nothing to say about this. The Code was designed around the question of what I do to opponents. It was not designed around the question of what I do when opponents do things to me that the Code did not anticipate. I am going to extend the Code. I am not going to extend it today, because the Quiet is still filing, and I have learned that I do not write code while the filing is happening. But I am going to extend it. The extension will address the class of opponent who is first-column and superior in a specific dimension on a specific night. I do not yet know what the extension will say. I will know when I know. This is, I think, the most accurate way to describe what happened to me last night. Not that I lost. Not that I was beaten. The loss is incidental. What happened is that the system I built across many years discovered a case it had not yet seen, and the system is, even now, busy adapting to the new information. ———————————————— The discipline holds. I want this on the record because I anticipate, when the Quiet completes its filing, that I will want to verify that the discipline was not the thing that changed. The meal last night was correct, the meal tonight will be correct, the meal tomorrow will be correct. The body will be read at the same intervals it has always been read. The hour of silence in the morning, before any match, will be observed. None of these are negotiable. None of these are under review. What is under review is the Code's response to a kind of opponent it did not previously have a response to. The discipline is what permits the review. Without the discipline I would be answering the question with feeling rather than with thought, and the answer would be less useful. I am not feeling anything. I am noting this without alarm. The Quiet is busy. I am letting it work. ———————————————— A final note. I have not, in the time I have been at this work, lost a match before. I want to acknowledge that fact for the record, because the record will eventually be read by someone, possibly only me, and I would like that reader to know what last night was. It was the first time. It is going to be useful. I will see. — W.