Garden Health — Milner Bigraph Topology & Vespa Coverage Dashboard

Epistemic Contract (INV-004): This dashboard is deterministically synthesized from governed markdown notes by tools/garden/analyze_garden.py (telemetry_not_authority: true). Counts and topology metrics are diagnostic signals, never autonomous promotion authority.

1. Milner Bigraph Topology Summary

Metric	Value	Notes
Governed Notes ($	V	$)
Place Graph Edges ($	E_{\text{place}}	$)
Link Graph Edges ($	E_{\text{link}}	$)
Connected Components	1	Target = 1 unified bigraph component
Articulation Points	4	GDN-NOTE-0002, GDN-NOTE-0003, GDN-NOTE-0004, GDN-NOTE-0006

flowchart TD
    ROOT["GDN-NOTE-0001: Root MOC"]
    JDISC["GDN-NOTE-0002: Container jDisc"]
    PROTON["GDN-NOTE-0003: Content Nodes"]
    CFG["GDN-NOTE-0004: Config & Admin"]
    LIBS["GDN-NOTE-0005: Utility Libs"]
    WORK["GDN-NOTE-0006: Work Areas"]
    PARA["GDN-NOTE-0026: PARA Governance Area"]
    ROOT --> JDISC
    ROOT --> PROTON
    ROOT --> CFG
    ROOT --> LIBS
    ROOT --> WORK
    ROOT --> PARA
    JDISC <-->|"Bridge: Tensor & Config"| PROTON
    CFG -->|"Derived Configs"| PROTON
    LIBS -->|"vespalib / vespajlib"| PROTON

2. Role & PARA Distribution

Role / Layer	Count	PARA Bucket	Count
adr	4	archive	1
analysis	3	area	2
archive	1	evergreen-zettelkasten	41
area	2	project	3
bridge	3	resource	3
concept	2	—	—
contradiction	1	—	—
evidence	2	—	—
guide	5	—	—
invariant	2	—	—
moc	7	—	—
plan	4	—	—
resource	1	—	—
zettel	13	—	—

3. HITS Hub & Authority Ranking

Rank	Top Place/Link Hubs (doc_id)	Hub Score	Top Authorities (doc_id)	Authority Score
1	GDN-NOTE-0001	0.3798	GDN-NOTE-0001	0.3798
2	GDN-NOTE-0003	0.3276	GDN-NOTE-0003	0.3276
3	GDN-NOTE-0006	0.2626	GDN-NOTE-0006	0.2626
4	GDN-NOTE-0002	0.2596	GDN-NOTE-0002	0.2596
5	GDN-NOTE-0004	0.2072	GDN-NOTE-0004	0.2072
6	GDN-NOTE-0011	0.1969	GDN-NOTE-0011	0.1969

4. Upstream Vespa Module Coverage (vespa/)

• Top-Level Modules Discovered: 126
• Covered in Garden sources:: 126 (100.0%)
• Covered Modules: abi-check-plugin, annotations, application, bundle-plugin, bundle-plugin-test, client, cloud, clustercontroller-apps, clustercontroller-core, clustercontroller-reindexer, clustercontroller-utils, component, config, config-application-package, config-bundle, config-class-plugin, config-lib, config-model, config-model-api, config-model-fat, config-provisioning, config-proxy, configd, configdefinitions, configgen, configserver, configserver-flags, configutil, container, container-apache-http-client-bundle, container-dependencies-enforcer, container-dependency-versions, container-dev, container-disc, container-documentapi, container-llama, container-messagebus, container-onnxruntime, container-opentelemetry, container-search, container-search-and-docproc, container-spifly, container-test, datasketches-java25, defaults, dependency-versions, docproc, docprocs, document, documentapi, documentapi-dependencies, documentgen-test, eval, fat-model-dependencies, fbench, fileacquirer, filedistribution, flags, fnet, fsa, hosted-zone-api, http-client, http-utils, indexinglanguage, integration, jaxrs_utils, jdisc_core, jdisc_core_test, jrt, jrt_test, linguistics, linguistics-components, logd, logforwarder, logserver, lowercasing_test, lucene-linguistics, maven-plugins, messagebus, messagebus_test, metrics, metrics-proxy, model-evaluation, model-integration, opennlp-linguistics, parent, persistence, predicate-search, predicate-search-core, provided-dependencies, searchcore, searchlib, searchsummary, security-utils, slobrok, socket_test, standalone-container, storage, storageserver, streamingvisitors, testutil, vbench, vdslib, vespa-3party-bundles, vespa-3party-jars, vespa-application-maven-plugin, vespa-dependencies-enforcer, vespa-documentgen-plugin, vespa-enforcer-extensions, vespa-feed-client, vespa-feed-client-api, vespa-feed-client-cli, vespabase, vespaclient, vespaclient-container-plugin, vespaclient-core, vespaclient-java, vespajlib, vespalib, vespalog, vespamalloc, zkfacade, zookeeper-client-common, zookeeper-command-line-client, zookeeper-common, zookeeper-server
• High-Priority Unmapped Sample:

