POIEO-GGUF

POIEO is a lightweight bilingual creative-writing assistant, continually pre-trained and fine-tuned from Liquid AI's LFM2.5-2.6B-Base. It's built to help writers overcome creative blocks, develop ideas, and continue stories naturally in English and Yoruba โ€” including code-switched writing that shifts between the two mid-scene.

POIEO is optimized for local, on-device inference on consumer hardware, not cloud deployment. Development and testing targeted a mid-range laptop class (Intel Core i5, 8GB RAM, integrated graphics, no discrete GPU) to keep the bar realistic for the hardware most writers actually have.

โœจ What POIEO can do

  • โœ๏ธ Generate and develop creative ideas
  • ๐Ÿ“– Continue stories from where the writer stopped
  • ๐Ÿ“ Write creatively in English and Yoruba, including within a single scene
  • ๐Ÿ”„ Maintain context across a conversation
  • ๐Ÿ’ป Run locally on consumer hardware, entirely offline
  • ๐Ÿ”’ Keep creative work on-device โ€” nothing sent to a remote service

How POIEO was built

Training was continued pre-training (CPT) followed by supervised fine-tuning (SFT) โ€” there is no DPO or other preference-tuning stage in this release. That's worth knowing going in: the model hasn't been optimized against pairwise preference judgments, so tone, verbosity, and consistency are shaped entirely by the SFT data itself rather than a separate alignment pass. If you notice uneven quality across similar prompts, this is the likely reason, and it's the natural next step for a future version.

  1. CPT โ€” LFM2.5-2.6B-Base was continually pre-trained on Yoruba text (quality-filtered Yoruba Wikipedia plus additional Yoruba corpora) to strengthen the base model's fluency and diacritic accuracy in Yoruba before any instruction tuning.
  2. SFT โ€” the CPT checkpoint was then fine-tuned on bilingual creative-writing prompt/response pairs (Yoruba, English, and bilingual code-switched examples), trained with LoRA via Unsloth, with loss computed only on the assistant's response.

(Fill in your actual dataset sizes and sources here before publishing โ€” e.g. "X,XXX Yoruba CPT tokens across Wikipedia/JW300/Bible/local corpus" and "Y,YYY SFT examples" โ€” reviewers and users will ask.)

Available Model Files

Quantization File Recommended use
Q8_0 lfm2.5-yoruba-sft-final.Q8_0.gguf Highest quality, largest memory footprint. Use if you have 16GB+ RAM and want the closest match to full-precision output.
Q5_K_M lfm2.5-yoruba-sft-final.Q5_K_M.gguf Quality/performance balance.
Q4_K_M lfm2.5-yoruba-sft-final.Q4_K_M.gguf Smallest footprint of the three, but known to run slower than expected on this architecture โ€” see note below.

Known issue: LFM2.5's hybrid short-convolution + GQA architecture doesn't yet have fully optimized K-quant dequantization kernels in llama.cpp. In testing, Q4_K_M was measurably slower than a plain Q4_0 quant despite being a similar size โ€” the "smaller/smarter" format isn't the faster one here. Liquid AI's own official LFM2.5 quantized releases use Q4_0 for this reason. A Q4_0 build is planned for this repo; until then, Q5_K_M or Q8_0 are the safer picks if inference speed matters more than footprint. If you already have Q4_K_M downloaded, benchmark it on your own hardware before assuming it's the fastest option.

Usage with llama.cpp

llama-cli -hf Obotu/POIEO-GGUF --jinja

Or download a specific .gguf file and run it directly. Recommended flags for constrained hardware (tune --threads to your actual physical core count):

llama-cli -m lfm2.5-yoruba-sft-final.Q5_K_M.gguf \
  --threads 4 --ctx-size 2048 \
  --batch-size 128 --ubatch-size 128 \
  --n-gpu-layers 999

--n-gpu-layers 999 offloads as many layers as fit to an Intel integrated GPU via llama.cpp's Vulkan or SYCL backend, if built with one enabled โ€” this reduces CPU load and thermal pressure on laptops with Iris Xe/UHD graphics. On CPU-only builds, drop that flag.

Example

User:
Kแป รฌtร n kรบkรบrรบ kan nรญpa แปฬ€dแปฬkรนnrin kan tรญ รณ rรญ ร แนฃรญrรญ kan
nรญ abแบนฬ ilรฉ ร gbร  rแบนฬ€.

POIEO:
[Generates a Yoruba creative story...]
User:
Continue this story, keeping the narrator's voice in Yoruba and
switching to English for the foreign character's dialogue:

Adรฉ wo แปฬ€nร  รฒkรนnkรนn tรณ wร  nรญwรกjรบ rแบนฬ€...

Limitations

POIEO is an experimental fine-tuned model. Known limitations:

  • No DPO/preference-tuning stage โ€” outputs can be inconsistent in tone or quality across similar prompts (see "How POIEO was built" above)
  • Identity/self-description questions ("who are you?") are not yet reliably handled โ€” the model may give a vague or off-topic answer rather than a consistent persona response
  • Can produce factual inaccuracies โ€” this is a creative-writing model, not a factual-knowledge model
  • Yoruba grammar and diacritics are generally strong but not guaranteed correct in every output
  • May lose coherence in very long conversations
  • Output quality varies with sampling parameters (temperature, top-p) โ€” the examples above used moderate settings; adjust for your use case

POIEO should be treated as a creative writing companion, not a factual authority or a finished product โ€” this is an active work in progress.

Roadmap

  • DPO/preference-tuning pass to improve consistency and reduce the identity-question gap above
  • Expand beyond Yoruba and English to additional African languages
  • Explore multimodal and voice-based creative workflows

Credits

Built on Liquid AI's LFM2.5-2.6B-Base and fine-tuned with Unsloth.

Downloads last month
185
GGUF
Model size
3B params
Architecture
lfm2
Hardware compatibility
Log In to add your hardware

4-bit

5-bit

8-bit

Inference Providers NEW
This model isn't deployed by any Inference Provider. ๐Ÿ™‹ Ask for provider support

Model tree for Obotu/POIEO-GGUF

Quantized
(10)
this model