File size: 2,093 Bytes
8168419
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
---
license: apache-2.0
base_model: google/gemma-4-E4B-it
pipeline_tag: text-generation
tags:
- nvfp4
- toolkoder
- toolkode
- agentic-coding
- local-coding-agent
- gemma4
---

# ToolKoder E4B NVFP4

ToolKoder E4B NVFP4 is the GPU-oriented ToolKoder E4B runtime lane. It is
planned as the sibling of `toolkit-cli/toolkoder-e4b-mlx`, exported from the
same private merged checkpoint after RC 0.1 blessing.

RC note: this card is staged documentation. The final NVFP4 runtime is not
published until the private merge, exact export, Toolkit R2 head-verified
manifest, runtime smoke, ToolKode telemetry, and adversarial blessing all pass.

## Intended Role

ToolKoder E4B is the local worker lane. It is designed for bounded inspect,
patch, refactor, summarize, and repair tasks under a captain model or developer.

| Field | Value |
| --- | --- |
| Public repo | `toolkit-cli/toolkoder-e4b-nvfp4` |
| Sibling repo | `toolkit-cli/toolkoder-e4b-mlx` |
| Model line | ToolKoder |
| Origin family | Gemma 4 |
| Runtime | NVFP4 |
| Primary role | Local/GPU coding worker |

## Release Policy

The public artifact may contain only quantized runtime files, sanitized model
metadata, tokenizer/config files, license text, and origin provenance.

No private SFT rows, private prompts, eval predictions, execution traces,
holdouts, LoRA adapters, full-precision roots, or BF16 roots belong in this
repository. BF16/full-precision merged checkpoints are private Toolkit R2
artifacts only.

## Finalization Path

1. Freeze the E4B v179+ SFT inventory.
2. Train and merge LoRA into a private higher-precision checkpoint.
3. Export MLX and NVFP4 variants from that same checkpoint.
4. Upload the exact exports to Toolkit R2 with head verification.
5. Run runtime smokes and ToolKode worker telemetry.
6. Run adversarial release review over the exact public staging folders.
7. Publish only after `release_ready` and `blessed` are true.

## Claims

No benchmark claims are made from this staged card. Public quality claims require
the final exported artifact and reproducible telemetry for that exact artifact.