Embedding-based `semantic` chunking (the strategy behind ingestion's `NotImplementedError`) — deferred until a deterministic-snapshot mode is designed
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 8/100
Línea de trabajo
The stub is _chunk_semantic in forgelm/ingestion.py, which raises NotImplementedError; its message points at docs/roadmap/risks-and-decisions.md rather than this issue. The feature is explicitly deferred until a deterministic-snapshot mode is designed, so there is no implementation to start. A newcomer can only usefully link this issue from the error message (via #712) and wait for the condition to hold.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Deferred work ·
F-PR29-A6-05· severity Low · cost the feature: not estimated · recorded indocs/roadmap/risks-and-decisions.md:98
Summary
forgelm/ingestion.py reserves a semantic chunking strategy that raises NotImplementedError, and its message points users at a roadmap table row instead of an issue. The work was deferred at Phase 12 because a runtime embedding-model dependency and non-deterministic chunk counts conflict with air-gapped, reproducible Annex IV evidence. This issue is the tracker the error message should link to.
Condition or budget
Only viable once a deterministic-snapshot mode is designed (Phase 12's won't-do list in completed-phases.md).
State today (re-checked 2026-10-09)
_chunk_semantic raises NotImplementedError; no issue tracked the feature before this one.
Related
#712 asks for a real issue URL in the NotImplementedError message — this issue; #837 suggested pointing at the roadmap row instead.
Acceptance criteria
- The
NotImplementedErrormessage links this issue (through #712). - When the condition holds: a deterministic, air-gap-safe semantic chunker with a pinned embedding snapshot and reproducible chunk counts.
- The row is removed from the deferral table and the CHANGELOG names its ID (the table's removal contract).
Recorded in docs/roadmap/risks-and-decisions.md (read at f94595f) and re-checked against the code on 2026-10-09. The row leaves that table only when the fix is on main, the CHANGELOG names its ID and any promised guard exists.
- Lenguaje dominante
- Python
- Estrellas
- 9
- Forks
- 1
- Merge medio
- 4 h 3 min
- PR fusionados (30 d)
- 3
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de HodeTech/ForgeLM
-
area: dev-tooling bug severity: low source: roadmap wave: 4
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
area: site bug good first issue severity: low source: review-2026-09 wave: 4
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
-
documentation good first issue severity: medium source: review-2026-09 wave: 3
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
documentation good first issue severity: low source: review-2026-09 wave: 4
Dificultad 1/5 1-3 horas Aptitud para principiantes 80/100
-
documentation severity: medium source: review-2026-09 wave: 3
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Todos los issues de HodeTech/ForgeLM
Issues similares
-
[BUG] Container scenario crashes without expected_recovery_time, kube DNS example uses retry_waitAbiertoneeds-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
krkn-chaos/krkn#1627 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
NousResearch/hermes-agent#136483 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
[BUG] LazyStackedTensorDictStore zeroes the last byte of a new key set on the last elementPosiblemente ocupada @peterdsharpe la tomó hoy. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
pytorch/tensordict#2307 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día