Repository navigation
Gemini Decision 1 as a decision model; models start on the current SCR base image - #86
Merged
Merged
Conversation
…ated inside the SCR container Google's Decisions API takes the System One questions and returns the System One answers, but wants the state as `input`, the key in the x-goog-api-key header, and names its token counts total_input_tokens and total_output_tokens. The new dec_gemini score template translates, so the container keeps the System One contract for the Prompt Builder and SAS Intelligent Decisioning. A JSON state is sent as text: Google takes an object there for a content block and refuses it. - google adapter: decision_template dec_gemini, endpoint /v1beta/decisions, createDecision models listed as kind decision, a decision smoke test - Decision-Definitions/gemini_decision_1 (`Google` key entry), its fact sheet row; Google's and OpenRouter's snapshots list the model - importer: recognises a dec_gemini scorer Fixed: `answer` and `confidence` took the first answer in the provider's order. Gemini Decision 1 returns the answers in another order than the questions were asked (via Google and via OpenRouter), so the headline answered the wrong question in 4 of 5 calls. They now answer the first question asked (partials/_decision_answers.py.j2, used by dec_systemone_api, dec_von and dec_gemini); every decision scorer is regenerated. Live, 2026-11-12: mdb validate --live, mdb test (5 runs) and --mas pass; a JSON state, MAS-style inputs and a bad key behave as expected. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: David Weik <geekupyourlife@gmail.com>
gemini_decision_1 published on zeus (2026-11-12) did not start: the container exited with code 3 and "C extension: None not built" before it loaded the scorer. The SCR base image now ships pandas 3.1.1 for Python 3.11, built for numpy 2, and SCR's own server imports pandas at start; the api-wrapper profile's numpy==1.26.4 pin downgraded numpy under it. Jev's image of 2026-10-20 still had pandas 3.0.3, which takes numpy 1.26. The api-wrapper profile installs requests only - no scorer of an API model uses numpy. Every requirements.json of an API model is regenerated. Republished on zeus, the container starts and answers. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: David Weik <geekupyourlife@gmail.com>
The hf-transformers and hf-sentence-transformers profiles pinned numpy==1.26.4 as well, and so did the hand-kept requirements of llama_32_1b, llama_32_3b, mistral_nemo, phi_35_mini, phi_3_mini_4k and the _Base_Definition: on the base image of 2026-11 (pandas 3.1.1 for Python 3.11, built for numpy 2) every republished one would exit at start like gemini_decision_1 did. An install that could move numpy now requires the numpy the image already has (KEEP_BASE_NUMPY: "numpy==$(python3 -c '...numpy.__version__')"), on an old base image as on the new one; an install that needs another numpy fails at publish time instead of in the running container. The _Base_Definition installs requests and tiktoken, which need no numpy. Built on zeus 2026-11-12 from copies with their own ids (qwen_25_05b_check, all_minilm_l6_v2_check; not committed): both images kept numpy 2.4.6 with pandas 3.1.1, started, and answered - Qwen "OK" in 0.42 s, all-MiniLM-L6-v2 an embedding of 11 tokens. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: David Weik <geekupyourlife@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Google released Gemini Decision 1, a decision (System One) model behind its own Decisions API. This adds it as a decision model that the SCR container calls directly at Google, and fixes two defects found on the way.
input, the key in thex-goog-api-keyheader, and the token counts are namedtotal_input_tokens/total_output_tokens.dec_geminiscore template translates inside the SCR container, so the container keeps the System One contract. The Prompt Builder and SAS Intelligent Decisioning need no change.googleadapter serves decision models:mdb add google gemini-decision-1 --kind decisionfinds the model in Google's live list (createDecision), andmdb validate --livemakes a decision call.Decision-Definitions/gemini_decision_1with theGooglekey entry and its fact-sheet row. Google's and OpenRouter's catalog snapshots list the model; OpenRouter serves it on its System One endpoint with the unchanged template.answerandconfidenceanswer the first question. The scorers took the first answer in the provider's order. Gemini Decision 1 returns the answers in another order than the questions were asked, via Google and via OpenRouter alike, so the headline answered the wrong question in 4 of 5 calls. The sharedpartials/_decision_answers.py.j2picks the first question asked; every decision scorer is regenerated. Jev keeps the order, so it was not affected.numpy==1.26.4, so a freshly published container exited with "C extension: None not built" before it loaded the scorer. Every republished model would have hit this.requestsonly; no API scorer uses numpy.hf-transformers,hf-sentence-transformers,hf-onnx) and the hand-kept requirements of Llama 3.2, Mistral Nemo and Phi-3/3.5 require the numpy the base image already has (KEEP_BASE_NUMPY). An install that needs another numpy fails at publish time, not in the running container._Base_Definitioninstallsrequestsandtiktokenonly.Validated on viya4-s2 (2026-11-12)
llm.API_KEY, and a call took about 0.3 s in the container.Googleentry of the credential domain.qwen_25_05bandall_minilm_l6_v2under their own ids were built on the current base image. Both kept numpy 2.4.6 with pandas 3.1.1, started, and answered (Qwen "OK" in 0.42 s, an embedding of 11 tokens). The copies were removed afterwards. Von and the hand-kept definitions were not rebuilt.Tests
dec_geminitemplate (request shape, header, headline order, usage, MAS-style inputs), the Google adapter's catalog and smoke test, the importer, the headline order of the System One template, and the numpy handling of every profile and every committedrequirements.json.mdb generate --all --check,mdb validate --allandmdb package-checkpass.Release note
mdb package-check --releasereports the new row ofData/decision_fact_sheet.csvuntil the next package export, beside theenable_weaviatedrift that RAG Builder: Weaviate as a vector store #84 left.mdb register --updateand a republish.🤖 Generated with Claude Code