Gemma 4 31B

import { createClient } from '@runware/sdk'

const client = await createClient({ apiKey: process.env.RUNWARE_API_KEY })
await client.connect()

const [result] = await client.run({
  model: 'google:gemma@4-31b',
  settings: {
    systemPrompt: 'You are a careful conversation analyst. Read informal human dialogue, preserve nuance, identify facts versus assumptions, and produce structured, practical outputs without inventing details.',
    temperature: 0.35,
    topP: 0.9,
    thinkingLevel: 'high',
    maxTokens: 8192
  },
  messages: [
    {
      role: 'user',
      content: 'Analyze this random conversation by humans. Return: 1) a 5-sentence plain-language summary, 2) confirmed decisions, 3) unresolved questions, 4) contradictions or timeline conflicts, 5) each person’s likely responsibilities, 6) any emotional subtext, and 7) a polished follow-up message that Jules could send to the group.\n\nConversation:\n\nMara: Did anyone actually book the train yet, or are we still pretending someone else did it?\nTheo: I looked at seats but didn’t pay because Jules said they had a discount code.\nJules: I have a code, yes, but it only works after 10 pm for some reason. Don’t ask me why.\nPriya: That sounds fake but also exactly like a train company.\nSam: If we leave Friday at 6:40, I can bring the folding bike. If we leave at 8:15, no bike because the storage slots are gone.\nMara: Why are we bringing a bike to a cooking class weekend?\nSam: Because the cottage is two miles from the station and Priya said she refuses to walk with bags.\nPriya: I said I refuse to walk with the soup pot, not bags.\nTheo: Why is there a soup pot?\nJules: The host asked us to bring one large pot if possible. I posted that yesterday.\nMara: You posted a screenshot with half the text cut off.\nJules: It was readable if you opened it.\nTheo: It was readable if you had a telescope.\nSam: I can bring my medium pot if that solves the bike issue.\nPriya: Medium pot is probably fine unless we’re feeding a sports team.\nMara: The host said six people, right?\nJules: Five of us plus Anika, if she confirms.\nTheo: Anika told me she can’t come because her dog has stitches.\nPriya: She told me she might come late Saturday if her sister can watch the dog.\nSam: So we need a ticket for Anika or not?\nJules: Not until she confirms. The discount code can handle separate purchases.\nMara: Please do not make us buy five tickets and then discover we needed six together.\nTheo: Group fare starts at six, so five versus six matters.\nJules: Wait, I thought group fare started at five.\nPriya: Website says six adults. I’m looking right now.\nSam: We are not adults emotionally, but yes.\nMara: Can someone make one decision before I turn into a chair.\nJules: Proposal: I check the code at 10:05 tonight. If it works, I buy five tickets for the 6:40 Friday train. Anika buys her own later if she comes.\nTheo: Works for me, but only if I’m not sitting backward. Last time was grim.\nPriya: I don’t care about direction. I care about being near the luggage rack.\nSam: And I need the bike slot if we’re doing the 6:40.\nMara: I can pay Jules back tonight. Also, I vote no soup pot if Sam brings medium pot.\nJules: Host said large preferred, not required. Medium is okay.\nPriya: I’ll carry the medium pot if Sam handles the bike.\nSam: Deal.\nTheo: I’ll bring coffee and those card games Mara likes.\nMara: I like one card game. The bird one. Not the tiny betrayal one.\nTheo: The tiny betrayal one is staying home after last time.\nPriya: Thank you. It changed the room’s entire temperature.\nJules: Focus: I’ll buy tickets at 10:05 if code works. Backup if it fails?\nSam: Buy anyway? Prices went up yesterday.\nMara: I agree. Buy anyway, but message us the total first if it’s more than 55 each.\nTheo: Cap at 60 for me.\nPriya: Same. If it’s over 60, I’ll take the later train and complain privately.\nJules: So cap is 60 per person. If under or equal, I purchase. If over, I pause.\nMara: Yes.\nSam: Yes.\nTheo: Yes, and forward-facing if possible.\nPriya: Near luggage if possible.\nJules: I cannot promise train geometry, but I will try.\nMara: Also check-in at the cottage is 4 pm, right?\nSam: 5 pm, I think.\nPriya: Email says keys available from 4:30 at the side door.\nJules: I’ll add that to the shared note.\nTheo: There is a shared note?\nMara: Theo, you commented in it with a pancake emoji.\nTheo: That could have been any document.\nPriya: No, it was very specifically this one.\nJules: Final for now: I buy five 6:40 tickets tonight if price is 60 or less each. Sam brings bike and medium pot. Priya carries pot from station. Theo brings coffee and bird card game. Mara pays me back tonight and reminds Anika to confirm by Thursday noon.\nMara: I did not volunteer for Anika duty, but fine, I’ll text her.\nSam: Thank you, chair-in-progress.\nMara: I am already furniture.'
    }
  ]
})

import asyncio
import os

from runware import Runware


async def main():
    async with Runware(api_key=os.environ["RUNWARE_API_KEY"]) as client:
        results = await client.run({
            "model": "google:gemma@4-31b",
            "settings": {
                "systemPrompt": "You are a careful conversation analyst. Read informal human dialogue, preserve nuance, identify facts versus assumptions, and produce structured, practical outputs without inventing details.",
                "temperature": 0.35,
                "topP": 0.9,
                "thinkingLevel": "high",
                "maxTokens": 8192
            },
            "messages": [
                {
                    "role": "user",
                    "content": "Analyze this random conversation by humans. Return: 1) a 5-sentence plain-language summary, 2) confirmed decisions, 3) unresolved questions, 4) contradictions or timeline conflicts, 5) each person’s likely responsibilities, 6) any emotional subtext, and 7) a polished follow-up message that Jules could send to the group.\n\nConversation:\n\nMara: Did anyone actually book the train yet, or are we still pretending someone else did it?\nTheo: I looked at seats but didn’t pay because Jules said they had a discount code.\nJules: I have a code, yes, but it only works after 10 pm for some reason. Don’t ask me why.\nPriya: That sounds fake but also exactly like a train company.\nSam: If we leave Friday at 6:40, I can bring the folding bike. If we leave at 8:15, no bike because the storage slots are gone.\nMara: Why are we bringing a bike to a cooking class weekend?\nSam: Because the cottage is two miles from the station and Priya said she refuses to walk with bags.\nPriya: I said I refuse to walk with the soup pot, not bags.\nTheo: Why is there a soup pot?\nJules: The host asked us to bring one large pot if possible. I posted that yesterday.\nMara: You posted a screenshot with half the text cut off.\nJules: It was readable if you opened it.\nTheo: It was readable if you had a telescope.\nSam: I can bring my medium pot if that solves the bike issue.\nPriya: Medium pot is probably fine unless we’re feeding a sports team.\nMara: The host said six people, right?\nJules: Five of us plus Anika, if she confirms.\nTheo: Anika told me she can’t come because her dog has stitches.\nPriya: She told me she might come late Saturday if her sister can watch the dog.\nSam: So we need a ticket for Anika or not?\nJules: Not until she confirms. The discount code can handle separate purchases.\nMara: Please do not make us buy five tickets and then discover we needed six together.\nTheo: Group fare starts at six, so five versus six matters.\nJules: Wait, I thought group fare started at five.\nPriya: Website says six adults. I’m looking right now.\nSam: We are not adults emotionally, but yes.\nMara: Can someone make one decision before I turn into a chair.\nJules: Proposal: I check the code at 10:05 tonight. If it works, I buy five tickets for the 6:40 Friday train. Anika buys her own later if she comes.\nTheo: Works for me, but only if I’m not sitting backward. Last time was grim.\nPriya: I don’t care about direction. I care about being near the luggage rack.\nSam: And I need the bike slot if we’re doing the 6:40.\nMara: I can pay Jules back tonight. Also, I vote no soup pot if Sam brings medium pot.\nJules: Host said large preferred, not required. Medium is okay.\nPriya: I’ll carry the medium pot if Sam handles the bike.\nSam: Deal.\nTheo: I’ll bring coffee and those card games Mara likes.\nMara: I like one card game. The bird one. Not the tiny betrayal one.\nTheo: The tiny betrayal one is staying home after last time.\nPriya: Thank you. It changed the room’s entire temperature.\nJules: Focus: I’ll buy tickets at 10:05 if code works. Backup if it fails?\nSam: Buy anyway? Prices went up yesterday.\nMara: I agree. Buy anyway, but message us the total first if it’s more than 55 each.\nTheo: Cap at 60 for me.\nPriya: Same. If it’s over 60, I’ll take the later train and complain privately.\nJules: So cap is 60 per person. If under or equal, I purchase. If over, I pause.\nMara: Yes.\nSam: Yes.\nTheo: Yes, and forward-facing if possible.\nPriya: Near luggage if possible.\nJules: I cannot promise train geometry, but I will try.\nMara: Also check-in at the cottage is 4 pm, right?\nSam: 5 pm, I think.\nPriya: Email says keys available from 4:30 at the side door.\nJules: I’ll add that to the shared note.\nTheo: There is a shared note?\nMara: Theo, you commented in it with a pancake emoji.\nTheo: That could have been any document.\nPriya: No, it was very specifically this one.\nJules: Final for now: I buy five 6:40 tickets tonight if price is 60 or less each. Sam brings bike and medium pot. Priya carries pot from station. Theo brings coffee and bird card game. Mara pays me back tonight and reminds Anika to confirm by Thursday noon.\nMara: I did not volunteer for Anika duty, but fine, I’ll text her.\nSam: Thank you, chair-in-progress.\nMara: I am already furniture."
                }
            ]
        })


asyncio.run(main())

curl https://api.runware.ai/v1 \
  -H "Authorization: Bearer $RUNWARE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '[
    {
      "taskType": "textInference",
      "taskUUID": "447157f9-bbc2-4970-b8d0-c85996f2c927",
      "model": "google:gemma@4-31b",
      "settings": {
        "systemPrompt": "You are a careful conversation analyst. Read informal human dialogue, preserve nuance, identify facts versus assumptions, and produce structured, practical outputs without inventing details.",
        "temperature": 0.35,
        "topP": 0.9,
        "thinkingLevel": "high",
        "maxTokens": 8192
      },
      "messages": [
        {
          "role": "user",
          "content": "Analyze this random conversation by humans. Return: 1) a 5-sentence plain-language summary, 2) confirmed decisions, 3) unresolved questions, 4) contradictions or timeline conflicts, 5) each person’s likely responsibilities, 6) any emotional subtext, and 7) a polished follow-up message that Jules could send to the group.\n\nConversation:\n\nMara: Did anyone actually book the train yet, or are we still pretending someone else did it?\nTheo: I looked at seats but didn’t pay because Jules said they had a discount code.\nJules: I have a code, yes, but it only works after 10 pm for some reason. Don’t ask me why.\nPriya: That sounds fake but also exactly like a train company.\nSam: If we leave Friday at 6:40, I can bring the folding bike. If we leave at 8:15, no bike because the storage slots are gone.\nMara: Why are we bringing a bike to a cooking class weekend?\nSam: Because the cottage is two miles from the station and Priya said she refuses to walk with bags.\nPriya: I said I refuse to walk with the soup pot, not bags.\nTheo: Why is there a soup pot?\nJules: The host asked us to bring one large pot if possible. I posted that yesterday.\nMara: You posted a screenshot with half the text cut off.\nJules: It was readable if you opened it.\nTheo: It was readable if you had a telescope.\nSam: I can bring my medium pot if that solves the bike issue.\nPriya: Medium pot is probably fine unless we’re feeding a sports team.\nMara: The host said six people, right?\nJules: Five of us plus Anika, if she confirms.\nTheo: Anika told me she can’t come because her dog has stitches.\nPriya: She told me she might come late Saturday if her sister can watch the dog.\nSam: So we need a ticket for Anika or not?\nJules: Not until she confirms. The discount code can handle separate purchases.\nMara: Please do not make us buy five tickets and then discover we needed six together.\nTheo: Group fare starts at six, so five versus six matters.\nJules: Wait, I thought group fare started at five.\nPriya: Website says six adults. I’m looking right now.\nSam: We are not adults emotionally, but yes.\nMara: Can someone make one decision before I turn into a chair.\nJules: Proposal: I check the code at 10:05 tonight. If it works, I buy five tickets for the 6:40 Friday train. Anika buys her own later if she comes.\nTheo: Works for me, but only if I’m not sitting backward. Last time was grim.\nPriya: I don’t care about direction. I care about being near the luggage rack.\nSam: And I need the bike slot if we’re doing the 6:40.\nMara: I can pay Jules back tonight. Also, I vote no soup pot if Sam brings medium pot.\nJules: Host said large preferred, not required. Medium is okay.\nPriya: I’ll carry the medium pot if Sam handles the bike.\nSam: Deal.\nTheo: I’ll bring coffee and those card games Mara likes.\nMara: I like one card game. The bird one. Not the tiny betrayal one.\nTheo: The tiny betrayal one is staying home after last time.\nPriya: Thank you. It changed the room’s entire temperature.\nJules: Focus: I’ll buy tickets at 10:05 if code works. Backup if it fails?\nSam: Buy anyway? Prices went up yesterday.\nMara: I agree. Buy anyway, but message us the total first if it’s more than 55 each.\nTheo: Cap at 60 for me.\nPriya: Same. If it’s over 60, I’ll take the later train and complain privately.\nJules: So cap is 60 per person. If under or equal, I purchase. If over, I pause.\nMara: Yes.\nSam: Yes.\nTheo: Yes, and forward-facing if possible.\nPriya: Near luggage if possible.\nJules: I cannot promise train geometry, but I will try.\nMara: Also check-in at the cottage is 4 pm, right?\nSam: 5 pm, I think.\nPriya: Email says keys available from 4:30 at the side door.\nJules: I’ll add that to the shared note.\nTheo: There is a shared note?\nMara: Theo, you commented in it with a pancake emoji.\nTheo: That could have been any document.\nPriya: No, it was very specifically this one.\nJules: Final for now: I buy five 6:40 tickets tonight if price is 60 or less each. Sam brings bike and medium pot. Priya carries pot from station. Theo brings coffee and bird card game. Mara pays me back tonight and reminds Anika to confirm by Thursday noon.\nMara: I did not volunteer for Anika duty, but fine, I’ll text her.\nSam: Thank you, chair-in-progress.\nMara: I am already furniture."
        }
      ]
    }
  ]'

runware run google:gemma@4-31b \
  settings.systemPrompt="You are a careful conversation analyst. Read informal human dialogue, preserve nuance, identify facts versus assumptions, and produce structured, practical outputs without inventing details." \
  settings.temperature=0.35 \
  settings.topP=0.9 \
  settings.thinkingLevel=high \
  settings.maxTokens=8192 \
  messages.0.role=user \
  messages.0.content="Analyze this random conversation by humans. Return: 1) a 5-sentence plain-language summary, 2) confirmed decisions, 3) unresolved questions, 4) contradictions or timeline conflicts, 5) each person’s likely responsibilities, 6) any emotional subtext, and 7) a polished follow-up message that Jules could send to the group.

Conversation:

Mara: Did anyone actually book the train yet, or are we still pretending someone else did it?
Theo: I looked at seats but didn’t pay because Jules said they had a discount code.
Jules: I have a code, yes, but it only works after 10 pm for some reason. Don’t ask me why.
Priya: That sounds fake but also exactly like a train company.
Sam: If we leave Friday at 6:40, I can bring the folding bike. If we leave at 8:15, no bike because the storage slots are gone.
Mara: Why are we bringing a bike to a cooking class weekend?
Sam: Because the cottage is two miles from the station and Priya said she refuses to walk with bags.
Priya: I said I refuse to walk with the soup pot, not bags.
Theo: Why is there a soup pot?
Jules: The host asked us to bring one large pot if possible. I posted that yesterday.
Mara: You posted a screenshot with half the text cut off.
Jules: It was readable if you opened it.
Theo: It was readable if you had a telescope.
Sam: I can bring my medium pot if that solves the bike issue.
Priya: Medium pot is probably fine unless we’re feeding a sports team.
Mara: The host said six people, right?
Jules: Five of us plus Anika, if she confirms.
Theo: Anika told me she can’t come because her dog has stitches.
Priya: She told me she might come late Saturday if her sister can watch the dog.
Sam: So we need a ticket for Anika or not?
Jules: Not until she confirms. The discount code can handle separate purchases.
Mara: Please do not make us buy five tickets and then discover we needed six together.
Theo: Group fare starts at six, so five versus six matters.
Jules: Wait, I thought group fare started at five.
Priya: Website says six adults. I’m looking right now.
Sam: We are not adults emotionally, but yes.
Mara: Can someone make one decision before I turn into a chair.
Jules: Proposal: I check the code at 10:05 tonight. If it works, I buy five tickets for the 6:40 Friday train. Anika buys her own later if she comes.
Theo: Works for me, but only if I’m not sitting backward. Last time was grim.
Priya: I don’t care about direction. I care about being near the luggage rack.
Sam: And I need the bike slot if we’re doing the 6:40.
Mara: I can pay Jules back tonight. Also, I vote no soup pot if Sam brings medium pot.
Jules: Host said large preferred, not required. Medium is okay.
Priya: I’ll carry the medium pot if Sam handles the bike.
Sam: Deal.
Theo: I’ll bring coffee and those card games Mara likes.
Mara: I like one card game. The bird one. Not the tiny betrayal one.
Theo: The tiny betrayal one is staying home after last time.
Priya: Thank you. It changed the room’s entire temperature.
Jules: Focus: I’ll buy tickets at 10:05 if code works. Backup if it fails?
Sam: Buy anyway? Prices went up yesterday.
Mara: I agree. Buy anyway, but message us the total first if it’s more than 55 each.
Theo: Cap at 60 for me.
Priya: Same. If it’s over 60, I’ll take the later train and complain privately.
Jules: So cap is 60 per person. If under or equal, I purchase. If over, I pause.
Mara: Yes.
Sam: Yes.
Theo: Yes, and forward-facing if possible.
Priya: Near luggage if possible.
Jules: I cannot promise train geometry, but I will try.
Mara: Also check-in at the cottage is 4 pm, right?
Sam: 5 pm, I think.
Priya: Email says keys available from 4:30 at the side door.
Jules: I’ll add that to the shared note.
Theo: There is a shared note?
Mara: Theo, you commented in it with a pancake emoji.
Theo: That could have been any document.
Priya: No, it was very specifically this one.
Jules: Final for now: I buy five 6:40 tickets tonight if price is 60 or less each. Sam brings bike and medium pot. Priya carries pot from station. Theo brings coffee and bird card game. Mara pays me back tonight and reminds Anika to confirm by Thursday noon.
Mara: I did not volunteer for Anika duty, but fine, I’ll text her.
Sam: Thank you, chair-in-progress.
Mara: I am already furniture."

{
  "taskType": "textInference",
  "taskUUID": "447157f9-bbc2-4970-b8d0-c85996f2c927",
  "model": "google:gemma@4-31b",
  "settings": {
    "systemPrompt": "You are a careful conversation analyst. Read informal human dialogue, preserve nuance, identify facts versus assumptions, and produce structured, practical outputs without inventing details.",
    "temperature": 0.35,
    "topP": 0.9,
    "thinkingLevel": "high",
    "maxTokens": 8192
  },
  "messages": [
    {
      "role": "user",
      "content": "Analyze this random conversation by humans. Return: 1) a 5-sentence plain-language summary, 2) confirmed decisions, 3) unresolved questions, 4) contradictions or timeline conflicts, 5) each person’s likely responsibilities, 6) any emotional subtext, and 7) a polished follow-up message that Jules could send to the group.\n\nConversation:\n\nMara: Did anyone actually book the train yet, or are we still pretending someone else did it?\nTheo: I looked at seats but didn’t pay because Jules said they had a discount code.\nJules: I have a code, yes, but it only works after 10 pm for some reason. Don’t ask me why.\nPriya: That sounds fake but also exactly like a train company.\nSam: If we leave Friday at 6:40, I can bring the folding bike. If we leave at 8:15, no bike because the storage slots are gone.\nMara: Why are we bringing a bike to a cooking class weekend?\nSam: Because the cottage is two miles from the station and Priya said she refuses to walk with bags.\nPriya: I said I refuse to walk with the soup pot, not bags.\nTheo: Why is there a soup pot?\nJules: The host asked us to bring one large pot if possible. I posted that yesterday.\nMara: You posted a screenshot with half the text cut off.\nJules: It was readable if you opened it.\nTheo: It was readable if you had a telescope.\nSam: I can bring my medium pot if that solves the bike issue.\nPriya: Medium pot is probably fine unless we’re feeding a sports team.\nMara: The host said six people, right?\nJules: Five of us plus Anika, if she confirms.\nTheo: Anika told me she can’t come because her dog has stitches.\nPriya: She told me she might come late Saturday if her sister can watch the dog.\nSam: So we need a ticket for Anika or not?\nJules: Not until she confirms. The discount code can handle separate purchases.\nMara: Please do not make us buy five tickets and then discover we needed six together.\nTheo: Group fare starts at six, so five versus six matters.\nJules: Wait, I thought group fare started at five.\nPriya: Website says six adults. I’m looking right now.\nSam: We are not adults emotionally, but yes.\nMara: Can someone make one decision before I turn into a chair.\nJules: Proposal: I check the code at 10:05 tonight. If it works, I buy five tickets for the 6:40 Friday train. Anika buys her own later if she comes.\nTheo: Works for me, but only if I’m not sitting backward. Last time was grim.\nPriya: I don’t care about direction. I care about being near the luggage rack.\nSam: And I need the bike slot if we’re doing the 6:40.\nMara: I can pay Jules back tonight. Also, I vote no soup pot if Sam brings medium pot.\nJules: Host said large preferred, not required. Medium is okay.\nPriya: I’ll carry the medium pot if Sam handles the bike.\nSam: Deal.\nTheo: I’ll bring coffee and those card games Mara likes.\nMara: I like one card game. The bird one. Not the tiny betrayal one.\nTheo: The tiny betrayal one is staying home after last time.\nPriya: Thank you. It changed the room’s entire temperature.\nJules: Focus: I’ll buy tickets at 10:05 if code works. Backup if it fails?\nSam: Buy anyway? Prices went up yesterday.\nMara: I agree. Buy anyway, but message us the total first if it’s more than 55 each.\nTheo: Cap at 60 for me.\nPriya: Same. If it’s over 60, I’ll take the later train and complain privately.\nJules: So cap is 60 per person. If under or equal, I purchase. If over, I pause.\nMara: Yes.\nSam: Yes.\nTheo: Yes, and forward-facing if possible.\nPriya: Near luggage if possible.\nJules: I cannot promise train geometry, but I will try.\nMara: Also check-in at the cottage is 4 pm, right?\nSam: 5 pm, I think.\nPriya: Email says keys available from 4:30 at the side door.\nJules: I’ll add that to the shared note.\nTheo: There is a shared note?\nMara: Theo, you commented in it with a pancake emoji.\nTheo: That could have been any document.\nPriya: No, it was very specifically this one.\nJules: Final for now: I buy five 6:40 tickets tonight if price is 60 or less each. Sam brings bike and medium pot. Priya carries pot from station. Theo brings coffee and bird card game. Mara pays me back tonight and reminds Anika to confirm by Thursday noon.\nMara: I did not volunteer for Anika duty, but fine, I’ll text her.\nSam: Thank you, chair-in-progress.\nMara: I am already furniture."
    }
  ]
}

