Skip to content

Cross-encoder rerank — only if 60-02 shows retrieval is the bottleneck (v3.2 / 62) #44

Description

@RichardHightower

Tracking Phase 62 from docs/plans/v3.2-prove-it-plan.md.

README: Cross-encoder rerank is Not implemented. The extension point exists and returns an explicit NotImplemented error — it is not silently degraded. That honesty is the v3.1 outcome and must stay until a number says otherwise.

Rule

Do not build ahead of evidence. Phase 62 exists only if the 60-02 LOCOMO result (see #39) shows retrieval, not generation, is the bottleneck. The harness's per-type breakdown will say. If the number is bad for another reason, this stays closed.

Blocked on #39.

Activity

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

    enhancementNew feature or requestv3.2v3.2 Prove It milestone

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions