Skip to content

v0.1.1: stabilize the embeddable search primitive #8

Closed

Description

@codewarnab

Outcome

Make the current library safe to evaluate as an embedded search primitive before expanding its API. This release must describe what it actually does and fail predictably across CPU and WebGPU.

Workstreams

  • Land a single limit/maxResults contract across CPU and WebGPU.
  • Gate release checks on the real browser WebGPU regression suite.
  • Cover concurrent searches, cancellation/latest-query behavior, and GPU failure fallback.
  • Replace fixed performance guarantees with reproducible, device-qualified measurements.
  • Document current text, query-length, candidate-overflow, and browser-support boundaries.
  • Expose enough timing/fallback information for an embedding app to diagnose which path ran.

Acceptance boundary

  • Existing string[] and search-result APIs remain compatible.
  • A GPU failure returns a valid CPU result or a documented error rather than leaving the index unusable.
  • The release has no unqualified FPS or latency promise.
  • This phase does not add document fields, persistence, filters, framework adapters, or a hosted service.

Related current work

Activity

  1. codewarnab commented on Sep 18, 2026

    @codewarnab
    OwnerAuthor

    Closing as completed. All workstreams and acceptance criteria for v0.1.1 stabilization were delivered across PRs #3, #4, #5, and #6:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions