kb_lookup
Read all notes anchored to an exact file path before editing it. Surfaces cross-file flows, lessons, and absences with freshness stamps, so you can see what might break.
Instructions
Read everything the NOTEBOOK knows at ONE exact address — the file you are about to edit. Address-keyed, not concept-keyed: unlike kb_search (fuzzy, ranked), this filters notes by exact anchor path, so it is exhaustive at that path. Returns the file note's facets, every cross-file flow that passes THROUGH this file, and lessons/absences anchored here — each with a live freshness stamp against the current code.
Reach for this the moment you have DECIDED on a file and are about to modify it: it surfaces the flow you might break, the absence you are about to violate, the rationale for the code's shape. A clean result ("nothing known here") is itself a positive signal — proceed. Anything marked [evidence changed: ] drifted since it was verified; re-verify before relying on it, and correct the note with kb_write if it proved wrong. Pass an optional symbol to narrow to one top-level symbol at that path.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Exact repo-relative path of the file (e.g. "src/auth/service.ts"). | |
| symbol | No | Optional top-level symbol name to narrow the lookup to notes anchored at that symbol. |