🤓 Latest Submissions
JourneyOps
Modern software teams can have a completely green test suite while real users are still experiencing broken journeys. JourneyOps addresses this gap by connecting user-journey telemetry, application state, source code, and IBM Bob into a single engineering workflow. For this hackathon, we created a controlled synthetic ticketing lab with a realistic failure scenario. A visitor arrives from an event-sharing link with one simple intent: buy a ticket. During checkout, the visitor needs to create an account. The existing automated suite reports 45 passing tests and 165 assertions, yet the actual user journey fails: the new account is created as a producer, the buyer is redirected into organizer onboarding, checkout never resumes, and the purchase is abandoned. JourneyOps captures the sequence of events that actually occurred and turns that evidence into engineering context. Instead of giving IBM Bob a predefined bug location, we asked it to independently determine whether the purchasing experience was operating normally. Bob reconstructed the failing journey from telemetry, correlated it with application state and source code, identified the causal chain, compared remediation strategies, implemented a safer fix, added regression coverage, and independently verified the corrected state. After remediation, the same journey creates the correct buyer account, resumes checkout, creates the order, completes the simulated payment, and finishes successfully. Bob's verified engineering state reached 48 passing tests and 191 assertions with no regressions. The key idea behind JourneyOps is simple: a green test suite can create a false sense of confidence. Traditional tests tell developers whether expected code paths pass. JourneyOps adds another layer by asking whether the user journey itself actually worked. The workflow is: User Journey → Journey Telemetry + Application State + Source Code → IBM Bob → Discover → Plan → Fix → Verify → Verified User Journey. The project uses only synthetic data in the hackathon environment. The ticketing application is a controlled lab designed to demonstrate the workflow, while JourneyOps is the developer-oriented concept being evaluated. The result is a workflow that helps engineering teams move from an unexplained user failure to a verified fix with traceable evidence at every step.
27 Sep 2026
