Why

Investigate the motivation behind code. Companion to how. how answers what the code does. why answers what forces led to its shape.

Historical context spreads across seven evidence categories. Enumerate available connectors at run time, query every available category in parallel, then synthesize with explicit confidence calibration. A null result is first-class evidence.

Contract

Inputs:

• A why-question about a chunk of code, pattern, feature, or named decision

Outputs:

• A confidence-separated, cited narrative with a coverage map