The Museum of Almost: Redefining Digital Narrative through Speculative Design and Technical Rigor

In the evolving landscape of digital art and web development, the boundary between functional software and narrative experience is increasingly blurred. A striking example of this intersection has emerged in the form of "The Museum of Almost," an interactive digital exhibition developed for the Sanity Challenge. Specifically crafted for the "Path Two: Vibe-Code Something Strange" category, the project invites visitors to navigate a world of speculative design, where everyday objects are reimagined through the lens of poetic fiction and complex branching logic.

The Museum of Almost is not merely a collection of stories but a technical study in how structured content can drive immersive, choice-based experiences. At its core, the exhibition presents six fictional inventions, each starting with a familiar, mundane object that has been transformed by a surreal or philosophical twist. From an umbrella that preserves the acoustic memory of a rainstorm to a clock that deliberately leaves time uncounted, the project challenges the user to reconsider their relationship with the physical world through a series of consequential decisions.

A Curated Journey Through Speculative Inventions

The experience begins with a fundamental question: "Who should be allowed to borrow your rain?" This inquiry serves as the gateway to the first exhibit, The Rain Library. Here, the developer introduces an umbrella that does not just shield the user from the elements but replays the specific sounds of a past walk. The narrative then branches based on user agency. A visitor might choose to "give their rain to the neighborhood," a decision that leads them toward a story path culminating at The Listening Bench, an invention designed to facilitate shared silence. Alternatively, keeping the afternoon for oneself leads to the discovery of The Borrowed Minute, a clock-based exhibit exploring the value of unrecorded time.

These stories are not generated by artificial intelligence at runtime; rather, they are authored branches that ensure a cohesive and intentional narrative arc. Each invention is accompanied by an "imagined prototype anecdote," providing a layer of historical flavor to the fictional objects. To visualize these concepts, the developer opted for CSS object studies rather than traditional image files. This choice highlights a commitment to technical craftsmanship, using code to render the visual essence of the exhibits directly within the browser’s styling engine.

The navigation of the museum is facilitated by a "possibility map." This feature allows visitors to see the connective tissue between the six exhibits, visualizing how a choice in one room might echo or lead to another. While the experience is designed for exploration, it maintains a structured integrity where exhibit links and initial map choices can be shared via URL, though subsequent choices within a specific visit remain temporary to preserve the ephemeral nature of the "almost."

The Technical Framework and Curator Workflow

Behind the minimalist aesthetic of The Museum of Almost lies a sophisticated technical stack. Built using the Next.js framework and integrated with Sanity, the project serves as a demonstration of high-level content management and deployment strategies. The developer has provided a "local curator sandbox" for those interested in the underlying mechanics, requiring Node.js 24 and pnpm 11.19.0 for local replication.

The curator workflow is perhaps the most technically distinct aspect of the project. Unlike standard content management systems where an "edit and save" cycle is the norm, the Museum of Almost implements a rigorous revision-based process. In the curator room, a user can edit an exhibit’s description, but the change does not immediately go "on the wall." Instead, the workflow necessitates a "Review changes" phase, followed by a formal request for review, an approval of the specific revision, and finally, a publication action that moves the content across the "draft boundary."

This sandbox environment stores changes in a local JSON file to demonstrate the workflow without requiring a live Sanity connection, though the hosted version of the museum utilizes Sanity’s full suite of tools. This distinction is vital for understanding the project’s goal: to treat the administrative schema as an integral part of the artistic experience. The act of "approving" a story is as much a part of the "Museum of Almost" as the story itself.

Development Process and the Role of Agent-Led Implementation

The creation of the Museum of Almost was a collaborative effort between the developer and a suite of digital agents. According to the project’s documentation, Codex desktop was responsible for producing the bulk of the implementation, including the exhibition copy, the CSS-based illustrations, and the automated tests. Other agents were utilized to review the code and verify the tests, while browser inspections were conducted to ensure the running application met the desired specifications.

This build process was guided by a precise constraint: the curator must be able to approve an exact revision and publish only that unchanged revision. This requirement turned the content schema into a narrative device. The developer noted that the first implementation faced significant hurdles. For instance, an early version of the possibility map would open an object but lose the user’s selected branch. This led to a refactoring of the state management to ensure that a choice and its consequence remained tethered together during navigation.

Further technical challenges arose during the integration of Sanity. A generated mapper initially caused a collision by overwriting Sanity’s document types with embedded content types, a bug that was caught by the suite of 127 automated tests. Additionally, the use of namespaced document IDs required authenticated server reads despite the public nature of the dataset, necessitating a reconfiguration of the adapter’s access settings.

By September 26, a major revision was deployed to make the invitation to the visitor more explicit and to repair critical browser behaviors, such as URL restoration, keyboard focus, and the functionality of the "Back" and "Forward" buttons. The final build passed all type-checking and production tests, ensuring a stable environment for both desktop and mobile users.

Sanity Integration and Workflow Logic

The project’s reliance on Sanity goes beyond simple data storage. Sanity holds the entire collection and manages the lifecycle of the editing process. Branch destinations within the stories utilize native Sanity references, creating a robust web of interconnected content. The workspace is configured to store not just the exhibits themselves, but also drafts, reviews, approvals, snapshots, and a full audit trail of events.

The logic governing the "Museum" is designed to prevent content errors. Any edit made to a document automatically invalidates its previous approval status. The publication process is similarly guarded; it rejects stale revisions, missing destinations, or any logical cycles that might break the branching narrative. These checks occur within a revision-guarded Sanity transaction, ensuring that visitors continue to see the previously published version while a new edit is under review.

It is important to note that this is a custom application workflow. While the app simulates roles like "curator" and "reviewer," these are not separately authenticated individuals within the Sanity ecosystem but rather simulated roles within the app’s logic. The project deliberately avoids using Sanity’s managed Workflows product or the App SDK, opting instead for a bespoke implementation that matches the unique requirements of the "Vibe-Code" challenge.

Verification and Final Deployment

The integrity of the Museum of Almost was verified through a series of rigorous checks in late September. On September 21, the developer conducted eight workflow checks through a local server, exercising real-time Sanity reads and writes. These tests confirmed the system’s ability to reject stale requests and handle approval invalidations correctly. A total of fourteen successful transitions were recorded, restoring the original fictional content while maintaining a complete audit log.

A final round of checks was performed on September 26, focusing on the Netlify deployment. These checks confirmed that all six Sanity-backed exhibits were functioning as intended. The "Rain Library" correctly branched to the "Listening Bench" upon the selection of the neighborhood-sharing option, and the security protocols were validated when an empty curator key was rejected by the system.

The project stands as a completed study in speculative design and structured content. By documenting every failure and implementation decision in a curated build log, the developer has provided a roadmap for how complex, choice-driven narratives can be managed with the same precision as enterprise software. The Museum of Almost remains a quiet, interactive space on the web, inviting visitors to explore the "almosts" of invention while showcasing the "how" of modern digital curation.