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

[uk-ai-advisory:campaign-improvement] [UK-AI-020] Gate closure advice on minimum-standard evidence

Aperta
  • Qualcosa non va?
#19,469 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
45/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions
Ambito
devops

Direzione di ricerca

Start by reading .github/workflows/uk-ai-advisory-operational-resilience.md and locate its C/D scoring gate, Open-Code Exception Register, and minimum-standard verification. Check the related tests or contract fixtures to see how the advisory outputs are validated. Done means unmet or unevidenced capabilities cap recommendations at B, while fully evidenced exceptions still require every listed safeguard and preserve open-by-default behavior and human review.

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

Descrizione

Why this matters

The authoritative GOV.UK guidance says that only once a system meets the minimum operational standard may leaders use the existing exception rule for a specific, credible publication harm. Privacy must not compensate for missing ownership, maintenance, patching, or operational assurance. Source verified 2026-10-22: https://www.gov.uk/guidance/ai-open-code-and-vulnerability-risk-in-the-public-sector.

Observed campaign evidence

  • .github/workflows/uk-ai-advisory-operational-resilience.md separately performs minimum-standard verification and says privacy and closure do not substitute for controls or remediation.
  • Its C/D scoring gate and Open-Code Exception Register require the threat-model triad and exception fields, but do not require satisfactory minimum-standard evidence before a C or D closure recommendation.
  • The durable ledger records this gap as UK-AI-020 with status PARTIAL.

Requested improvement

Add a fail-closed closure-eligibility gate to the operational-resilience advisory. This is an advisory boundary only: it must not authorize opening, restricting, hiding, or decommissioning code.

Acceptance criteria

  • A C or D closure recommendation is ineligible whenever any minimum-standard capability is failed, partial, inaccessible, or unevidenced.
  • In that state, the workflow caps the proposed tier at B and recommends remediation or retirement review rather than privacy as a substitute control.
  • A satisfactory gate remains necessary but never sufficient for closure; the credible-attacker, publication-added-risk, realistic-harm-path, narrow scope, expiry, ownership, mitigation, and periodic re-approval requirements remain mandatory.
  • Outputs remain non-binding, incomplete by design, and explicitly require human review.
  • Tests or contract fixtures cover both an unmet-minimum-standard case and a fully evidenced exception case while preserving the open-by-default model.

Generated by 📋 UK AI Advisory / Maintenance · pi · gpt56 · 60.8 AIC · ⌖ 25.7 AIC · ⊞ 9.7K · ◷

  • expires on Nov 21, 2026, 9:41 AM UTC
Lingua principale
JavaScript
Stelle
8
Fork
5
Merge medio
2h 12m
PR unite (30g)
852

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 githubnext/gh-cao

Tutte le issue di githubnext/gh-cao

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.