ADR 0001: Defer Graphify repository indexing

Audience: maintainers and compiler contributors.

Status: accepted, revisit as the platform-host codebase grows.

Decision

Do not add Graphify as a SEMAPRAX build, development, or agent bootstrap dependency yet. Use lean-ctx for bounded repository navigation and SEMAPRAX's own graph and context commands for .spx program meaning.

Evidence

A local code-only assessment used Graphify 0.9.25 against commit 7e3d294 with generated output isolated under /private/tmp:

graphify extract . --code-only --no-cluster --out /private/tmp/semaprax-graphify
graphify query Parser --budget 500 --graph /private/tmp/semaprax-graphify/graphify-out/graph.json
graphify benchmark /private/tmp/semaprax-graphify/graphify-out/graph.json

Observation	Result
Indexed corpus	17 code files; .spx, .spatch, and Cargo.toml skipped
Extracted structure	232 nodes and 712 edges
Size	254,636-byte graph for 120,266 bytes of indexed source
Bounded query	The 500-token Parser slice was useful
Benchmark	Failed with KeyError: 'links' against the newly generated graph

The assessment therefore found useful bounded symbol queries, but also found that:

• .spx, .spatch, and Cargo.toml were not indexed;
• the generated graph was larger than the indexed source;
• the tested pre-1.0 tool's benchmark command failed on its newly generated graph;
• SEMAPRAX already owns the authoritative semantic graph for the language it compiles.

Committing a second, incomplete generated graph would currently increase cache churn and create competing notions of program meaning.

Revisit gate

Re-evaluate when substantial Rust, Swift, Kotlin, JavaScript/TypeScript, C/C++, and platform-host trees exist. Adoption requires:

1. A pinned, audited tool version installed outside the Cargo dependency graph.
2. Local code-only extraction by default; no model-backed document ingestion without explicit capability approval.
3. Generated graphs and caches excluded from Git.
4. Benchmarks showing lower tokens and equal-or-better answer accuracy on real maintenance tasks.
5. An adapter that merges SEMAPRAX graph nodes into the repository index instead of treating .spx as opaque text.

Relevant upstream references: repository, documentation, and security model.