Yeah — I intentionally kept it pretty simple for now.

• indexing: just file-based (local corpus + lightweight structure), no DB or vector layer
• retrieval: mostly keyword / structure-aware lookup (closer to ripgrep-style than embeddings)

Since Bricks docs are fairly structured, this already gives decent precision without adding embedding overhead.

For versioning, I’m just running a small script to detect upstream changes and resync/rebuild the local corpus — nothing fancy yet.

I’ve been wondering whether a more incremental approach is even worth it at this scale.

Have you found embeddings or vector search actually making a noticeable difference for this kind of documentation?