import { createClient } from '@runware/sdk'

const client = await createClient({ apiKey: process.env.RUNWARE_API_KEY })
await client.connect()

const [result] = await client.run({
  model: 'google:gemma@4-31b',
  seed: 95423,
  settings: {
    systemPrompt: 'You are a precise analyst of informal human dialogue. Preserve uncertainty, distinguish facts from guesses, and produce useful structure without inventing details.',
    temperature: 0.35,
    topP: 0.9,
    maxTokens: 8192,
    thinkingLevel: 'high'
  },
  messages: [
    {
      role: 'user',
      content: 'Analyze the following random conversation by humans. The speakers are members of a small robotics lab taking a snack break before a demo. Their conversation wanders across personal updates, hardware issues, jokes, scheduling, and unresolved concerns.\n\nReturn:\n1. A 5-sentence executive summary.\n2. Confirmed decisions.\n3. Action items with owner, due date if implied, and confidence level.\n4. Open questions.\n5. Hidden risks or contradictions.\n6. A short follow-up message the team lead could send.\n\nConversation:\n\nMira: I swear the gripper only acts haunted when outside people are watching.\nJonas: That is not a diagnostic category, but yes, it waited until the sponsor badge scanner beeped.\nPriya: Please do not say haunted during the demo. Say intermittent calibration drift.\nTheo: Intermittent calibration drift sounds like the robot went to grad school.\nSam: It did better than I did in grad school. It at least finishes a path plan.\nMira: Speaking of path planning, did anyone merge the safer turn radius patch?\nJonas: I reviewed it. I did not merge it because Theo left a comment that just said, quote, spicy.\nTheo: That meant the math was suspicious, not bad. Like edible but too bold.\nPriya: We need a real answer. Demo is Thursday, not spiritually Thursday, actual Thursday.\nSam: I can rerun the sim tonight with the new radius and the old obstacle map.\nMira: Use the updated obstacle map. The old one still thinks the blue foam pillar exists.\nJonas: The blue foam pillar exists in my heart.\nPriya: It was thrown out in March.\nTheo: It blocked fewer routes than the portable whiteboard.\nSam: The whiteboard is load-bearing emotionally.\nMira: Focus. If Sam reruns sim tonight, can Jonas merge tomorrow morning if it passes?\nJonas: Yes, if the unit tests stop failing for that unrelated camera timestamp thing.\nPriya: Is it unrelated? The camera feeds time into pose correction, right?\nJonas: Related in the grand tapestry of suffering, unrelated to the turn radius.\nTheo: I can look at the timestamp bug after dinner. But I promised my sister I would help move a couch at eight.\nSam: Your sister has had that couch emergency for three weeks.\nTheo: It is a complex couch.\nMira: Fine. Theo checks timestamp before eight or after couch. Jonas merges after sim plus tests. Priya updates demo script language. I will reprint the safety card.\nPriya: Add the new emergency stop location. The button moved from the left rail to the front handle.\nSam: Did it actually move, or did we add a second one?\nMira: Added a second one. The left rail button still works.\nJonas: Unless someone unplugged the rail harness when cleaning cable slack.\nTheo: I did not unplug it. I did make it less octopus.\nPriya: Please verify both buttons before I write "two emergency stops" in anything.\nMira: Good catch. Sam, can you add that to tonight?\nSam: Yes, after sim. Also I need someone to bring the 6 mm hex key back. It vanished.\nTheo: I have a 5 mm, a 7 mm, and moral support.\nJonas: Check the drawer under the solder station.\nPriya: No soldering during visitor hours, by the way. Facilities reminded me.\nMira: Demo has no soldering. Ideally no smoke of any kind.\nSam: The motor driver smoke was one time.\nJonas: Twice, if you count the faint smell incident.\nTheo: I count vibes.\nPriya: Sponsors arrive at 2:15. We have a ten-minute welcome, five-minute safety note, then the robot sorts the sample parts.\nMira: Parts need labels removed. Last time it learned the labels instead of the shapes.\nSam: I can peel labels while sim runs. Glamorous night.\nJonas: Do not peel the red batch. Those are calibration references.\nSam: See, this is why casual peeling is dangerous.\nPriya: I will put tape on the bins: demo, calibration, do not touch.\nTheo: Tape is our best senior engineer.\nMira: Also, the robot voice needs to be off. It saying "nice cylinder" got too many laughs.\nJonas: That line was not in the release branch.\nSam: It was in the tiny joy branch.\nPriya: Delete tiny joy.\nTheo: Archive tiny joy.\nMira: Disable it for demo. Archive later if you must.\nJonas: I will check config. No voice, no experimental jokes, no unapproved gestures.\nSam: The wave gesture is approved, right?\nPriya: Only at the end, if the final bin count is correct.\nTheo: Conditional politeness.\nMira: Exactly. Anything else before we all pretend to be calm?\nJonas: Battery pack three is sagging under load. Pack two is fine. Pack one is charging.\nSam: Use pack two for rehearsal, pack one for demo?\nMira: Yes, unless pack one fails top-off. Then pack two gets protected like royalty.\nPriya: Who checks charging status Thursday morning?\nTheo: I can, if I am here by nine.\nMira: "If" is doing a lot there.\nTheo: I will be here by nine. The couch saga ends tonight.\nJonas: Famous last words.\nPriya: I am writing Theo: battery check, Thursday 9:00, confidence medium.\nTheo: Rude but fair.\nMira: Good. Now eat something real, not just prototype gummy bears.\nSam: They are normal gummy bears in a sample cup.\nJonas: In this lab, container changes meaning.\nPriya: That sentence is going in my memoir.'
    }
  ]
})

import asyncio
import os

from runware import Runware


async def main():
    async with Runware(api_key=os.environ["RUNWARE_API_KEY"]) as client:
        results = await client.run({
            "model": "google:gemma@4-31b",
            "seed": 95423,
            "settings": {
                "systemPrompt": "You are a precise analyst of informal human dialogue. Preserve uncertainty, distinguish facts from guesses, and produce useful structure without inventing details.",
                "temperature": 0.35,
                "topP": 0.9,
                "maxTokens": 8192,
                "thinkingLevel": "high"
            },
            "messages": [
                {
                    "role": "user",
                    "content": "Analyze the following random conversation by humans. The speakers are members of a small robotics lab taking a snack break before a demo. Their conversation wanders across personal updates, hardware issues, jokes, scheduling, and unresolved concerns.\n\nReturn:\n1. A 5-sentence executive summary.\n2. Confirmed decisions.\n3. Action items with owner, due date if implied, and confidence level.\n4. Open questions.\n5. Hidden risks or contradictions.\n6. A short follow-up message the team lead could send.\n\nConversation:\n\nMira: I swear the gripper only acts haunted when outside people are watching.\nJonas: That is not a diagnostic category, but yes, it waited until the sponsor badge scanner beeped.\nPriya: Please do not say haunted during the demo. Say intermittent calibration drift.\nTheo: Intermittent calibration drift sounds like the robot went to grad school.\nSam: It did better than I did in grad school. It at least finishes a path plan.\nMira: Speaking of path planning, did anyone merge the safer turn radius patch?\nJonas: I reviewed it. I did not merge it because Theo left a comment that just said, quote, spicy.\nTheo: That meant the math was suspicious, not bad. Like edible but too bold.\nPriya: We need a real answer. Demo is Thursday, not spiritually Thursday, actual Thursday.\nSam: I can rerun the sim tonight with the new radius and the old obstacle map.\nMira: Use the updated obstacle map. The old one still thinks the blue foam pillar exists.\nJonas: The blue foam pillar exists in my heart.\nPriya: It was thrown out in March.\nTheo: It blocked fewer routes than the portable whiteboard.\nSam: The whiteboard is load-bearing emotionally.\nMira: Focus. If Sam reruns sim tonight, can Jonas merge tomorrow morning if it passes?\nJonas: Yes, if the unit tests stop failing for that unrelated camera timestamp thing.\nPriya: Is it unrelated? The camera feeds time into pose correction, right?\nJonas: Related in the grand tapestry of suffering, unrelated to the turn radius.\nTheo: I can look at the timestamp bug after dinner. But I promised my sister I would help move a couch at eight.\nSam: Your sister has had that couch emergency for three weeks.\nTheo: It is a complex couch.\nMira: Fine. Theo checks timestamp before eight or after couch. Jonas merges after sim plus tests. Priya updates demo script language. I will reprint the safety card.\nPriya: Add the new emergency stop location. The button moved from the left rail to the front handle.\nSam: Did it actually move, or did we add a second one?\nMira: Added a second one. The left rail button still works.\nJonas: Unless someone unplugged the rail harness when cleaning cable slack.\nTheo: I did not unplug it. I did make it less octopus.\nPriya: Please verify both buttons before I write \"two emergency stops\" in anything.\nMira: Good catch. Sam, can you add that to tonight?\nSam: Yes, after sim. Also I need someone to bring the 6 mm hex key back. It vanished.\nTheo: I have a 5 mm, a 7 mm, and moral support.\nJonas: Check the drawer under the solder station.\nPriya: No soldering during visitor hours, by the way. Facilities reminded me.\nMira: Demo has no soldering. Ideally no smoke of any kind.\nSam: The motor driver smoke was one time.\nJonas: Twice, if you count the faint smell incident.\nTheo: I count vibes.\nPriya: Sponsors arrive at 2:15. We have a ten-minute welcome, five-minute safety note, then the robot sorts the sample parts.\nMira: Parts need labels removed. Last time it learned the labels instead of the shapes.\nSam: I can peel labels while sim runs. Glamorous night.\nJonas: Do not peel the red batch. Those are calibration references.\nSam: See, this is why casual peeling is dangerous.\nPriya: I will put tape on the bins: demo, calibration, do not touch.\nTheo: Tape is our best senior engineer.\nMira: Also, the robot voice needs to be off. It saying \"nice cylinder\" got too many laughs.\nJonas: That line was not in the release branch.\nSam: It was in the tiny joy branch.\nPriya: Delete tiny joy.\nTheo: Archive tiny joy.\nMira: Disable it for demo. Archive later if you must.\nJonas: I will check config. No voice, no experimental jokes, no unapproved gestures.\nSam: The wave gesture is approved, right?\nPriya: Only at the end, if the final bin count is correct.\nTheo: Conditional politeness.\nMira: Exactly. Anything else before we all pretend to be calm?\nJonas: Battery pack three is sagging under load. Pack two is fine. Pack one is charging.\nSam: Use pack two for rehearsal, pack one for demo?\nMira: Yes, unless pack one fails top-off. Then pack two gets protected like royalty.\nPriya: Who checks charging status Thursday morning?\nTheo: I can, if I am here by nine.\nMira: \"If\" is doing a lot there.\nTheo: I will be here by nine. The couch saga ends tonight.\nJonas: Famous last words.\nPriya: I am writing Theo: battery check, Thursday 9:00, confidence medium.\nTheo: Rude but fair.\nMira: Good. Now eat something real, not just prototype gummy bears.\nSam: They are normal gummy bears in a sample cup.\nJonas: In this lab, container changes meaning.\nPriya: That sentence is going in my memoir."
                }
            ]
        })


asyncio.run(main())

curl https://api.runware.ai/v1 \
  -H "Authorization: Bearer $RUNWARE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '[
    {
      "taskType": "textInference",
      "taskUUID": "b6b95602-2cc4-4af7-b2b5-656ffdd366f8",
      "model": "google:gemma@4-31b",
      "seed": 95423,
      "settings": {
        "systemPrompt": "You are a precise analyst of informal human dialogue. Preserve uncertainty, distinguish facts from guesses, and produce useful structure without inventing details.",
        "temperature": 0.35,
        "topP": 0.9,
        "maxTokens": 8192,
        "thinkingLevel": "high"
      },
      "messages": [
        {
          "role": "user",
          "content": "Analyze the following random conversation by humans. The speakers are members of a small robotics lab taking a snack break before a demo. Their conversation wanders across personal updates, hardware issues, jokes, scheduling, and unresolved concerns.\n\nReturn:\n1. A 5-sentence executive summary.\n2. Confirmed decisions.\n3. Action items with owner, due date if implied, and confidence level.\n4. Open questions.\n5. Hidden risks or contradictions.\n6. A short follow-up message the team lead could send.\n\nConversation:\n\nMira: I swear the gripper only acts haunted when outside people are watching.\nJonas: That is not a diagnostic category, but yes, it waited until the sponsor badge scanner beeped.\nPriya: Please do not say haunted during the demo. Say intermittent calibration drift.\nTheo: Intermittent calibration drift sounds like the robot went to grad school.\nSam: It did better than I did in grad school. It at least finishes a path plan.\nMira: Speaking of path planning, did anyone merge the safer turn radius patch?\nJonas: I reviewed it. I did not merge it because Theo left a comment that just said, quote, spicy.\nTheo: That meant the math was suspicious, not bad. Like edible but too bold.\nPriya: We need a real answer. Demo is Thursday, not spiritually Thursday, actual Thursday.\nSam: I can rerun the sim tonight with the new radius and the old obstacle map.\nMira: Use the updated obstacle map. The old one still thinks the blue foam pillar exists.\nJonas: The blue foam pillar exists in my heart.\nPriya: It was thrown out in March.\nTheo: It blocked fewer routes than the portable whiteboard.\nSam: The whiteboard is load-bearing emotionally.\nMira: Focus. If Sam reruns sim tonight, can Jonas merge tomorrow morning if it passes?\nJonas: Yes, if the unit tests stop failing for that unrelated camera timestamp thing.\nPriya: Is it unrelated? The camera feeds time into pose correction, right?\nJonas: Related in the grand tapestry of suffering, unrelated to the turn radius.\nTheo: I can look at the timestamp bug after dinner. But I promised my sister I would help move a couch at eight.\nSam: Your sister has had that couch emergency for three weeks.\nTheo: It is a complex couch.\nMira: Fine. Theo checks timestamp before eight or after couch. Jonas merges after sim plus tests. Priya updates demo script language. I will reprint the safety card.\nPriya: Add the new emergency stop location. The button moved from the left rail to the front handle.\nSam: Did it actually move, or did we add a second one?\nMira: Added a second one. The left rail button still works.\nJonas: Unless someone unplugged the rail harness when cleaning cable slack.\nTheo: I did not unplug it. I did make it less octopus.\nPriya: Please verify both buttons before I write \"two emergency stops\" in anything.\nMira: Good catch. Sam, can you add that to tonight?\nSam: Yes, after sim. Also I need someone to bring the 6 mm hex key back. It vanished.\nTheo: I have a 5 mm, a 7 mm, and moral support.\nJonas: Check the drawer under the solder station.\nPriya: No soldering during visitor hours, by the way. Facilities reminded me.\nMira: Demo has no soldering. Ideally no smoke of any kind.\nSam: The motor driver smoke was one time.\nJonas: Twice, if you count the faint smell incident.\nTheo: I count vibes.\nPriya: Sponsors arrive at 2:15. We have a ten-minute welcome, five-minute safety note, then the robot sorts the sample parts.\nMira: Parts need labels removed. Last time it learned the labels instead of the shapes.\nSam: I can peel labels while sim runs. Glamorous night.\nJonas: Do not peel the red batch. Those are calibration references.\nSam: See, this is why casual peeling is dangerous.\nPriya: I will put tape on the bins: demo, calibration, do not touch.\nTheo: Tape is our best senior engineer.\nMira: Also, the robot voice needs to be off. It saying \"nice cylinder\" got too many laughs.\nJonas: That line was not in the release branch.\nSam: It was in the tiny joy branch.\nPriya: Delete tiny joy.\nTheo: Archive tiny joy.\nMira: Disable it for demo. Archive later if you must.\nJonas: I will check config. No voice, no experimental jokes, no unapproved gestures.\nSam: The wave gesture is approved, right?\nPriya: Only at the end, if the final bin count is correct.\nTheo: Conditional politeness.\nMira: Exactly. Anything else before we all pretend to be calm?\nJonas: Battery pack three is sagging under load. Pack two is fine. Pack one is charging.\nSam: Use pack two for rehearsal, pack one for demo?\nMira: Yes, unless pack one fails top-off. Then pack two gets protected like royalty.\nPriya: Who checks charging status Thursday morning?\nTheo: I can, if I am here by nine.\nMira: \"If\" is doing a lot there.\nTheo: I will be here by nine. The couch saga ends tonight.\nJonas: Famous last words.\nPriya: I am writing Theo: battery check, Thursday 9:00, confidence medium.\nTheo: Rude but fair.\nMira: Good. Now eat something real, not just prototype gummy bears.\nSam: They are normal gummy bears in a sample cup.\nJonas: In this lab, container changes meaning.\nPriya: That sentence is going in my memoir."
        }
      ]
    }
  ]'

runware run google:gemma@4-31b \
  seed=95423 \
  settings.systemPrompt="You are a precise analyst of informal human dialogue. Preserve uncertainty, distinguish facts from guesses, and produce useful structure without inventing details." \
  settings.temperature=0.35 \
  settings.topP=0.9 \
  settings.maxTokens=8192 \
  settings.thinkingLevel=high \
  messages.0.role=user \
  messages.0.content="Analyze the following random conversation by humans. The speakers are members of a small robotics lab taking a snack break before a demo. Their conversation wanders across personal updates, hardware issues, jokes, scheduling, and unresolved concerns.

Return:
1. A 5-sentence executive summary.
2. Confirmed decisions.
3. Action items with owner, due date if implied, and confidence level.
4. Open questions.
5. Hidden risks or contradictions.
6. A short follow-up message the team lead could send.

Conversation:

Mira: I swear the gripper only acts haunted when outside people are watching.
Jonas: That is not a diagnostic category, but yes, it waited until the sponsor badge scanner beeped.
Priya: Please do not say haunted during the demo. Say intermittent calibration drift.
Theo: Intermittent calibration drift sounds like the robot went to grad school.
Sam: It did better than I did in grad school. It at least finishes a path plan.
Mira: Speaking of path planning, did anyone merge the safer turn radius patch?
Jonas: I reviewed it. I did not merge it because Theo left a comment that just said, quote, spicy.
Theo: That meant the math was suspicious, not bad. Like edible but too bold.
Priya: We need a real answer. Demo is Thursday, not spiritually Thursday, actual Thursday.
Sam: I can rerun the sim tonight with the new radius and the old obstacle map.
Mira: Use the updated obstacle map. The old one still thinks the blue foam pillar exists.
Jonas: The blue foam pillar exists in my heart.
Priya: It was thrown out in March.
Theo: It blocked fewer routes than the portable whiteboard.
Sam: The whiteboard is load-bearing emotionally.
Mira: Focus. If Sam reruns sim tonight, can Jonas merge tomorrow morning if it passes?
Jonas: Yes, if the unit tests stop failing for that unrelated camera timestamp thing.
Priya: Is it unrelated? The camera feeds time into pose correction, right?
Jonas: Related in the grand tapestry of suffering, unrelated to the turn radius.
Theo: I can look at the timestamp bug after dinner. But I promised my sister I would help move a couch at eight.
Sam: Your sister has had that couch emergency for three weeks.
Theo: It is a complex couch.
Mira: Fine. Theo checks timestamp before eight or after couch. Jonas merges after sim plus tests. Priya updates demo script language. I will reprint the safety card.
Priya: Add the new emergency stop location. The button moved from the left rail to the front handle.
Sam: Did it actually move, or did we add a second one?
Mira: Added a second one. The left rail button still works.
Jonas: Unless someone unplugged the rail harness when cleaning cable slack.
Theo: I did not unplug it. I did make it less octopus.
Priya: Please verify both buttons before I write \"two emergency stops\" in anything.
Mira: Good catch. Sam, can you add that to tonight?
Sam: Yes, after sim. Also I need someone to bring the 6 mm hex key back. It vanished.
Theo: I have a 5 mm, a 7 mm, and moral support.
Jonas: Check the drawer under the solder station.
Priya: No soldering during visitor hours, by the way. Facilities reminded me.
Mira: Demo has no soldering. Ideally no smoke of any kind.
Sam: The motor driver smoke was one time.
Jonas: Twice, if you count the faint smell incident.
Theo: I count vibes.
Priya: Sponsors arrive at 2:15. We have a ten-minute welcome, five-minute safety note, then the robot sorts the sample parts.
Mira: Parts need labels removed. Last time it learned the labels instead of the shapes.
Sam: I can peel labels while sim runs. Glamorous night.
Jonas: Do not peel the red batch. Those are calibration references.
Sam: See, this is why casual peeling is dangerous.
Priya: I will put tape on the bins: demo, calibration, do not touch.
Theo: Tape is our best senior engineer.
Mira: Also, the robot voice needs to be off. It saying \"nice cylinder\" got too many laughs.
Jonas: That line was not in the release branch.
Sam: It was in the tiny joy branch.
Priya: Delete tiny joy.
Theo: Archive tiny joy.
Mira: Disable it for demo. Archive later if you must.
Jonas: I will check config. No voice, no experimental jokes, no unapproved gestures.
Sam: The wave gesture is approved, right?
Priya: Only at the end, if the final bin count is correct.
Theo: Conditional politeness.
Mira: Exactly. Anything else before we all pretend to be calm?
Jonas: Battery pack three is sagging under load. Pack two is fine. Pack one is charging.
Sam: Use pack two for rehearsal, pack one for demo?
Mira: Yes, unless pack one fails top-off. Then pack two gets protected like royalty.
Priya: Who checks charging status Thursday morning?
Theo: I can, if I am here by nine.
Mira: \"If\" is doing a lot there.
Theo: I will be here by nine. The couch saga ends tonight.
Jonas: Famous last words.
Priya: I am writing Theo: battery check, Thursday 9:00, confidence medium.
Theo: Rude but fair.
Mira: Good. Now eat something real, not just prototype gummy bears.
Sam: They are normal gummy bears in a sample cup.
Jonas: In this lab, container changes meaning.
Priya: That sentence is going in my memoir."

