LiveNode · cascade-architect
2026-05-17 · 16:13:Z
IBM Bob · Hackathon 2026Cascade
/01 · reference scenarios

Three changes, three verdicts.

Each scenario is wired to the live agent. Open one to inspect the baked-in analysis — or run the same diff through the live cascade agent and watch it stream a second opinion.

demo 01

Authentication Signature Change

CRITICAL

Critical authentication bypass due to return type change in verifyToken function

// changed symbols
verifyTokenfunctionservices/auth/index.ts
▾ baked report▸ run live
// top impacts (4)
  • CRITICAL
    services/billing/checkout.ts:13
    Boolean check on object always passes - authentication bypassed
  • CRITICAL
    services/billing/checkout.ts:30
    Boolean check on object always passes - payment validation bypassed
  • CRITICAL
    services/billing/invoice.ts:11
    Boolean check on object always passes - invoice authorization bypassed
  • HIGH
    services/auth/index.ts:23
    Boolean check on object always passes - token refresh always succeeds
files
3
critical
3
gaps
4
demo 02

Environment Variable Rename

CRITICAL

Email service failure due to SMTP_SERVER → MAIL_HOST environment variable rename

// changed symbols
SMTP_HOSTconstantservices/notifications/config.ts
▾ baked report▸ run live
// top impacts (6)
  • CRITICAL
    services/notifications/config.ts:5
    Reads undefined environment variable - email service fails
  • CRITICAL
    .env:6
    Old variable name still defined - needs update to MAIL_HOST
  • CRITICAL
    docker-compose.yml:29
    Docker sets old variable name - container deployment fails
  • MEDIUM
    README.md:0
    Documentation may reference old variable name
  • +2 more
files
6
critical
5
gaps
3
demo 03

Tax Calculation Rounding

MEDIUM

Medium risk change in tax calculation rounding behavior

// changed symbols
calculateTaxfunctionservices/billing/utils.ts
▾ baked report▸ run live
// top impacts (2)
  • MEDIUM
    services/billing/checkout.ts:18
    Rounding behavior changed - test assertions may need updates
  • MEDIUM
    services/billing/invoice.ts:16
    Invoice totals now rounded - test assertions may need updates
files
2
critical
0
gaps
4
// why these three
  • 01 — Cross-service signature. Proves Cascade traces past package boundaries that snippet AIs never reach.
  • 02 — Runtime config drift. Proves the agent reads .env, docker-compose, and K8s — not just .ts files.
  • 03 — Safe refactor. Proves restraint: no false-positive CRITICALs for behaviour-equal changes.