Urgent.News

What's breaking now, across thousands of outlets.

Tech

I built Salt Wharf, a callboard where the later posted sheet wins

This is a submission for the Sanity Challenge, Path Two: Vibe-Code Something Strange What I Built I built Salt Wharf as a stage-door callboard for a fictional Valletta theatre company. The public page is meant to feel like the sheet taped beside the stage door, not an admin dashboard. It answers one question for tonight: who is actually called. The story is 4 October 2026. Two posted call sheets…

In this submission for the Sanity Challenge, Path Two: Vibe-Code Something Strange, the author presents Salt Wharf, a fictional Valletta theatre company's callboard. The public page acts like a sheet taped beside a stage door, revealing who was called, rather than serving as an admin dashboard. The goal is to determine who was actually called that night.

Two call sheets are available for that specific night: an earlier one still lists Mara Camilleri as Rosa, while the later one supersedes it and lists Lina Borg due to Camilleri being unavailable. The public door displays Borg and provides the reason for her substitution. The earlier sheet remains in the system, marked as replaced.

Backstage displays the entire call stack. The author aimed to maintain historical accuracy without altering the public door's content. Both call sheets remain as separate documents. The later posted sheet includes a "supersedes" notation, linking it to the earlier one. The door prints the most recent posted sheet that is not superseded by any other sheet.

If a later sheet reverts to draft status, it ceases to hide the older document. The backstage desk displays the first failed predicate for each rejected candidate. In the example provided, Lina Borg clears Rosa's role as she is unavailable that night. The public door is live and accessible without login at https://saltwharf.vibefy.net/.

Backstage is accessed through a fake stage door printed for demonstration purposes. It does not secure Sanity, GitHub, or any genuine system. To run the application locally, one must clone the GitHub repository, navigate to the 'salt-wharf' directory, install dependencies, and execute the development server. No environment variables are necessary.

The npm run verify command ensures the application accurately reflects the 4 October story. The committed log is located in the docs/proof/verify.txt file. The full codebase is available on GitHub at https://github.com/mascarock/salt-wharf. Building the application took place in Cursor as a Next.js application designed around Sanity.

After completing the proof, the author had a Codex review it. The public-door screenshot, backstage stack, and verification output are included in the docs/proof directory. The most challenging aspect was implementing the standing-sheet rule, which required printing the newest document, rather than the earlier one, while maintaining its posted status.

The application operates using the committed seed, which does not necessitate a live Sanity write token. This token is absent from the repository. The stage-manager component, in fixture mode, stores a browser cookie to prevent unauthorized modifications from multiple visitors. The same application powers https://saltwharf.vibefy.net/.

The Sanity project details, including the Project ID and dataset information, are specified in the provided materials.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

My Health Check Watched the Wrong File

I wrote a rule for my own agents: Liveness is not usefulness. Artifact age beats PID. A job that is loaded, looks healthy to the supervisor, and is producing nothing is the failure worth catching.

  • Health check tool misidentified Telegram poller jobs as dead
  • Jobs were actually functioning correctly, not stopped
  • Tool relied on outdated file, misunderstanding job behavior

pfft...yet another finance tracker? think again :)

This is a submission for the Hacktoberfest Weekend Challenge: Build for a Friend Why I Built Living in India, we heavily utilise UPI for payments.

  • Designed for iPhone users in India to track spending without manual logging
  • Uses text messages to automatically read bank transactions, prioritizing privacy
  • Categorizes transactions via AI open-weight model on local Mac processing

Port 22 Explained: Check SSH Connectivity Without Guessing

When an SSH connection fails, “port 22 is open” can mean several different things. A service might be listening on the server but blocked by a firewall, or a TCP connection might succeed without the…

  • Port 22 is default TCP port for SSH protocol.
  • TCP connection test verifies server reachability.
  • Open port 22 exposes server to potential attacks.

More from Sunday 4 October →