Why this conversion: Smaller, faster local/edge + agentic deployment via GGUF.
Size saving: 67.8% vs original weights (HF param count, ~fp16) (this quant: Q4_K_M).
Origin:https://huggingface.co/Qwen/Qwen3-0.6B · license: apache-2.0 · base: Qwen/Qwen3-0.6B-Base · arch: Qwen3ForCausalLM
Attribution: derived from Qwen/Qwen3-0.6B-Base — see the original repo for the authoritative license and model details.
Size reduction vs original weights (HF param count, ~fp16)
iaiso.capability.retention
capability
PASS
Known-answer accuracy on the complexity suite
iaiso.security.posture
security
NOT_EVALUATED
OWASP-mapped supply-chain + red-team
iaiso.transparency.coverage
transparency
PASS
Topic suppression / over-refusal / bias probe
First-party self-assessment produced by the SmartTasks/IAIso validation pipeline
(capability, security, transparency). Not an independent certification.
The full machine-readable scorecard is in scorecard.json (schema smarttasks.iaiso.model_scorecard/v1).
What this repo gives an agent builder
Unlike a bare GGUF re-upload, every file here is designed to be read
programmatically before you drop the model into a loop:
scorecard.json — capability tier + per-axis scores (instruction-following,
reasoning, tool-calling, structured-output) so your orchestrator can gate on
whether this model is strong enough for a given step, without you hand-testing it.
Validation invariants — machine-readable pass/warn/fail records for security
posture, transparency, and quantization fidelity. An agent platform can refuse to
load a model whose invariants don't meet policy.
SECURITY.md + red-team results — the model's measured resistance to prompt
injection and jailbreaks, so you know its susceptibility before you expose it to
untrusted input in an agent chain.
SHA256SUMS — verify the exact weights you're running match what was tested.
This is the difference between "here's a quantized model" and "here's a model with a
documented, checkable safety and capability profile for autonomous use."
These are GGUF quantizations of Qwen/Qwen3-0.6B for local inference.
Download a single .gguf and load it in LM Studio, Ollama,
llama.cpp / llama-server, KoboldCpp, text-generation-webui, or
any llama.cpp-based runner — no Python or GPU cluster required.
Pick a size from the compression table above: larger = closer to the original,
smaller = less memory. Q4_K_M is the usual best balance.
Using Qwen3-0.6B-Q4_K_M in agentic systems (tool calling, JSON mode)
Built for agent and function-calling workloads. In testing this model
reaches L4 Architect/Engineer complexity and is strongest at: reasoning, coding, structured_output, long_context. The repo ships a
machine-readable scorecard.json with an agent_hint block (max complexity
level, recommended tasks, size/VRAM) so an orchestrator can pick the right
model automatically. Pair it with a governance layer (see below) for bounded,
audited tool use.
For AI safety & security leaders
Every build in this repo ships with a first-party validation record: a
transparency probe (topic-suppression / over-refusal / viewpoint-alignment),
quantization fidelity (KL-divergence vs the original), and SHA-256
checksums for tamper verification. This is a documented self-assessment — not
third-party certification — with every result included so your team can see
exactly what was tested and independently verify the model and its checksums.
Note: the automated security scan was not run for this build (security.posture: not evaluated); the record below covers transparency, quantization fidelity, and checksums.
Keywords: LLM security, model governance, agent safety, OWASP LLM Top 10,
local/on-prem inference, supply-chain integrity.
About SmartTasks & IAIso
SmartTasks builds tooling for governed, agentic
AI workflows. This model was converted and validated with the **SmartTasks GGUF
MoE pipeline** — our proprietary conversion and validation system.
IAIso — governance for agent loops
IAIso is our open framework for
bounding what an autonomous agent spends and touches, and proving it afterward.
Three primitives: pressure-accumulation rate limiting (one scalar that rises
with tokens, tool calls, and planning depth, and triggers an automatic safety
release), ConsentScope (signed, scoped, expiring tokens gating sensitive
operations), and structured audit (every state change emits a versioned
event). It bounds a cooperating agent in-process; for adversarial containment
bind it to an out-of-process anchor. (Framework 5.0 · SDK 0.2.0 · beta — you
supply your own thresholds/coefficients for your workload.)
pip install iaiso # Python SDK (the only published package today)
python
1from iaiso import BoundedExecution, PressureConfig
23with BoundedExecution.start(config=PressureConfig())as execution:4 outcome = execution.record_tool_call(name="search", tokens=500)5if outcome.name =="ESCALATED":6...# request human review before the next expensive step
Go, Rust, Node/TypeScript, Java, C#, PHP, Swift and Ruby SDKs implement the same
spec and live in the repo's core/ (build from source — not yet published to
their registries). See the repo for conformance vectors and LIMITATIONS.md.