Skip to content

Known limitations

This page distinguishes product boundaries from defects.

  • Similarity is not clinical equivalence.
  • Highly specific qualifiers can be underweighted.
  • Post-coordinated expressions may not have one indexed point matching the complete meaning.
  • External results depend on the selected version being indexed.

Mitigation: constrain, inspect, and verify; never apply solely from score order. Reranking and specificity behavior are discussed in issue #2389.

Moving HEAD

HEAD changes during review. A report can become stale and a result count can change after refresh.

Mitigation: record the report time and preserve long-running work as a worklist. Use a fixed release for reproducibility.

Cache and index recovery

Valkey and Qdrant are rebuildable projections. Immediately after a reset:

  • QA may fail or look empty;
  • semantic search may be incomplete;
  • dashboard values may temporarily fall back or lag.

Mitigation: complete the regular HEAD refresh and indexing chain before manual data repair.

Retired-code replacement

A terminology may not publish a replacement, or may publish a non-equivalent one-to-many change.

Mitigation: keep the finding open and perform manual terminology review.

MCP scope

The MCP experience is intentionally preview-first. It cannot remove human approval or grant OCL permissions that the current user does not have.

MkDocs indexes the text around a video, not its audio stream.

Mitigation: add a concise caption and an English transcript. The transcript is then included in the normal local search index.

Public-site boundary

GitHub Pages and the R2 custom domain are public in this design. They must not contain raw transcripts, credentials, protected terminology distributions, or unreviewed Slack attachments.