← Back to live playground

CollisionLab

IBM Bob-assisted semantic conflict analysis
Interactive evidence viewer · Saved scenario results. The website displays recorded test runs; run the commands below to reproduce them or analyze branches in IBM Bob.
Catch the bug Git can’t see

The merge is clean.
The behavior isn’t.

CollisionLab checks what happens when individually valid branch changes meet. It helps developers find incompatible assumptions before they become production bugs.

Explore the 3 scenarios ↓Reproduce a test
This public page shows saved evidence. IBM Bob performs fresh analysis when you run the command in a local project.
What a semantic collision looks like
Branch Atests pass
+
Branch Btests pass
Clean Git merge  ·  Combined behavior fails
The workflow

From branch assumptions to proof

CollisionLab pairs Bob’s code reasoning with tests that check the behavior of the combined branches.

01

Compare the branches

Bob reads each branch and the requirements, then looks for assumptions that cross feature boundaries.

02

Test the combination

A clean merge is checked with a generated integration test. The test asks whether both behaviors work together.

03

Review the evidence

See which controls passed, what failed after the merge, and the smallest suggested fix.

Three real behavior collisions

Red indicates the expected failing integration check—not an error in the evidence viewer. Branch-level checks and the merge are shown separately.

Loading bundled evidence…

IBM Bob analysis records

These are saved analyses from the demo. This page does not call IBM Bob or analyze new branches by itself.

Loading analysis records…
Try it yourself

Run the demo on your computer

The hosted page is read-only. Use the repository to replay all three prepared scenarios or have Bob analyze branches.

Replay the prepared demo

Runs the known sample scenarios and checks their expected outcomes. You need Git and Node.js 20 or later.

  1. Clone the repository and open its folder in a terminal.
  2. Switch to the demo branch.
  3. Run the demo command.
git clone https://github.com/TonyWu1/Collision-lab-demo-.git
cd Collision-lab-demo-
git switch feature/public-demo
npm run demo

The prepared demo intentionally includes integration-test failures that demonstrate the collisions.

Analyze branches with IBM Bob

For Bob to inspect branches and generate fresh verification evidence, open the cloned repository in IBM Bob and switch to Agent mode.

  1. Make sure the two branches are available in the local clone.
  2. Enter this command in Bob’s chat.
  3. Review Bob’s hypothesis, generated test, and test results.
/collision feature/email-auth feature/profile-cache-v2 demo/combined-auth-cache:requirements/authentication-v2.md

To inspect another pair, replace the two branch names. The command analyzes locally; the public website only displays saved reports.