PARA Project — Unmapped Vespa Modules & Anchor File Harvest

Time-bounded PARA project (para: project) to systematically map the remaining top-level modules under vespa/ that are not covered in vespa/Code-map.md, using the parallel lease batches generated by tools/garden/analyze_garden.py.

Project Scope & Priority Waves

1. Wave A — Transport & RPC Substrate (fnet, jrt, messagebus):
   • Map C++ fnet transport framing and Java/C++ jrt RPC invocation used by config subscriptions and scatter-gather search dispatch.
2. Wave B — Streaming Search & Summaries (vsm, searchsummary, linguistics):
   • Contrast vsm (Vespa Streaming Matcher over raw storage buckets) against indexed proton matching (proton-lid-space-and-attribute-vectors).
3. Wave C — Cloud/Security & Observability (flags, metrics-proxy, security-utils):
   • Document feature flag distribution and Prometheus/OpenTelemetry metrics aggregation.

Exit Criteria (Archive Trigger)

• Raise top-level vespa/ module citation coverage above 35% in garden-health with 0 unreciprocated edges (INV-003), then move this plan to content/archives/ (para: archive).