@jam-overture/ loom/ anthropic
The model seam: an interpreter that turns a sentence into a proposal. Optional.
Everything below is exported from that import. The names, the signatures and the sentences are read from the package itself rather than written here, so this page says what the copy of Loom in your node_modules says — and it changes in the same pull request the code does.
2 exports, in 1 module. Generated from ./dist/interpretation/anthropic.d.ts, which is the declaration file this package publishes for @jam-overture/loom/anthropic.
Your program runs without this one. Your type-checker will not. Nothing this import loads reaches it — the mention is in the types, which are gone by the time the code runs. Install it to write against this import; skip it and the import still works.
@anthropic-ai/sdk^0.115.0optional peer dependency
No import here has everything behind it. @jam-overture/loom/anthropic publishes 2 of the 1,298 names this package publishes. The other 1,296 are behind one of the 16 other imports, and not one of those imports publishes a single name this one does. The imports do not nest: a name that is not on this page is not a name that does not exist, and the search at the top of the page says which import it comes from.
Anthropic
interpretation/anthropic
The Anthropic adapter: the one module in Loom that knows a specific vendor exists. It is not exported from the package root — a host that brings its own model never loads it, and the SDK stays an optional peer dependency.
AnthropicMessagestype
Structurally satisfied by an Anthropic instance, so production passes the real client and tests pass a stub, without either needing the other.
type AnthropicMessages = {
readonly create: (params: Anthropic.MessageCreateParamsNonStreaming, options?: {
readonly signal?: AbortSignal;
}) => Promise<Anthropic.Message>;
};anthropicModelClientfunction
Shown in use on Connecting a model — The slot, and what goes in it
const anthropicModelClient: (messages: AnthropicMessages) => ModelClient