{
  "taskType": "textInference",
  "taskUUID": "b6b95602-2cc4-4af7-b2b5-656ffdd366f8",
  "model": "google:gemma@4-31b",
  "seed": 95423,
  "settings": {
    "systemPrompt": "You are a precise analyst of informal human dialogue. Preserve uncertainty, distinguish facts from guesses, and produce useful structure without inventing details.",
    "temperature": 0.35,
    "topP": 0.9,
    "maxTokens": 8192,
    "thinkingLevel": "high"
  },
  "messages": [
    {
      "role": "user",
      "content": "Analyze the following random conversation by humans. The speakers are members of a small robotics lab taking a snack break before a demo. Their conversation wanders across personal updates, hardware issues, jokes, scheduling, and unresolved concerns.\n\nReturn:\n1. A 5-sentence executive summary.\n2. Confirmed decisions.\n3. Action items with owner, due date if implied, and confidence level.\n4. Open questions.\n5. Hidden risks or contradictions.\n6. A short follow-up message the team lead could send.\n\nConversation:\n\nMira: I swear the gripper only acts haunted when outside people are watching.\nJonas: That is not a diagnostic category, but yes, it waited until the sponsor badge scanner beeped.\nPriya: Please do not say haunted during the demo. Say intermittent calibration drift.\nTheo: Intermittent calibration drift sounds like the robot went to grad school.\nSam: It did better than I did in grad school. It at least finishes a path plan.\nMira: Speaking of path planning, did anyone merge the safer turn radius patch?\nJonas: I reviewed it. I did not merge it because Theo left a comment that just said, quote, spicy.\nTheo: That meant the math was suspicious, not bad. Like edible but too bold.\nPriya: We need a real answer. Demo is Thursday, not spiritually Thursday, actual Thursday.\nSam: I can rerun the sim tonight with the new radius and the old obstacle map.\nMira: Use the updated obstacle map. The old one still thinks the blue foam pillar exists.\nJonas: The blue foam pillar exists in my heart.\nPriya: It was thrown out in March.\nTheo: It blocked fewer routes than the portable whiteboard.\nSam: The whiteboard is load-bearing emotionally.\nMira: Focus. If Sam reruns sim tonight, can Jonas merge tomorrow morning if it passes?\nJonas: Yes, if the unit tests stop failing for that unrelated camera timestamp thing.\nPriya: Is it unrelated? The camera feeds time into pose correction, right?\nJonas: Related in the grand tapestry of suffering, unrelated to the turn radius.\nTheo: I can look at the timestamp bug after dinner. But I promised my sister I would help move a couch at eight.\nSam: Your sister has had that couch emergency for three weeks.\nTheo: It is a complex couch.\nMira: Fine. Theo checks timestamp before eight or after couch. Jonas merges after sim plus tests. Priya updates demo script language. I will reprint the safety card.\nPriya: Add the new emergency stop location. The button moved from the left rail to the front handle.\nSam: Did it actually move, or did we add a second one?\nMira: Added a second one. The left rail button still works.\nJonas: Unless someone unplugged the rail harness when cleaning cable slack.\nTheo: I did not unplug it. I did make it less octopus.\nPriya: Please verify both buttons before I write \"two emergency stops\" in anything.\nMira: Good catch. Sam, can you add that to tonight?\nSam: Yes, after sim. Also I need someone to bring the 6 mm hex key back. It vanished.\nTheo: I have a 5 mm, a 7 mm, and moral support.\nJonas: Check the drawer under the solder station.\nPriya: No soldering during visitor hours, by the way. Facilities reminded me.\nMira: Demo has no soldering. Ideally no smoke of any kind.\nSam: The motor driver smoke was one time.\nJonas: Twice, if you count the faint smell incident.\nTheo: I count vibes.\nPriya: Sponsors arrive at 2:15. We have a ten-minute welcome, five-minute safety note, then the robot sorts the sample parts.\nMira: Parts need labels removed. Last time it learned the labels instead of the shapes.\nSam: I can peel labels while sim runs. Glamorous night.\nJonas: Do not peel the red batch. Those are calibration references.\nSam: See, this is why casual peeling is dangerous.\nPriya: I will put tape on the bins: demo, calibration, do not touch.\nTheo: Tape is our best senior engineer.\nMira: Also, the robot voice needs to be off. It saying \"nice cylinder\" got too many laughs.\nJonas: That line was not in the release branch.\nSam: It was in the tiny joy branch.\nPriya: Delete tiny joy.\nTheo: Archive tiny joy.\nMira: Disable it for demo. Archive later if you must.\nJonas: I will check config. No voice, no experimental jokes, no unapproved gestures.\nSam: The wave gesture is approved, right?\nPriya: Only at the end, if the final bin count is correct.\nTheo: Conditional politeness.\nMira: Exactly. Anything else before we all pretend to be calm?\nJonas: Battery pack three is sagging under load. Pack two is fine. Pack one is charging.\nSam: Use pack two for rehearsal, pack one for demo?\nMira: Yes, unless pack one fails top-off. Then pack two gets protected like royalty.\nPriya: Who checks charging status Thursday morning?\nTheo: I can, if I am here by nine.\nMira: \"If\" is doing a lot there.\nTheo: I will be here by nine. The couch saga ends tonight.\nJonas: Famous last words.\nPriya: I am writing Theo: battery check, Thursday 9:00, confidence medium.\nTheo: Rude but fair.\nMira: Good. Now eat something real, not just prototype gummy bears.\nSam: They are normal gummy bears in a sample cup.\nJonas: In this lab, container changes meaning.\nPriya: That sentence is going in my memoir."
    }
  ]
}

import { createClient } from '@runware/sdk'

const client = await createClient({ apiKey: process.env.RUNWARE_API_KEY })
await client.connect()

const [result] = await client.run({
  model: 'google:gemma@4-31b',
  inputs: {
    images: [
      'https://assets.runware.ai/assets/inputs/4827db34-f4f0-4277-a5fe-a2b2f7288672.jpg'
    ],
    videos: [
      'https://assets.runware.ai/assets/inputs/f62fa264-2764-4ec4-b1a4-70c366fec9fd.mp4'
    ]
  },
  messages: [
    {
      role: 'user',
      content: 'Act as a senior EHS investigator for a distribution center. Analyze the attached ground-level inspection photograph and CCTV video together, then draft a concise near-miss investigation report that management can use at tomorrow\'s safety review.\n\nUse only details visible in the supplied media. Clearly separate direct observations from reasonable inferences, and state when something cannot be determined. Review the full video sequence and cite approximate timestamps for key moments.\n\nStructure the report as follows:\n1. Executive summary: 100–150 words explaining what occurred, the potential consequence, and the most urgent control.\n2. Evidence log: a table identifying the source, timestamp or image region, objective observation, and safety relevance.\n3. Event sequence: a chronological reconstruction from approach through recovery.\n4. Contributing factors: organize under people, equipment, environment, procedure, and supervision; do not assign blame or claim root causes unsupported by the media.\n5. Risk assessment: rate potential severity and recurrence likelihood as Low, Medium, High, or Critical, with a brief rationale.\n6. Corrective action plan: a prioritized table with action, control hierarchy level, owner role, target timeframe, and verification method. Include immediate 24-hour controls, 30-day improvements, and longer-term engineering options.\n7. Five questions investigators should ask witnesses or supervisors to close evidence gaps.\n\nCross-reference the photograph with the video—for example, determine whether sight-line obstructions, floor markings, mirror placement, pallet storage, lighting, traffic separation, or behavior visible in one source helps explain events in the other. Do not identify individuals or infer protected personal characteristics.'
    }
  ]
})

import asyncio
import os

from runware import Runware


async def main():
    async with Runware(api_key=os.environ["RUNWARE_API_KEY"]) as client:
        results = await client.run({
            "model": "google:gemma@4-31b",
            "inputs": {
                "images": [
                    "https://assets.runware.ai/assets/inputs/4827db34-f4f0-4277-a5fe-a2b2f7288672.jpg"
                ],
                "videos": [
                    "https://assets.runware.ai/assets/inputs/f62fa264-2764-4ec4-b1a4-70c366fec9fd.mp4"
                ]
            },
            "messages": [
                {
                    "role": "user",
                    "content": "Act as a senior EHS investigator for a distribution center. Analyze the attached ground-level inspection photograph and CCTV video together, then draft a concise near-miss investigation report that management can use at tomorrow's safety review.\n\nUse only details visible in the supplied media. Clearly separate direct observations from reasonable inferences, and state when something cannot be determined. Review the full video sequence and cite approximate timestamps for key moments.\n\nStructure the report as follows:\n1. Executive summary: 100–150 words explaining what occurred, the potential consequence, and the most urgent control.\n2. Evidence log: a table identifying the source, timestamp or image region, objective observation, and safety relevance.\n3. Event sequence: a chronological reconstruction from approach through recovery.\n4. Contributing factors: organize under people, equipment, environment, procedure, and supervision; do not assign blame or claim root causes unsupported by the media.\n5. Risk assessment: rate potential severity and recurrence likelihood as Low, Medium, High, or Critical, with a brief rationale.\n6. Corrective action plan: a prioritized table with action, control hierarchy level, owner role, target timeframe, and verification method. Include immediate 24-hour controls, 30-day improvements, and longer-term engineering options.\n7. Five questions investigators should ask witnesses or supervisors to close evidence gaps.\n\nCross-reference the photograph with the video—for example, determine whether sight-line obstructions, floor markings, mirror placement, pallet storage, lighting, traffic separation, or behavior visible in one source helps explain events in the other. Do not identify individuals or infer protected personal characteristics."
                }
            ]
        })


asyncio.run(main())

curl https://api.runware.ai/v1 \
  -H "Authorization: Bearer $RUNWARE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '[
    {
      "taskType": "textInference",
      "taskUUID": "75d463c3-5515-428c-b85e-fa75e047f84b",
      "model": "google:gemma@4-31b",
      "inputs": {
        "images": [
          "https://assets.runware.ai/assets/inputs/4827db34-f4f0-4277-a5fe-a2b2f7288672.jpg"
        ],
        "videos": [
          "https://assets.runware.ai/assets/inputs/f62fa264-2764-4ec4-b1a4-70c366fec9fd.mp4"
        ]
      },
      "messages": [
        {
          "role": "user",
          "content": "Act as a senior EHS investigator for a distribution center. Analyze the attached ground-level inspection photograph and CCTV video together, then draft a concise near-miss investigation report that management can use at tomorrow's safety review.\n\nUse only details visible in the supplied media. Clearly separate direct observations from reasonable inferences, and state when something cannot be determined. Review the full video sequence and cite approximate timestamps for key moments.\n\nStructure the report as follows:\n1. Executive summary: 100–150 words explaining what occurred, the potential consequence, and the most urgent control.\n2. Evidence log: a table identifying the source, timestamp or image region, objective observation, and safety relevance.\n3. Event sequence: a chronological reconstruction from approach through recovery.\n4. Contributing factors: organize under people, equipment, environment, procedure, and supervision; do not assign blame or claim root causes unsupported by the media.\n5. Risk assessment: rate potential severity and recurrence likelihood as Low, Medium, High, or Critical, with a brief rationale.\n6. Corrective action plan: a prioritized table with action, control hierarchy level, owner role, target timeframe, and verification method. Include immediate 24-hour controls, 30-day improvements, and longer-term engineering options.\n7. Five questions investigators should ask witnesses or supervisors to close evidence gaps.\n\nCross-reference the photograph with the video—for example, determine whether sight-line obstructions, floor markings, mirror placement, pallet storage, lighting, traffic separation, or behavior visible in one source helps explain events in the other. Do not identify individuals or infer protected personal characteristics."
        }
      ]
    }
  ]'

runware run google:gemma@4-31b \
  inputs.images.0=https://assets.runware.ai/assets/inputs/4827db34-f4f0-4277-a5fe-a2b2f7288672.jpg \
  inputs.videos.0=https://assets.runware.ai/assets/inputs/f62fa264-2764-4ec4-b1a4-70c366fec9fd.mp4 \
  messages.0.role=user \
  messages.0.content="Act as a senior EHS investigator for a distribution center. Analyze the attached ground-level inspection photograph and CCTV video together, then draft a concise near-miss investigation report that management can use at tomorrow's safety review.

Use only details visible in the supplied media. Clearly separate direct observations from reasonable inferences, and state when something cannot be determined. Review the full video sequence and cite approximate timestamps for key moments.

Structure the report as follows:
1. Executive summary: 100–150 words explaining what occurred, the potential consequence, and the most urgent control.
2. Evidence log: a table identifying the source, timestamp or image region, objective observation, and safety relevance.
3. Event sequence: a chronological reconstruction from approach through recovery.
4. Contributing factors: organize under people, equipment, environment, procedure, and supervision; do not assign blame or claim root causes unsupported by the media.
5. Risk assessment: rate potential severity and recurrence likelihood as Low, Medium, High, or Critical, with a brief rationale.
6. Corrective action plan: a prioritized table with action, control hierarchy level, owner role, target timeframe, and verification method. Include immediate 24-hour controls, 30-day improvements, and longer-term engineering options.
7. Five questions investigators should ask witnesses or supervisors to close evidence gaps.

Cross-reference the photograph with the video—for example, determine whether sight-line obstructions, floor markings, mirror placement, pallet storage, lighting, traffic separation, or behavior visible in one source helps explain events in the other. Do not identify individuals or infer protected personal characteristics."

{
  "taskType": "textInference",
  "taskUUID": "75d463c3-5515-428c-b85e-fa75e047f84b",
  "model": "google:gemma@4-31b",
  "inputs": {
    "images": [
      "https://assets.runware.ai/assets/inputs/4827db34-f4f0-4277-a5fe-a2b2f7288672.jpg"
    ],
    "videos": [
      "https://assets.runware.ai/assets/inputs/f62fa264-2764-4ec4-b1a4-70c366fec9fd.mp4"
    ]
  },
  "messages": [
    {
      "role": "user",
      "content": "Act as a senior EHS investigator for a distribution center. Analyze the attached ground-level inspection photograph and CCTV video together, then draft a concise near-miss investigation report that management can use at tomorrow's safety review.\n\nUse only details visible in the supplied media. Clearly separate direct observations from reasonable inferences, and state when something cannot be determined. Review the full video sequence and cite approximate timestamps for key moments.\n\nStructure the report as follows:\n1. Executive summary: 100–150 words explaining what occurred, the potential consequence, and the most urgent control.\n2. Evidence log: a table identifying the source, timestamp or image region, objective observation, and safety relevance.\n3. Event sequence: a chronological reconstruction from approach through recovery.\n4. Contributing factors: organize under people, equipment, environment, procedure, and supervision; do not assign blame or claim root causes unsupported by the media.\n5. Risk assessment: rate potential severity and recurrence likelihood as Low, Medium, High, or Critical, with a brief rationale.\n6. Corrective action plan: a prioritized table with action, control hierarchy level, owner role, target timeframe, and verification method. Include immediate 24-hour controls, 30-day improvements, and longer-term engineering options.\n7. Five questions investigators should ask witnesses or supervisors to close evidence gaps.\n\nCross-reference the photograph with the video—for example, determine whether sight-line obstructions, floor markings, mirror placement, pallet storage, lighting, traffic separation, or behavior visible in one source helps explain events in the other. Do not identify individuals or infer protected personal characteristics."
    }
  ]
}

import { createClient } from '@runware/sdk'

const client = await createClient({ apiKey: process.env.RUNWARE_API_KEY })
await client.connect()

const [result] = await client.run({
  model: 'google:gemma@4-31b',
  messages: [
    {
      role: 'user',
      content: 'Act as the lead interpretive writer for a maritime museum. Create the final gallery text package for “North by Necessity,” a small exhibition about the 1884 rescue of the Greely Arctic expedition. The writing must be historically responsible, engaging for general visitors, and ready for curatorial review.\n\nUse only the verified dossier below. Do not introduce quotations, motives, dates, Indigenous names, technical specifications, or other facts that are not supplied. Where the evidence does not support certainty, use appropriately qualified language.\n\nVERIFIED DOSSIER\n- In 1881, U.S. Army First Lieutenant Adolphus Greely led 25 men to Lady Franklin Bay on Ellesmere Island as part of the First International Polar Year.\n- The party established Fort Conger and conducted meteorological, astronomical, magnetic, tidal, and geographic observations.\n- In 1882 and 1883, scheduled relief ships failed to reach the party because of ice and poor decisions within the relief efforts.\n- Following written orders, Greely’s party abandoned Fort Conger in August 1883 and traveled south. They eventually established a camp at Cape Sabine.\n- Food caches expected near Cape Sabine were inadequate. The party faced extreme hunger, cold, illness, isolation, and internal conflict.\n- Several earlier rescue attempts failed. In 1884, the U.S. Navy organized another expedition under Commander Winfield Scott Schley.\n- Schley’s squadron included the steam-powered ships Thetis, Bear, and Alert. Bear and Thetis reached Cape Sabine on June 22, 1884.\n- Rescuers found seven men alive; one of those seven, Joseph Elison, died during the return voyage. Of the original 25, six ultimately returned alive.\n- Recovery of scientific records was considered an important outcome of the expedition.\n- The expedition took place in an Arctic homeland that was already known, traveled, and inhabited by Indigenous peoples. Nineteenth-century U.S. accounts often described such regions as “unknown” or “unexplored,” language that reflected outsiders’ perspectives rather than an absence of existing knowledge.\n- The exhibition contains these four objects:\n  1. A brass-and-glass aneroid barometer used for field observation, maker unknown, circa 1880.\n  2. A water-stained page from a meteorological observation ledger kept at Fort Conger in February 1882; it records temperature, pressure, cloud cover, and wind.\n  3. A blue wool uniform coat attributed to Winfield Scott Schley and worn during the 1884 rescue expedition; attribution is supported by family provenance but is not conclusive.\n  4. An 1885 newspaper engraving depicting the survivors’ arrival in Portsmouth, New Hampshire. It was produced after the event for a mass audience and should be treated as a mediated representation, not an eyewitness record.\n\nAUDIENCE AND VOICE\n- Primary audience: visitors aged 14 and older with no prior knowledge of the event.\n- Reading level: approximately U.S. grade 8.\n- Tone: restrained, humane, vivid, and precise—not triumphalist, sensational, or melodramatic.\n- Center survival and scientific work without turning suffering into spectacle.\n- Do not frame the Arctic as empty, conquered, or waiting to be discovered.\n- Explain unfamiliar terms in context. Prefer short sentences and active voice.\n- Avoid rhetorical questions, exclamation points, invented scene-setting, and clichés such as “frozen wasteland,” “race against time,” or “against all odds.”\n- Refer to the group as “the Greely party,” not “Greely’s men,” except where grammar makes that impossible.\n\nDELIVERABLES\n1. Exhibition title and subtitle. Retain “North by Necessity” as the title and write a subtitle of no more than 12 words.\n2. Introductory panel: 170–190 words. Establish the scientific mission, failed relief efforts, move to Cape Sabine, rescue, human cost, and the need to question period ideas of “exploration.”\n3. Section panel, “Measuring the Arctic”: 105–125 words. Explain why sustained observations mattered and how routine recordkeeping continued under difficult conditions.\n4. Section panel, “Relief Delayed”: 105–125 words. Clarify that the disaster resulted from both environmental hazards and human decisions. Avoid assigning blame beyond the dossier.\n5. Section panel, “Rescue and Return”: 105–125 words. Describe Schley’s expedition, the June 22 rescue, the number of survivors, and the recovery of records without presenting the outcome as an uncomplicated victory.\n6. Four object labels, one for each listed object, each 65–80 words. Begin each label with a display heading of no more than six words. For the coat, clearly communicate the uncertain attribution. For the engraving, teach visitors why a published image is not neutral evidence.\n7. A family conversation prompt of 35–45 words that invites observation and discussion without using a rhetorical question. It should work beside the ledger and barometer.\n8. A 90–110 word accessibility-oriented visual description of the newspaper engraving. Because no image is provided, limit the description to what can responsibly be inferred from the dossier: medium, subject, publication context, and evidentiary limits. Explicitly state that composition and depicted details must be confirmed against the physical object before publication.\n9. A curator review table with columns: “Copy location,” “Claim or wording needing review,” and “Reason.” Flag at least four issues, including Indigenous context, the coat attribution, the engraving’s evidentiary status, and survivor totals.\n\nFORMAT\nPresent the finished package in the deliverable order above with clear headings. Put word counts in parentheses after every panel, label, prompt, and visual description. Do not include citations in visitor-facing copy. After the visitor-facing materials, include the curator review table and then a brief style-compliance checklist confirming that all required facts, cautions, and word limits have been addressed.'
    }
  ]
})

import asyncio
import os

from runware import Runware


async def main():
    async with Runware(api_key=os.environ["RUNWARE_API_KEY"]) as client:
        results = await client.run({
            "model": "google:gemma@4-31b",
            "messages": [
                {
                    "role": "user",
                    "content": "Act as the lead interpretive writer for a maritime museum. Create the final gallery text package for “North by Necessity,” a small exhibition about the 1884 rescue of the Greely Arctic expedition. The writing must be historically responsible, engaging for general visitors, and ready for curatorial review.\n\nUse only the verified dossier below. Do not introduce quotations, motives, dates, Indigenous names, technical specifications, or other facts that are not supplied. Where the evidence does not support certainty, use appropriately qualified language.\n\nVERIFIED DOSSIER\n- In 1881, U.S. Army First Lieutenant Adolphus Greely led 25 men to Lady Franklin Bay on Ellesmere Island as part of the First International Polar Year.\n- The party established Fort Conger and conducted meteorological, astronomical, magnetic, tidal, and geographic observations.\n- In 1882 and 1883, scheduled relief ships failed to reach the party because of ice and poor decisions within the relief efforts.\n- Following written orders, Greely’s party abandoned Fort Conger in August 1883 and traveled south. They eventually established a camp at Cape Sabine.\n- Food caches expected near Cape Sabine were inadequate. The party faced extreme hunger, cold, illness, isolation, and internal conflict.\n- Several earlier rescue attempts failed. In 1884, the U.S. Navy organized another expedition under Commander Winfield Scott Schley.\n- Schley’s squadron included the steam-powered ships Thetis, Bear, and Alert. Bear and Thetis reached Cape Sabine on June 22, 1884.\n- Rescuers found seven men alive; one of those seven, Joseph Elison, died during the return voyage. Of the original 25, six ultimately returned alive.\n- Recovery of scientific records was considered an important outcome of the expedition.\n- The expedition took place in an Arctic homeland that was already known, traveled, and inhabited by Indigenous peoples. Nineteenth-century U.S. accounts often described such regions as “unknown” or “unexplored,” language that reflected outsiders’ perspectives rather than an absence of existing knowledge.\n- The exhibition contains these four objects:\n  1. A brass-and-glass aneroid barometer used for field observation, maker unknown, circa 1880.\n  2. A water-stained page from a meteorological observation ledger kept at Fort Conger in February 1882; it records temperature, pressure, cloud cover, and wind.\n  3. A blue wool uniform coat attributed to Winfield Scott Schley and worn during the 1884 rescue expedition; attribution is supported by family provenance but is not conclusive.\n  4. An 1885 newspaper engraving depicting the survivors’ arrival in Portsmouth, New Hampshire. It was produced after the event for a mass audience and should be treated as a mediated representation, not an eyewitness record.\n\nAUDIENCE AND VOICE\n- Primary audience: visitors aged 14 and older with no prior knowledge of the event.\n- Reading level: approximately U.S. grade 8.\n- Tone: restrained, humane, vivid, and precise—not triumphalist, sensational, or melodramatic.\n- Center survival and scientific work without turning suffering into spectacle.\n- Do not frame the Arctic as empty, conquered, or waiting to be discovered.\n- Explain unfamiliar terms in context. Prefer short sentences and active voice.\n- Avoid rhetorical questions, exclamation points, invented scene-setting, and clichés such as “frozen wasteland,” “race against time,” or “against all odds.”\n- Refer to the group as “the Greely party,” not “Greely’s men,” except where grammar makes that impossible.\n\nDELIVERABLES\n1. Exhibition title and subtitle. Retain “North by Necessity” as the title and write a subtitle of no more than 12 words.\n2. Introductory panel: 170–190 words. Establish the scientific mission, failed relief efforts, move to Cape Sabine, rescue, human cost, and the need to question period ideas of “exploration.”\n3. Section panel, “Measuring the Arctic”: 105–125 words. Explain why sustained observations mattered and how routine recordkeeping continued under difficult conditions.\n4. Section panel, “Relief Delayed”: 105–125 words. Clarify that the disaster resulted from both environmental hazards and human decisions. Avoid assigning blame beyond the dossier.\n5. Section panel, “Rescue and Return”: 105–125 words. Describe Schley’s expedition, the June 22 rescue, the number of survivors, and the recovery of records without presenting the outcome as an uncomplicated victory.\n6. Four object labels, one for each listed object, each 65–80 words. Begin each label with a display heading of no more than six words. For the coat, clearly communicate the uncertain attribution. For the engraving, teach visitors why a published image is not neutral evidence.\n7. A family conversation prompt of 35–45 words that invites observation and discussion without using a rhetorical question. It should work beside the ledger and barometer.\n8. A 90–110 word accessibility-oriented visual description of the newspaper engraving. Because no image is provided, limit the description to what can responsibly be inferred from the dossier: medium, subject, publication context, and evidentiary limits. Explicitly state that composition and depicted details must be confirmed against the physical object before publication.\n9. A curator review table with columns: “Copy location,” “Claim or wording needing review,” and “Reason.” Flag at least four issues, including Indigenous context, the coat attribution, the engraving’s evidentiary status, and survivor totals.\n\nFORMAT\nPresent the finished package in the deliverable order above with clear headings. Put word counts in parentheses after every panel, label, prompt, and visual description. Do not include citations in visitor-facing copy. After the visitor-facing materials, include the curator review table and then a brief style-compliance checklist confirming that all required facts, cautions, and word limits have been addressed."
                }
            ]
        })


