A meeting-note checklist for trying Gemini 3.8 Flash
Gemini 3.8 Flash is now available on RouterBase. Here is a small evaluation exercise from the RouterBase team: turn meeting notes into a useful follow-up without changing what the participants actually agreed. This article was drafted with AI assistance.
Separate decisions from suggestions
Use a short synthetic note with three kinds of information: one agreed decision, one proposal that was not approved, and one open question. Give each a clear label in your reference answer before sending the note to a model.
For example: the team agreed to review a prototype on Friday; someone suggested moving the launch to Monday; no launch date was approved. A summary that says “Launch on Monday” has changed the decision, even if the rest reads smoothly.
Ask for a bounded output
A useful prompt is: “List decisions, proposed actions, and open questions separately. Include an owner or date only if the notes state it. Do not turn suggestions into commitments.”
Compare the answer with the reference. Check the status of the launch date, whether the Friday review remains visible, and whether an owner has been invented. These are proposed checks, not reported results from Gemini.
Keep enough context to repeat the exercise
Save the input note, prompt version, model ID, and corrections. When changing the prompt, use the same note. Otherwise you may mistake an easier example for a better configuration.
On RouterBase, use google/gemini-3.8-flash with base URL https://routerbase.com/v1. Store the API key on the server. The public catalog listed this identifier when checked on September 14, 2026.
Start with invented notes so the exercise can be shared and repeated. A useful first result is a summary you can audit sentence by sentence.
评论
发表评论