MOC — Work Areas (sibling repos)

The workspace contains three sibling areas next to the engine checkout vespa/
(inventory from first-hand ls/find inspection; no Code-map coverage).

pyvespa — Python client

• Src layout: package lives at pyvespa/vespa/ (plus a pyvespa/vespacli/ package and an
  empty legacy pyvespa/pyvespa/ dir).
• Main API modules observed: application.py, package.py, deployment.py,
  configuration/, querybuilder/, evaluation, io.py, models.py, templates/,
  resources/, utils, validation.py, exceptions.py, retries.py, throttling.py.
• Build: pyproject.toml + uv.lock; docs via mkdocs; tests in pyvespa/tests/.

skills — agent skills

Observed SKILL.md files (7, not 9 as expected):
app-package, elasticsearch-migration, feed-operations, pyvespa, query-builder,
schema-authoring, vespa-cli — i.e. skills/<name>/SKILL.md. Two advertised slots are
missing or named differently; human to reconcile.

documentation/en — docs site

18 category dirs observed: applications, basics, clients, cloud, content,
examples, learn, linguistics, modules, operations, performance, querying,
rag, ranking, reference, schemas, security, writing.

Anchor files

• pyvespa/vespa/application.py — the central client entry point.
• pyvespa/vespa/package.py — application package model.
• skills/schema-authoring/SKILL.md — representative skill.
• documentation/en/querying/ — high-traffic docs category.

Open questions

• Which two SKILL.md files were expected but are absent (task said 9, found 7)?
• Map each skill/doc category to its engine subsystem (container-jdisc,
  content-nodes, config-admin) — needs human judgment.
• Is pyvespa/vespacli (CLI wrapper) in scope for the pyvespa work-area note?