LiveNode · cascade-architect
2026-05-17 · 16:13:Z
IBM Bob · Hackathon 2026Cascade
/00 · cascade — blast radius observatory

Predict the blast radius
before the merge.

Most AI coding tools see snippets. Cascade reads the entire repository, traces every cross-service call, follows env-vars into Docker, K8s, CI — and tells you exactly which lines will burn when your diff merges. Live analysis runs on **IBM Bob Shell** (non-interactive, full CASCADE-ARCHITECT prompt on the server).

▸ run live analysis▾ inspect demos
demos analyzed
3
impacts detected
12
critical
8
files traced
11
/01

What snippet AIs miss

01·

Cross-service breaks

A signature change in `services/auth` silently rewires four callers in `services/billing`. The compiler shrugs. Cascade catches it.

02·

Silent runtime failures

`SMTP_SERVER` → `MAIL_HOST` in code, but .env / docker-compose / K8s manifest disagree. No type checker sees this. Cascade does.

03·

No false positives

Refactor `calculateTax` with identical contract? Cascade flags it MEDIUM, not CRITICAL. Trust depends on restraint.

/02

Reference scenarios

01
Authentication Signature Change
Critical authentication bypass due to return type change in verifyToken function
impacts
4
files
3
CRITICAL
02
Environment Variable Rename
Email service failure due to SMTP_SERVER → MAIL_HOST environment variable rename
impacts
6
files
6
CRITICAL
03
Tax Calculation Rounding
Medium risk change in tax calculation rounding behavior
impacts
2
files
2
MEDIUM
/03

Pipeline

  1. 01
    parse
    unified diff → changed-symbol candidates
  2. 02
    context
    load cross-service source files
  3. 03
    analyze
    invoke IBM Bob Shell with cascade-architect
  4. 04
    classify
    CRITICAL · HIGH · MEDIUM · LOW
  5. 05
    emit
    JSON · Mermaid · Jest tests · PR comment
/04 · try it

Watch the agent think — live.

Run a preset and watch Bob Shell return the reasoning trace and strict JSON impact report. Engine · IBM Bob Shell.

▸ open observatory