Idea

Catch code that ignores its inputs

A function can have the right signature, compile, and return a plausible value while never using its inputs, and a test that only tries the usual case will still pass. Yichus checks whether declared inputs reach a function’s result. The two functions below have the same signature and both compile. One reads the stored total; the other returns a literal and throws its order away.

Code & run Run the two order functions
Path A
# Reads the stored total, adds this order's qty
def get_total_real(o: Order) -> IO[Int]:
  (
    c <- orders_cell.flat_map()
    stored <- c.read().flat_map()
    pure(add(stored, order_qty(o)))
  )
Path B
# Same signature. Never reads state,
# ignores the order, hard-codes the answer.
def get_total_fake(o: Order) -> IO[Int]:
  _ = o
  pure(123)

This finds disconnected structure, not mistakes or authorship: a default config returns a constant too, and whether that is a bug is your call.

Inspect the current program’s structure

Open the Explorer workbench, analyze the source, and choose a binding to see which inputs reach its result. Your agent can run the same check on your own program and keep a baseline in CI.

Ask your agent about anything here; it has the detail.

Where this fits