STUDY BRIEF • 2026-08-16
# Private Study Brief — 2026-08-16 **Topic Focus:** Verifier Rules, Release Date Truth & Ollama v0.32.13 Developer Instructions --- ## 1. Five Important Discoveries 1. **Release Date vs Discovery Date:** Automated research pipelines must never substitute `date_found` for `date_released`. Signal verification requires auditing canonical tag timestamps (`published_at`). 2. **Ollama v0.32.13 Verified Release:** Official release tag `v0.32.13` published on August 14, 2026, introduces developer instruction parameters for Qwen 3.8 models. 3. **Developer Instructions for Local Models:** System-level developer instructions provide deterministic behavior boundaries for LLM agents without consuming user prompt token budgets. 4. **Stale Version Filtering:** Stale version tags (e.g. `v0.5.8`) must be automatically quarantined (`publication_state = "QUARANTINED"`) to prevent publishing outdated software claims as breaking news. 5. **Fail-Closed Verification:** Signal evidence tier `HIGH` strictly requires a verified primary source URL (`https://github.com/ollama/ollama/releases/tag/v0.32.13`). --- ## 2. One Deeper Explanation: Developer Instruction Boundaries in Local Models In models supporting developer instructions (such as Qwen 3.8), developer system instructions are encoded in dedicated system-level context slots rather than general user message turns. This prevents prompt-injection attacks where user input attempts to override system safety or formatting rules. --- ## 3. Connections to Prior Signals - Connects to earlier verifier incident `VERIFY-001` where stale version numbers were misclassified. - Strengthens n8n tool-calling nodes by providing hardened system instructions via local Ollama inference endpoints. --- ## 4. STAR System & Build Implications - **Control Node Verifier:** Deterministic verifier script `scripts/run-pipeline.js` filters out quarantined signals prior to Astro static site compilation. - **Agent Governance:** Custom agents under `.agents/agents/` run strict release tag validation. --- ## 5. Three Memory Points 1. *Date Rule:* `DATE_FOUND` $\neq$ `DATE_RELEASED`. Always verify canonical source release timestamps. 2. *Version Guard:* Check GitHub API `/releases/latest` to verify exact release tags. 3. *Publication Gate:* Only signals with `public_safe = true` and `publication_state = "PUBLISHED"` are compiled to static pages. --- ## 6. Three Self-Quiz Questions 1. **Q:** What caused incident `VERIFY-001` during the initial RADAR-001 run? - **A:** The verifier conflated `date_found` with `date_released` and accepted stale version `v0.5.8` as current. 2. **Q:** What is the verified production release tag for Ollama as of August 14, 2026? - **A:** Tag `v0.32.13` (`published_at: 2026-08-14T19:16:07Z`). 3. **Q:** What main feature was introduced in Ollama v0.32.13? - **A:** Developer instructions support for the Qwen 3.8 model family. --- ## 7. Recommended Next Study Topic - **Constrained Grammar Sampling & KV-Cache Management:** Implementing GGUF context cache optimizations for local Qwen 3.8 32B model serving.