Downloads · 30 days
9
30% of all-time downloads
metafloor-ai/manifest-specialist-demand-planning-v0.6.0
manifest-specialist-demand-planning-v0.6.0 is a text generation model from metafloor-ai. Use it when you need the model to write or continue text. It is set up for peft. The card lists the license as cc-by-nc-4.0.
A specialized supply-chain domain-expert — focused entirely on demand planning & forecasting.
Downloads · 30 days
9
30% of all-time downloads
All-time downloads
30
Public
Repo size
63.7 MB
Likes
0
Public
Click a slice to open those files.
.safetensors43.7 MB · 69%
From the Hugging Face model README
A specialized supply-chain domain-expert — focused entirely on demand planning & forecasting.
Manifest Demand Planning is a domain-expert in the Manifest family: where the general Manifest orchestrator models cover all of supply chain, this one is tuned specifically for demand planning and forecasting — baseline vs promotional uplift, forecast methods, seasonality, and forecast accuracy.
Preferred 82.5% of the time over the base model — 85.0% with matched format
On a focused 20-question demand planning benchmark, an independent LLM judge panel preferred this model's answer over the base model's 82.5% of the time (16 / 3 / 1 W/L/T), and 85.0% with the same answer format. (20 items is a small sample — treat exact figures as directional.)
metafloor-ai/manifest-specialist-demand-planning, unchanged) keeps its own history and download stats.v0.5 → v0.6 (preferred over the untuned base, same benchmark):
| Release | Preferred over base | vs base + matched format |
|---|---|---|
| v0.5.0 | 82.5% | 100.0% |
| v0.6.0 | 82.5% | 85.0% |
Demand planning and forecasting questions where a focused, practitioner's answer beats a generic one:
Same question. Base model vs this specialist.
Ask (supply-chain director, mostly manual planning, prepping a trade promotion): "Why separate baseline demand from promotional uplift?"
Base model → "…the separation of baseline demand from promotional uplift is critical for this mid-market scenario due to the company's reliance on a simple moving average…" — hedged and generic.
Manifest Demand Planning → "A moving average of total history lumps every past period together, so it smears a one-time promo into a baseline and then over-forecasts the weeks after the event…" — direct, mechanism-first, practitioner framing.
Two kinds of models:
🧭 Orchestrators — general-purpose, handle any supply-chain area
| Model | Size | Preferred over base | Status |
|---|---|---|---|
| Manifest 0.8B | 0.8B | 79.9% | ✅ available |
| Manifest 2B | 2B | 85.1% | ✅ available |
| Manifest 4B | 4B | 95.1% | ✅ available |
| Manifest 9B | 9B | — | 🔜 coming soon |
🎯 Domain-experts — specialized for a single area
| Model | Preferred over base | Status |
|---|---|---|
| Manifest Specialist · Risk & Resilience | 100% (20 / 0) | ✅ available |
| Manifest Specialist · Inventory Optimization | 80.0% | ✅ available |
| Manifest Specialist · Demand Planning | 82.5% | ✅ available |
Orchestrators are scored on the general supply-chain benchmark; domain-experts on their focused domain benchmark (20 items each — treat those exact figures as directional).
This is a LoRA adapter (~44 MB), applied on top of its base model at load time.
from peft import PeftModel
from transformers import AutoModelForCausalLM, AutoTokenizer
base = "Qwen/Qwen3.5-2B" # base model — see "Built on" below
tok = AutoTokenizer.from_pretrained(base)
model = AutoModelForCausalLM.from_pretrained(base, device_map="auto")
model = PeftModel.from_pretrained(model, "metafloor-ai/manifest-specialist-demand-planning-v0.6.0")
SYSTEM = "You are a senior supply chain expert. Answer correctly and concisely."
msgs = [{"role": "system", "content": SYSTEM},
{"role": "user", "content": "How should I forecast a new SKU with only 8 weeks of history and a promo coming up?"}]
inputs = tok.apply_chat_template(msgs, add_generation_prompt=True, return_dict=True, return_tensors="pt")
out = model.generate(**inputs, max_new_tokens=512, temperature=0.7)
print(tok.decode(out[0][inputs["input_ids"].shape[-1]:], skip_special_tokens=True))
Prompt tip: include the asker's role and operating scale (revenue, SKUs, suppliers, nodes, lead time) for the sharpest answers.
| Method | LoRA (PEFT 0.20.0), rank 16 / alpha 16 / dropout 0.05 |
| Target modules | all attention + MLP projections |
| Trainable params | 10,911,744 (~0.9% of the 1.21B base) |
| Epochs | 3 |
| Training examples | ~4,000 |
| Final loss | 1.32 (from 2.64) |
The training data is a focused, proprietary demand-planning dataset and is not open-sourced — only the held-out evaluation benchmark (supply-chain-eval) is public.
Scored on a focused 20-question demand-planning benchmark — pairwise LLM-as-judge (2-model panel), this model's answer vs the base model's for the same prompt.
| Comparison | Win-rate | W / L / T |
|---|---|---|
| Manifest Demand Planning vs base | 82.5% | 16 / 3 / 1 |
| Manifest Demand Planning vs base + format | 100% | 20 / 0 / 0 |
Benchmark: supply-chain-eval (planning split). The sample is small (20 items), so treat exact figures as directional.
Released under CC-BY-NC-4.0 — free for research and non-commercial use, with attribution. Commercial use requires a license from MetaFloor — get in touch at metafloor.ai.
This model is a LoRA adapter over Qwen/Qwen3.5-2B (used under its own license); the base model is required to load the adapter.
@misc{metafloor_manifest_demand_planning,
title = {Manifest Specialist — Demand Planning: a demand-planning domain-expert (MetaFloor Manifest family)},
author = {MetaFloor AI},
year = {2026},
howpublished = {\url{https://huggingface.co/metafloor-ai/manifest-specialist-demand-planning-v0.6.0}}
}