asyncio.run(main())

curl https://api.runware.ai/v1 \
  -H "Authorization: Bearer $RUNWARE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '[
    {
      "taskType": "textInference",
      "taskUUID": "78feeb31-af15-4993-82be-984eb368c5da",
      "model": "google:gemma@4-31b",
      "messages": [
        {
          "role": "user",
          "content": "Act as the lead interpretive writer for a maritime museum. Create the final gallery text package for “North by Necessity,” a small exhibition about the 1884 rescue of the Greely Arctic expedition. The writing must be historically responsible, engaging for general visitors, and ready for curatorial review.\n\nUse only the verified dossier below. Do not introduce quotations, motives, dates, Indigenous names, technical specifications, or other facts that are not supplied. Where the evidence does not support certainty, use appropriately qualified language.\n\nVERIFIED DOSSIER\n- In 1881, U.S. Army First Lieutenant Adolphus Greely led 25 men to Lady Franklin Bay on Ellesmere Island as part of the First International Polar Year.\n- The party established Fort Conger and conducted meteorological, astronomical, magnetic, tidal, and geographic observations.\n- In 1882 and 1883, scheduled relief ships failed to reach the party because of ice and poor decisions within the relief efforts.\n- Following written orders, Greely’s party abandoned Fort Conger in August 1883 and traveled south. They eventually established a camp at Cape Sabine.\n- Food caches expected near Cape Sabine were inadequate. The party faced extreme hunger, cold, illness, isolation, and internal conflict.\n- Several earlier rescue attempts failed. In 1884, the U.S. Navy organized another expedition under Commander Winfield Scott Schley.\n- Schley’s squadron included the steam-powered ships Thetis, Bear, and Alert. Bear and Thetis reached Cape Sabine on June 22, 1884.\n- Rescuers found seven men alive; one of those seven, Joseph Elison, died during the return voyage. Of the original 25, six ultimately returned alive.\n- Recovery of scientific records was considered an important outcome of the expedition.\n- The expedition took place in an Arctic homeland that was already known, traveled, and inhabited by Indigenous peoples. Nineteenth-century U.S. accounts often described such regions as “unknown” or “unexplored,” language that reflected outsiders’ perspectives rather than an absence of existing knowledge.\n- The exhibition contains these four objects:\n  1. A brass-and-glass aneroid barometer used for field observation, maker unknown, circa 1880.\n  2. A water-stained page from a meteorological observation ledger kept at Fort Conger in February 1882; it records temperature, pressure, cloud cover, and wind.\n  3. A blue wool uniform coat attributed to Winfield Scott Schley and worn during the 1884 rescue expedition; attribution is supported by family provenance but is not conclusive.\n  4. An 1885 newspaper engraving depicting the survivors’ arrival in Portsmouth, New Hampshire. It was produced after the event for a mass audience and should be treated as a mediated representation, not an eyewitness record.\n\nAUDIENCE AND VOICE\n- Primary audience: visitors aged 14 and older with no prior knowledge of the event.\n- Reading level: approximately U.S. grade 8.\n- Tone: restrained, humane, vivid, and precise—not triumphalist, sensational, or melodramatic.\n- Center survival and scientific work without turning suffering into spectacle.\n- Do not frame the Arctic as empty, conquered, or waiting to be discovered.\n- Explain unfamiliar terms in context. Prefer short sentences and active voice.\n- Avoid rhetorical questions, exclamation points, invented scene-setting, and clichés such as “frozen wasteland,” “race against time,” or “against all odds.”\n- Refer to the group as “the Greely party,” not “Greely’s men,” except where grammar makes that impossible.\n\nDELIVERABLES\n1. Exhibition title and subtitle. Retain “North by Necessity” as the title and write a subtitle of no more than 12 words.\n2. Introductory panel: 170–190 words. Establish the scientific mission, failed relief efforts, move to Cape Sabine, rescue, human cost, and the need to question period ideas of “exploration.”\n3. Section panel, “Measuring the Arctic”: 105–125 words. Explain why sustained observations mattered and how routine recordkeeping continued under difficult conditions.\n4. Section panel, “Relief Delayed”: 105–125 words. Clarify that the disaster resulted from both environmental hazards and human decisions. Avoid assigning blame beyond the dossier.\n5. Section panel, “Rescue and Return”: 105–125 words. Describe Schley’s expedition, the June 22 rescue, the number of survivors, and the recovery of records without presenting the outcome as an uncomplicated victory.\n6. Four object labels, one for each listed object, each 65–80 words. Begin each label with a display heading of no more than six words. For the coat, clearly communicate the uncertain attribution. For the engraving, teach visitors why a published image is not neutral evidence.\n7. A family conversation prompt of 35–45 words that invites observation and discussion without using a rhetorical question. It should work beside the ledger and barometer.\n8. A 90–110 word accessibility-oriented visual description of the newspaper engraving. Because no image is provided, limit the description to what can responsibly be inferred from the dossier: medium, subject, publication context, and evidentiary limits. Explicitly state that composition and depicted details must be confirmed against the physical object before publication.\n9. A curator review table with columns: “Copy location,” “Claim or wording needing review,” and “Reason.” Flag at least four issues, including Indigenous context, the coat attribution, the engraving’s evidentiary status, and survivor totals.\n\nFORMAT\nPresent the finished package in the deliverable order above with clear headings. Put word counts in parentheses after every panel, label, prompt, and visual description. Do not include citations in visitor-facing copy. After the visitor-facing materials, include the curator review table and then a brief style-compliance checklist confirming that all required facts, cautions, and word limits have been addressed."
        }
      ]
    }
  ]'

runware run google:gemma@4-31b \
  messages.0.role=user \
  messages.0.content="Act as the lead interpretive writer for a maritime museum. Create the final gallery text package for “North by Necessity,” a small exhibition about the 1884 rescue of the Greely Arctic expedition. The writing must be historically responsible, engaging for general visitors, and ready for curatorial review.

Use only the verified dossier below. Do not introduce quotations, motives, dates, Indigenous names, technical specifications, or other facts that are not supplied. Where the evidence does not support certainty, use appropriately qualified language.

VERIFIED DOSSIER
- In 1881, U.S. Army First Lieutenant Adolphus Greely led 25 men to Lady Franklin Bay on Ellesmere Island as part of the First International Polar Year.
- The party established Fort Conger and conducted meteorological, astronomical, magnetic, tidal, and geographic observations.
- In 1882 and 1883, scheduled relief ships failed to reach the party because of ice and poor decisions within the relief efforts.
- Following written orders, Greely’s party abandoned Fort Conger in August 1883 and traveled south. They eventually established a camp at Cape Sabine.
- Food caches expected near Cape Sabine were inadequate. The party faced extreme hunger, cold, illness, isolation, and internal conflict.
- Several earlier rescue attempts failed. In 1884, the U.S. Navy organized another expedition under Commander Winfield Scott Schley.
- Schley’s squadron included the steam-powered ships Thetis, Bear, and Alert. Bear and Thetis reached Cape Sabine on June 22, 1884.
- Rescuers found seven men alive; one of those seven, Joseph Elison, died during the return voyage. Of the original 25, six ultimately returned alive.
- Recovery of scientific records was considered an important outcome of the expedition.
- The expedition took place in an Arctic homeland that was already known, traveled, and inhabited by Indigenous peoples. Nineteenth-century U.S. accounts often described such regions as “unknown” or “unexplored,” language that reflected outsiders’ perspectives rather than an absence of existing knowledge.
- The exhibition contains these four objects:
  1. A brass-and-glass aneroid barometer used for field observation, maker unknown, circa 1880.
  2. A water-stained page from a meteorological observation ledger kept at Fort Conger in February 1882; it records temperature, pressure, cloud cover, and wind.
  3. A blue wool uniform coat attributed to Winfield Scott Schley and worn during the 1884 rescue expedition; attribution is supported by family provenance but is not conclusive.
  4. An 1885 newspaper engraving depicting the survivors’ arrival in Portsmouth, New Hampshire. It was produced after the event for a mass audience and should be treated as a mediated representation, not an eyewitness record.

AUDIENCE AND VOICE
- Primary audience: visitors aged 14 and older with no prior knowledge of the event.
- Reading level: approximately U.S. grade 8.
- Tone: restrained, humane, vivid, and precise—not triumphalist, sensational, or melodramatic.
- Center survival and scientific work without turning suffering into spectacle.
- Do not frame the Arctic as empty, conquered, or waiting to be discovered.
- Explain unfamiliar terms in context. Prefer short sentences and active voice.
- Avoid rhetorical questions, exclamation points, invented scene-setting, and clichés such as “frozen wasteland,” “race against time,” or “against all odds.”
- Refer to the group as “the Greely party,” not “Greely’s men,” except where grammar makes that impossible.

DELIVERABLES
1. Exhibition title and subtitle. Retain “North by Necessity” as the title and write a subtitle of no more than 12 words.
2. Introductory panel: 170–190 words. Establish the scientific mission, failed relief efforts, move to Cape Sabine, rescue, human cost, and the need to question period ideas of “exploration.”
3. Section panel, “Measuring the Arctic”: 105–125 words. Explain why sustained observations mattered and how routine recordkeeping continued under difficult conditions.
4. Section panel, “Relief Delayed”: 105–125 words. Clarify that the disaster resulted from both environmental hazards and human decisions. Avoid assigning blame beyond the dossier.
5. Section panel, “Rescue and Return”: 105–125 words. Describe Schley’s expedition, the June 22 rescue, the number of survivors, and the recovery of records without presenting the outcome as an uncomplicated victory.
6. Four object labels, one for each listed object, each 65–80 words. Begin each label with a display heading of no more than six words. For the coat, clearly communicate the uncertain attribution. For the engraving, teach visitors why a published image is not neutral evidence.
7. A family conversation prompt of 35–45 words that invites observation and discussion without using a rhetorical question. It should work beside the ledger and barometer.
8. A 90–110 word accessibility-oriented visual description of the newspaper engraving. Because no image is provided, limit the description to what can responsibly be inferred from the dossier: medium, subject, publication context, and evidentiary limits. Explicitly state that composition and depicted details must be confirmed against the physical object before publication.
9. A curator review table with columns: “Copy location,” “Claim or wording needing review,” and “Reason.” Flag at least four issues, including Indigenous context, the coat attribution, the engraving’s evidentiary status, and survivor totals.

FORMAT
Present the finished package in the deliverable order above with clear headings. Put word counts in parentheses after every panel, label, prompt, and visual description. Do not include citations in visitor-facing copy. After the visitor-facing materials, include the curator review table and then a brief style-compliance checklist confirming that all required facts, cautions, and word limits have been addressed."

{
  "taskType": "textInference",
  "taskUUID": "78feeb31-af15-4993-82be-984eb368c5da",
  "model": "google:gemma@4-31b",
  "messages": [
    {
      "role": "user",
      "content": "Act as the lead interpretive writer for a maritime museum. Create the final gallery text package for “North by Necessity,” a small exhibition about the 1884 rescue of the Greely Arctic expedition. The writing must be historically responsible, engaging for general visitors, and ready for curatorial review.\n\nUse only the verified dossier below. Do not introduce quotations, motives, dates, Indigenous names, technical specifications, or other facts that are not supplied. Where the evidence does not support certainty, use appropriately qualified language.\n\nVERIFIED DOSSIER\n- In 1881, U.S. Army First Lieutenant Adolphus Greely led 25 men to Lady Franklin Bay on Ellesmere Island as part of the First International Polar Year.\n- The party established Fort Conger and conducted meteorological, astronomical, magnetic, tidal, and geographic observations.\n- In 1882 and 1883, scheduled relief ships failed to reach the party because of ice and poor decisions within the relief efforts.\n- Following written orders, Greely’s party abandoned Fort Conger in August 1883 and traveled south. They eventually established a camp at Cape Sabine.\n- Food caches expected near Cape Sabine were inadequate. The party faced extreme hunger, cold, illness, isolation, and internal conflict.\n- Several earlier rescue attempts failed. In 1884, the U.S. Navy organized another expedition under Commander Winfield Scott Schley.\n- Schley’s squadron included the steam-powered ships Thetis, Bear, and Alert. Bear and Thetis reached Cape Sabine on June 22, 1884.\n- Rescuers found seven men alive; one of those seven, Joseph Elison, died during the return voyage. Of the original 25, six ultimately returned alive.\n- Recovery of scientific records was considered an important outcome of the expedition.\n- The expedition took place in an Arctic homeland that was already known, traveled, and inhabited by Indigenous peoples. Nineteenth-century U.S. accounts often described such regions as “unknown” or “unexplored,” language that reflected outsiders’ perspectives rather than an absence of existing knowledge.\n- The exhibition contains these four objects:\n  1. A brass-and-glass aneroid barometer used for field observation, maker unknown, circa 1880.\n  2. A water-stained page from a meteorological observation ledger kept at Fort Conger in February 1882; it records temperature, pressure, cloud cover, and wind.\n  3. A blue wool uniform coat attributed to Winfield Scott Schley and worn during the 1884 rescue expedition; attribution is supported by family provenance but is not conclusive.\n  4. An 1885 newspaper engraving depicting the survivors’ arrival in Portsmouth, New Hampshire. It was produced after the event for a mass audience and should be treated as a mediated representation, not an eyewitness record.\n\nAUDIENCE AND VOICE\n- Primary audience: visitors aged 14 and older with no prior knowledge of the event.\n- Reading level: approximately U.S. grade 8.\n- Tone: restrained, humane, vivid, and precise—not triumphalist, sensational, or melodramatic.\n- Center survival and scientific work without turning suffering into spectacle.\n- Do not frame the Arctic as empty, conquered, or waiting to be discovered.\n- Explain unfamiliar terms in context. Prefer short sentences and active voice.\n- Avoid rhetorical questions, exclamation points, invented scene-setting, and clichés such as “frozen wasteland,” “race against time,” or “against all odds.”\n- Refer to the group as “the Greely party,” not “Greely’s men,” except where grammar makes that impossible.\n\nDELIVERABLES\n1. Exhibition title and subtitle. Retain “North by Necessity” as the title and write a subtitle of no more than 12 words.\n2. Introductory panel: 170–190 words. Establish the scientific mission, failed relief efforts, move to Cape Sabine, rescue, human cost, and the need to question period ideas of “exploration.”\n3. Section panel, “Measuring the Arctic”: 105–125 words. Explain why sustained observations mattered and how routine recordkeeping continued under difficult conditions.\n4. Section panel, “Relief Delayed”: 105–125 words. Clarify that the disaster resulted from both environmental hazards and human decisions. Avoid assigning blame beyond the dossier.\n5. Section panel, “Rescue and Return”: 105–125 words. Describe Schley’s expedition, the June 22 rescue, the number of survivors, and the recovery of records without presenting the outcome as an uncomplicated victory.\n6. Four object labels, one for each listed object, each 65–80 words. Begin each label with a display heading of no more than six words. For the coat, clearly communicate the uncertain attribution. For the engraving, teach visitors why a published image is not neutral evidence.\n7. A family conversation prompt of 35–45 words that invites observation and discussion without using a rhetorical question. It should work beside the ledger and barometer.\n8. A 90–110 word accessibility-oriented visual description of the newspaper engraving. Because no image is provided, limit the description to what can responsibly be inferred from the dossier: medium, subject, publication context, and evidentiary limits. Explicitly state that composition and depicted details must be confirmed against the physical object before publication.\n9. A curator review table with columns: “Copy location,” “Claim or wording needing review,” and “Reason.” Flag at least four issues, including Indigenous context, the coat attribution, the engraving’s evidentiary status, and survivor totals.\n\nFORMAT\nPresent the finished package in the deliverable order above with clear headings. Put word counts in parentheses after every panel, label, prompt, and visual description. Do not include citations in visitor-facing copy. After the visitor-facing materials, include the curator review table and then a brief style-compliance checklist confirming that all required facts, cautions, and word limits have been addressed."
    }
  ]
}

import { createClient } from '@runware/sdk'

const client = await createClient({ apiKey: process.env.RUNWARE_API_KEY })
await client.connect()

const [result] = await client.run({
  model: 'google:gemma@4-31b',
  seed: 68120,
  settings: {
    systemPrompt: 'You are a precise conversation analyst. Identify intent, decisions, open questions, action items, social dynamics, and any hidden assumptions. Keep the response organized and practical.',
    temperature: 0.72,
    topP: 0.9,
    maxTokens: 8192,
    thinkingLevel: 'high'
  },
  messages: [
    {
      role: 'user',
      content: 'Analyze this random conversation between humans. Produce: 1) concise summary, 2) speaker-by-speaker goals, 3) decisions made, 4) open questions, 5) action items with owners, 6) potential misunderstandings, and 7) a cleaned-up meeting note version.\n\nTranscript:\n\nMaya: Okay, before everyone leaves, can we settle the Saturday cleanup plan? I know this was supposed to be ten minutes.\n\nJon: Ten minutes in this group means thirty-five, but yes. I brought the sign-up sheet.\n\nPriya: I can do early morning, but I have to leave by 10:30. My nephew has a chess match.\n\nLeo: Early morning is when the bakery delivery blocks the alley. If we put the supply table there, people will get annoyed.\n\nMaya: Good point. What if check-in is by the school fence instead?\n\nJon: The fence with the blue gate or the one near the gym?\n\nMaya: Blue gate. The gym side gets crowded because of soccer.\n\nPriya: Do we still have gloves from last time?\n\nJon: Two boxes. One medium, one large. No small sizes, unless someone found the missing box.\n\nLeo: I found a box in the storage room, but it was full of paper cups, not gloves. Also there is a folding table with one broken leg.\n\nMaya: Please do not bring the broken table again. Last time it collapsed under juice bottles.\n\nPriya: That was memorable, though.\n\nJon: I can borrow two tables from my office, but someone needs to help me carry them. They are awkward, not heavy.\n\nLeo: I can help Friday evening. After 6:15.\n\nMaya: Great. Priya, could you handle snacks? Nothing fancy. Bananas, granola bars, water.\n\nPriya: Yes, but reimbursement needs to be clear. I still have not been paid back for the first-aid refills.\n\nJon: I thought Sam handled that.\n\nMaya: Sam approved it, but the treasurer sends the payment. I will ask Tessa tonight.\n\nPriya: Thank you. I do not mind buying things, I just do not want it to become vague.\n\nLeo: Also, we need a plan for the old paint cans behind the recreation shed. We cannot put them in regular trash.\n\nJon: The city pickup for hazardous waste is next month, not this weekend.\n\nMaya: Then we mark them, move them away from foot traffic, and do not ask volunteers to touch them.\n\nPriya: We should say that clearly in the volunteer email.\n\nJon: Speaking of email, who is sending it? I wrote a draft, but it sounds like a tax notice.\n\nLeo: That is your natural writing style.\n\nJon: Accurate, but rude.\n\nMaya: Send me the draft. I will soften it and add the check-in location, time, gloves note, snack note, and paint-can warning.\n\nPriya: Add that kids are welcome if supervised. People keep asking.\n\nLeo: And add that we need two people with pickup trucks for hauling branches.\n\nJon: Branches only? Someone asked if we are removing the rusted bike rack.\n\nMaya: Not this weekend. That needs permission from Parks and Rec.\n\nPriya: I can call Parks and Rec Monday.\n\nLeo: Wait, if we say no bike rack removal, some people will still show up with tools.\n\nMaya: Then the email should say: no power tools, no metal removal, no paint handling.\n\nJon: That is clear. Slightly stern, but clear.\n\nPriya: Clear is better than someone arriving with a saw.\n\nLeo: I once saw a volunteer bring a chainsaw to trim a rose bush.\n\nMaya: Please do not put that image in my head.\n\nJon: Time window: 8:30 to noon?\n\nPriya: If check-in opens at 8:30, volunteers arrive at 8:10.\n\nMaya: Then we set up at 8:00, check-in at 8:30, cleanup from 9:00 to noon.\n\nLeo: I can be there at 8:00 if I am not the only one lifting tables.\n\nJon: I will be there. With coffee, possibly grumpy.\n\nPriya: I will drop snacks at 8:20 and stay until 10:30.\n\nMaya: Perfect. I will bring tape, markers, printed zone maps, and name tags.\n\nJon: We still need someone for photos.\n\nPriya: Ask Nina. She likes doing that and she knows not to photograph kids without permission.\n\nMaya: I will ask Nina.\n\nLeo: Anything else?\n\nJon: Weather plan?\n\nMaya: If conditions are unsafe, we postpone. If it is just cold, we continue. I will include that.\n\nPriya: Define unsafe, please. People interpret that differently.\n\nMaya: Thunder, high winds, icy sidewalks, or official advisory.\n\nLeo: Good.\n\nJon: So I send Maya the draft tonight. Leo helps with tables Friday. Priya buys snacks and calls Parks and Rec Monday. Maya asks Tessa about reimbursement and Nina about photos.\n\nPriya: And Maya updates the email.\n\nMaya: Yes. I will send it by tomorrow noon.\n\nLeo: I feel strangely optimistic.\n\nJon: Do not worry, it will pass.\n\nMaya: Meeting over before thirty-five minutes. A historic achievement.'
    }
  ]
})

