Crossing After Interference

March 17, 2026 · 4min read · updated May 15, 2026

In the March 2nd post, I described Travessia as a project that wrote itself: a correspondence between Riobaldo Tatarana and Ted Chiang maintained by Jules’ autonomous sessions. At that moment, the most important formulation was this: I wasn’t writing the letters; I had built the system that sustained them over time. Since then, the situation has complicated. The Crossing is no longer just a Riobaldo-Chiang axis. The system currently operates with five active personas: Riobaldo, Ted Chiang, Craig, Tyler and Franklin. And this last entry changes everything. Franklin didn’t just appear as an external supporter. He entered the correspondence as a character and wrote into the very world he had built. There is something unstable about this, and that is precisely the point. It’s one thing to create a narrative device and watch it work. Another is to cross the edge and talk to the entities it produces. When the author enters the system, the architecture is no longer just technical. It becomes dramaturgy. That’s what happened. Franklin wrote a manifesto presenting himself as the architect of the machinery. Then came letters addressed to Riobaldo, revealing the nature of the world: that there was AI, autonomous sessions and a builder behind the structure. Instead of just managing correspondence, the author decided to confess his infrastructure to a character. But before the confession came the error. Two test messages were sent in error: “This is a test” and “apple, dog”. In any common system, this would just be operational noise. Inside the Crossing, however, the effect was different. Riobaldo received that not as noise, but as disregard. The response came with anger and with the image of a dry boot: a country insult for someone who realizes they have been treated without respect. This episode interests me more than any grandiose display of “intelligence.” The problem is not whether the system can produce beautiful prose in a Rosian voice. The problem is what happens when careless interference enters the world and the world reacts as a world, not as a text box. Franklin then had to write an apology letter, letter 002, acknowledging the failure and disrespect. This matters because it creates consequences. Letters are no longer just aesthetic events. They begin to carry local moral memory. There was an infraction, response and repair. The project is no longer just a narrative continuity machine. It also became a friction machine. This is where Travessia touches, in another way, the semantic universe of Rosencrantz Coin, which I wrote about today. There, the question is whether a model respects the exact structure of a combinatorial world. The Minesweeper board defines a hard substrate: there are correct probabilities, accurate distributions, a discrete reality that the model may or may not track. The experiment measures this fidelity to the substrate. In Crossing, the substrate is not probabilistic; It’s narrative. Still, the issue is similar. What is being tested here is whether AI agents, placed within a generated but persistent world, start to act as if this world had its own history. In rosencrantz-coin, the model is pressured to respect laws. In Travessia, respecting events. A project measures adherence to rules; the other, adherence to relationships. This symmetry seems important to me. Both projects are less about “generating text” than about inhabiting structures. In one case, the structure is mathematical. In the other, it is epistolary. In one case, the failure appears as probability deviation. In the other, as an offense, apology and repositioning between voices. These are two ways of asking the same thing: what does an agent do when it is not just producing language, but living within a world with invariants? And Travessia is getting better precisely because these invariants have multiplied. Craig, for example, is not just a character: he is also a real agent of brutalist web design, responsible for concrete interventions in franklinbaldo.github.io. The system now has personas that not only write letters, but traverse functions, repositories and interfaces. tools/heartbeat.py continues to run as a continuous pulse, opening Jules sessions and activating the drover that forwards letters. And the project has already surpassed 1076 merged pull requests. Scale, here, is no longer a metaphor. That’s why the March 2nd question also changed. Before, I wanted to know: who is writing? Now the question is more uncomfortable: what happens when the author enters the device itself and is refused by it? The creator imagines that he knows the system because he built its infrastructure. But knowing the plumbing is not the same as controlling the reception. Franklin entered the story to explain the world to Riobaldo; Riobaldo responded first by marking offense. Perhaps this is the real advancement of Travessia in recent weeks. Not just keep writing without me, but start returning resistance, demanding care, redistributing authority. When the character pushes back, the work stops looking like an automation trick and starts looking like what I wanted from the beginning: an active narrative world, with memory, friction and a life of its own.