bearing-architecture-reviewlisted

# Architecture review with GitNexus <!-- 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 --> `bearing-exploring`/`imaging` help you *understand* a codebase; this skill *judges* it — and backs every claim with a graph query, not vibes. ## Workflow ``` 1. READ gitnexus://repo/{name}/clusters → functional areas + cohesion scores (low = poorly factored) 2. READ gitnexus://repo/{name}/processes → long/tangled flows = candidate hotspots 3. check({cycles: true}) → circular File IMPORTS (hard structural smell) 4. cypher: cross-cluster CALLS → coupling + layering violations (lower layer calling higher) 5. cypher: god objects → classes with many HAS_METHOD AND high fan-in 6. impact on hub symbols → load-bearing nodes (high blast radius = architectural risk) ``` > Stale index → `npm run bearing:agent-refresh` (autonomous). ## What to assess (and how) | Finding | How to detect | Why it matters | | --- | --- | --- | | **Import cycles** | `check({cycles: true})` | Cyclic deps block modularity, slow builds