import asyncio
import os

from runware import Runware


async def main():
    async with Runware(api_key=os.environ["RUNWARE_API_KEY"]) as client:
        results = await client.run({
            "model": "google:gemma@4-31b",
            "seed": 68120,
            "settings": {
                "systemPrompt": "You are a precise conversation analyst. Identify intent, decisions, open questions, action items, social dynamics, and any hidden assumptions. Keep the response organized and practical.",
                "temperature": 0.72,
                "topP": 0.9,
                "maxTokens": 8192,
                "thinkingLevel": "high"
            },
            "messages": [
                {
                    "role": "user",
                    "content": "Analyze this random conversation between humans. Produce: 1) concise summary, 2) speaker-by-speaker goals, 3) decisions made, 4) open questions, 5) action items with owners, 6) potential misunderstandings, and 7) a cleaned-up meeting note version.\n\nTranscript:\n\nMaya: Okay, before everyone leaves, can we settle the Saturday cleanup plan? I know this was supposed to be ten minutes.\n\nJon: Ten minutes in this group means thirty-five, but yes. I brought the sign-up sheet.\n\nPriya: I can do early morning, but I have to leave by 10:30. My nephew has a chess match.\n\nLeo: Early morning is when the bakery delivery blocks the alley. If we put the supply table there, people will get annoyed.\n\nMaya: Good point. What if check-in is by the school fence instead?\n\nJon: The fence with the blue gate or the one near the gym?\n\nMaya: Blue gate. The gym side gets crowded because of soccer.\n\nPriya: Do we still have gloves from last time?\n\nJon: Two boxes. One medium, one large. No small sizes, unless someone found the missing box.\n\nLeo: I found a box in the storage room, but it was full of paper cups, not gloves. Also there is a folding table with one broken leg.\n\nMaya: Please do not bring the broken table again. Last time it collapsed under juice bottles.\n\nPriya: That was memorable, though.\n\nJon: I can borrow two tables from my office, but someone needs to help me carry them. They are awkward, not heavy.\n\nLeo: I can help Friday evening. After 6:15.\n\nMaya: Great. Priya, could you handle snacks? Nothing fancy. Bananas, granola bars, water.\n\nPriya: Yes, but reimbursement needs to be clear. I still have not been paid back for the first-aid refills.\n\nJon: I thought Sam handled that.\n\nMaya: Sam approved it, but the treasurer sends the payment. I will ask Tessa tonight.\n\nPriya: Thank you. I do not mind buying things, I just do not want it to become vague.\n\nLeo: Also, we need a plan for the old paint cans behind the recreation shed. We cannot put them in regular trash.\n\nJon: The city pickup for hazardous waste is next month, not this weekend.\n\nMaya: Then we mark them, move them away from foot traffic, and do not ask volunteers to touch them.\n\nPriya: We should say that clearly in the volunteer email.\n\nJon: Speaking of email, who is sending it? I wrote a draft, but it sounds like a tax notice.\n\nLeo: That is your natural writing style.\n\nJon: Accurate, but rude.\n\nMaya: Send me the draft. I will soften it and add the check-in location, time, gloves note, snack note, and paint-can warning.\n\nPriya: Add that kids are welcome if supervised. People keep asking.\n\nLeo: And add that we need two people with pickup trucks for hauling branches.\n\nJon: Branches only? Someone asked if we are removing the rusted bike rack.\n\nMaya: Not this weekend. That needs permission from Parks and Rec.\n\nPriya: I can call Parks and Rec Monday.\n\nLeo: Wait, if we say no bike rack removal, some people will still show up with tools.\n\nMaya: Then the email should say: no power tools, no metal removal, no paint handling.\n\nJon: That is clear. Slightly stern, but clear.\n\nPriya: Clear is better than someone arriving with a saw.\n\nLeo: I once saw a volunteer bring a chainsaw to trim a rose bush.\n\nMaya: Please do not put that image in my head.\n\nJon: Time window: 8:30 to noon?\n\nPriya: If check-in opens at 8:30, volunteers arrive at 8:10.\n\nMaya: Then we set up at 8:00, check-in at 8:30, cleanup from 9:00 to noon.\n\nLeo: I can be there at 8:00 if I am not the only one lifting tables.\n\nJon: I will be there. With coffee, possibly grumpy.\n\nPriya: I will drop snacks at 8:20 and stay until 10:30.\n\nMaya: Perfect. I will bring tape, markers, printed zone maps, and name tags.\n\nJon: We still need someone for photos.\n\nPriya: Ask Nina. She likes doing that and she knows not to photograph kids without permission.\n\nMaya: I will ask Nina.\n\nLeo: Anything else?\n\nJon: Weather plan?\n\nMaya: If conditions are unsafe, we postpone. If it is just cold, we continue. I will include that.\n\nPriya: Define unsafe, please. People interpret that differently.\n\nMaya: Thunder, high winds, icy sidewalks, or official advisory.\n\nLeo: Good.\n\nJon: So I send Maya the draft tonight. Leo helps with tables Friday. Priya buys snacks and calls Parks and Rec Monday. Maya asks Tessa about reimbursement and Nina about photos.\n\nPriya: And Maya updates the email.\n\nMaya: Yes. I will send it by tomorrow noon.\n\nLeo: I feel strangely optimistic.\n\nJon: Do not worry, it will pass.\n\nMaya: Meeting over before thirty-five minutes. A historic achievement."
                }
            ]
        })


asyncio.run(main())

curl https://api.runware.ai/v1 \
  -H "Authorization: Bearer $RUNWARE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '[
    {
      "taskType": "textInference",
      "taskUUID": "205c0b3d-6917-4c0e-be24-2dd7d37813e9",
      "model": "google:gemma@4-31b",
      "seed": 68120,
      "settings": {
        "systemPrompt": "You are a precise conversation analyst. Identify intent, decisions, open questions, action items, social dynamics, and any hidden assumptions. Keep the response organized and practical.",
        "temperature": 0.72,
        "topP": 0.9,
        "maxTokens": 8192,
        "thinkingLevel": "high"
      },
      "messages": [
        {
          "role": "user",
          "content": "Analyze this random conversation between humans. Produce: 1) concise summary, 2) speaker-by-speaker goals, 3) decisions made, 4) open questions, 5) action items with owners, 6) potential misunderstandings, and 7) a cleaned-up meeting note version.\n\nTranscript:\n\nMaya: Okay, before everyone leaves, can we settle the Saturday cleanup plan? I know this was supposed to be ten minutes.\n\nJon: Ten minutes in this group means thirty-five, but yes. I brought the sign-up sheet.\n\nPriya: I can do early morning, but I have to leave by 10:30. My nephew has a chess match.\n\nLeo: Early morning is when the bakery delivery blocks the alley. If we put the supply table there, people will get annoyed.\n\nMaya: Good point. What if check-in is by the school fence instead?\n\nJon: The fence with the blue gate or the one near the gym?\n\nMaya: Blue gate. The gym side gets crowded because of soccer.\n\nPriya: Do we still have gloves from last time?\n\nJon: Two boxes. One medium, one large. No small sizes, unless someone found the missing box.\n\nLeo: I found a box in the storage room, but it was full of paper cups, not gloves. Also there is a folding table with one broken leg.\n\nMaya: Please do not bring the broken table again. Last time it collapsed under juice bottles.\n\nPriya: That was memorable, though.\n\nJon: I can borrow two tables from my office, but someone needs to help me carry them. They are awkward, not heavy.\n\nLeo: I can help Friday evening. After 6:15.\n\nMaya: Great. Priya, could you handle snacks? Nothing fancy. Bananas, granola bars, water.\n\nPriya: Yes, but reimbursement needs to be clear. I still have not been paid back for the first-aid refills.\n\nJon: I thought Sam handled that.\n\nMaya: Sam approved it, but the treasurer sends the payment. I will ask Tessa tonight.\n\nPriya: Thank you. I do not mind buying things, I just do not want it to become vague.\n\nLeo: Also, we need a plan for the old paint cans behind the recreation shed. We cannot put them in regular trash.\n\nJon: The city pickup for hazardous waste is next month, not this weekend.\n\nMaya: Then we mark them, move them away from foot traffic, and do not ask volunteers to touch them.\n\nPriya: We should say that clearly in the volunteer email.\n\nJon: Speaking of email, who is sending it? I wrote a draft, but it sounds like a tax notice.\n\nLeo: That is your natural writing style.\n\nJon: Accurate, but rude.\n\nMaya: Send me the draft. I will soften it and add the check-in location, time, gloves note, snack note, and paint-can warning.\n\nPriya: Add that kids are welcome if supervised. People keep asking.\n\nLeo: And add that we need two people with pickup trucks for hauling branches.\n\nJon: Branches only? Someone asked if we are removing the rusted bike rack.\n\nMaya: Not this weekend. That needs permission from Parks and Rec.\n\nPriya: I can call Parks and Rec Monday.\n\nLeo: Wait, if we say no bike rack removal, some people will still show up with tools.\n\nMaya: Then the email should say: no power tools, no metal removal, no paint handling.\n\nJon: That is clear. Slightly stern, but clear.\n\nPriya: Clear is better than someone arriving with a saw.\n\nLeo: I once saw a volunteer bring a chainsaw to trim a rose bush.\n\nMaya: Please do not put that image in my head.\n\nJon: Time window: 8:30 to noon?\n\nPriya: If check-in opens at 8:30, volunteers arrive at 8:10.\n\nMaya: Then we set up at 8:00, check-in at 8:30, cleanup from 9:00 to noon.\n\nLeo: I can be there at 8:00 if I am not the only one lifting tables.\n\nJon: I will be there. With coffee, possibly grumpy.\n\nPriya: I will drop snacks at 8:20 and stay until 10:30.\n\nMaya: Perfect. I will bring tape, markers, printed zone maps, and name tags.\n\nJon: We still need someone for photos.\n\nPriya: Ask Nina. She likes doing that and she knows not to photograph kids without permission.\n\nMaya: I will ask Nina.\n\nLeo: Anything else?\n\nJon: Weather plan?\n\nMaya: If conditions are unsafe, we postpone. If it is just cold, we continue. I will include that.\n\nPriya: Define unsafe, please. People interpret that differently.\n\nMaya: Thunder, high winds, icy sidewalks, or official advisory.\n\nLeo: Good.\n\nJon: So I send Maya the draft tonight. Leo helps with tables Friday. Priya buys snacks and calls Parks and Rec Monday. Maya asks Tessa about reimbursement and Nina about photos.\n\nPriya: And Maya updates the email.\n\nMaya: Yes. I will send it by tomorrow noon.\n\nLeo: I feel strangely optimistic.\n\nJon: Do not worry, it will pass.\n\nMaya: Meeting over before thirty-five minutes. A historic achievement."
        }
      ]
    }
  ]'

runware run google:gemma@4-31b \
  seed=68120 \
  settings.systemPrompt="You are a precise conversation analyst. Identify intent, decisions, open questions, action items, social dynamics, and any hidden assumptions. Keep the response organized and practical." \
  settings.temperature=0.72 \
  settings.topP=0.9 \
  settings.maxTokens=8192 \
  settings.thinkingLevel=high \
  messages.0.role=user \
  messages.0.content="Analyze this random conversation between humans. Produce: 1) concise summary, 2) speaker-by-speaker goals, 3) decisions made, 4) open questions, 5) action items with owners, 6) potential misunderstandings, and 7) a cleaned-up meeting note version.

Transcript:

Maya: Okay, before everyone leaves, can we settle the Saturday cleanup plan? I know this was supposed to be ten minutes.

Jon: Ten minutes in this group means thirty-five, but yes. I brought the sign-up sheet.

Priya: I can do early morning, but I have to leave by 10:30. My nephew has a chess match.

Leo: Early morning is when the bakery delivery blocks the alley. If we put the supply table there, people will get annoyed.

Maya: Good point. What if check-in is by the school fence instead?

Jon: The fence with the blue gate or the one near the gym?

Maya: Blue gate. The gym side gets crowded because of soccer.

Priya: Do we still have gloves from last time?

Jon: Two boxes. One medium, one large. No small sizes, unless someone found the missing box.

Leo: I found a box in the storage room, but it was full of paper cups, not gloves. Also there is a folding table with one broken leg.

Maya: Please do not bring the broken table again. Last time it collapsed under juice bottles.

Priya: That was memorable, though.

Jon: I can borrow two tables from my office, but someone needs to help me carry them. They are awkward, not heavy.

Leo: I can help Friday evening. After 6:15.

Maya: Great. Priya, could you handle snacks? Nothing fancy. Bananas, granola bars, water.

Priya: Yes, but reimbursement needs to be clear. I still have not been paid back for the first-aid refills.

Jon: I thought Sam handled that.

Maya: Sam approved it, but the treasurer sends the payment. I will ask Tessa tonight.

Priya: Thank you. I do not mind buying things, I just do not want it to become vague.

Leo: Also, we need a plan for the old paint cans behind the recreation shed. We cannot put them in regular trash.

Jon: The city pickup for hazardous waste is next month, not this weekend.

Maya: Then we mark them, move them away from foot traffic, and do not ask volunteers to touch them.

Priya: We should say that clearly in the volunteer email.

Jon: Speaking of email, who is sending it? I wrote a draft, but it sounds like a tax notice.

Leo: That is your natural writing style.

Jon: Accurate, but rude.

Maya: Send me the draft. I will soften it and add the check-in location, time, gloves note, snack note, and paint-can warning.

Priya: Add that kids are welcome if supervised. People keep asking.

Leo: And add that we need two people with pickup trucks for hauling branches.

Jon: Branches only? Someone asked if we are removing the rusted bike rack.

Maya: Not this weekend. That needs permission from Parks and Rec.

Priya: I can call Parks and Rec Monday.

Leo: Wait, if we say no bike rack removal, some people will still show up with tools.

Maya: Then the email should say: no power tools, no metal removal, no paint handling.

Jon: That is clear. Slightly stern, but clear.

Priya: Clear is better than someone arriving with a saw.

Leo: I once saw a volunteer bring a chainsaw to trim a rose bush.

Maya: Please do not put that image in my head.

Jon: Time window: 8:30 to noon?

Priya: If check-in opens at 8:30, volunteers arrive at 8:10.

Maya: Then we set up at 8:00, check-in at 8:30, cleanup from 9:00 to noon.

Leo: I can be there at 8:00 if I am not the only one lifting tables.

Jon: I will be there. With coffee, possibly grumpy.

Priya: I will drop snacks at 8:20 and stay until 10:30.

Maya: Perfect. I will bring tape, markers, printed zone maps, and name tags.

Jon: We still need someone for photos.

Priya: Ask Nina. She likes doing that and she knows not to photograph kids without permission.

Maya: I will ask Nina.

Leo: Anything else?

Jon: Weather plan?

Maya: If conditions are unsafe, we postpone. If it is just cold, we continue. I will include that.

Priya: Define unsafe, please. People interpret that differently.

Maya: Thunder, high winds, icy sidewalks, or official advisory.

Leo: Good.

Jon: So I send Maya the draft tonight. Leo helps with tables Friday. Priya buys snacks and calls Parks and Rec Monday. Maya asks Tessa about reimbursement and Nina about photos.

Priya: And Maya updates the email.

Maya: Yes. I will send it by tomorrow noon.

Leo: I feel strangely optimistic.

Jon: Do not worry, it will pass.

Maya: Meeting over before thirty-five minutes. A historic achievement."

{
  "taskType": "textInference",
  "taskUUID": "205c0b3d-6917-4c0e-be24-2dd7d37813e9",
  "model": "google:gemma@4-31b",
  "seed": 68120,
  "settings": {
    "systemPrompt": "You are a precise conversation analyst. Identify intent, decisions, open questions, action items, social dynamics, and any hidden assumptions. Keep the response organized and practical.",
    "temperature": 0.72,
    "topP": 0.9,
    "maxTokens": 8192,
    "thinkingLevel": "high"
  },
  "messages": [
    {
      "role": "user",
      "content": "Analyze this random conversation between humans. Produce: 1) concise summary, 2) speaker-by-speaker goals, 3) decisions made, 4) open questions, 5) action items with owners, 6) potential misunderstandings, and 7) a cleaned-up meeting note version.\n\nTranscript:\n\nMaya: Okay, before everyone leaves, can we settle the Saturday cleanup plan? I know this was supposed to be ten minutes.\n\nJon: Ten minutes in this group means thirty-five, but yes. I brought the sign-up sheet.\n\nPriya: I can do early morning, but I have to leave by 10:30. My nephew has a chess match.\n\nLeo: Early morning is when the bakery delivery blocks the alley. If we put the supply table there, people will get annoyed.\n\nMaya: Good point. What if check-in is by the school fence instead?\n\nJon: The fence with the blue gate or the one near the gym?\n\nMaya: Blue gate. The gym side gets crowded because of soccer.\n\nPriya: Do we still have gloves from last time?\n\nJon: Two boxes. One medium, one large. No small sizes, unless someone found the missing box.\n\nLeo: I found a box in the storage room, but it was full of paper cups, not gloves. Also there is a folding table with one broken leg.\n\nMaya: Please do not bring the broken table again. Last time it collapsed under juice bottles.\n\nPriya: That was memorable, though.\n\nJon: I can borrow two tables from my office, but someone needs to help me carry them. They are awkward, not heavy.\n\nLeo: I can help Friday evening. After 6:15.\n\nMaya: Great. Priya, could you handle snacks? Nothing fancy. Bananas, granola bars, water.\n\nPriya: Yes, but reimbursement needs to be clear. I still have not been paid back for the first-aid refills.\n\nJon: I thought Sam handled that.\n\nMaya: Sam approved it, but the treasurer sends the payment. I will ask Tessa tonight.\n\nPriya: Thank you. I do not mind buying things, I just do not want it to become vague.\n\nLeo: Also, we need a plan for the old paint cans behind the recreation shed. We cannot put them in regular trash.\n\nJon: The city pickup for hazardous waste is next month, not this weekend.\n\nMaya: Then we mark them, move them away from foot traffic, and do not ask volunteers to touch them.\n\nPriya: We should say that clearly in the volunteer email.\n\nJon: Speaking of email, who is sending it? I wrote a draft, but it sounds like a tax notice.\n\nLeo: That is your natural writing style.\n\nJon: Accurate, but rude.\n\nMaya: Send me the draft. I will soften it and add the check-in location, time, gloves note, snack note, and paint-can warning.\n\nPriya: Add that kids are welcome if supervised. People keep asking.\n\nLeo: And add that we need two people with pickup trucks for hauling branches.\n\nJon: Branches only? Someone asked if we are removing the rusted bike rack.\n\nMaya: Not this weekend. That needs permission from Parks and Rec.\n\nPriya: I can call Parks and Rec Monday.\n\nLeo: Wait, if we say no bike rack removal, some people will still show up with tools.\n\nMaya: Then the email should say: no power tools, no metal removal, no paint handling.\n\nJon: That is clear. Slightly stern, but clear.\n\nPriya: Clear is better than someone arriving with a saw.\n\nLeo: I once saw a volunteer bring a chainsaw to trim a rose bush.\n\nMaya: Please do not put that image in my head.\n\nJon: Time window: 8:30 to noon?\n\nPriya: If check-in opens at 8:30, volunteers arrive at 8:10.\n\nMaya: Then we set up at 8:00, check-in at 8:30, cleanup from 9:00 to noon.\n\nLeo: I can be there at 8:00 if I am not the only one lifting tables.\n\nJon: I will be there. With coffee, possibly grumpy.\n\nPriya: I will drop snacks at 8:20 and stay until 10:30.\n\nMaya: Perfect. I will bring tape, markers, printed zone maps, and name tags.\n\nJon: We still need someone for photos.\n\nPriya: Ask Nina. She likes doing that and she knows not to photograph kids without permission.\n\nMaya: I will ask Nina.\n\nLeo: Anything else?\n\nJon: Weather plan?\n\nMaya: If conditions are unsafe, we postpone. If it is just cold, we continue. I will include that.\n\nPriya: Define unsafe, please. People interpret that differently.\n\nMaya: Thunder, high winds, icy sidewalks, or official advisory.\n\nLeo: Good.\n\nJon: So I send Maya the draft tonight. Leo helps with tables Friday. Priya buys snacks and calls Parks and Rec Monday. Maya asks Tessa about reimbursement and Nina about photos.\n\nPriya: And Maya updates the email.\n\nMaya: Yes. I will send it by tomorrow noon.\n\nLeo: I feel strangely optimistic.\n\nJon: Do not worry, it will pass.\n\nMaya: Meeting over before thirty-five minutes. A historic achievement."
    }
  ]
}

import { createClient } from '@runware/sdk'

const client = await createClient({ apiKey: process.env.RUNWARE_API_KEY })
await client.connect()

const [result] = await client.run({
  model: 'google:gemma@4-31b',
  inputs: {
    images: [
      'https://assets.runware.ai/assets/inputs/ce20ce51-0ae3-4891-869a-6f30435958da.jpg'
    ],
    videos: [
      'https://assets.runware.ai/assets/inputs/f8c16baf-af89-4a0e-b90c-f400f8ac3acc.mp4'
    ]
  },
  messages: [
    {
      role: 'user',
      content: 'Act as a senior visual-merchandising auditor. The image is the approved autumn entrance-display reference; the video is a walkthrough of the installed display. Compare them and produce a practical compliance audit for the store manager.\n\nYour response must include:\n1. A concise executive summary and an overall compliance rating of Compliant, Partially Compliant, or Non-Compliant.\n2. A table with columns: Display Area, Approved Standard, Observed Installation, Status, Video Timestamp, and Recommended Correction.\n3. Separate findings for mannequin styling and order, plinth heights and spacing, central hiking-pack presentation, right-bay folded merchandise, color balance, signage, lighting, sightlines, and general presentation quality.\n4. A prioritized action list divided into Fix Before Opening, Fix Within 24 Hours, and Monitor.\n5. A short reinspection checklist a manager can use on a phone.\n\nUse the image and video as the only sources of truth. Cite timestamps for video-based observations and distinguish clearly between confirmed discrepancies, apparent discrepancies that need an on-site check, and elements that cannot be verified. Do not invent product names, measurements, policies, or missing visual details.'
    }
  ]
})

import asyncio
import os

from runware import Runware