5. Non-Overlapping Parallel Lease Batches (for gardener lanes)

Batch	Subtree / Scope	Candidate Target Paths / Modules
LANE-CONTAINER-JDISC	content/zettels/ + content/bridges/ (Java Container)	vespa/jdisc_core, vespa/container-disc, vespa/container-search, vespa/docproc
LANE-PROTON-SEARCHLIB	content/zettels/ + content/invariants/ (C++ Content Plane)	vespa/searchcore, vespa/searchlib, vespa/eval, vespa/storage
LANE-CONFIG-ADMIN	content/bridges/ + content/guides/ (Config & Control Plane)	vespa/configserver, vespa/config-model, vespa/config, vespa/clustercontroller-core
LANE-UNMAPPED-HARVEST	content/projects/ + content/analyses/ (Unmapped Modules)	vespa/fnet, vespa/vsm, vespa/linguistics

6. Open Questions Rollup

• GDN-NOTE-0001 (index): Code-map covers “the modules you are most likely to encounter”; ~100 of ~150 modules are unmapped (e.g. fnet, search, vsm, linguistics, flags, logserver). Should any be folded into these MOCs or get their own notes?
• GDN-NOTE-0001 (index): Confirm subsystem boundaries: clustercontroller-core is Java and sits between content and config concerns — Code-map places it under Content nodes (see cr-clustercontroller-subsystem-placement-and-skills-count).
• GDN-NOTE-0002 (container-jdisc): Pin down 3-5 concrete file-level “read first” paths (e.g. which class in container-search implements the Query API entry?).
• GDN-NOTE-0002 (container-jdisc): Where do container-dev / container-search-and-docproc fit — build aggregations or code?
• GDN-NOTE-0002 (container-jdisc): Do the C++ halves of document and messagebus belong here or in content-nodes?
• GDN-NOTE-0003 (content-nodes): Exact proton entry class/file (vespa/searchcore/src/vespa/searchcore/proton/server/?) — human to confirm.
• GDN-NOTE-0003 (content-nodes): Why is clustercontroller-core grouped under content nodes rather than config-admin?
• GDN-NOTE-0003 (content-nodes): Do vespa/vespa-ann-benchmark/vespa-search (workspace siblings outside vespa/) relate here?
• GDN-NOTE-0004 (config-admin): Which of the unmapped config-* modules belong in this MOC vs utility-libs (e.g. config-lib, configutil)?
• GDN-NOTE-0004 (config-admin): Confirm the deployment/provisioning story (config-provisioning, hosted-zone-api) — in scope for this MOC or the cloud-only area Code-map explicitly excludes?
• GDN-NOTE-0005 (utility-libs): Verify the vespajlib tensor package path and pick the canonical “first file to read”.
• GDN-NOTE-0005 (utility-libs): Should other low-level modules (fnet, flags, jrt, http-utils, fsa) be folded in?