weavatrix-rust 2.0.1

Protocol-independent Rust repository intelligence: typed evidence graphs for impact, architecture, APIs, Git, search, and memory
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99

# Getting started

Choose the smallest surface that matches your application: an immutable
snapshot, a live repository engine, or the standalone CLI.

## 1. Build a snapshot

```toml
[dependencies]
weavatrix-rust = { version = "2.0.1", default-features = false }
```

```rust
use std::path::Path;
use weavatrix_rust::{Analyzer, AnalyzerConfig};

let analyzer = Analyzer::new(AnalyzerConfig::default());
let snapshot = analyzer.analyze(Path::new("."))?;

println!(
    "{} nodes, {} edges, revision {}",
    snapshot.nodes.len(),
    snapshot.edges.len(),
    snapshot.revision
);

# Ok::<(), weavatrix_rust::Error>(())
```

The minimal build includes deterministic scanning, the lossless parser,
language adapters, graph construction, snapshots, core operations, and the
CLI. It has no network implementation or external executable dependency.

## 2. Enable only the capabilities you need

```toml
[dependencies]
weavatrix-rust = {
    version = "2.0.1",
    default-features = false,
    features = ["lang-rust", "git", "search"]
}
```

Available features are `lang-rust`, `git`, `search`, `clone`, `vector`,
`semantic`, and `memory`. `full` enables every optional analysis capability.
Disabled operations disappear from the catalog instead of returning
advertised-but-unavailable stubs.

## 3. Query a repository session

```rust
use blazingly_json::json;
use weavatrix_rust::{Weavatrix, operations};

let mut engine = Weavatrix::open(".")?;
let impact = operations::call(
    &mut engine,
    "change_impact",
    json!({"files": ["src/lib.rs"], "depth": 3}),
)?;
println!("{}", blazingly_json::to_string_pretty(&impact)?);

# Ok::<(), Box<dyn std::error::Error>>(())
```

Use the typed `Analyzer`, `Snapshot`, `Graph`, `RepositoryState`, and
`Weavatrix` APIs when JSON operation contracts are unnecessary.

## 4. Use the CLI

```sh
cargo install weavatrix-rust
weavatrix-rust analyze /absolute/path/to/repository --pretty
weavatrix-rust list-tools
weavatrix-rust tool graph_stats /absolute/path/to/repository
```

`analyze` emits the native snapshot. Add `--format=legacy` for the historical
JavaScript-compatible graph shape.

## 5. Verify architecture

Create `.weavatrix/architecture.json`, then call:

```sh
weavatrix-rust tool verify_architecture .
```

The verifier checks dependency rules, runtime cycles, file size, and function
size. Missing contracts remain `NOT_CONFIGURED`; malformed budgets fail
closed.

## Product adapters

This crate deliberately contains no MCP or npm runtime. For prebuilt coding
agent integration use the separate
[`weavatrix`](https://www.npmjs.com/package/weavatrix) product. It wraps this
engine without moving protocol concerns into the core.