async def main():
    async with Runware(api_key=os.environ["RUNWARE_API_KEY"]) as client:
        results = await client.run({
            "model": "google:gemma@4-31b",
            "inputs": {
                "images": [
                    "https://assets.runware.ai/assets/inputs/ce20ce51-0ae3-4891-869a-6f30435958da.jpg"
                ],
                "videos": [
                    "https://assets.runware.ai/assets/inputs/f8c16baf-af89-4a0e-b90c-f400f8ac3acc.mp4"
                ]
            },
            "messages": [
                {
                    "role": "user",
                    "content": "Act as a senior visual-merchandising auditor. The image is the approved autumn entrance-display reference; the video is a walkthrough of the installed display. Compare them and produce a practical compliance audit for the store manager.\n\nYour response must include:\n1. A concise executive summary and an overall compliance rating of Compliant, Partially Compliant, or Non-Compliant.\n2. A table with columns: Display Area, Approved Standard, Observed Installation, Status, Video Timestamp, and Recommended Correction.\n3. Separate findings for mannequin styling and order, plinth heights and spacing, central hiking-pack presentation, right-bay folded merchandise, color balance, signage, lighting, sightlines, and general presentation quality.\n4. A prioritized action list divided into Fix Before Opening, Fix Within 24 Hours, and Monitor.\n5. A short reinspection checklist a manager can use on a phone.\n\nUse the image and video as the only sources of truth. Cite timestamps for video-based observations and distinguish clearly between confirmed discrepancies, apparent discrepancies that need an on-site check, and elements that cannot be verified. Do not invent product names, measurements, policies, or missing visual details."
                }
            ]
        })


asyncio.run(main())

curl https://api.runware.ai/v1 \
  -H "Authorization: Bearer $RUNWARE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '[
    {
      "taskType": "textInference",
      "taskUUID": "b4138620-4483-414b-b6d1-b5b8959b54eb",
      "model": "google:gemma@4-31b",
      "inputs": {
        "images": [
          "https://assets.runware.ai/assets/inputs/ce20ce51-0ae3-4891-869a-6f30435958da.jpg"
        ],
        "videos": [
          "https://assets.runware.ai/assets/inputs/f8c16baf-af89-4a0e-b90c-f400f8ac3acc.mp4"
        ]
      },
      "messages": [
        {
          "role": "user",
          "content": "Act as a senior visual-merchandising auditor. The image is the approved autumn entrance-display reference; the video is a walkthrough of the installed display. Compare them and produce a practical compliance audit for the store manager.\n\nYour response must include:\n1. A concise executive summary and an overall compliance rating of Compliant, Partially Compliant, or Non-Compliant.\n2. A table with columns: Display Area, Approved Standard, Observed Installation, Status, Video Timestamp, and Recommended Correction.\n3. Separate findings for mannequin styling and order, plinth heights and spacing, central hiking-pack presentation, right-bay folded merchandise, color balance, signage, lighting, sightlines, and general presentation quality.\n4. A prioritized action list divided into Fix Before Opening, Fix Within 24 Hours, and Monitor.\n5. A short reinspection checklist a manager can use on a phone.\n\nUse the image and video as the only sources of truth. Cite timestamps for video-based observations and distinguish clearly between confirmed discrepancies, apparent discrepancies that need an on-site check, and elements that cannot be verified. Do not invent product names, measurements, policies, or missing visual details."
        }
      ]
    }
  ]'

runware run google:gemma@4-31b \
  inputs.images.0=https://assets.runware.ai/assets/inputs/ce20ce51-0ae3-4891-869a-6f30435958da.jpg \
  inputs.videos.0=https://assets.runware.ai/assets/inputs/f8c16baf-af89-4a0e-b90c-f400f8ac3acc.mp4 \
  messages.0.role=user \
  messages.0.content="Act as a senior visual-merchandising auditor. The image is the approved autumn entrance-display reference; the video is a walkthrough of the installed display. Compare them and produce a practical compliance audit for the store manager.

Your response must include:
1. A concise executive summary and an overall compliance rating of Compliant, Partially Compliant, or Non-Compliant.
2. A table with columns: Display Area, Approved Standard, Observed Installation, Status, Video Timestamp, and Recommended Correction.
3. Separate findings for mannequin styling and order, plinth heights and spacing, central hiking-pack presentation, right-bay folded merchandise, color balance, signage, lighting, sightlines, and general presentation quality.
4. A prioritized action list divided into Fix Before Opening, Fix Within 24 Hours, and Monitor.
5. A short reinspection checklist a manager can use on a phone.

Use the image and video as the only sources of truth. Cite timestamps for video-based observations and distinguish clearly between confirmed discrepancies, apparent discrepancies that need an on-site check, and elements that cannot be verified. Do not invent product names, measurements, policies, or missing visual details."

{
  "taskType": "textInference",
  "taskUUID": "b4138620-4483-414b-b6d1-b5b8959b54eb",
  "model": "google:gemma@4-31b",
  "inputs": {
    "images": [
      "https://assets.runware.ai/assets/inputs/ce20ce51-0ae3-4891-869a-6f30435958da.jpg"
    ],
    "videos": [
      "https://assets.runware.ai/assets/inputs/f8c16baf-af89-4a0e-b90c-f400f8ac3acc.mp4"
    ]
  },
  "messages": [
    {
      "role": "user",
      "content": "Act as a senior visual-merchandising auditor. The image is the approved autumn entrance-display reference; the video is a walkthrough of the installed display. Compare them and produce a practical compliance audit for the store manager.\n\nYour response must include:\n1. A concise executive summary and an overall compliance rating of Compliant, Partially Compliant, or Non-Compliant.\n2. A table with columns: Display Area, Approved Standard, Observed Installation, Status, Video Timestamp, and Recommended Correction.\n3. Separate findings for mannequin styling and order, plinth heights and spacing, central hiking-pack presentation, right-bay folded merchandise, color balance, signage, lighting, sightlines, and general presentation quality.\n4. A prioritized action list divided into Fix Before Opening, Fix Within 24 Hours, and Monitor.\n5. A short reinspection checklist a manager can use on a phone.\n\nUse the image and video as the only sources of truth. Cite timestamps for video-based observations and distinguish clearly between confirmed discrepancies, apparent discrepancies that need an on-site check, and elements that cannot be verified. Do not invent product names, measurements, policies, or missing visual details."
    }
  ]
}

import { createClient } from '@runware/sdk'

const client = await createClient({ apiKey: process.env.RUNWARE_API_KEY })
await client.connect()

const [result] = await client.run({
  model: 'google:gemma@4-31b',
  messages: [
    {
      role: 'user',
      content: 'Act as an energy-infrastructure strategy consultant. Write a board-ready investment memo for Northline Cold Logistics, a regional seafood cold-storage operator, recommending whether to procure a microgrid for its Harbor Point facility. Use only the facts and assumptions below; do not introduce outside data.\n\nAUDIENCE AND DECISION\nThe memo will go to the CEO, CFO, COO, and two nontechnical board members. They must decide whether to select one of three binding vendor proposals or defer the project for one year. Their priorities, in order, are: preventing inventory loss, maintaining an acceptable financial return, limiting implementation risk, and reducing emissions.\n\nFACILITY BASELINE\n- Harbor Point is a 24/7 refrigerated warehouse in coastal Maine.\n- Annual electricity consumption: 8,400 MWh.\n- Peak demand: 1.65 MW.\n- Current blended electricity cost: $0.142/kWh, comprising energy, demand, and delivery charges.\n- Assume the blended cost rises 3% annually.\n- A controlled shutdown requires four hours; an uncontrolled outage begins threatening product integrity after six hours.\n- Average inventory value on site: $11.8 million.\n- Management estimates a 35% probability of at least one outage lasting longer than six hours during any five-year period.\n- Expected uninsured loss from such an event, after salvage and customer recoveries: $2.4 million.\n- For this analysis, annualize the outage risk as 7% per year and treat avoided expected loss as 7% × $2.4 million × the proposal’s stated share of long-outage exposure mitigated.\n- Existing diesel backup supports only safety systems and office IT, not refrigeration.\n- Current operational emissions: 2,950 metric tons CO2e per year.\n\nFINANCIAL RULES\n- Evaluation period: 15 years from commercial operation.\n- Discount rate: 8% nominal.\n- All listed annual benefits and operating costs begin at the end of Year 1.\n- Electricity savings increase 3% annually unless otherwise stated.\n- O&M costs increase 2% annually.\n- Carbon has no cash value in the base case.\n- Ignore taxes, depreciation, financing costs, residual value, and construction-period discounting.\n- Treat grants as reductions to upfront capital cost.\n- Battery replacement costs occur at the end of the specified year.\n- Calculate net present value, simple payback, and approximate internal rate of return for each proposal. Round dollar results to the nearest $10,000 and percentages to one decimal place. Clearly label reasonable approximations.\n\nPROPOSAL A — TIDAL GRIDWORKS\n- 1.2 MW rooftop solar plus 3.6 MWh lithium-ion battery.\n- Gross capital cost: $5.60 million.\n- Confirmed state resilience grant: $900,000.\n- Annual Year 1 electricity savings: $545,000.\n- Annual Year 1 O&M: $74,000.\n- Battery replacement: $1.05 million at end of Year 10.\n- Mitigates 78% of modeled long-outage exposure.\n- Estimated emissions reduction: 1,090 metric tons CO2e annually.\n- Can sustain critical refrigeration for approximately 10 hours without grid power under typical conditions.\n- Fixed-price EPC contract; completion in 11 months.\n- Vendor has completed nine comparable cold-storage projects.\n- Roof reinforcement is included, but final structural verification remains a condition before notice to proceed.\n\nPROPOSAL B — PINE STATE ENERGY\n- 1.0 MW solar, 2.4 MWh battery, and 1.1 MW renewable-diesel generator.\n- Gross capital cost: $6.35 million.\n- Confirmed federal grant: $1.25 million.\n- Annual Year 1 electricity savings: $495,000.\n- Annual Year 1 O&M: $128,000.\n- Battery replacement: $720,000 at end of Year 10.\n- Mitigates 96% of modeled long-outage exposure, assuming fuel delivery remains available.\n- Estimated emissions reduction: 820 metric tons CO2e annually under expected generator use.\n- Can sustain critical refrigeration for at least 48 hours with a full fuel tank.\n- Completion in 14 months.\n- Vendor has completed three comparable cold-storage projects and 22 hospital microgrids.\n- Contract price may increase by up to $300,000 if interconnection protection upgrades are required; assign a 40% probability to this cost and include its expected value in the base-case economics.\n\nPROPOSAL C — ATLANTIC STORAGE SYSTEMS\n- 4.8 MWh battery with no on-site generation.\n- Gross capital cost: $3.45 million.\n- No grant.\n- Annual Year 1 electricity savings: $430,000.\n- Annual Year 1 O&M: $52,000.\n- Battery replacement: $1.30 million at end of Year 9.\n- Mitigates 52% of modeled long-outage exposure.\n- Estimated emissions reduction: 210 metric tons CO2e annually.\n- Can sustain critical refrigeration for approximately eight hours at current loads.\n- Completion in seven months.\n- Vendor has completed 31 commercial battery projects, but none at refrigerated warehouses.\n- The proposal guarantees 90% usable battery capacity through Year 8; there is no performance guarantee after replacement.\n\nDEFERRAL OPTION\n- No Year 0 capital outlay.\n- The procurement adviser expects equipment and labor pricing to rise 6% over the next year.\n- Tidal Gridworks’ state grant is reserved for nine months and would probably be lost if the decision is deferred.\n- Pine State Energy’s federal grant remains available for 18 months.\n- No vendor will hold its current completion schedule.\n- Outage exposure and current electricity costs continue during the delay.\n\nREQUIRED DELIVERABLE\nWrite a polished memo of approximately 1,500–1,900 words with these sections:\n1. To / From / Date / Subject header.\n2. Executive recommendation stating the decision in the first paragraph.\n3. Decision rationale, explaining why the recommended option best fits the board’s ordered priorities.\n4. A compact comparison table covering net upfront cost, Year 1 net operating benefit, annualized avoided outage loss, base-case NPV, simple payback, approximate IRR, outage capability, emissions reduction, schedule, and major execution risk.\n5. Financial analysis describing the cash-flow method and separating electricity savings, O&M, avoided expected inventory loss, replacement costs, and proposal-specific expected costs. Define simple payback as the first year cumulative undiscounted net cash flow becomes positive.\n6. Sensitivity analysis for the recommended proposal under three separate downside cases: electricity savings are 20% below forecast; no avoided-loss benefit is credited; and upfront cost is 10% higher. Report the revised NPV for each case and explain what each reveals.\n7. Key risks and mitigations, with named owners by role, such as COO, CFO, facilities director, or general counsel.\n8. A 90-day action plan with concrete milestones.\n9. A final board resolution written as one sentence that can be copied into meeting minutes.\n\nMaintain a decisive, sober tone. Explain technical concepts in plain English without oversimplifying the economics. Distinguish calculated facts from judgment. Do not recommend deferral merely because information is incomplete; assess whether the identified uncertainties can be managed through contract terms, diligence, contingencies, or approval conditions.'
    }
  ]
})

import asyncio
import os

from runware import Runware


async def main():
    async with Runware(api_key=os.environ["RUNWARE_API_KEY"]) as client:
        results = await client.run({
            "model": "google:gemma@4-31b",
            "messages": [
                {
                    "role": "user",
                    "content": "Act as an energy-infrastructure strategy consultant. Write a board-ready investment memo for Northline Cold Logistics, a regional seafood cold-storage operator, recommending whether to procure a microgrid for its Harbor Point facility. Use only the facts and assumptions below; do not introduce outside data.\n\nAUDIENCE AND DECISION\nThe memo will go to the CEO, CFO, COO, and two nontechnical board members. They must decide whether to select one of three binding vendor proposals or defer the project for one year. Their priorities, in order, are: preventing inventory loss, maintaining an acceptable financial return, limiting implementation risk, and reducing emissions.\n\nFACILITY BASELINE\n- Harbor Point is a 24/7 refrigerated warehouse in coastal Maine.\n- Annual electricity consumption: 8,400 MWh.\n- Peak demand: 1.65 MW.\n- Current blended electricity cost: $0.142/kWh, comprising energy, demand, and delivery charges.\n- Assume the blended cost rises 3% annually.\n- A controlled shutdown requires four hours; an uncontrolled outage begins threatening product integrity after six hours.\n- Average inventory value on site: $11.8 million.\n- Management estimates a 35% probability of at least one outage lasting longer than six hours during any five-year period.\n- Expected uninsured loss from such an event, after salvage and customer recoveries: $2.4 million.\n- For this analysis, annualize the outage risk as 7% per year and treat avoided expected loss as 7% × $2.4 million × the proposal’s stated share of long-outage exposure mitigated.\n- Existing diesel backup supports only safety systems and office IT, not refrigeration.\n- Current operational emissions: 2,950 metric tons CO2e per year.\n\nFINANCIAL RULES\n- Evaluation period: 15 years from commercial operation.\n- Discount rate: 8% nominal.\n- All listed annual benefits and operating costs begin at the end of Year 1.\n- Electricity savings increase 3% annually unless otherwise stated.\n- O&M costs increase 2% annually.\n- Carbon has no cash value in the base case.\n- Ignore taxes, depreciation, financing costs, residual value, and construction-period discounting.\n- Treat grants as reductions to upfront capital cost.\n- Battery replacement costs occur at the end of the specified year.\n- Calculate net present value, simple payback, and approximate internal rate of return for each proposal. Round dollar results to the nearest $10,000 and percentages to one decimal place. Clearly label reasonable approximations.\n\nPROPOSAL A — TIDAL GRIDWORKS\n- 1.2 MW rooftop solar plus 3.6 MWh lithium-ion battery.\n- Gross capital cost: $5.60 million.\n- Confirmed state resilience grant: $900,000.\n- Annual Year 1 electricity savings: $545,000.\n- Annual Year 1 O&M: $74,000.\n- Battery replacement: $1.05 million at end of Year 10.\n- Mitigates 78% of modeled long-outage exposure.\n- Estimated emissions reduction: 1,090 metric tons CO2e annually.\n- Can sustain critical refrigeration for approximately 10 hours without grid power under typical conditions.\n- Fixed-price EPC contract; completion in 11 months.\n- Vendor has completed nine comparable cold-storage projects.\n- Roof reinforcement is included, but final structural verification remains a condition before notice to proceed.\n\nPROPOSAL B — PINE STATE ENERGY\n- 1.0 MW solar, 2.4 MWh battery, and 1.1 MW renewable-diesel generator.\n- Gross capital cost: $6.35 million.\n- Confirmed federal grant: $1.25 million.\n- Annual Year 1 electricity savings: $495,000.\n- Annual Year 1 O&M: $128,000.\n- Battery replacement: $720,000 at end of Year 10.\n- Mitigates 96% of modeled long-outage exposure, assuming fuel delivery remains available.\n- Estimated emissions reduction: 820 metric tons CO2e annually under expected generator use.\n- Can sustain critical refrigeration for at least 48 hours with a full fuel tank.\n- Completion in 14 months.\n- Vendor has completed three comparable cold-storage projects and 22 hospital microgrids.\n- Contract price may increase by up to $300,000 if interconnection protection upgrades are required; assign a 40% probability to this cost and include its expected value in the base-case economics.\n\nPROPOSAL C — ATLANTIC STORAGE SYSTEMS\n- 4.8 MWh battery with no on-site generation.\n- Gross capital cost: $3.45 million.\n- No grant.\n- Annual Year 1 electricity savings: $430,000.\n- Annual Year 1 O&M: $52,000.\n- Battery replacement: $1.30 million at end of Year 9.\n- Mitigates 52% of modeled long-outage exposure.\n- Estimated emissions reduction: 210 metric tons CO2e annually.\n- Can sustain critical refrigeration for approximately eight hours at current loads.\n- Completion in seven months.\n- Vendor has completed 31 commercial battery projects, but none at refrigerated warehouses.\n- The proposal guarantees 90% usable battery capacity through Year 8; there is no performance guarantee after replacement.\n\nDEFERRAL OPTION\n- No Year 0 capital outlay.\n- The procurement adviser expects equipment and labor pricing to rise 6% over the next year.\n- Tidal Gridworks’ state grant is reserved for nine months and would probably be lost if the decision is deferred.\n- Pine State Energy’s federal grant remains available for 18 months.\n- No vendor will hold its current completion schedule.\n- Outage exposure and current electricity costs continue during the delay.\n\nREQUIRED DELIVERABLE\nWrite a polished memo of approximately 1,500–1,900 words with these sections:\n1. To / From / Date / Subject header.\n2. Executive recommendation stating the decision in the first paragraph.\n3. Decision rationale, explaining why the recommended option best fits the board’s ordered priorities.\n4. A compact comparison table covering net upfront cost, Year 1 net operating benefit, annualized avoided outage loss, base-case NPV, simple payback, approximate IRR, outage capability, emissions reduction, schedule, and major execution risk.\n5. Financial analysis describing the cash-flow method and separating electricity savings, O&M, avoided expected inventory loss, replacement costs, and proposal-specific expected costs. Define simple payback as the first year cumulative undiscounted net cash flow becomes positive.\n6. Sensitivity analysis for the recommended proposal under three separate downside cases: electricity savings are 20% below forecast; no avoided-loss benefit is credited; and upfront cost is 10% higher. Report the revised NPV for each case and explain what each reveals.\n7. Key risks and mitigations, with named owners by role, such as COO, CFO, facilities director, or general counsel.\n8. A 90-day action plan with concrete milestones.\n9. A final board resolution written as one sentence that can be copied into meeting minutes.\n\nMaintain a decisive, sober tone. Explain technical concepts in plain English without oversimplifying the economics. Distinguish calculated facts from judgment. Do not recommend deferral merely because information is incomplete; assess whether the identified uncertainties can be managed through contract terms, diligence, contingencies, or approval conditions."
                }
            ]
        })


asyncio.run(main())

curl https://api.runware.ai/v1 \
  -H "Authorization: Bearer $RUNWARE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '[
    {
      "taskType": "textInference",
      "taskUUID": "67646ffa-2dff-4dd7-8b8d-8625d73bbe6e",
      "model": "google:gemma@4-31b",
      "messages": [
        {
          "role": "user",
          "content": "Act as an energy-infrastructure strategy consultant. Write a board-ready investment memo for Northline Cold Logistics, a regional seafood cold-storage operator, recommending whether to procure a microgrid for its Harbor Point facility. Use only the facts and assumptions below; do not introduce outside data.\n\nAUDIENCE AND DECISION\nThe memo will go to the CEO, CFO, COO, and two nontechnical board members. They must decide whether to select one of three binding vendor proposals or defer the project for one year. Their priorities, in order, are: preventing inventory loss, maintaining an acceptable financial return, limiting implementation risk, and reducing emissions.\n\nFACILITY BASELINE\n- Harbor Point is a 24/7 refrigerated warehouse in coastal Maine.\n- Annual electricity consumption: 8,400 MWh.\n- Peak demand: 1.65 MW.\n- Current blended electricity cost: $0.142/kWh, comprising energy, demand, and delivery charges.\n- Assume the blended cost rises 3% annually.\n- A controlled shutdown requires four hours; an uncontrolled outage begins threatening product integrity after six hours.\n- Average inventory value on site: $11.8 million.\n- Management estimates a 35% probability of at least one outage lasting longer than six hours during any five-year period.\n- Expected uninsured loss from such an event, after salvage and customer recoveries: $2.4 million.\n- For this analysis, annualize the outage risk as 7% per year and treat avoided expected loss as 7% × $2.4 million × the proposal’s stated share of long-outage exposure mitigated.\n- Existing diesel backup supports only safety systems and office IT, not refrigeration.\n- Current operational emissions: 2,950 metric tons CO2e per year.\n\nFINANCIAL RULES\n- Evaluation period: 15 years from commercial operation.\n- Discount rate: 8% nominal.\n- All listed annual benefits and operating costs begin at the end of Year 1.\n- Electricity savings increase 3% annually unless otherwise stated.\n- O&M costs increase 2% annually.\n- Carbon has no cash value in the base case.\n- Ignore taxes, depreciation, financing costs, residual value, and construction-period discounting.\n- Treat grants as reductions to upfront capital cost.\n- Battery replacement costs occur at the end of the specified year.\n- Calculate net present value, simple payback, and approximate internal rate of return for each proposal. Round dollar results to the nearest $10,000 and percentages to one decimal place. Clearly label reasonable approximations.\n\nPROPOSAL A — TIDAL GRIDWORKS\n- 1.2 MW rooftop solar plus 3.6 MWh lithium-ion battery.\n- Gross capital cost: $5.60 million.\n- Confirmed state resilience grant: $900,000.\n- Annual Year 1 electricity savings: $545,000.\n- Annual Year 1 O&M: $74,000.\n- Battery replacement: $1.05 million at end of Year 10.\n- Mitigates 78% of modeled long-outage exposure.\n- Estimated emissions reduction: 1,090 metric tons CO2e annually.\n- Can sustain critical refrigeration for approximately 10 hours without grid power under typical conditions.\n- Fixed-price EPC contract; completion in 11 months.\n- Vendor has completed nine comparable cold-storage projects.\n- Roof reinforcement is included, but final structural verification remains a condition before notice to proceed.\n\nPROPOSAL B — PINE STATE ENERGY\n- 1.0 MW solar, 2.4 MWh battery, and 1.1 MW renewable-diesel generator.\n- Gross capital cost: $6.35 million.\n- Confirmed federal grant: $1.25 million.\n- Annual Year 1 electricity savings: $495,000.\n- Annual Year 1 O&M: $128,000.\n- Battery replacement: $720,000 at end of Year 10.\n- Mitigates 96% of modeled long-outage exposure, assuming fuel delivery remains available.\n- Estimated emissions reduction: 820 metric tons CO2e annually under expected generator use.\n- Can sustain critical refrigeration for at least 48 hours with a full fuel tank.\n- Completion in 14 months.\n- Vendor has completed three comparable cold-storage projects and 22 hospital microgrids.\n- Contract price may increase by up to $300,000 if interconnection protection upgrades are required; assign a 40% probability to this cost and include its expected value in the base-case economics.\n\nPROPOSAL C — ATLANTIC STORAGE SYSTEMS\n- 4.8 MWh battery with no on-site generation.\n- Gross capital cost: $3.45 million.\n- No grant.\n- Annual Year 1 electricity savings: $430,000.\n- Annual Year 1 O&M: $52,000.\n- Battery replacement: $1.30 million at end of Year 9.\n- Mitigates 52% of modeled long-outage exposure.\n- Estimated emissions reduction: 210 metric tons CO2e annually.\n- Can sustain critical refrigeration for approximately eight hours at current loads.\n- Completion in seven months.\n- Vendor has completed 31 commercial battery projects, but none at refrigerated warehouses.\n- The proposal guarantees 90% usable battery capacity through Year 8; there is no performance guarantee after replacement.\n\nDEFERRAL OPTION\n- No Year 0 capital outlay.\n- The procurement adviser expects equipment and labor pricing to rise 6% over the next year.\n- Tidal Gridworks’ state grant is reserved for nine months and would probably be lost if the decision is deferred.\n- Pine State Energy’s federal grant remains available for 18 months.\n- No vendor will hold its current completion schedule.\n- Outage exposure and current electricity costs continue during the delay.\n\nREQUIRED DELIVERABLE\nWrite a polished memo of approximately 1,500–1,900 words with these sections:\n1. To / From / Date / Subject header.\n2. Executive recommendation stating the decision in the first paragraph.\n3. Decision rationale, explaining why the recommended option best fits the board’s ordered priorities.\n4. A compact comparison table covering net upfront cost, Year 1 net operating benefit, annualized avoided outage loss, base-case NPV, simple payback, approximate IRR, outage capability, emissions reduction, schedule, and major execution risk.\n5. Financial analysis describing the cash-flow method and separating electricity savings, O&M, avoided expected inventory loss, replacement costs, and proposal-specific expected costs. Define simple payback as the first year cumulative undiscounted net cash flow becomes positive.\n6. Sensitivity analysis for the recommended proposal under three separate downside cases: electricity savings are 20% below forecast; no avoided-loss benefit is credited; and upfront cost is 10% higher. Report the revised NPV for each case and explain what each reveals.\n7. Key risks and mitigations, with named owners by role, such as COO, CFO, facilities director, or general counsel.\n8. A 90-day action plan with concrete milestones.\n9. A final board resolution written as one sentence that can be copied into meeting minutes.\n\nMaintain a decisive, sober tone. Explain technical concepts in plain English without oversimplifying the economics. Distinguish calculated facts from judgment. Do not recommend deferral merely because information is incomplete; assess whether the identified uncertainties can be managed through contract terms, diligence, contingencies, or approval conditions."
        }
      ]
    }
  ]'

