> ## Documentation Index
> Fetch the complete documentation index at: https://docs.graphify.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Repository graphs
> Explore code relationships within a repository and across your connected workspace.
Use **Graphs** in [Graphify Cloud](https://app.graphify.com) to explore code relationships within a repository or across your workspace.
## Choose your scope
Expand **Graphs** in the sidebar:
* **Single Repository** focuses on one indexed codebase.
* **Cross-Repository** follows relationships that cross repository or service boundaries.
Choose the repository context you need before interpreting a node or connection. A missing connection can reflect the selected scope or the indexed source rather than the absence of a runtime dependency.
## Explore the map
Search for a node, inspect its neighbors, and use community filters to narrow the canvas. Node and edge totals help describe the current graph; provenance categories explain how its connections were obtained.
The graph is useful for tracing a call path, finding dependent code, and identifying boundaries between services. Follow source references when you need to inspect the implementation behind a relationship.
## Read provenance
Graphify distinguishes extracted relationships from inferred or ambiguous ones. Keep those labels visible when using graph context to assess a change. A traversable connection provides evidence to investigate; it is not a formal proof of application behavior.
See [Edges and provenance](/concepts/provenance) for the evidence labels and [Formal verification](/platform/verification) for behavior comparisons.
## Keep the graph current
The canvas reflects an indexed build. Check **Repositories** and **Builds** when recent code is missing. [Wiki](/platform/wiki) provides a written view of the same indexed repository, while [MCP](/platform/connections) makes workspace context available to your coding assistant.