docs(i7): sharpen D7 boundary in extending.md — CSV+SQL built, HTTP/MCP MAF-only

This commit is contained in:
Kjell Tore Guttormsen 2026-07-04 22:48:01 +02:00
commit 329bcda67d

View file

@ -94,11 +94,17 @@ payloads, so the suite runs offline against a **local mock** — no live source,
The spec (§4) documents an **MCP-based connector as an extension of the `http` family**, not a new
client wired into the optimiser run path — that stays a **Non-Goal** here: the in-process
`FunctionTool` seam is the default in the run path, and MCP is demonstrated (via `build_mcp_server`
in `datasource.py`), not wired in. On the Claude Agent SDK sibling (D7), the in-process server
in `datasource.py`), not wired in.
**Where the D7 sibling stands (målbilde §11 boundary).** The Claude Agent SDK sibling (D7) built
the **file/CSV and SQL** connectors — mirroring I3/I5 — with bit-identical golden extractions.
**HTTP and MCP are demonstrated on the MAF side only** (MAF-only), against a local mock; the
sibling ships no network connector and no live-source integration. On D7 the in-process server
hook is `create_sdk_mcp_server(name, version="1.0.0", tools=...) -> McpSdkServerConfig` (package
`claude-agent-sdk`) — verified 2026-07-04 against the official Claude Agent SDK Python docs. A
deployer who wants a network- or MCP-mediated source extends this family behind the same explicit,
per-run network grant; nothing here contacts a live endpoint.
`claude-agent-sdk`) — verified 2026-07-04 against the official Claude Agent SDK Python docs — but
that is a **documented hook a deployer would reach for, not a shipped D7 connector**; no D7 HTTP
or MCP session is planned. A deployer who wants a network- or MCP-mediated source extends this
family behind the same explicit, per-run network grant; nothing here contacts a live endpoint.
## Bevisst ikke bygget (90 %-kuttlista)