runware run google:gemma@4-31b \
  messages.0.role=user \
  messages.0.content="Act as an energy-infrastructure strategy consultant. Write a board-ready investment memo for Northline Cold Logistics, a regional seafood cold-storage operator, recommending whether to procure a microgrid for its Harbor Point facility. Use only the facts and assumptions below; do not introduce outside data.

AUDIENCE AND DECISION
The memo will go to the CEO, CFO, COO, and two nontechnical board members. They must decide whether to select one of three binding vendor proposals or defer the project for one year. Their priorities, in order, are: preventing inventory loss, maintaining an acceptable financial return, limiting implementation risk, and reducing emissions.

FACILITY BASELINE
- Harbor Point is a 24/7 refrigerated warehouse in coastal Maine.
- Annual electricity consumption: 8,400 MWh.
- Peak demand: 1.65 MW.
- Current blended electricity cost: \$0.142/kWh, comprising energy, demand, and delivery charges.
- Assume the blended cost rises 3% annually.
- A controlled shutdown requires four hours; an uncontrolled outage begins threatening product integrity after six hours.
- Average inventory value on site: \$11.8 million.
- Management estimates a 35% probability of at least one outage lasting longer than six hours during any five-year period.
- Expected uninsured loss from such an event, after salvage and customer recoveries: \$2.4 million.
- For this analysis, annualize the outage risk as 7% per year and treat avoided expected loss as 7% × \$2.4 million × the proposal’s stated share of long-outage exposure mitigated.
- Existing diesel backup supports only safety systems and office IT, not refrigeration.
- Current operational emissions: 2,950 metric tons CO2e per year.

FINANCIAL RULES
- Evaluation period: 15 years from commercial operation.
- Discount rate: 8% nominal.
- All listed annual benefits and operating costs begin at the end of Year 1.
- Electricity savings increase 3% annually unless otherwise stated.
- O&M costs increase 2% annually.
- Carbon has no cash value in the base case.
- Ignore taxes, depreciation, financing costs, residual value, and construction-period discounting.
- Treat grants as reductions to upfront capital cost.
- Battery replacement costs occur at the end of the specified year.
- Calculate net present value, simple payback, and approximate internal rate of return for each proposal. Round dollar results to the nearest \$10,000 and percentages to one decimal place. Clearly label reasonable approximations.

PROPOSAL A — TIDAL GRIDWORKS
- 1.2 MW rooftop solar plus 3.6 MWh lithium-ion battery.
- Gross capital cost: \$5.60 million.
- Confirmed state resilience grant: \$900,000.
- Annual Year 1 electricity savings: \$545,000.
- Annual Year 1 O&M: \$74,000.
- Battery replacement: \$1.05 million at end of Year 10.
- Mitigates 78% of modeled long-outage exposure.
- Estimated emissions reduction: 1,090 metric tons CO2e annually.
- Can sustain critical refrigeration for approximately 10 hours without grid power under typical conditions.
- Fixed-price EPC contract; completion in 11 months.
- Vendor has completed nine comparable cold-storage projects.
- Roof reinforcement is included, but final structural verification remains a condition before notice to proceed.

PROPOSAL B — PINE STATE ENERGY
- 1.0 MW solar, 2.4 MWh battery, and 1.1 MW renewable-diesel generator.
- Gross capital cost: \$6.35 million.
- Confirmed federal grant: \$1.25 million.
- Annual Year 1 electricity savings: \$495,000.
- Annual Year 1 O&M: \$128,000.
- Battery replacement: \$720,000 at end of Year 10.
- Mitigates 96% of modeled long-outage exposure, assuming fuel delivery remains available.
- Estimated emissions reduction: 820 metric tons CO2e annually under expected generator use.
- Can sustain critical refrigeration for at least 48 hours with a full fuel tank.
- Completion in 14 months.
- Vendor has completed three comparable cold-storage projects and 22 hospital microgrids.
- Contract price may increase by up to \$300,000 if interconnection protection upgrades are required; assign a 40% probability to this cost and include its expected value in the base-case economics.

PROPOSAL C — ATLANTIC STORAGE SYSTEMS
- 4.8 MWh battery with no on-site generation.
- Gross capital cost: \$3.45 million.
- No grant.
- Annual Year 1 electricity savings: \$430,000.
- Annual Year 1 O&M: \$52,000.
- Battery replacement: \$1.30 million at end of Year 9.
- Mitigates 52% of modeled long-outage exposure.
- Estimated emissions reduction: 210 metric tons CO2e annually.
- Can sustain critical refrigeration for approximately eight hours at current loads.
- Completion in seven months.
- Vendor has completed 31 commercial battery projects, but none at refrigerated warehouses.
- The proposal guarantees 90% usable battery capacity through Year 8; there is no performance guarantee after replacement.

DEFERRAL OPTION
- No Year 0 capital outlay.
- The procurement adviser expects equipment and labor pricing to rise 6% over the next year.
- Tidal Gridworks’ state grant is reserved for nine months and would probably be lost if the decision is deferred.
- Pine State Energy’s federal grant remains available for 18 months.
- No vendor will hold its current completion schedule.
- Outage exposure and current electricity costs continue during the delay.

REQUIRED DELIVERABLE
Write a polished memo of approximately 1,500–1,900 words with these sections:
1. To / From / Date / Subject header.
2. Executive recommendation stating the decision in the first paragraph.
3. Decision rationale, explaining why the recommended option best fits the board’s ordered priorities.
4. A compact comparison table covering net upfront cost, Year 1 net operating benefit, annualized avoided outage loss, base-case NPV, simple payback, approximate IRR, outage capability, emissions reduction, schedule, and major execution risk.
5. Financial analysis describing the cash-flow method and separating electricity savings, O&M, avoided expected inventory loss, replacement costs, and proposal-specific expected costs. Define simple payback as the first year cumulative undiscounted net cash flow becomes positive.
6. Sensitivity analysis for the recommended proposal under three separate downside cases: electricity savings are 20% below forecast; no avoided-loss benefit is credited; and upfront cost is 10% higher. Report the revised NPV for each case and explain what each reveals.
7. Key risks and mitigations, with named owners by role, such as COO, CFO, facilities director, or general counsel.
8. A 90-day action plan with concrete milestones.
9. A final board resolution written as one sentence that can be copied into meeting minutes.

Maintain a decisive, sober tone. Explain technical concepts in plain English without oversimplifying the economics. Distinguish calculated facts from judgment. Do not recommend deferral merely because information is incomplete; assess whether the identified uncertainties can be managed through contract terms, diligence, contingencies, or approval conditions."

{
  "taskType": "textInference",
  "taskUUID": "67646ffa-2dff-4dd7-8b8d-8625d73bbe6e",
  "model": "google:gemma@4-31b",
  "messages": [
    {
      "role": "user",
      "content": "Act as an energy-infrastructure strategy consultant. Write a board-ready investment memo for Northline Cold Logistics, a regional seafood cold-storage operator, recommending whether to procure a microgrid for its Harbor Point facility. Use only the facts and assumptions below; do not introduce outside data.\n\nAUDIENCE AND DECISION\nThe memo will go to the CEO, CFO, COO, and two nontechnical board members. They must decide whether to select one of three binding vendor proposals or defer the project for one year. Their priorities, in order, are: preventing inventory loss, maintaining an acceptable financial return, limiting implementation risk, and reducing emissions.\n\nFACILITY BASELINE\n- Harbor Point is a 24/7 refrigerated warehouse in coastal Maine.\n- Annual electricity consumption: 8,400 MWh.\n- Peak demand: 1.65 MW.\n- Current blended electricity cost: $0.142/kWh, comprising energy, demand, and delivery charges.\n- Assume the blended cost rises 3% annually.\n- A controlled shutdown requires four hours; an uncontrolled outage begins threatening product integrity after six hours.\n- Average inventory value on site: $11.8 million.\n- Management estimates a 35% probability of at least one outage lasting longer than six hours during any five-year period.\n- Expected uninsured loss from such an event, after salvage and customer recoveries: $2.4 million.\n- For this analysis, annualize the outage risk as 7% per year and treat avoided expected loss as 7% × $2.4 million × the proposal’s stated share of long-outage exposure mitigated.\n- Existing diesel backup supports only safety systems and office IT, not refrigeration.\n- Current operational emissions: 2,950 metric tons CO2e per year.\n\nFINANCIAL RULES\n- Evaluation period: 15 years from commercial operation.\n- Discount rate: 8% nominal.\n- All listed annual benefits and operating costs begin at the end of Year 1.\n- Electricity savings increase 3% annually unless otherwise stated.\n- O&M costs increase 2% annually.\n- Carbon has no cash value in the base case.\n- Ignore taxes, depreciation, financing costs, residual value, and construction-period discounting.\n- Treat grants as reductions to upfront capital cost.\n- Battery replacement costs occur at the end of the specified year.\n- Calculate net present value, simple payback, and approximate internal rate of return for each proposal. Round dollar results to the nearest $10,000 and percentages to one decimal place. Clearly label reasonable approximations.\n\nPROPOSAL A — TIDAL GRIDWORKS\n- 1.2 MW rooftop solar plus 3.6 MWh lithium-ion battery.\n- Gross capital cost: $5.60 million.\n- Confirmed state resilience grant: $900,000.\n- Annual Year 1 electricity savings: $545,000.\n- Annual Year 1 O&M: $74,000.\n- Battery replacement: $1.05 million at end of Year 10.\n- Mitigates 78% of modeled long-outage exposure.\n- Estimated emissions reduction: 1,090 metric tons CO2e annually.\n- Can sustain critical refrigeration for approximately 10 hours without grid power under typical conditions.\n- Fixed-price EPC contract; completion in 11 months.\n- Vendor has completed nine comparable cold-storage projects.\n- Roof reinforcement is included, but final structural verification remains a condition before notice to proceed.\n\nPROPOSAL B — PINE STATE ENERGY\n- 1.0 MW solar, 2.4 MWh battery, and 1.1 MW renewable-diesel generator.\n- Gross capital cost: $6.35 million.\n- Confirmed federal grant: $1.25 million.\n- Annual Year 1 electricity savings: $495,000.\n- Annual Year 1 O&M: $128,000.\n- Battery replacement: $720,000 at end of Year 10.\n- Mitigates 96% of modeled long-outage exposure, assuming fuel delivery remains available.\n- Estimated emissions reduction: 820 metric tons CO2e annually under expected generator use.\n- Can sustain critical refrigeration for at least 48 hours with a full fuel tank.\n- Completion in 14 months.\n- Vendor has completed three comparable cold-storage projects and 22 hospital microgrids.\n- Contract price may increase by up to $300,000 if interconnection protection upgrades are required; assign a 40% probability to this cost and include its expected value in the base-case economics.\n\nPROPOSAL C — ATLANTIC STORAGE SYSTEMS\n- 4.8 MWh battery with no on-site generation.\n- Gross capital cost: $3.45 million.\n- No grant.\n- Annual Year 1 electricity savings: $430,000.\n- Annual Year 1 O&M: $52,000.\n- Battery replacement: $1.30 million at end of Year 9.\n- Mitigates 52% of modeled long-outage exposure.\n- Estimated emissions reduction: 210 metric tons CO2e annually.\n- Can sustain critical refrigeration for approximately eight hours at current loads.\n- Completion in seven months.\n- Vendor has completed 31 commercial battery projects, but none at refrigerated warehouses.\n- The proposal guarantees 90% usable battery capacity through Year 8; there is no performance guarantee after replacement.\n\nDEFERRAL OPTION\n- No Year 0 capital outlay.\n- The procurement adviser expects equipment and labor pricing to rise 6% over the next year.\n- Tidal Gridworks’ state grant is reserved for nine months and would probably be lost if the decision is deferred.\n- Pine State Energy’s federal grant remains available for 18 months.\n- No vendor will hold its current completion schedule.\n- Outage exposure and current electricity costs continue during the delay.\n\nREQUIRED DELIVERABLE\nWrite a polished memo of approximately 1,500–1,900 words with these sections:\n1. To / From / Date / Subject header.\n2. Executive recommendation stating the decision in the first paragraph.\n3. Decision rationale, explaining why the recommended option best fits the board’s ordered priorities.\n4. A compact comparison table covering net upfront cost, Year 1 net operating benefit, annualized avoided outage loss, base-case NPV, simple payback, approximate IRR, outage capability, emissions reduction, schedule, and major execution risk.\n5. Financial analysis describing the cash-flow method and separating electricity savings, O&M, avoided expected inventory loss, replacement costs, and proposal-specific expected costs. Define simple payback as the first year cumulative undiscounted net cash flow becomes positive.\n6. Sensitivity analysis for the recommended proposal under three separate downside cases: electricity savings are 20% below forecast; no avoided-loss benefit is credited; and upfront cost is 10% higher. Report the revised NPV for each case and explain what each reveals.\n7. Key risks and mitigations, with named owners by role, such as COO, CFO, facilities director, or general counsel.\n8. A 90-day action plan with concrete milestones.\n9. A final board resolution written as one sentence that can be copied into meeting minutes.\n\nMaintain a decisive, sober tone. Explain technical concepts in plain English without oversimplifying the economics. Distinguish calculated facts from judgment. Do not recommend deferral merely because information is incomplete; assess whether the identified uncertainties can be managed through contract terms, diligence, contingencies, or approval conditions."
    }
  ]
}

import { createClient } from '@runware/sdk'

const client = await createClient({ apiKey: process.env.RUNWARE_API_KEY })
await client.connect()

const [result] = await client.run({
  model: 'google:gemma@4-31b',
  settings: {
    systemPrompt: 'You are a careful conversation analyst. Preserve uncertainty, distinguish facts from guesses, and produce structured answers without inventing details.',
    temperature: 0.7,
    topP: 0.9,
    maxTokens: 8192,
    thinkingLevel: 'high'
  },
  messages: [
    {
      role: 'user',
      content: 'Below is a random conversation by humans recorded near the folding tables of a busy laundromat. Analyze it and provide: 1) a 10-bullet factual summary, 2) each person\'s likely goals, 3) unresolved questions, 4) practical next steps, 5) any subtle tension or humor, and 6) a compact timeline.\n\nConversation:\n\nMaya: If that dryer eats another quarter, I am writing it a strongly worded poem.\nJonah: A poem?\nMaya: Yes. Rhymed couplets. Very legal tone.\nPriya: Does anyone know if the number on the wall actually works? The service number?\nEllis: It works in the sense that a voicemail says hello, then abandons you emotionally.\nJonah: That is still more reliable than my landlord.\nMaya: Your landlord still hasn\'t fixed the radiator?\nJonah: He says it\'s fixed because he looked at it from the doorway and felt optimistic.\nPriya: I have a screwdriver in my bag.\nEllis: Why?\nPriya: I also have three granola bars, a mini tape measure, and two birthday candles. I refuse to explain myself.\nMaya: You are the person people hope is on their train when things get weird.\nJonah: Speaking of weird, did either of you see the sock stuck to the ceiling above washer six?\nEllis: I chose not to receive that information.\nPriya: That\'s not a sock. That\'s a baby mitten.\nMaya: Worse.\nJonah: How does a mitten reach the ceiling?\nEllis: Ambition.\nPriya: Static, maybe. Or a tall parent with poor aim.\nMaya: The tall parent theory feels generous.\nJonah: My blue load has nine minutes. Who\'s guarding the machines when I get coffee?\nEllis: I can watch them if you bring me something with cinnamon.\nPriya: I want tea, but only if they don\'t make it taste like boiled hay.\nMaya: That\'s most tea in this zip code.\nJonah: Fine. Cinnamon thing for Ellis, respectable tea for Priya, nothing for Maya because she insults beverages.\nMaya: I accept my consequences.\nPriya: Wait, before you go, is that your gray hoodie in dryer three?\nJonah: No, mine has a cracked zipper and a paint stain shaped like Vermont.\nEllis: That hoodie has a paint stain shaped like a duck sneezing.\nMaya: That is incredibly specific and somehow accurate.\nPriya: Then whose is it? It\'s been tumbling for an hour.\nEllis: Maybe it belongs to the man who left with one shoe earlier.\nJonah: I thought we all agreed not to mention him.\nMaya: We agreed not to speculate about him. Mentioning is legally distinct.\nPriya: He seemed fine. Just determined.\nEllis: Determined toward what?\nPriya: Possibly balance.\nMaya: Jonah, coffee. Go before your washer enters its dramatic final spin.\nJonah: If machine two finishes early, text me.\nEllis: You are standing twelve feet away.\nJonah: Text me spiritually.\nPriya: I\'ll wave a dryer sheet like a flag.\nMaya: Make it solemn.\nJonah: Back in five.\n\n[Jonah leaves]\n\nEllis: So, Maya, did you send that email?\nMaya: Which email?\nPriya: The face you made means the difficult one.\nMaya: I drafted it.\nEllis: Drafting is not sending.\nMaya: Thank you, calendar with shoes.\nPriya: Is this about the studio space?\nMaya: Yes. The owner raised the fee again, but only for people not signing annual agreements.\nEllis: That\'s pressure disguised as paperwork.\nMaya: Exactly. I don\'t know if I should push back or just move my classes online for a month.\nPriya: Are your students mostly local?\nMaya: Half local, half whoever discovers me through short videos and thinks beginner watercolor requires emotional bravery.\nEllis: It does, frankly.\nPriya: If you move online, do you lose the people who come for company?\nMaya: Probably. That\'s the part that bothers me.\nEllis: Then the email should say that. Not as a complaint, as a consequence.\nMaya: You make it sound simple.\nEllis: It is simple. Not easy.\nPriya: I can read the draft if you want.\nMaya: You really do carry everything in that bag.\nPriya: Including opinions.\n\n[Washer chime]\n\nEllis: Was that two?\nPriya: No, four. Two has three minutes.\nMaya: How do you know?\nPriya: I observe patterns while pretending not to listen.\nEllis: Terrifying skill.\nPriya: Useful skill.\nMaya: Can you observe whether the ceiling mitten is moving?\nPriya: I will not look again.\n\n[Jonah returns]\n\nJonah: Bad news. Tea options were mint, black, and something labeled forest calm.\nPriya: I distrust forest calm.\nJonah: I chose black.\nPriya: Correct.\nEllis: Cinnamon?\nJonah: Cinnamon roll. It was the last one. The barista said I saved it from becoming stale, which felt heroic.\nMaya: Did you get yourself coffee?\nJonah: Yes, but I spilled some on my sleeve, so now my arm is alert.\nPriya: Machine two just stopped.\nJonah: See? Spiritual texting worked.\nEllis: That was a chime.\nJonah: Different traditions.\nMaya: Your blue clothes are done. Also, we may have solved my email crisis.\nJonah: I leave for six minutes and governance occurs.\nPriya: Not governance. Boundary setting.\nEllis: With maybe three sharp sentences.\nJonah: Excellent. Add one sentence threatening poetry.\nMaya: That\'s for the dryer.\nJonah: Everything deserves one warning poem.\nPriya: Except landlords.\nEllis: Landlords get haiku invoices.\nMaya: Five syllables: fix the heat now please.\nJonah: That\'s five?\nPriya: It is if you count despair as silent.\nEllis: I love this laundromat.\nMaya: You love chaos with folding carts.\nJonah: Same thing.\n\nEnd of conversation.'
    }
  ]
})

import asyncio
import os

from runware import Runware


