bearing-imaginglisted

# GitNexus Imaging (graph-first thinking) <!-- BEGIN GENERATED: graph-uncertainty — bearing regenerates this block; edits here are replaced on update --> ## The graph can be wrong A zero is not absence; a near-0.5 `r.confidence` edge is a lead, not proof (~92% of `USES`); a count can be a floor — `impact` says which in `epistemic`. Before a conclusion that matters, confirm with a scoped `Grep` (allowed here, not a gate violation) and say which check you ran. <!-- END GENERATED: graph-uncertainty --> Use this when the task needs **structure in your head**, not a single symbol lookup. **Output contract:** cite a **process** or **cluster** for any cross-module flow. If none is found, or the result looks wrong, say so, verify classically, and say why in one sentence. ## Thinking modes → tools | Mental model | Tool | Instead of | | --- | --- | --- | | Business flow ("request → handler → storage") | `query` → **processes** | reading five files linearly | | Call chain ("who calls X?") | `context` (incoming CALLS) | `Grep("X")` | | Module map ("what lives in area Y?") | `READ clusters` → `cluster/{Area}` | a broad Glob on `src/` | | Pipeline step trace | `READ process/{name}` | following imports by hand | | Blast radius | `impact` + `detect_changes` | grepping for callers | | Field / data flow | `cypher` with `ACCESSES` | grepping the field name | Every recipe starts by READing `gitnexus://repo/__GITNEXUS_REPO__/context` for staleness. Stale → refresh first (`bearing:agent-ref