The Software That Analyzed Its Own Birth
WeftOS is a 173,923-line Rust project with 22 crates. We pointed its own Weaver at the codebase that built it. Not a demo. Not a simulation. A real analysis of a production system.
What It Found
Identified in the code — design discussions happening across modules.
43 implemented, 12 pending, 10 deferred.
The kernel's main execution loop had 1,831 lines and zero tests. No other module depended on it directly — a critical single point of failure invisible to conventional analysis.
Across 29,029 data points analyzed.
The Data
Domain Maturity Profile
Relative strengths across analysis domains
What We Did About It
The analysis led to targeted improvements. Tests were added for the agent_loop module. Architectural decisions that existed only in commit messages were documented formally. Five of the twelve conversations were resolved with explicit design decisions and code changes.
This Is What We Do For Your Organization
Same technology. Same depth. Applied to your systems. Whether you have 10,000 lines or 10 million, the Weaver traces cause and effect — not just keywords.
External Validation
We also analyzed an external codebase we had never seen before — ruvector, a Rust project with 109 crates and 2,484 commits.
See What We Find In Your Systems
Start with a free assessment. 15 questions, instant results.