async def main():
    async with Runware(api_key=os.environ["RUNWARE_API_KEY"]) as client:
        results = await client.run({
            "model": "google:gemma@4-31b",
            "settings": {
                "systemPrompt": "You are a careful conversation analyst. Preserve uncertainty, distinguish facts from guesses, and produce structured answers without inventing details.",
                "temperature": 0.7,
                "topP": 0.9,
                "maxTokens": 8192,
                "thinkingLevel": "high"
            },
            "messages": [
                {
                    "role": "user",
                    "content": "Below is a random conversation by humans recorded near the folding tables of a busy laundromat. Analyze it and provide: 1) a 10-bullet factual summary, 2) each person's likely goals, 3) unresolved questions, 4) practical next steps, 5) any subtle tension or humor, and 6) a compact timeline.\n\nConversation:\n\nMaya: If that dryer eats another quarter, I am writing it a strongly worded poem.\nJonah: A poem?\nMaya: Yes. Rhymed couplets. Very legal tone.\nPriya: Does anyone know if the number on the wall actually works? The service number?\nEllis: It works in the sense that a voicemail says hello, then abandons you emotionally.\nJonah: That is still more reliable than my landlord.\nMaya: Your landlord still hasn't fixed the radiator?\nJonah: He says it's fixed because he looked at it from the doorway and felt optimistic.\nPriya: I have a screwdriver in my bag.\nEllis: Why?\nPriya: I also have three granola bars, a mini tape measure, and two birthday candles. I refuse to explain myself.\nMaya: You are the person people hope is on their train when things get weird.\nJonah: Speaking of weird, did either of you see the sock stuck to the ceiling above washer six?\nEllis: I chose not to receive that information.\nPriya: That's not a sock. That's a baby mitten.\nMaya: Worse.\nJonah: How does a mitten reach the ceiling?\nEllis: Ambition.\nPriya: Static, maybe. Or a tall parent with poor aim.\nMaya: The tall parent theory feels generous.\nJonah: My blue load has nine minutes. Who's guarding the machines when I get coffee?\nEllis: I can watch them if you bring me something with cinnamon.\nPriya: I want tea, but only if they don't make it taste like boiled hay.\nMaya: That's most tea in this zip code.\nJonah: Fine. Cinnamon thing for Ellis, respectable tea for Priya, nothing for Maya because she insults beverages.\nMaya: I accept my consequences.\nPriya: Wait, before you go, is that your gray hoodie in dryer three?\nJonah: No, mine has a cracked zipper and a paint stain shaped like Vermont.\nEllis: That hoodie has a paint stain shaped like a duck sneezing.\nMaya: That is incredibly specific and somehow accurate.\nPriya: Then whose is it? It's been tumbling for an hour.\nEllis: Maybe it belongs to the man who left with one shoe earlier.\nJonah: I thought we all agreed not to mention him.\nMaya: We agreed not to speculate about him. Mentioning is legally distinct.\nPriya: He seemed fine. Just determined.\nEllis: Determined toward what?\nPriya: Possibly balance.\nMaya: Jonah, coffee. Go before your washer enters its dramatic final spin.\nJonah: If machine two finishes early, text me.\nEllis: You are standing twelve feet away.\nJonah: Text me spiritually.\nPriya: I'll wave a dryer sheet like a flag.\nMaya: Make it solemn.\nJonah: Back in five.\n\n[Jonah leaves]\n\nEllis: So, Maya, did you send that email?\nMaya: Which email?\nPriya: The face you made means the difficult one.\nMaya: I drafted it.\nEllis: Drafting is not sending.\nMaya: Thank you, calendar with shoes.\nPriya: Is this about the studio space?\nMaya: Yes. The owner raised the fee again, but only for people not signing annual agreements.\nEllis: That's pressure disguised as paperwork.\nMaya: Exactly. I don't know if I should push back or just move my classes online for a month.\nPriya: Are your students mostly local?\nMaya: Half local, half whoever discovers me through short videos and thinks beginner watercolor requires emotional bravery.\nEllis: It does, frankly.\nPriya: If you move online, do you lose the people who come for company?\nMaya: Probably. That's the part that bothers me.\nEllis: Then the email should say that. Not as a complaint, as a consequence.\nMaya: You make it sound simple.\nEllis: It is simple. Not easy.\nPriya: I can read the draft if you want.\nMaya: You really do carry everything in that bag.\nPriya: Including opinions.\n\n[Washer chime]\n\nEllis: Was that two?\nPriya: No, four. Two has three minutes.\nMaya: How do you know?\nPriya: I observe patterns while pretending not to listen.\nEllis: Terrifying skill.\nPriya: Useful skill.\nMaya: Can you observe whether the ceiling mitten is moving?\nPriya: I will not look again.\n\n[Jonah returns]\n\nJonah: Bad news. Tea options were mint, black, and something labeled forest calm.\nPriya: I distrust forest calm.\nJonah: I chose black.\nPriya: Correct.\nEllis: Cinnamon?\nJonah: Cinnamon roll. It was the last one. The barista said I saved it from becoming stale, which felt heroic.\nMaya: Did you get yourself coffee?\nJonah: Yes, but I spilled some on my sleeve, so now my arm is alert.\nPriya: Machine two just stopped.\nJonah: See? Spiritual texting worked.\nEllis: That was a chime.\nJonah: Different traditions.\nMaya: Your blue clothes are done. Also, we may have solved my email crisis.\nJonah: I leave for six minutes and governance occurs.\nPriya: Not governance. Boundary setting.\nEllis: With maybe three sharp sentences.\nJonah: Excellent. Add one sentence threatening poetry.\nMaya: That's for the dryer.\nJonah: Everything deserves one warning poem.\nPriya: Except landlords.\nEllis: Landlords get haiku invoices.\nMaya: Five syllables: fix the heat now please.\nJonah: That's five?\nPriya: It is if you count despair as silent.\nEllis: I love this laundromat.\nMaya: You love chaos with folding carts.\nJonah: Same thing.\n\nEnd of conversation."
                }
            ]
        })


asyncio.run(main())

curl https://api.runware.ai/v1 \
  -H "Authorization: Bearer $RUNWARE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '[
    {
      "taskType": "textInference",
      "taskUUID": "b6bdff4c-255b-4c94-a3c7-b75a32549519",
      "model": "google:gemma@4-31b",
      "settings": {
        "systemPrompt": "You are a careful conversation analyst. Preserve uncertainty, distinguish facts from guesses, and produce structured answers without inventing details.",
        "temperature": 0.7,
        "topP": 0.9,
        "maxTokens": 8192,
        "thinkingLevel": "high"
      },
      "messages": [
        {
          "role": "user",
          "content": "Below is a random conversation by humans recorded near the folding tables of a busy laundromat. Analyze it and provide: 1) a 10-bullet factual summary, 2) each person's likely goals, 3) unresolved questions, 4) practical next steps, 5) any subtle tension or humor, and 6) a compact timeline.\n\nConversation:\n\nMaya: If that dryer eats another quarter, I am writing it a strongly worded poem.\nJonah: A poem?\nMaya: Yes. Rhymed couplets. Very legal tone.\nPriya: Does anyone know if the number on the wall actually works? The service number?\nEllis: It works in the sense that a voicemail says hello, then abandons you emotionally.\nJonah: That is still more reliable than my landlord.\nMaya: Your landlord still hasn't fixed the radiator?\nJonah: He says it's fixed because he looked at it from the doorway and felt optimistic.\nPriya: I have a screwdriver in my bag.\nEllis: Why?\nPriya: I also have three granola bars, a mini tape measure, and two birthday candles. I refuse to explain myself.\nMaya: You are the person people hope is on their train when things get weird.\nJonah: Speaking of weird, did either of you see the sock stuck to the ceiling above washer six?\nEllis: I chose not to receive that information.\nPriya: That's not a sock. That's a baby mitten.\nMaya: Worse.\nJonah: How does a mitten reach the ceiling?\nEllis: Ambition.\nPriya: Static, maybe. Or a tall parent with poor aim.\nMaya: The tall parent theory feels generous.\nJonah: My blue load has nine minutes. Who's guarding the machines when I get coffee?\nEllis: I can watch them if you bring me something with cinnamon.\nPriya: I want tea, but only if they don't make it taste like boiled hay.\nMaya: That's most tea in this zip code.\nJonah: Fine. Cinnamon thing for Ellis, respectable tea for Priya, nothing for Maya because she insults beverages.\nMaya: I accept my consequences.\nPriya: Wait, before you go, is that your gray hoodie in dryer three?\nJonah: No, mine has a cracked zipper and a paint stain shaped like Vermont.\nEllis: That hoodie has a paint stain shaped like a duck sneezing.\nMaya: That is incredibly specific and somehow accurate.\nPriya: Then whose is it? It's been tumbling for an hour.\nEllis: Maybe it belongs to the man who left with one shoe earlier.\nJonah: I thought we all agreed not to mention him.\nMaya: We agreed not to speculate about him. Mentioning is legally distinct.\nPriya: He seemed fine. Just determined.\nEllis: Determined toward what?\nPriya: Possibly balance.\nMaya: Jonah, coffee. Go before your washer enters its dramatic final spin.\nJonah: If machine two finishes early, text me.\nEllis: You are standing twelve feet away.\nJonah: Text me spiritually.\nPriya: I'll wave a dryer sheet like a flag.\nMaya: Make it solemn.\nJonah: Back in five.\n\n[Jonah leaves]\n\nEllis: So, Maya, did you send that email?\nMaya: Which email?\nPriya: The face you made means the difficult one.\nMaya: I drafted it.\nEllis: Drafting is not sending.\nMaya: Thank you, calendar with shoes.\nPriya: Is this about the studio space?\nMaya: Yes. The owner raised the fee again, but only for people not signing annual agreements.\nEllis: That's pressure disguised as paperwork.\nMaya: Exactly. I don't know if I should push back or just move my classes online for a month.\nPriya: Are your students mostly local?\nMaya: Half local, half whoever discovers me through short videos and thinks beginner watercolor requires emotional bravery.\nEllis: It does, frankly.\nPriya: If you move online, do you lose the people who come for company?\nMaya: Probably. That's the part that bothers me.\nEllis: Then the email should say that. Not as a complaint, as a consequence.\nMaya: You make it sound simple.\nEllis: It is simple. Not easy.\nPriya: I can read the draft if you want.\nMaya: You really do carry everything in that bag.\nPriya: Including opinions.\n\n[Washer chime]\n\nEllis: Was that two?\nPriya: No, four. Two has three minutes.\nMaya: How do you know?\nPriya: I observe patterns while pretending not to listen.\nEllis: Terrifying skill.\nPriya: Useful skill.\nMaya: Can you observe whether the ceiling mitten is moving?\nPriya: I will not look again.\n\n[Jonah returns]\n\nJonah: Bad news. Tea options were mint, black, and something labeled forest calm.\nPriya: I distrust forest calm.\nJonah: I chose black.\nPriya: Correct.\nEllis: Cinnamon?\nJonah: Cinnamon roll. It was the last one. The barista said I saved it from becoming stale, which felt heroic.\nMaya: Did you get yourself coffee?\nJonah: Yes, but I spilled some on my sleeve, so now my arm is alert.\nPriya: Machine two just stopped.\nJonah: See? Spiritual texting worked.\nEllis: That was a chime.\nJonah: Different traditions.\nMaya: Your blue clothes are done. Also, we may have solved my email crisis.\nJonah: I leave for six minutes and governance occurs.\nPriya: Not governance. Boundary setting.\nEllis: With maybe three sharp sentences.\nJonah: Excellent. Add one sentence threatening poetry.\nMaya: That's for the dryer.\nJonah: Everything deserves one warning poem.\nPriya: Except landlords.\nEllis: Landlords get haiku invoices.\nMaya: Five syllables: fix the heat now please.\nJonah: That's five?\nPriya: It is if you count despair as silent.\nEllis: I love this laundromat.\nMaya: You love chaos with folding carts.\nJonah: Same thing.\n\nEnd of conversation."
        }
      ]
    }
  ]'

runware run google:gemma@4-31b \
  settings.systemPrompt="You are a careful conversation analyst. Preserve uncertainty, distinguish facts from guesses, and produce structured answers without inventing details." \
  settings.temperature=0.7 \
  settings.topP=0.9 \
  settings.maxTokens=8192 \
  settings.thinkingLevel=high \
  messages.0.role=user \
  messages.0.content="Below is a random conversation by humans recorded near the folding tables of a busy laundromat. Analyze it and provide: 1) a 10-bullet factual summary, 2) each person's likely goals, 3) unresolved questions, 4) practical next steps, 5) any subtle tension or humor, and 6) a compact timeline.

Conversation:

Maya: If that dryer eats another quarter, I am writing it a strongly worded poem.
Jonah: A poem?
Maya: Yes. Rhymed couplets. Very legal tone.
Priya: Does anyone know if the number on the wall actually works? The service number?
Ellis: It works in the sense that a voicemail says hello, then abandons you emotionally.
Jonah: That is still more reliable than my landlord.
Maya: Your landlord still hasn't fixed the radiator?
Jonah: He says it's fixed because he looked at it from the doorway and felt optimistic.
Priya: I have a screwdriver in my bag.
Ellis: Why?
Priya: I also have three granola bars, a mini tape measure, and two birthday candles. I refuse to explain myself.
Maya: You are the person people hope is on their train when things get weird.
Jonah: Speaking of weird, did either of you see the sock stuck to the ceiling above washer six?
Ellis: I chose not to receive that information.
Priya: That's not a sock. That's a baby mitten.
Maya: Worse.
Jonah: How does a mitten reach the ceiling?
Ellis: Ambition.
Priya: Static, maybe. Or a tall parent with poor aim.
Maya: The tall parent theory feels generous.
Jonah: My blue load has nine minutes. Who's guarding the machines when I get coffee?
Ellis: I can watch them if you bring me something with cinnamon.
Priya: I want tea, but only if they don't make it taste like boiled hay.
Maya: That's most tea in this zip code.
Jonah: Fine. Cinnamon thing for Ellis, respectable tea for Priya, nothing for Maya because she insults beverages.
Maya: I accept my consequences.
Priya: Wait, before you go, is that your gray hoodie in dryer three?
Jonah: No, mine has a cracked zipper and a paint stain shaped like Vermont.
Ellis: That hoodie has a paint stain shaped like a duck sneezing.
Maya: That is incredibly specific and somehow accurate.
Priya: Then whose is it? It's been tumbling for an hour.
Ellis: Maybe it belongs to the man who left with one shoe earlier.
Jonah: I thought we all agreed not to mention him.
Maya: We agreed not to speculate about him. Mentioning is legally distinct.
Priya: He seemed fine. Just determined.
Ellis: Determined toward what?
Priya: Possibly balance.
Maya: Jonah, coffee. Go before your washer enters its dramatic final spin.
Jonah: If machine two finishes early, text me.
Ellis: You are standing twelve feet away.
Jonah: Text me spiritually.
Priya: I'll wave a dryer sheet like a flag.
Maya: Make it solemn.
Jonah: Back in five.

[Jonah leaves]

Ellis: So, Maya, did you send that email?
Maya: Which email?
Priya: The face you made means the difficult one.
Maya: I drafted it.
Ellis: Drafting is not sending.
Maya: Thank you, calendar with shoes.
Priya: Is this about the studio space?
Maya: Yes. The owner raised the fee again, but only for people not signing annual agreements.
Ellis: That's pressure disguised as paperwork.
Maya: Exactly. I don't know if I should push back or just move my classes online for a month.
Priya: Are your students mostly local?
Maya: Half local, half whoever discovers me through short videos and thinks beginner watercolor requires emotional bravery.
Ellis: It does, frankly.
Priya: If you move online, do you lose the people who come for company?
Maya: Probably. That's the part that bothers me.
Ellis: Then the email should say that. Not as a complaint, as a consequence.
Maya: You make it sound simple.
Ellis: It is simple. Not easy.
Priya: I can read the draft if you want.
Maya: You really do carry everything in that bag.
Priya: Including opinions.

[Washer chime]

Ellis: Was that two?
Priya: No, four. Two has three minutes.
Maya: How do you know?
Priya: I observe patterns while pretending not to listen.
Ellis: Terrifying skill.
Priya: Useful skill.
Maya: Can you observe whether the ceiling mitten is moving?
Priya: I will not look again.

[Jonah returns]

Jonah: Bad news. Tea options were mint, black, and something labeled forest calm.
Priya: I distrust forest calm.
Jonah: I chose black.
Priya: Correct.
Ellis: Cinnamon?
Jonah: Cinnamon roll. It was the last one. The barista said I saved it from becoming stale, which felt heroic.
Maya: Did you get yourself coffee?
Jonah: Yes, but I spilled some on my sleeve, so now my arm is alert.
Priya: Machine two just stopped.
Jonah: See? Spiritual texting worked.
Ellis: That was a chime.
Jonah: Different traditions.
Maya: Your blue clothes are done. Also, we may have solved my email crisis.
Jonah: I leave for six minutes and governance occurs.
Priya: Not governance. Boundary setting.
Ellis: With maybe three sharp sentences.
Jonah: Excellent. Add one sentence threatening poetry.
Maya: That's for the dryer.
Jonah: Everything deserves one warning poem.
Priya: Except landlords.
Ellis: Landlords get haiku invoices.
Maya: Five syllables: fix the heat now please.
Jonah: That's five?
Priya: It is if you count despair as silent.
Ellis: I love this laundromat.
Maya: You love chaos with folding carts.
Jonah: Same thing.

End of conversation."

{
  "taskType": "textInference",
  "taskUUID": "b6bdff4c-255b-4c94-a3c7-b75a32549519",
  "model": "google:gemma@4-31b",
  "settings": {
    "systemPrompt": "You are a careful conversation analyst. Preserve uncertainty, distinguish facts from guesses, and produce structured answers without inventing details.",
    "temperature": 0.7,
    "topP": 0.9,
    "maxTokens": 8192,
    "thinkingLevel": "high"
  },
  "messages": [
    {
      "role": "user",
      "content": "Below is a random conversation by humans recorded near the folding tables of a busy laundromat. Analyze it and provide: 1) a 10-bullet factual summary, 2) each person's likely goals, 3) unresolved questions, 4) practical next steps, 5) any subtle tension or humor, and 6) a compact timeline.\n\nConversation:\n\nMaya: If that dryer eats another quarter, I am writing it a strongly worded poem.\nJonah: A poem?\nMaya: Yes. Rhymed couplets. Very legal tone.\nPriya: Does anyone know if the number on the wall actually works? The service number?\nEllis: It works in the sense that a voicemail says hello, then abandons you emotionally.\nJonah: That is still more reliable than my landlord.\nMaya: Your landlord still hasn't fixed the radiator?\nJonah: He says it's fixed because he looked at it from the doorway and felt optimistic.\nPriya: I have a screwdriver in my bag.\nEllis: Why?\nPriya: I also have three granola bars, a mini tape measure, and two birthday candles. I refuse to explain myself.\nMaya: You are the person people hope is on their train when things get weird.\nJonah: Speaking of weird, did either of you see the sock stuck to the ceiling above washer six?\nEllis: I chose not to receive that information.\nPriya: That's not a sock. That's a baby mitten.\nMaya: Worse.\nJonah: How does a mitten reach the ceiling?\nEllis: Ambition.\nPriya: Static, maybe. Or a tall parent with poor aim.\nMaya: The tall parent theory feels generous.\nJonah: My blue load has nine minutes. Who's guarding the machines when I get coffee?\nEllis: I can watch them if you bring me something with cinnamon.\nPriya: I want tea, but only if they don't make it taste like boiled hay.\nMaya: That's most tea in this zip code.\nJonah: Fine. Cinnamon thing for Ellis, respectable tea for Priya, nothing for Maya because she insults beverages.\nMaya: I accept my consequences.\nPriya: Wait, before you go, is that your gray hoodie in dryer three?\nJonah: No, mine has a cracked zipper and a paint stain shaped like Vermont.\nEllis: That hoodie has a paint stain shaped like a duck sneezing.\nMaya: That is incredibly specific and somehow accurate.\nPriya: Then whose is it? It's been tumbling for an hour.\nEllis: Maybe it belongs to the man who left with one shoe earlier.\nJonah: I thought we all agreed not to mention him.\nMaya: We agreed not to speculate about him. Mentioning is legally distinct.\nPriya: He seemed fine. Just determined.\nEllis: Determined toward what?\nPriya: Possibly balance.\nMaya: Jonah, coffee. Go before your washer enters its dramatic final spin.\nJonah: If machine two finishes early, text me.\nEllis: You are standing twelve feet away.\nJonah: Text me spiritually.\nPriya: I'll wave a dryer sheet like a flag.\nMaya: Make it solemn.\nJonah: Back in five.\n\n[Jonah leaves]\n\nEllis: So, Maya, did you send that email?\nMaya: Which email?\nPriya: The face you made means the difficult one.\nMaya: I drafted it.\nEllis: Drafting is not sending.\nMaya: Thank you, calendar with shoes.\nPriya: Is this about the studio space?\nMaya: Yes. The owner raised the fee again, but only for people not signing annual agreements.\nEllis: That's pressure disguised as paperwork.\nMaya: Exactly. I don't know if I should push back or just move my classes online for a month.\nPriya: Are your students mostly local?\nMaya: Half local, half whoever discovers me through short videos and thinks beginner watercolor requires emotional bravery.\nEllis: It does, frankly.\nPriya: If you move online, do you lose the people who come for company?\nMaya: Probably. That's the part that bothers me.\nEllis: Then the email should say that. Not as a complaint, as a consequence.\nMaya: You make it sound simple.\nEllis: It is simple. Not easy.\nPriya: I can read the draft if you want.\nMaya: You really do carry everything in that bag.\nPriya: Including opinions.\n\n[Washer chime]\n\nEllis: Was that two?\nPriya: No, four. Two has three minutes.\nMaya: How do you know?\nPriya: I observe patterns while pretending not to listen.\nEllis: Terrifying skill.\nPriya: Useful skill.\nMaya: Can you observe whether the ceiling mitten is moving?\nPriya: I will not look again.\n\n[Jonah returns]\n\nJonah: Bad news. Tea options were mint, black, and something labeled forest calm.\nPriya: I distrust forest calm.\nJonah: I chose black.\nPriya: Correct.\nEllis: Cinnamon?\nJonah: Cinnamon roll. It was the last one. The barista said I saved it from becoming stale, which felt heroic.\nMaya: Did you get yourself coffee?\nJonah: Yes, but I spilled some on my sleeve, so now my arm is alert.\nPriya: Machine two just stopped.\nJonah: See? Spiritual texting worked.\nEllis: That was a chime.\nJonah: Different traditions.\nMaya: Your blue clothes are done. Also, we may have solved my email crisis.\nJonah: I leave for six minutes and governance occurs.\nPriya: Not governance. Boundary setting.\nEllis: With maybe three sharp sentences.\nJonah: Excellent. Add one sentence threatening poetry.\nMaya: That's for the dryer.\nJonah: Everything deserves one warning poem.\nPriya: Except landlords.\nEllis: Landlords get haiku invoices.\nMaya: Five syllables: fix the heat now please.\nJonah: That's five?\nPriya: It is if you count despair as silent.\nEllis: I love this laundromat.\nMaya: You love chaos with folding carts.\nJonah: Same thing.\n\nEnd of conversation."
    }
  ]
}