Changelog

Surface narrowed to /v2

The public surface is brought back to what is actually served: retrieval over the knowledge graph, and what comes around it.Removed:

The POST /v1/search, POST /v1/answer and POST /v1/context endpoints, along with the Meilisearch engine behind them. They belonged to the legacy V1 contract, which no client calls any more.
The MCP server (/mcp), its OAuth flow and its three tools (search, answer, context) — all built on those same V1 endpoints.
The atb and drug capabilities leave the published roadmap: they had no code, and documenting an unbuilt capability promises what does not exist.

Unchanged: /v2/retrieve, /v2/retrieve/stream, /v2/drugs/* and /v2/feedback keep their contracts to the character. lsk_… authentication does not move.

Surface narrowed to search, answer, and context

The API surface is trimmed down to the capabilities that carry the product.Removed:

analyse — the POST /v1/analyse endpoint and the analyse MCP tool are gone. Rule evaluation over health records is no longer part of the knowledge layer.
The experimental knowledge-graph context endpoint (POST /v2/context) and its playground route are withdrawn. The stable POST /v1/context is unaffected and remains the supported way to get a patient-aware answer.

Unchanged: search, answer, and context keep their contracts on both REST and MCP. atb and drug stay on the roadmap.

Initial knowledge layer

First release of the Locus knowledge layer — REST + MCP over the shared clinical knowledge base.Capabilities (REST + MCP):

search — structured, citable retrieval.
answer — grounded, cited answers.
context — answer accounting for a coarse patient profile, with conflicts.
analyse — apply a clinical rule to inline health records, with sourced recommendations.

Platform:

Roadmap: atb (deterministic antibiotic decision) and drug (BDPM medication data) are designed, not yet available.