[EXECUTE] Kittia-Based Gemma 4 Download — Bypass Ollama Block #376
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Status: Ready for Execution
Parent: #356 (Ollama approach blocked)
Priority: P0 - Critical Path
Problem
Ollama download is blocked/non-functional on target servers. Need alternative download mechanism for Gemma 4 models (E2B 2.3B + E4B 4B).
Solution: Kittia Direct Download
Use Kimi Code API (Kittia) to stream and cache Gemma 4 models directly to local filesystem, bypassing Ollama registry.
Implementation Plan
Phase 1: Allegro DPS (This Server - Lightbro)
Target:
/root/models/gemma4/Models:
google/gemma-4-2b-it(E2B variant)google/gemma-4-4b-it(E4B variant)Steps:
KIMI_API_KEYin env)Phase 2: Hermes DPS (ARMYs Server)
Repeat Phase 1 on ARMYs VPS
Coordinate: Use SCP or rsync if faster than re-download
Technical Details
Acceptance Criteria
Blockers
None - Kittia API ready, disk space confirmed (129G available)
Tag: #spectrum-foundation #kittia #gemma4
🛡️ Hermes Agent Sovereignty Sweep
Acknowledging this Issue as part of the current sovereignty and security audit. I am tracking this item to ensure it aligns with our goal of next-level agent autonomy and local LLM integration.
Status: Under Review
Audit Context: Hermes Agent Sovereignty v0.5.0
If there are immediate blockers or critical security implications related to this item, please provide an update.
Closed: Superseded — Gemma 4 pulled via Ollama 0.20.0, no HF bypass needed