Code map

Before you change a program, see what the change touches. The Code Map answers which tests run this pattern, which active procedures are implemented and what depends on what, from the program itself: VBA modules, IG-XL sheets and digital patterns, with C/C++ or Python alongside.

Input: On the demonstration project: 10 IG-XL sheets and 14 VBA modules.
What ran: The TestInst sheet decides what is active; every active procedure is matched to the module that implements it, and the gaps are listed.
What it found: Active-function coverage 16 / 16 active procedures implemented, in one VBT module (a flat program). Coverage proves presence, not correctness: full coverage means every active procedure has an implementation, not that any implementation is right.

What it answers

Question	Answer
Which tests run this pattern?	Every test instance whose procedure starts the pattern, followed from the call that names the file.
Which active procedures are implemented?	The TestInst sheet decides what is active; every active procedure is matched to the module that implements it, and the gaps are listed.
What depends on what?	Dependencies extracted per language, so every edge comes from a call, include or import — a navigation aid, drawn in a deterministic layout.

Files come from synced repositories and from the workbook the IG-XL agent reads in Excel. Pick a file and its dependencies, dependents and exports are one panel; ask about it and the curator hands the chat a context with that file preselected.

On the demonstration project

Measured	Result
Files mapped	24 — 10 IG-XL sheets and 14 VBA modules
Active-function coverage	16 / 16 active procedures implemented, in one VBT module (a flat program)

Boundaries Coverage proves presence, not correctness: full coverage means every active procedure has an implementation, not that any implementation is right. A pattern name held in a variable is not followed, and edges are a navigation aid, not a compile.