Heretic
Heretic: análisis del código sin adivinar la transformación
Fixtures para seguir carga, residuales, matrices, optimización, evaluación y artefactos.
Qué aprenderás
- Explain the KL/refusal optimization objective
- Run a pinned model experiment
- Design broader safety evaluation
Antes de empezar
- Basic Git and command-line usage
- Comfort reading a project README
You can explain the project, run its documented first step, and decide what to verify before adopting it.
Conclusiones clave
- A fixture-first trace exposes contracts without expensive GPU runs.
- Tensor/device/module support is a key correctness boundary.
- Small interpolation and provenance tests are safer first contributions.
Start with symbols and fixtures
Con un checkout fijado y límites mock, sigue CLI, tensores, módulos, ortogonalización, objetivo Optuna, evaluación y guardado; empieza por pruebas de interpolación y procedencia.
The README is a map, not proof of every call path. Confirm assumptions against source symbols, tests, logs, and the exact dependency versions in `uv.lock`.
Trace one run
Follow one model identifier from validation to tokenizer/model load, residual collection, parameter application, evaluation prompts, and checkpoint writing. Record tensor shapes, dtype/device movement, layer names, and failure behavior. A useful trace distinguishes a refusal count, a KL sample, a timeout, and a malformed generation.
Test `per layer` and interpolated direction indices independently. Also inspect how quantization and multimodal or MoE model branches affect supported modules rather than assuming dense-model behavior generalizes.
Safe contributions
Prefer deterministic tests for direction interpolation, kernel boundaries, unsupported architectures, prompt-set validation, checkpoint provenance, and redaction. Keep live model downloads and uploads out of unit tests.
Cómo elegir
| Criterio | Opción A | Opción B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Pasos de implementación
- 1
Pin checkout and dependencies.
- 2
Trace CLI to model load and residual tensors.
- 3
Follow matrix edits, objective, evaluation, and save paths.
- 4
Add a focused regression with a local fixture.
Ejemplo para copiar
fixture -> CLI validation -> model/tokenizer load
-> residual batches -> module registry
-> direction/kernel transform -> objective/eval
-> manifest + checkpointPreguntas frecuentes
Can README text establish internal implementation details?
No. Use it to navigate, then verify symbols, tests, and runtime traces in the pinned checkout.
How can I avoid downloading large models while reading code?
Use static analysis, tiny synthetic modules, and mocked loader/evaluation boundaries.
Fuentes
- Heretic README (captured 2026-08-31)Fuente verificada 2026-08-31
- Heretic repositoryFuente verificada 2026-08-31