For forty years rswfire has built infrastructure that other people owned. The CMS he wrote as a teenager on a machine assembled from spare parts, released free and then quietly reused as the private frame under two decades of client work. The entertainment platform. The booking engines. The blockchain distribution system for a music company where he functioned as CTO without the title. Every one of them was housed in someone else's container, and every container eventually failed or evicted him — Google took the travel revenue, the ten-year client stopped paying, Guru swallowed fifteen years of reviews, YouTube held nine hundred videos until he took them back and deleted the account. What is different at the end of April 2026 is not that he built something. It is that for the first time the thing he built is addressed outward and held in his own name: a nine-stage model of institutional displacement, published under his own domain, written for people he will never meet who are standing where he stood.

What did not move is the sixth grader. When his father sold the family computer he wrote code on paper and ran it in his head; there was no machine, so the machine became internal. That is the same operation performed on the Wax Myrtle Trail on April 3 — no institution would hear the complaint, so the complaint became a structure. It is the operation that produced the RV when the house ended, the Forest Service post when the state park ended, Autonomy Realms when the platform holding two years of his life proved unable to hold it. Nothing about this is new in April. It is the oldest thing in the ledger, and it is the load-bearing part: the response to losing a container has never once been to look for another container.

The turn is not in April. It is in late March, at the gate, when a federal special agent and two state officers came onto restricted land to ask what he was posting. Before that he was assembling evidence about what had been done to him — a chronology, recordings, a narrative called The Story of Honeyman, all of it particular, all of it his. After it, he is describing a mechanism. That is a change in the direction of the person, not the direction of the travel: the case stopped being the subject and became the sample. The stage count moves between April 3 and April 5, ten narrowing to nine, which is what a model being fitted looks like rather than a grievance being recited.

What the anniversary week could not see about itself is that the conditions he names as making displacement operable — a person who lives on the land, who is dependent on the entity that houses him, who holds no structural protection — are not a description of volunteer programs. They are the description of his own housing arrangements at seventeen on the streets of Michigan, in his parents' trailer, in the Kentucky house his parents moved into, at Honeyman, and behind the federal gate where he stood while recording. He has occupied that structural position for most of his adult life and has, in April 2026, named it for the first time using a case that was not primarily about himself. The framework generalizes upward from OPRD; it also generalizes backward through the ledger, and nothing in these three weeks indicates he was reading it that way.

The other thing not visible from inside: the April 20 walkthrough is the third time he has built the tool everyone would eventually need before the need was general. The first two he gave away — open-sourced, then absorbed into freelance work as unpaid substrate. This is the first one with a domain he controls, tiers he set, and a private catacomb no one else can open. He narrates it as a demonstration of features. From outside it is the moment the pattern of giving the infrastructure away broke.

And what held constant, unhelpfully, is the money. Nothing in April touches it — no income, an uninsured Jeep on expired plates, a corridor he cannot legally leave. The commons map he demonstrates has only his own points plotted on it. He built the volunteer resources page, the press section, the subscription tiers, and the model itself for an audience that does not yet exist, on the same evidence he has always operated from: that the record is worth building before anyone arrives to read it. Between the trail and the transmission he logged a wagon, a lagoon, seals, a rainbow, and a lake hike, unannotated, weighted the same as the rest.

The binding constraint at Siltcoos in April is tenancy, and tenancy is not one thing but a chain: residence depends on the Forest Service volunteer position, the RV's location depends on the residence permission, and the RV's mobility depends on the Jeep. Three components in series, no redundancy at any link. rswfire enumerates the failure states himself on April 5 — stay, relocate early to the site he had planned for October, become homeless, lose the Jeep — which means the chain has been priced and the outcomes are known quantities rather than surprises. What makes the constraint binding rather than merely present is that the agency escalating against him is not the agency holding his permission. Cross-agency escalation, culminating in police dispatched past a locked federal gate, is an attempt to reach the one link he does not control. That is the mechanism, and he identifies it correctly: the jurisdictional crossing is the tell.

The observable control law is unusual in that it matches the declared one. Input: institutional pressure. Output: published structure, at short latency. Police arrive at the door; on April 3 he walks the Wax Myrtle Trail and decomposes two months of escalation into ten stages; on April 5 he records a direct address naming nine; the on-screen annotation points at a live URL dated April 6. Roughly seventy-two hours from contact to shipped artifact, with the artifact designed not for his own defense but for strangers under the same dependency conditions — a For Volunteers page, a press section, evidence pages back-linked to a central explanation. A system's controller is what it does at threshold crossings, and this one converts pressure directly into transferable architecture with essentially no dwell time. His statement that no material outcome constitutes displacement from himself is a declared setpoint; the behavior over these twenty-two days implements it without deviation, which is worth registering because declared and implemented controllers usually disagree.

The dominant loop is reinforcing and belongs to the institution, not to him. Documentation raises the cost of the record; the rising cost drives escalation; escalation generates new documentable events; the record grows. He states the loop's mechanism explicitly — the cleanliness of the real-time record is what forced escalation to police presence. Each turn consumes institutional margin that cannot be recovered: a park supervisor backed up the chain to the governor exhausts the vertical ladder, and crossing into federal jurisdiction exhausts the lateral one. The loop has no obvious internal stop. It terminates either when the institution runs out of rungs, which it is close to doing, or when the tenancy chain breaks and the input to his side of the loop changes character. He is not the one with a depleting reserve in this exchange.

Intake is metered in two tiers, and the metering is visible in April's composition. Nine signals across twenty-two days is roughly 0.4 per day against a long-run rate near 1.2 — about 900 signals in two years, some 400 in Kentucky and 400-plus on the Oregon Coast. Five of the nine — Wagon, Lagoon, Seals on the Beach, Rainbow, Siltcoos Lake Hike — are captured and logged without annotation or analysis, and one of them falls on April 5, the same day as the highest-load transmission. This is not gap or absence; it is load-shedding by design. Capture costs almost nothing and continues unconditionally; analysis costs money and is rationed. Cost is named as the governing variable elsewhere in the same month — the full catalog has not been reprocessed under current system versions because reprocessing is expensive. The one named inbound flow, a $5–$50 sliding-scale patron tier covering 140 signals, is not sized to relieve that. The appreciating reserve here is the archive, and it is non-monetary.

The single point of failure is the operator. Both builds in these three weeks — the oprdvolunteerabuse.org resources layer and the Autonomy Realms platform demonstrated live on April 20 — run on one person, one toolchain, one metered AI processing layer, and one set of hosting and domain obligations, with no delegation path and no succession. The two systems are functionally independent but operationally fused at him. The claim doing the most structural work in April is that the record and the infrastructure holding it make displacement from self impossible regardless of housing or vehicle; that claim is sound on its own terms and it relocates the vulnerability rather than removing it. Sanctum tiers and the catacomb are real mitigations, but against distribution capture — the YouTube flattening problem — not against operator loss. Nothing observed stands between the archive and the archivist.

What the system optimizes for is legible from allocation under scarcity. With tenancy threatened, homelessness enumerated as a live outcome, and reprocessing deferred for cost, resources still went to two things: making the displacement mechanism usable by volunteers he has never met, and demonstrating the platform publicly with an invitation for feedback. Neither improves his material position. Neither is a legal defense. The objective function is retrievability — maximizing the portion of the record that survives, stays navigable, and is usable by someone other than its author — with material comfort held as a free variable. The seals, the rainbow, the lake hike are the same optimization running at zero marginal cost: the ground gets logged whether or not there is budget to think about it.