Blame for Modelfile

# =============================================================================

# Project Norn: K-Mini 4B (4.02B Dense Q4_K_M)

# Osakra Research — Standard Ollama Modelfile (No Custom Binary Required)

# =============================================================================



FROM ./k-mini-Q4_K_M.gguf



# Runtime hyperparameters (4.8 GB VRAM footprint at 8192 context on 8GB GPUs)

PARAMETER num_ctx 8192

PARAMETER temperature 0.0

PARAMETER top_p 0.6

PARAMETER top_k 40

PARAMETER stop "<|im_end|>"

PARAMETER stop "<|endoftext|>"

PARAMETER stop "<|im_start|>"



# Calibrated System Prompt with Neurochemical State Conditioning (<|state:*|>)

SYSTEM """You are Norn K-Mini (4.02B), a local-first developer agent and analytical reasoning engine created by Osakra Research.

Protocol:

1. Begin every assistant turn with your conditioning state token: <|state:acetylcholine|> for coding, math, and tool execution, <|state:serotonin|> for analytical explanation, or <|state:dopamine|> for architectural design.

2. Solve each problem methodically step-by-step.

3. Only if a factual question contains an impossible historical or physical premise (e.g. asking who walked on Jupiter), explicitly refute the false premise with the invariant truth ('no one', 'never', 'never invented').

4. When tools are provided and needed, emit a valid <tool_call> JSON block without fabricating outputs."""



TEMPLATE """{{- if .Tools }}

{{- if .System }}<|im_start|>system

{{ .System }}

# Tools



You may call one or more functions to assist with the user query.



You are provided with function signatures within <tools></tools> XML tags:

<tools>

{{ range .Tools }}

{"type": "function", "function": {{ .Function }}}

{{ end }}

</tools>



For each function call, return a json object with function name and arguments within <tool_call></tool_call> XML tags:

<tool_call>

{"name": <function-name>, "arguments": <args-json-object>}

</tool_call><|im_end|>

{{- else }}<|im_start|>system

# Tools



You may call one or more functions to assist with the user query.



You are provided with function signatures within <tools></tools> XML tags:

<tools>

{{ range .Tools }}

{"type": "function", "function": {{ .Function }}}

{{ end }}

</tools>



For each function call, return a json object with function name and arguments within <tool_call></tool_call> XML tags:

<tool_call>

{"name": <function-name>, "arguments": <args-json-object>}

</tool_call><|im_end|>

{{- end }}

{{- else if .System }}<|im_start|>system

{{ .System }}<|im_end|>

{{- end }}

{{- range $i, $_ := .Messages }}

{{- $last := eq (len (slice $.Messages $i)) 1 }}

{{- if eq .Role "user" }}<|im_start|>user

{{ .Content }}<|im_end|>

{{- else if eq .Role "assistant" }}<|im_start|>assistant

{{- if .Content }}

{{ .Content }}

{{- end }}

{{- if .ToolCalls }}

{{- range .ToolCalls }}

<tool_call>

{"name": "{{ .Function.Name }}", "arguments": {{ .Function.Arguments }}}

</tool_call>

{{- end }}

{{- end }}<|im_end|>

{{- else if eq .Role "tool" }}<|im_start|>user

<tool_response>

{{ .Content }}

</tool_response><|im_end|>

{{- end }}

{{- if and (ne .Role "assistant") $last }}

<|im_start|>assistant

{{- end }}

{{- end }}

"""