FunctionGemma 270M — event commands, Q4_K_M

Selected fine-tune (epoch-2), merged with the pinned upstream model and quantized for offline CPU use in an Android application. This is a modified derivative, not the stock upstream model.

Intended use

Extract baby-tracking requests into proposed function calls. It is not a conversational assistant, medical adviser, memory-navigation model or storytelling model. Validate names, arguments, dates, quantities, permissions and record IDs in application code. Require user review before writes. No calibrated confidence score is provided.

Artifact

  • File: q4_k_m.gguf
  • Size: 261,329,984 bytes
  • SHA-256: 007e3e5e6857652f0ccea8e205ad47467328817b4f7db48111506ab24106c88d
  • Base: google/functiongemma-270m-it, revision 39eccb091651513a5dfb56892d3714c1b5b8276c
  • Export: LoRA merge, GGUF, Q4_K_M; pinned llama.cpp 3d65c90d04d337e88f2b1f7f0061f40a5324e662.

App protocol

Use the functiongemma-native chat template, the extraction instruction and context layout in prompt_protocol.json, and the thirteen supported functions in command_tools.json. Those files are technical protocol definitions, not family data. JSON call envelopes are used for Granite/Qwen; FunctionGemma emits its native <start_function_call> format. An ordinary chat prompt or a broad application planning schema is not equivalent. The app converts complete, validated calls into reviewable plans; it does not fabricate confidence.

The tokenizer and chat template are embedded in GGUF. The tested mobile configuration uses an 8,192-token context, greedy command decoding and a 512-token output cap. JSON syntax constraints do not establish factual correctness; reject partial/truncated outputs.

Evaluation and limits

The earlier BF16 desktop checkpoint scored 74.5% exact tool/argument matches across 440 synthetic matched cases in ten languages, with separate weak-language Amharic stress tests. This is not a mobile-Q4 accuracy claim or native-speaker validation. The desktop tool catalog was broader than the thirteen-tool app protocol. Quantization, different prompts/catalogs and hardware can change results. Errors can include wrong quantities, dates, IDs and unwanted writes despite valid syntax. English and Brazilian Portuguese were the training languages.

No dataset, family conversations, logs, credentials or app database is included in this release. See MODEL_MANIFEST.json for provenance and NOTICE for modifications. The model weights remain subject to the upstream license in LICENSE.

Gemma use terms

Use and redistribution are governed by the included Gemma Terms of Use, including Section 3.2 and the Gemma Prohibited Use Policy. Gemma is provided under and subject to the Gemma Terms of Use found at https://ai.google.dev/gemma/terms.

Mobile integration check

Eight synthetic app-catalog requests (six English and two Portuguese) through the actual Android runtime on Samsung SM-S901E, Q4_K_M, CPU, 8K context. Exact complete tool/argument matches: 7/8. Peak whole Flutter debug app RSS 1.34 GiB, maximum request-baseline increase 622 MiB, median 21.5 seconds. This tiny integration sample is not a production accuracy estimate, model-only RAM measurement, or validation on smaller phones.

The published prompt examples omit application branding; the integration measurements used the original corresponding prompts.

Downloads last month
353
GGUF
Model size
0.3B params
Architecture
gemma3
Hardware compatibility
Log In to add your hardware

4-bit

Inference Providers NEW
This model isn't deployed by any Inference Provider. 🙋 Ask for provider support

Model tree for rbrmafort/functiongemma-270m-event-commands-gguf

Finetuned
(472)
this model