Idea

Lenses / Reading and changing programs

See how a program fits together.

A function can look reasonable on its own while the whole program repeats a policy or reads data through the wrong key. Is this stock calculation defined once, or copied into cart, checkout, and support? Does each handler read notes with the caller’s own user ID? Which definitions are shared? Usually you find out by reading every function. The examples below draw these relationships from the compiled program, before and after each fix.

01 / Organization

Replace three copies of a stock rule with one definition.

Watch the refactor step by step → Follow scripted actions in the real editor, then take control.

Cart, checkout, and support need the same stock-allocation rule.

Loading recorded program evidence…

Code & run Experiment with the stock rule

The useful change is visible reuse: the same rule has one definition. A bounded execution comparison checks both versions; it is not a proof of equivalence.

02 / Correctness

Fix a handler that reads the wrong user’s notes.

Each user’s notes are stored under their own user ID. One handler used the wrong key.

Loading recorded program evidence…

Code & run Run and repair the Notes handler

The dependency map alone does not expose this bug; the access lens does. A green access result covers owner keys, not everything else.

03 / Explore a larger program

Find shared building blocks without opening every function.

A full dependency map gets hard to scan as a service grows, so the browser also groups definitions by package and type. Open ProjectHub below, choose Rebuild diagram, and search for respond to see everything that uses the response helper.

Code & run Compile, browse, and edit the ProjectHub service

A shared type does not prove shared behavior or a permission policy.

Generate diagrams for your own program.

Ask your agent which view answers your question, then have it draw your program before and after a change. It knows what each view can and cannot tell you. Explore the Forum’s whole-program map →

The figures on this page come from saved analysis results that the site build regenerates from their linked source files.

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

Where this fits