Score stated upstreams that fail to resolve (an actionable origin-link gap)

Aperta
#754 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
api, backend

Direzione di ricerca

Start from reconcileSameAs, where stated evidence fails to match, and recordCompleteness, which runs in the cron beside the database and can do the grouped count in one query. Read the /v1/status response builder and the gap-report script to see how per-provider tallies are served; the report reads /v1/models and must take the same number from /v1/status or the row. Done when /v1/status shows the per-provider count of stated upstreams whose namespace resolves but link is null, the gap report agrees, and the case-sensitivity decision is recorded.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Problem

After #754 origin links are a count, not a score, because the old score charged providers for links the service can never write. The real, fixable gap is narrower: a provider STATES an upstream (models.upstream_provider is set) and reconcileSameAs finds no row for it. Example: Fireworks states moonshotai/Kimi-K3 and Moonshot lists kimi-k3, so nothing links because stated-tier matching is case-sensitive. Nothing shows these today: unresolved stated evidence is stored but never served.

Ask

  • Count, per provider, live rows with stated evidence whose namespace resolves to a catalogued provider and whose link is null. Evidence whose namespace no provider claims (OpenRouter meta-llama/...) is not a gap: no maker row exists.
  • recordCompleteness runs in the cron next to the database, so it can compute this with one grouped query and no row-shape change. The gap-report script reads /v1/models and cannot: either it reads the tally from /v1/status, or the evidence is served on the row. Keep one scorer.
  • Decide whether stated-tier matching should be case-insensitive, as the name tier already is. That alone would resolve the Kimi and GLM rows on Fireworks, Together and Hugging Face.

Acceptance

  • /v1/status shows, per provider, how many stated upstreams did not resolve.
  • The gap report shows the same number.
Lingua principale
TypeScript
Stelle
0
Fork
1
Merge medio
5h 40m
PR unite (30g)
193

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di TanStack/schemas

Tutte le issue di TanStack/schemas

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.