{
  "id": 9590309,
  "title": "INKSHIFT: cross out a table, keep the booking",
  "url": "https://urgent.news/2026/09/24/inkshift-cross-out-a-table-keep-the-booking",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-24T17:03:36.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/himanshu_748/inkshift-cross-out-a-table-keep-the-booking-344i"
  },
  "original_language": "en",
  "account": "The story revolves around a tool called INKSHIFT, which helps manage changes to plans for events like games nights or club meetups. When a plan changes, such as moving a game from one table to another, INKSHIFT keeps track of bookings and ensures continuity.\n\nTo demonstrate INKSHIFT, the author created a scenario where a game was booked at Table B and then needed to be moved to Table C. Moving the game to the new table is straightforward, but the challenge arises when another person is already attached to that plan, and their booking needs to be preserved. INKSHIFT handles this by allowing the organiser to review the proposed move, check if there are enough seats and availability for the new table, and then approve the change. After approval, the guest's existing booking is automatically transferred to the new table, and they don't need to sign up again.\n\nINKSHIFT works by separating spaces, sessions, and registrations into separate records with stable IDs. When a booking moves from one location to another, only the space reference changes, while the session ID remains the same. This ensures that the registrations still belong to the correct session. The app also includes a live content inspector that shows the updated schedule after the move, demonstrating that the booking is correctly attached to the new location.\n\nTo prevent issues when someone joins an event while the organiser is reviewing a move, INKSHIFT treats the edited plan as a saved proposal. Sanity Workflows tracks the review through Reading, Review, and either Applied or Discarded stages, ensuring that the organiser can return to the review if needed. The system checks the event and proposal revisions and recomputes the constraints before applying the approved change. If the event has changed, the organiser must recheck the move.\n\nINKSHIFT is built using Next.js and React, Sanity Content Lake, App SDK, and Workflows. It utilizes AI-native tools like Codex for the initial build and upgrade, and Claude Code for further improvements. The app reads photos using Qwen3-VL through Hugging Face Inference Providers, and it includes verification records that cover booking preservation, handling concurrent changes, access recovery, and private-data checks.",
  "summary": "This is a submission for the Sanity Challenge, Path Two: Vibe-Code Something Strange . What I Built Someone has booked Ticket to Ride at Table B. Then Table B becomes unavailable. Moving the game to Table C sounds easy. But there is already a person attached to that plan, and their booking needs to survive the edit. I built INKSHIFT for this kind of change. It turns a plan for a games night,…",
  "key_points": [
    "INKSHIFT manages event plan changes, preserving bookings when moving sessions.",
    "Organizers can review proposed moves, check seat availability and approve changes.",
    "Bookings automatically transfer to new tables, maintaining continuity for attendees."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}