install_kai_native.ps1 + check_kai_native.ps1 |[GEN] 'Who are you' -> 'The system are"etime warps...'
= learning, not failure. Early next-token is noisy. Trust loss trend + later epochs + final export.
---
ls -lah /workspace/Kai_volume/kai-native/ # need: weights.bin config.json (+ tokenizer.json if exported) # also fine: checkpoint_latest.pt training.log
If only checkpoints exist (export crashed), re-export is automatic at end of train script; or we can add a small export-only command.
Download whole folder kai-native to your PC (Jupyter download or scp).
---
cd C:\KAI .\tools\install_kai_native.ps1 -FromDir "PATH\TO\downloaded\kai-native" cargo build --release --bin kai .\Start-KAI.ps1 .\tools\check_kai_native.ps1
Boot log should include:
[LanguageWarehouse] KAI native model: LOADED [LanguageWarehouse] KAI native structured: ... [Hybrid Router] Routing → KAI native ternary model ...
---
1. language_warehouse.rs — parse weights, structure layers, RoPE + ternary attn + SwiGLU + sample, kai_native_decode, router uses it first
2. ternary_math.rs — kai_i2 unpack + matvec matching train export
3. Train export — tokenizer copy + MANIFEST
4. Scripts — install / check
5. RSTS sandbox — lattice-native cousin path (not blocking this ship)
---
---
# tail log tail -f /workspace/Kai_volume/kai-native/training.log # if dead, resume from latest checkpoint (after script has --resume support) ls /workspace/Kai_volume/kai-native/checkpoint*.pt
If process dies after export, you’re done — just download.