External integration inspection
Inspected on 2026-10-21. External pages are references, not execution instructions.
MESA
The MESA technical documentation describes MCP-based CyVerse/iRODS access, ontology-backed AVUs, DataCite, and DuckLake metadata history. The mesa-mcp server page lists tool families rather than a generic REST search/fetch API. Its AVU contract keeps ontology CURIEs in the unit slot and history/provenance in separate columns. Do not discard that distinction when building a future normalizer.
The mesa-mcp source README currently labels
the implementation pre-alpha and says only ds_ping is registered, with the
broader data/ontology/history tool families planned. This is a material discrepancy
between the overview documentation and source status. Verify deployed tool schemas
and versions before treating any advertised family as an available API.
MESAClient reserves search, describe, fetch, register, and get_provenance
boundaries. These deliberately raise NotImplementedError until an actual deployed
capability and source normalizer are verified. No endpoint is guessed and MESA is
not installed into the user's environment. Local fixtures use MockMESAClient.
There is no real external MESA data integration in V0.
| Capability | State |
|---|---|
| Local search/describe/fetch/provenance | Working mock with typed fixtures and checksum validation |
| External MESA data search/access/registration/history | Planned; blocked on verified deployed tool schemas and normalization |
| Source metadata ontology decisions | Deterministic local curated comparisons, not a MESA ontology integration |
| Authentication and transport | Future user-configured MCP session; no secrets in repository |
OpenClaw
Inspected openclaw_container. It supplies a container/workspace and file review workflow, with specialist roles and human approval. This prototype can map discovery, semantic, harmonization, and QA objects onto workers exchanging typed JSON and recipe/review files. The deterministic executor remains a separate capability. No OpenClaw API is invented, code copied, container started, or integration claimed.
Representation precedent
Read the MOSAIKS paper through its full-text primary publication. Its reusable image features motivate keeping feature computation separate from task-specific downstream analyses. It does not supply this prototype's multimodal semantic harmonization or governance.
Live STAC and real model inference — 2026-10-21
Earth Search was queried through its real STAC API. Native Sentinel-2 L2A Items supplied HTTPS COG URLs; rasterio/GDAL read bounded NIR and SCL windows, preserving raw DN and calibration/support metadata. Native Items, collection/license evidence, request/response, indices, window checksums and rejection evidence are persisted under ignored outputs.
The installed local Ollama server was inspected without changing models. Ollama's schema-output API is used for four roles, with no tools. Actual calls completed and persisted exact model digest, prompts, outputs, timestamps and token counts. The latest model QA rejected its proposed recipe; no scientific execution or human approval was fabricated. An earlier source-ID hallucination was rejected, prompting a narrower output contract that keeps identifiers in code. These runtime facts are not mocked tests.
The NEON API public product metadata worked;
its authenticated data-file endpoint returned 403 without a configured token.
X-API-Token native file discovery/download is implemented and offline-tested.
Actual authenticated download and sensor-aware normalization remain pending.
See real-data and agent workflow for limits and next steps.
OpenClaw + Verde adapter — 2026-10-21
Docker was initially stopped. The existing openclaw-local image contains
OpenClaw 2026.5.18 and its bundled llm-task plugin. Installed documentation/source
confirmed disableTools: true, JSON Schema validation, /tools/invoke, and
returned provider/model identities. This avoids relying on incompatible latest docs.
The existing Verde key successfully listed the configured js2/gpt-oss-120b model.
The adapter starts a separate loopback-published gateway with only the task plugin,
no channels/heartbeat/fallbacks, and no existing working-group or project mounts.
Model IDs containing slashes need the full verde/js2/gpt-oss-120b reference.
Verde rejected an empty tools array; the installed compat.supportsTools: false
setting removes that unsupported request field without granting tools. Failed
compatibility attempts remain auditable. The plugin returns normalized validated
JSON, not raw provider text, token usage or weight hashes. See the
setup and limitations.
After those compatibility fixes, all four OpenClaw/Verde roles completed against
the actual Sentinel snapshot, with both plugin and client schema validation.
The returned model identity matched verde / js2/gpt-oss-120b. QA requested
revision and the deterministic gate blocked execution. This verifies the runtime
path, not the correctness or acceptance of the scientific proposal.