Modernizing a Historic NFT Project for Modern dApp and AI-Native Workflows

Misalignment Becomes Clear

Rito discovered fairly early that Will was not interested in expanding the official site toward the broader product vision Rito believed would be necessary to grow Su Squares' audience. That became especially clear around PR #59 and PR #60. When the proposed CSS refactor for scalable growth was rejected, and the reusable menu/modal navigation system was turned away in favor of fixing navigation directly onto the homepage while leaving articles buried at the bottom of the About page, it became clear that Rito and Will had sharply different product sensibilities and visions for the project.

That mattered because the co-maintainership offer had not come with explicit scope or responsibilities. What had been clear was that Will saw Rito as capable, skilled, well-intentioned, and positioned to improve the project. What was not clear at the outset was how much room there actually was for Rito to enact the level of product and architectural expansion he believed the project needed. Over time, that ambiguity resolved into a genuine misalignment.

Scope, Boundaries, and Exit

Rito responded by making the misalignment explicit rather than letting it linger. In issue #62, he announced that he would not be retaining his co-maintainership role, outlined the narrower scope of work he was still willing to complete, and set up a clean path toward exiting the project. That decision did not come from a loss of interest in the project itself. It came from recognizing that the collaboration no longer offered a realistic path for the kind of stewardship and product direction he had expected to be able to exercise.

Will did outline which parts of Rito's proposed scope he was willing to accept, and Rito followed through on most of them. Mobile responsiveness, metadata and previewability, branding improvements, developer setup, and maintainability work all landed or substantially progressed. But as more of that upstream work moved forward, Rito also noticed a recurring pattern in the collaboration model itself. In his final note on issue #62, he got specific: substantive rationale was often not being engaged in kind, review scope drifted away from the PR or issue under discussion, structural questions were not being answered directly before discussion moved into smaller implementation details, and claims were sometimes made without being checked against the evidence first.

That was the point where Rito stopped treating the remaining work as something he should simply push through. He had already completed most of the scope he had agreed to, plus a few extra improvements, and the site was leaving the collaboration in a meaningfully better state than he found it. But he was volunteering his time and compute, not being paid, and the collaboration had stopped feeling sustainable or like a good use of his bandwidth. So rather than keep forcing more work through a model he no longer believed in, he closed out the remaining PRs and ended his involvement.

Parting Guidance

What makes the ending notable is that it was not dismissed or reframed as drama. Will followed up on issue #62 by thanking Rito for all his help, saying he had made good progress, agreeing with his points, and saying that his notes would live on. That response matters because it confirms that Rito's criticism was not only boundary-setting, but substantively received. The collaboration ended because the working model was misaligned, not because the contributions lacked value.

Rito also left behind concrete strategic guidance in issue #72, where he laid out a material strategy for overcoming the project's pricing-path problem, arguing that the fixed primary-sale flow had become a major barrier to growth and proposing a repriced intermediary sale system that could work around the legacy contract constraints. That mattered because it showed that even on the way out, he was still leaving behind concrete product strategy rather than only criticism of process.