All posts
Engineering 1 min read

Vector-encoded knowledge graphs

How we build our own mini-internet, supercharging agentic feature development while fighting entropy.

Vest Engineering

Lines of code added and deleted per engineer, per month

Vest engineering, January 2025 to October 2026

Source: every pull request merged into a Vest repository's main branch, from vest-bi. *October includes November 1, 2026.

Source code only, excluding generated code, lockfiles and vendored dependencies.

Engineers: payroll engineering headcount, plus two team members outside engineering who ship code.

What the new lines are

Lines added per month: tests, everything else, and Vest's memory

Source: the pull requests of the chart above, plus the documents in vest-os-memory. Tests and everything else add up to its lines added times its engineers. *October includes November 1, 2026.

Tests: files in test directories or named as tests; the test modules inside Rust source files count as everything else. Vest's memory: the documents in vest-os-memory, the knowledge base our AI agents read before they work.

Vest's memory, document by document

Each dot is a document our AI agents read before they work; each line, a reference from one document to another.

Source: git history of vest-os-memory, daily snapshots, March 26 to November 3, 2026. Only the most-cited documents are named.

Hover or tap a dot to trace its references. Pinch, or hold Ctrl and scroll, to zoom.

Vest's memory, week by week

The same graph in April, July and November, and the edits that grew it.

Source: git history of vest-os-memory, daily snapshots, March 26 to November 3, 2026. A reference is a link from one document to another, counted once.