weavatrix-rust 1.0.1

Read-only Rust repository intelligence and MCP server
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

# Architecture

## Boundary

Weavatrix Rust is a local, read-only application boundary:

```text
weavatrix-scan manifest ----+
language/domain adapters ---+--> normalized facts --> weavatrix-graph
weavatrix-git objects ------+          |                    |
coverage reports -----------+          +--> snapshot/query -+
weavatrix-search/clone -----+                               |
vector/semantic/memory -----+-------------------------------+
                                                             |
                                         CLI / one stdio MCP
                                         all | code | seo view
```

The analyzer reads repository files and derived configuration. It does not edit
source, execute repository code, start language servers, invoke command-line
Git or ripgrep, or access the network.

## Independent packages

- `weavatrix-scan` owns walking, ignore rules, skip evidence, hashes, and
  incremental manifests.
- `weavatrix-graph` owns graph models, validation, canonical ordering,
  algorithms, topology, and serialization.
- `weavatrix-git` owns direct object-database, commit-graph, MIDX, diff, and
  cross-repository reads.
- `weavatrix-search` and `weavatrix-search-vector` own lexical and vector
  retrieval.
- `weavatrix-clone` owns Type-1/2/3 detection and stable report formats.
- `weavatrix-semantic` owns inferred semantic edges and SEO policy.
- `weavatrix-memory` owns append-only events, temporal projections, and bounded
  context compilation.

This crate composes those packages. It does not copy their algorithms into the
MCP layer.

## Stable seam

Language adapters return normalized symbols, imports, references, domains,
diagnostics, and source spans. The analyzer owns repository identity and
reference resolution. The graph package owns deduplication, validation, and
canonical ordering.

The native snapshot is deterministic. A compatibility projection emits the
JavaScript Weavatrix `{ nodes, links }` shape so existing consumers can migrate
without contaminating the graph model.

## One server, bounded profiles

Code and SEO use the same repository identity and evidence graph. They remain
one process to avoid duplicate scans and divergent revisions. `McpProfile`
filters the visible tool catalog:

- `all`: every compiled capability;
- `code`: repository intelligence without SEO-specific suggestions;
- `seo`: content, graph, search, semantic, vector, and memory tools.

SEO links are inferred evidence supplied by `weavatrix-semantic`. They never
become deterministic code edges merely because they share a server.

## Evidence model

Every relationship records extractor identity, evidence kind, confidence, and
an optional source span. Consumers must distinguish parsed/resolved evidence,
measured coverage, and inferred semantic links. Every tool either completes its
declared evaluation or returns an error. Optional external evidence that is not
present is represented as `{ "present": false, "reason": "..." }`; it is not
reported as an incomplete capability and it never invents a clean measured
result.

## Refresh model

The active repository stores its last scan report. The first MCP call performs
an incremental catch-up after the handshake, then starts a native recursive
filesystem watcher in the background. Later unchanged calls are constant-time
at the freshness boundary. After a real filesystem event, an incremental scan
compares source identity and hashes; a changed repository gets a fresh
immutable snapshot. The standalone library exposes explicit
`refresh_if_stale` and `rebuild` calls and has no watcher or MCP dependency.
Git history and cross-repository reads stay independent of worktree mutation.