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

Decide the provenance policy for generated packs and research signing

Aperta
  • Qualcosa non va?
#55 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
25/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, typescript
Ambito
documentation, release

Direzione di ricerca

Read docs/adr/0010-content-licensing.md, docs/authoring/pipeline.md, and CONTRIBUTING.md to understand the current provenance policy, then inspect .github/workflows/release.yml and packages/cli/src/generate/pipeline.ts for signing context. Compare the disclosure options and artifact attestation approaches, including offline verification and cost. Done means an accepted ADR, aligned contributor and pipeline documentation, and a signing research note with a recommendation.

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

Descrizione

area: community area: pipeline priority: medium type: decision

Context

author and generator are free text. By repository policy, design/run.json records no model identifiers, so reviewers learn which model wrote a pack only if the pull request says so. ADR 0010 lists open questions on structured provenance and on signing in the community pipeline.

Options

Disclosure:

  • A. Status quo: free text in the pack; the model is optional in the pull request.
  • B. Structured generator fields as an additive format change: pipeline, humanEdited (none, light, substantial), an optional model, a date.
  • C. The model is disclosed in the generated pull request and its run artifacts, not in the pack.

Signing research: GitHub artifact attestations for compiled .lexpack.json files built by the release and generation workflows; whether the player could verify anything offline, or verification stays in CI and the CLI.

Scope

  • Decide the disclosure policy, including whether run.json may record model identifiers, and record it in an ADR.
  • Update CONTRIBUTING.md, docs/authoring/pipeline.md and the references in ADR 0010.
  • If B: spec, schema and prompt kit changes in a follow-up pull request.
  • A short signing research note with a recommendation; if positive, a prototype attestation for release assets.

Acceptance criteria

  • An ADR on the provenance policy is accepted.
  • CONTRIBUTING.md and docs/authoring/pipeline.md match the decision.
  • The signing research note covers the options, offline verification, cost and a recommendation.

References

  • docs/adr/0010-content-licensing.md (Open questions)
  • docs/authoring/pipeline.md (Provenance, design/run.json)
  • CONTRIBUTING.md (Contributing a content pack)
  • .github/workflows/release.yml
  • packages/cli/src/generate/pipeline.ts
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.