Harvest Analysis -- 111 Unmapped vespa/ Modules Classified into MOC Families

Epistemics

This is a harvest manifest, not a deep-dive: every vespa/ top-level directory not yet
referenced by any governed note’s sources: was enumerated mechanically (directory listing,
cross-checked by analyze_garden.py) and classified into a MOC family by name-level
evidence plus a directory peek (CMakeLists.txt/pom.xml/README presence), not by
reading module internals. Enumeration is machine-checked; the family classification is
project-inferred (hence corpus-level confidence: low). Each family row names the target
MOC and the candidate next-depth note (zettel/bridge/guide) for the follow-up harvest waves.

Family Map

Config & Control Plane (target MOC: config-admin, GDN-NOTE-0004)

Modules	Candidate depth notes
configd, config-lib, config-bundle, config-class-plugin, configserver-flags, configutil, config-application-package, config-model-api, config-model-fat, config-provisioning, flags	zettel: config subscription & generation pipeline (configd -> config-proxy -> clients)
zkfacade, zookeeper-server, zookeeper-common, zookeeper-client-common, zookeeper-command-line-client	zettel: zookeeper-backed config/state storage; bridge to configserver
slobrok, fileacquirer, filedistribution, protocols	zettel: RPC name registry (slobrok) + file distribution protocol
logd, logforwarder, logserver, metrics, metrics-proxy, vespalog	guide: logging & metrics plane
cloud, hosted-zone-api	note: cloud/provisioning boundary (Code-map excludes hosted; record the seam)

Stateless Container / jDisc (target MOC: container-jdisc, GDN-NOTE-0002)

Modules	Candidate depth notes
container, container-dev, container-search-and-docproc, standalone-container, container-test, jdisc_core_test	zettel: container assembly & bundle wiring (aggregator vs code)
container-documentapi, container-messagebus, docproc, docprocs	bridge: documentapi/messagebus inside the container (resolves open question in container-jdisc)
container-onnxruntime, container-llama if unmapped at re-run	zettel: stateless model hosting
container-opentelemetry, container-apache-http-client-bundle, container-spifly, jaxrs_utils, http-utils, http-client	guide: container HTTP/telemetry surface
annotations, application, component	zettel: jDisc component model & annotation processing
container-dependencies-enforcer, container-dependency-versions	(build governance — see Build & Packaging)

Content / Search Plane (target MOC: content-nodes, GDN-NOTE-0003)

Modules	Candidate depth notes
clustercontroller-apps, clustercontroller-utils, clustercontroller-reindexer	zettel: cluster controller family (placement seam, see cr-clustercontroller-subsystem-placement-and-skills-count)
persistence, storageserver, vdslib, streamingvisitors	zettel: storage persistence & visitor framework
predicate-search, predicate-search-core	zettel: predicate indexing & matching
searchsummary, documentapi, documentapi-dependencies, documentgen-test	bridge: document API from container to content plane

Client / Feeding (target MOC: work-areas, GDN-NOTE-0006)

Modules	Candidate depth notes
vespaclient, vespaclient-core, vespaclient-java, vespaclient-container-plugin, client	guide: Java client stack vs container plugin
vespa-feed-client, vespa-feed-client-api, vespa-feed-client-cli	zettel: feed client protocol & backpressure

Linguistics (target MOC: utility-libs until a dedicated MOC exists, GDN-NOTE-0005)

Modules	Candidate depth notes
linguistics, linguistics-components, lucene-linguistics, opennlp-linguistics, indexinglanguage, fsa	zettel: linguistics provider SPI; guide: analyzer configuration

Utility / Platform Libraries (target MOC: utility-libs, GDN-NOTE-0005)

Modules	Candidate depth notes
fnet, jrt, vespamalloc, security-utils, datasketches-java25, searchsummary if C++	zettel: fnet networking; jrt Java runtime utilities
fbench, vbench, model-evaluation, model-integration	guide: benchmark harnesses

Build & Packaging (aggregators — record once, do not deep-dive)

parent, dist, defaults, cmake, maven-plugins, bundle-plugin, bundle-plugin-test,
vespa-application-maven-plugin, vespa-documentgen-plugin, vespa-dependencies-enforcer,
vespa-enforcer-extensions, dependency-versions, provided-dependencies,
fat-model-dependencies, documentapi-dependencies, container-dependencies-enforcer,
container-dependency-versions, vespa-3party-bundles, vespa-3party-jars, vespabase,
testutil, and the *_test modules (jrt_test, lowercasing_test, socket_test,
messagebus_test, documentgen-test, bundle-plugin-test, jdisc_core_test).

These are Maven/CMake aggregation or test-support artifacts. Decision recorded: they
count as covered by classification once this note lands; no zettels will be minted for
them individually. Re-visiting requires a contradiction-register entry.

Next Waves

1. Wave A (config plane): the config/zookeeper/slobrok family -> 2 zettels + 1 bridge.
2. Wave B (container assembly): container/container-dev/container-search-and-docproc
   aggregator-vs-code resolution -> resolves an open question in container-jdisc.
3. Wave C (storage plane): persistence/storageserver/vdslib/streamingvisitors.
4. Wave D: split a dedicated mocs/linguistics.md if the family grows past ~6 notes.