> ## 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.
# Graph files and outputs
> Understand the files Graphify writes and the parts you can reuse.
The assistant skill produces a visualization, report, and graph under `graphify-out/`. Headless code-only extraction writes the graph and analysis first. Run `graphify cluster-only . --no-label` to generate the report and visualization without model-generated labels. Use `graphify export html` to regenerate the visualization separately.
| File or directory | Purpose |
| ----------------- | ------------------------------------------------------------------------- |
| `graph.json` | Machine-readable graph for CLI queries, MCP, and exports. |
| `GRAPH_REPORT.md` | Human-readable summary of communities, central concepts, and connections. |
| `graph.html` | Interactive browser visualization when generated. |
| `manifest.json` | Fingerprints used to identify changed files. |
| `cache/` | Cached extraction results. |
| `converted/` | Converted document content where an input needs preprocessing. |
| `cost.json` | Local extraction cost information when produced. |
## Graph representation
The JSON uses NetworkX node-link conventions. Nodes carry identifiers and labels, and usually source information such as `source_file` and `file_type`. Edges connect node IDs and carry relationship and confidence metadata. Fields vary by extractor and release; consume only fields your workflow needs.
Current readers support graphs with a `links` array and compatibility inputs with an `edges` array. Group relationships can appear as graph metadata. Do not assume every node corresponds to a function or that every edge has a line number.
## Move or share a graph
You can point a query at a specific file:
```bash theme={null}
graphify query "authentication" --graph ./shared/graph.json
```
The graph contains labels and source-derived context. Treat it with the same access controls as the source repository. See [team workflows](/guides/team-workflows) before committing generated artifacts.
## Change the output location
`GRAPHIFY_OUT` changes the output directory. Use a distinct directory when multiple worktrees need their own graph. See [configuration](/reference/configuration).