plan: close RNK1 and start RNK2 (reranking) - #261
Merged
Conversation
Starmap pull request 107 names the rerank operation, derives it from a new model tag, and records the billing basis beside a search unit price. Two findings changed the plan. No provider in the shipped catalog serves reranking, so decision RNK-D10 moves the endpoint data to RNK2 and keeps the endpoint contract at RNK1. The verifier reads the Starport tree alone, so phase A now records 0 cumulative passing conditions rather than 4, and the phase table says when RNK-V01 through RNK-V04 turn green. Claude-Session: https://claude.ai/code/session_0131AtNgj1Qagv2csZGuxPFM
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes RNK1 of the reranking plan. The code landed in starmap#107; this pull request carries the proof file and the ledger.
Plan amendments
Decision RNK-D10. RNK1 planned to add a rerank path to a provider record. No provider in the shipped catalog serves reranking, and the four providers RNK0 read are absent from all fifteen. The endpoint contract still landed at RNK1: an endpoint that names
rerankvalidates, it needs a path, and it accepts an author-specific path. The data moves to RNK2, beside the providers that carry it.Phase A passes no condition.
scripts/verify-reranking.shreads the Starport tree alone, and phase A changes Starmap. ConditionsRNK-V01throughRNK-V04stay red until RNK4 raises the dependency. The phase table said 4 cumulative passing; it now says 0 and explains why.Evidence
bash scripts/verify-reranking.shbash scripts/verify.shgo test ./...technical-writing lint docs/proof/reranking/rnk1.mdhttps://claude.ai/code/session_0131AtNgj1Qagv2csZGuxPFM