Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Phase 16] S9 — Compliance evidence integrity and GDPR erasure completeness

Abierto
  • ¿Algo no está bien?
#895 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
22/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend, data

Línea de trabajo

Start with _artefact_targets_for_run and the _legacy_staging_owned_by marker pattern in _purge.py, then trace how generate_training_manifest() and export_compliance_artifacts() name the bundle files. The first step is a writer-to-reader integration test that exports a real bundle and purges by run id. Done means the matching run's bundle is fully removed, a wrong run id removes nothing, and pipeline_manifest.json and audit_log.jsonl survive.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

phase: 16 source: roadmap

Roadmap · Phase 16, step S9 · size L · 5 unit(s) · planned in docs/roadmap/phase-16-trust-surface-hardening.md:553-581

Summary

The compliance surface claims a stronger evidentiary state than it holds. purge --kind artefacts cannot find the compliance bundle ForgeLM itself writes: the exporter emits fixed basenames while the resolver looks for file names that embed the run id. It fails safe (deletes nothing, emits data.erasure_failed with NoMatchingArtefacts, exits 1), so the defect is completeness, not destruction. The trainer also writes data_governance_report.json there, and the pipeline writes compliance/pipeline_manifest.json, which belongs to the whole pipeline and must not be deleted by one run's purge.

Units

Unit Tracked by (October 2026 review)
F-W20260729-TRUST-02 #101 · #102 · #477 · #554 · #635
F-W20260729-TRUST-13, F-W20260729-TRUST-01 #386 · #651
F-W20260729-TRUST-14 #386 · #554
F-W20260729-TRUST-07 #386 · #679 · #680 · #681 · #715

Plan

  • Rewrite _artefact_targets_for_run to the allow-list + ownership-proof model the design document already specifies, mirroring the _legacy_staging_owned_by marker pattern in the same file.
  • Breaking changes planned here: AuditLogger.log_event becomes fail-closed; reverse-pii and purge move to non-zero exits on states that returned 0.

Exit criteria

  • A real bundle produced by generate_training_manifest() + export_compliance_artifacts() is fully removed by a matching run id and untouched by a wrong one, while pipeline_manifest.json and audit_log.jsonl survive — a writer → reader integration test, not a synthetic-filename fixture; the fabricated docstring examples in _purge.py are deleted.
  • A malformed line sharing an identifier blocks the completion record.
  • reverse-pii returns non-zero when AuditLogger initialisation raises.
  • An OSError injected separately at the manifest open, fsync and os.replace steps never yields silent success.
  • A required → rejected → required chain is served by one shared ordered-state helper across the listing and mutation surfaces.

How to deliver

  • One root-cause family, committed on its own; then an Opus review round and a Sonnet review round, each with verified findings fixed and committed before the next step begins.
  • A reproducer that is red before the fix and green after; the full gauntlet from CLAUDE.md passes under ./.venv/bin/python.
  • Every English documentation edit ships with its Turkish mirror in the same commit; a new or renamed audit event gets its EN and TR catalog rows in the same PR.
  • A step that grows a deferred module carries its budget_history justification in the same diff; a widened guard rolls out non-strict first, then flips.
  • Commit bodies cite Absorbs F-W20260729-…; the CHANGELOG [Unreleased] section gets an entry only for a change a user or library consumer can observe (decision C-20).

Planned in docs/roadmap/phase-16-trust-surface-hardening.md (read at f94595f). Unit IDs (F-W20260729-…) come from the 2026-07-29/30 full-project review; the issue numbers next to them are the October 2026 review's records of the same defects.

Lenguaje dominante
Python
Estrellas
9
Forks
1
Merge medio
7 h 42 min
PR fusionados (30 d)
4

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de HodeTech/ForgeLM

Todos los issues de HodeTech/ForgeLM

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.