Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Benchmark pack generation across model tiers

Aperta
  • Qualcosa non va?
#58 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
node.js, typescript
Ambito
testing, tooling

Direzione di ricerca

Start with the generation code in packages/cli/src/generate/, then read docs/authoring/pipeline.md and the related issues #44, #43, and #51 to understand the model options and playtest inputs. Build a benchmark around fixed ideas, durations, model configurations, and seeds, with a fake LLM path for CI and a cost confirmation guard. Done means the CI harness runs without API calls and docs contain a real run’s dated results, cost, harness version, raw logs, and recommendations per pack length.

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

Descrizione

area: pipeline priority: medium type: research

Context

Which models can write a good content pack is currently a guess. Small model tiers have improved sharply and cost one to two orders of magnitude less than large ones; whether they reach publishable 30-45 minute packs, and where they fall short (schema, consistency, walkthrough, puzzle design), should be measured. The result becomes the documented recommendation per pack length and feeds the v0.3 issue-to-PR generation workflow.

Scope

  • A benchmark harness (script under packages/cli or a separate tools/ directory) that runs lexvm generate for a fixed set of ideas at 15, 30 and 45 minutes, per model configuration (small, mid and large tier, plus the hybrid from the per-stage option), with a fixed seed set of prompts.
  • Metrics per run: check pass (zero errors), repair rounds, wall time, input/output tokens and cost, play-time deviation from target, explored states, and an automated LLM playtest score (#51).
  • A results table committed under docs/ with date and harness version; raw run logs as artifacts, no API keys or secrets.
  • Budget guard: the harness prints the estimated cost and requires confirmation before spending.

Acceptance criteria

  • Harness runs end to end with a fake LLM in CI (no API calls).
  • One real benchmark run is documented with a results table and cost.
  • docs/authoring/pipeline.md recommends model configurations per pack length based on the results.

References

  • packages/cli/src/generate/
  • docs/authoring/pipeline.md
  • Related: per-stage model selection (#44), walkthrough derivation with lexvm solve (#43), automated LLM playtests (#51)
Lingua principale
TypeScript
Stelle
0
Fork
0
Merge medio
28m
PR unite (30g)
2

Preparare l'ambiente

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 nullthrone/lexvm

Tutte le issue di nullthrone/lexvm

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.