Vector DB keyword anchors (Weaviate, Qdrant, Chroma, Milvus, Neon)
pkg/providers/registry
added
patterns
dual-location YAML
keyword-only detection
high-confidence prefixed regex
created
modified
providers/reka.yaml
providers/aleph-alpha.yaml
providers/lamini.yaml
providers/writer.yaml
providers/jasper.yaml
providers/typeface.yaml
providers/comet.yaml
providers/wandb.yaml
providers/langsmith.yaml
providers/pinecone.yaml
providers/weaviate.yaml
providers/qdrant.yaml
providers/chroma.yaml
providers/milvus.yaml
providers/neon.yaml
pkg/providers/definitions/reka.yaml
pkg/providers/definitions/aleph-alpha.yaml
pkg/providers/definitions/lamini.yaml
pkg/providers/definitions/writer.yaml
pkg/providers/definitions/jasper.yaml
pkg/providers/definitions/typeface.yaml
pkg/providers/definitions/comet.yaml
pkg/providers/definitions/wandb.yaml
pkg/providers/definitions/langsmith.yaml
pkg/providers/definitions/pinecone.yaml
pkg/providers/definitions/weaviate.yaml
pkg/providers/definitions/qdrant.yaml
pkg/providers/definitions/chroma.yaml
pkg/providers/definitions/milvus.yaml
pkg/providers/definitions/neon.yaml
Used high-confidence regex only for documented prefixes (lsv2_, pcsk_); all other Tier 6 providers rely on keyword-only detection to avoid false positives at scale
W&B pattern uses low-confidence 40-hex regex gated by keyword pre-filter (no documented prefix)
Jasper, Typeface, and all vector DBs use empty verify URL (keyword-only, verification deferred)
duration
completed
~6m
2026-04-05
Phase 03 Plan 07: Emerging/Niche Providers + Vector DBs Summary
High-confidence regex was applied only where documented prefixes exist:
LangSmith: lsv2_(pt|sk)_[a-f0-9]{32}_[a-f0-9]{10}
Pinecone: pcsk_[A-Za-z0-9]{40,}
W&B: 40-hex (confidence: low) gated by keyword pre-filter
All other providers rely on keyword-only detection (env var anchors, domain hostnames) to avoid false positives at scale — consistent with Phase 2 lessons documented in 03-CONTEXT.md.