Live Minutes

import { DecisionMachine } from "@cloudraker/milliseconds";

// Run on your server; reads MS_API_KEY from the environment.
const dm = new DecisionMachine();

const { result, usage } = await dm.classify(
  [
    "Morning everyone, let's get started, we've got a lot to cover today.",
    "Morning. Coffee hasn't kicked in yet, bear with me.",
    "Hey all. Quick heads up, I have a hard stop at the half hour.",
    "Hi hi. Sharing my screen in a sec for the address form stuff.",
    "Cool. Marcus, you want to kick off with the payment service migration?",
    "Sure. So the migration to the new payments service is basically done, all the write paths are cut over.",
    "Read paths are still going through the old service for about ten percent of traffic.",
    "Any issues so far?",
    "One thing, refund reconciliation is off by a few cents on some multi-currency orders.",
    "It's a rounding thing between the two services, not data loss, but finance will notice.",
    "Finance will definitely notice, they notice everything.",
    "Marcus, can you write up the rounding discrepancy and send it to finance before end of day tomorrow?",
    "Yep, I'll have the write-up to finance by tomorrow.",
    "I also need someone to double check the currency table, I'm not confident the JPY entries are right.",
    "I can take the currency table check, I've got the spreadsheet from the last audit anyway.",
    "Great, Sofia has the currency table.",
    "Can we talk about the launch date itself for a second?",
    "Sure, what's up?",
    "Marketing wants to send the announcement email on the Wednesday, the thirtieth, so the feature needs to be at a hundred percent by then.",
    "The plan says a hundred percent on October first.",
    "Right, and that's a day late for the email. Can we go to a hundred on Tuesday instead?",
    "If the reconciliation and idempotency stuff land next week, technically yes.",
    "Okay, let's move the hundred percent to Tuesday the twenty-ninth then.",
    "Tuesday is tight for the final QA pass on the address form though.",
    "Hmm. Actually, no, let's not. Scrap Tuesday, we keep October first and marketing shifts the email a day.",
    "Okay, I'll go back to marketing and ask them to move the email to Thursday the first.",
    "Thanks. Sorry for the flip-flop.",
    "Load testing. Marcus, where are we?",
    "I ran a load test on Tuesday, five hundred checkouts a minute, everything held.",
    "p99 latency on the payment call was about nine hundred milliseconds, which is fine, but the tax lookup was the slow part.",
    "Black Friday is going to be more than five hundred a minute though.",
    "Yeah, we should test at two thousand. But the staging tax API rate-limits us above about eight hundred."
  ],
  {
    "action_item": "the speaker says 'I'll do it', 'I can take that', 'can you do this', or asks a named person to do a new piece of work",
    "decision": "the speaker says 'let's do this', 'we're not doing that', 'we'll go with this one', 'park it', 'agreed, we keep the plan'",
    "open_question": "a question about the work that this line does not answer: 'any issues so far?', 'do we have that?', 'how many?', 'where are we on this?'",
    "risk": "the speaker warns that something is broken, flaky, missing, slipping, at risk, or could fail",
    "progress_report": "the speaker reports where the work already stands, with no new work handed out: 'the migration is done', 'conversion is up four percent', 'I spent yesterday on the address form'",
    "small_talk": "a greeting, a goodbye, a joke, thanks, a bare agreement like 'sounds good', or handing the floor to the next person"
  }
).withUsage();

console.log(result);
console.log({ inputTokens: usage.inputTokens, modelMs: usage.inferenceMs });

import { DecisionMachine } from "@cloudraker/milliseconds";

// Run on your server; reads MS_API_KEY from the environment.
const dm = new DecisionMachine();

const { result, usage } = await dm.yesNo(
  [
    "Morning everyone, let's get started, we've got a lot to cover today.",
    "Morning. Coffee hasn't kicked in yet, bear with me.",
    "Hey all. Quick heads up, I have a hard stop at the half hour.",
    "Hi hi. Sharing my screen in a sec for the address form stuff.",
    "Cool. Marcus, you want to kick off with the payment service migration?",
    "Sure. So the migration to the new payments service is basically done, all the write paths are cut over.",
    "Read paths are still going through the old service for about ten percent of traffic.",
    "Any issues so far?",
    "One thing, refund reconciliation is off by a few cents on some multi-currency orders.",
    "It's a rounding thing between the two services, not data loss, but finance will notice.",
    "Finance will definitely notice, they notice everything.",
    "Marcus, can you write up the rounding discrepancy and send it to finance before end of day tomorrow?",
    "Yep, I'll have the write-up to finance by tomorrow.",
    "I also need someone to double check the currency table, I'm not confident the JPY entries are right.",
    "I can take the currency table check, I've got the spreadsheet from the last audit anyway.",
    "Great, Sofia has the currency table.",
    "Can we talk about the launch date itself for a second?",
    "Sure, what's up?",
    "Marketing wants to send the announcement email on the Wednesday, the thirtieth, so the feature needs to be at a hundred percent by then.",
    "The plan says a hundred percent on October first.",
    "Right, and that's a day late for the email. Can we go to a hundred on Tuesday instead?",
    "If the reconciliation and idempotency stuff land next week, technically yes.",
    "Okay, let's move the hundred percent to Tuesday the twenty-ninth then.",
    "Tuesday is tight for the final QA pass on the address form though.",
    "Hmm. Actually, no, let's not. Scrap Tuesday, we keep October first and marketing shifts the email a day.",
    "Okay, I'll go back to marketing and ask them to move the email to Thursday the first.",
    "Thanks. Sorry for the flip-flop.",
    "Load testing. Marcus, where are we?",
    "I ran a load test on Tuesday, five hundred checkouts a minute, everything held.",
    "p99 latency on the payment call was about nine hundred milliseconds, which is fine, but the tax lookup was the slow part.",
    "Black Friday is going to be more than five hundred a minute though.",
    "Yeah, we should test at two thousand. But the staging tax API rate-limits us above about eight hundred."
  ],
  "Someone leaves this meeting owing a piece of work because of this line.",
  {
    "when_true": "the line hands work out, asks for it, takes it on, or repeats back what was just agreed: 'Marcus, add the upsell event this week', 'I'll send the write-up tomorrow', 'understood, idempotency before we widen the rollout', 'on it', 'I can take that', 'someone needs to file a ticket'",
    "when_false": "nobody picks up work here: a greeting or handing the floor over ('Dev, you're up'), a question, a warning, a report on work already finished, a decision about what to build, or an end-of-meeting recap of what everyone already agreed to"
  }
).withUsage();

console.log(result);
console.log({ inputTokens: usage.inputTokens, modelMs: usage.inferenceMs });

from milliseconds import DecisionMachine

# Reads MS_API_KEY from the environment.
dm = DecisionMachine()

result = dm.classify(
    [
      "Morning everyone, let's get started, we've got a lot to cover today.",
      "Morning. Coffee hasn't kicked in yet, bear with me.",
      "Hey all. Quick heads up, I have a hard stop at the half hour.",
      "Hi hi. Sharing my screen in a sec for the address form stuff.",
      "Cool. Marcus, you want to kick off with the payment service migration?",
      "Sure. So the migration to the new payments service is basically done, all the write paths are cut over.",
      "Read paths are still going through the old service for about ten percent of traffic.",
      "Any issues so far?",
      "One thing, refund reconciliation is off by a few cents on some multi-currency orders.",
      "It's a rounding thing between the two services, not data loss, but finance will notice.",
      "Finance will definitely notice, they notice everything.",
      "Marcus, can you write up the rounding discrepancy and send it to finance before end of day tomorrow?",
      "Yep, I'll have the write-up to finance by tomorrow.",
      "I also need someone to double check the currency table, I'm not confident the JPY entries are right.",
      "I can take the currency table check, I've got the spreadsheet from the last audit anyway.",
      "Great, Sofia has the currency table.",
      "Can we talk about the launch date itself for a second?",
      "Sure, what's up?",
      "Marketing wants to send the announcement email on the Wednesday, the thirtieth, so the feature needs to be at a hundred percent by then.",
      "The plan says a hundred percent on October first.",
      "Right, and that's a day late for the email. Can we go to a hundred on Tuesday instead?",
      "If the reconciliation and idempotency stuff land next week, technically yes.",
      "Okay, let's move the hundred percent to Tuesday the twenty-ninth then.",
      "Tuesday is tight for the final QA pass on the address form though.",
      "Hmm. Actually, no, let's not. Scrap Tuesday, we keep October first and marketing shifts the email a day.",
      "Okay, I'll go back to marketing and ask them to move the email to Thursday the first.",
      "Thanks. Sorry for the flip-flop.",
      "Load testing. Marcus, where are we?",
      "I ran a load test on Tuesday, five hundred checkouts a minute, everything held.",
      "p99 latency on the payment call was about nine hundred milliseconds, which is fine, but the tax lookup was the slow part.",
      "Black Friday is going to be more than five hundred a minute though.",
      "Yeah, we should test at two thousand. But the staging tax API rate-limits us above about eight hundred."
    ],
    {
      "action_item": "the speaker says 'I'll do it', 'I can take that', 'can you do this', or asks a named person to do a new piece of work",
      "decision": "the speaker says 'let's do this', 'we're not doing that', 'we'll go with this one', 'park it', 'agreed, we keep the plan'",
      "open_question": "a question about the work that this line does not answer: 'any issues so far?', 'do we have that?', 'how many?', 'where are we on this?'",
      "risk": "the speaker warns that something is broken, flaky, missing, slipping, at risk, or could fail",
      "progress_report": "the speaker reports where the work already stands, with no new work handed out: 'the migration is done', 'conversion is up four percent', 'I spent yesterday on the address form'",
      "small_talk": "a greeting, a goodbye, a joke, thanks, a bare agreement like 'sounds good', or handing the floor to the next person"
    }
)

print(result)

from milliseconds import DecisionMachine

# Reads MS_API_KEY from the environment.
dm = DecisionMachine()

result = dm.yes_no(
    [
      "Morning everyone, let's get started, we've got a lot to cover today.",
      "Morning. Coffee hasn't kicked in yet, bear with me.",
      "Hey all. Quick heads up, I have a hard stop at the half hour.",
      "Hi hi. Sharing my screen in a sec for the address form stuff.",
      "Cool. Marcus, you want to kick off with the payment service migration?",
      "Sure. So the migration to the new payments service is basically done, all the write paths are cut over.",
      "Read paths are still going through the old service for about ten percent of traffic.",
      "Any issues so far?",
      "One thing, refund reconciliation is off by a few cents on some multi-currency orders.",
      "It's a rounding thing between the two services, not data loss, but finance will notice.",
      "Finance will definitely notice, they notice everything.",
      "Marcus, can you write up the rounding discrepancy and send it to finance before end of day tomorrow?",
      "Yep, I'll have the write-up to finance by tomorrow.",
      "I also need someone to double check the currency table, I'm not confident the JPY entries are right.",
      "I can take the currency table check, I've got the spreadsheet from the last audit anyway.",
      "Great, Sofia has the currency table.",
      "Can we talk about the launch date itself for a second?",
      "Sure, what's up?",
      "Marketing wants to send the announcement email on the Wednesday, the thirtieth, so the feature needs to be at a hundred percent by then.",
      "The plan says a hundred percent on October first.",
      "Right, and that's a day late for the email. Can we go to a hundred on Tuesday instead?",
      "If the reconciliation and idempotency stuff land next week, technically yes.",
      "Okay, let's move the hundred percent to Tuesday the twenty-ninth then.",
      "Tuesday is tight for the final QA pass on the address form though.",
      "Hmm. Actually, no, let's not. Scrap Tuesday, we keep October first and marketing shifts the email a day.",
      "Okay, I'll go back to marketing and ask them to move the email to Thursday the first.",
      "Thanks. Sorry for the flip-flop.",
      "Load testing. Marcus, where are we?",
      "I ran a load test on Tuesday, five hundred checkouts a minute, everything held.",
      "p99 latency on the payment call was about nine hundred milliseconds, which is fine, but the tax lookup was the slow part.",
      "Black Friday is going to be more than five hundred a minute though.",
      "Yeah, we should test at two thousand. But the staging tax API rate-limits us above about eight hundred."
    ],
    "Someone leaves this meeting owing a piece of work because of this line.",
    when_true="the line hands work out, asks for it, takes it on, or repeats back what was just agreed: 'Marcus, add the upsell event this week', 'I'll send the write-up tomorrow', 'understood, idempotency before we widen the rollout', 'on it', 'I can take that', 'someone needs to file a ticket'",
    when_false="nobody picks up work here: a greeting or handing the floor over ('Dev, you're up'), a question, a warning, a report on work already finished, a decision about what to build, or an end-of-meeting recap of what everyone already agreed to"
)

print(result)

# Reads MS_API_KEY. JSON on stdin supplies the complete request.
dm1 classify --json --usage <<'DM1_REQUEST'
{
  "texts": [
    "Morning everyone, let's get started, we've got a lot to cover today.",
    "Morning. Coffee hasn't kicked in yet, bear with me.",
    "Hey all. Quick heads up, I have a hard stop at the half hour.",
    "Hi hi. Sharing my screen in a sec for the address form stuff.",
    "Cool. Marcus, you want to kick off with the payment service migration?",
    "Sure. So the migration to the new payments service is basically done, all the write paths are cut over.",
    "Read paths are still going through the old service for about ten percent of traffic.",
    "Any issues so far?",
    "One thing, refund reconciliation is off by a few cents on some multi-currency orders.",
    "It's a rounding thing between the two services, not data loss, but finance will notice.",
    "Finance will definitely notice, they notice everything.",
    "Marcus, can you write up the rounding discrepancy and send it to finance before end of day tomorrow?",
    "Yep, I'll have the write-up to finance by tomorrow.",
    "I also need someone to double check the currency table, I'm not confident the JPY entries are right.",
    "I can take the currency table check, I've got the spreadsheet from the last audit anyway.",
    "Great, Sofia has the currency table.",
    "Can we talk about the launch date itself for a second?",
    "Sure, what's up?",
    "Marketing wants to send the announcement email on the Wednesday, the thirtieth, so the feature needs to be at a hundred percent by then.",
    "The plan says a hundred percent on October first.",
    "Right, and that's a day late for the email. Can we go to a hundred on Tuesday instead?",
    "If the reconciliation and idempotency stuff land next week, technically yes.",
    "Okay, let's move the hundred percent to Tuesday the twenty-ninth then.",
    "Tuesday is tight for the final QA pass on the address form though.",
    "Hmm. Actually, no, let's not. Scrap Tuesday, we keep October first and marketing shifts the email a day.",
    "Okay, I'll go back to marketing and ask them to move the email to Thursday the first.",
    "Thanks. Sorry for the flip-flop.",
    "Load testing. Marcus, where are we?",
    "I ran a load test on Tuesday, five hundred checkouts a minute, everything held.",
    "p99 latency on the payment call was about nine hundred milliseconds, which is fine, but the tax lookup was the slow part.",
    "Black Friday is going to be more than five hundred a minute though.",
    "Yeah, we should test at two thousand. But the staging tax API rate-limits us above about eight hundred."
  ],
  "labels": {
    "action_item": "the speaker says 'I'll do it', 'I can take that', 'can you do this', or asks a named person to do a new piece of work",
    "decision": "the speaker says 'let's do this', 'we're not doing that', 'we'll go with this one', 'park it', 'agreed, we keep the plan'",
    "open_question": "a question about the work that this line does not answer: 'any issues so far?', 'do we have that?', 'how many?', 'where are we on this?'",
    "risk": "the speaker warns that something is broken, flaky, missing, slipping, at risk, or could fail",
    "progress_report": "the speaker reports where the work already stands, with no new work handed out: 'the migration is done', 'conversion is up four percent', 'I spent yesterday on the address form'",
    "small_talk": "a greeting, a goodbye, a joke, thanks, a bare agreement like 'sounds good', or handing the floor to the next person"
  }
}
DM1_REQUEST

# Reads MS_API_KEY. JSON on stdin supplies the complete request.
dm1 yes-no --json --usage <<'DM1_REQUEST'
{
  "texts": [
    "Morning everyone, let's get started, we've got a lot to cover today.",
    "Morning. Coffee hasn't kicked in yet, bear with me.",
    "Hey all. Quick heads up, I have a hard stop at the half hour.",
    "Hi hi. Sharing my screen in a sec for the address form stuff.",
    "Cool. Marcus, you want to kick off with the payment service migration?",
    "Sure. So the migration to the new payments service is basically done, all the write paths are cut over.",
    "Read paths are still going through the old service for about ten percent of traffic.",
    "Any issues so far?",
    "One thing, refund reconciliation is off by a few cents on some multi-currency orders.",
    "It's a rounding thing between the two services, not data loss, but finance will notice.",
    "Finance will definitely notice, they notice everything.",
    "Marcus, can you write up the rounding discrepancy and send it to finance before end of day tomorrow?",
    "Yep, I'll have the write-up to finance by tomorrow.",
    "I also need someone to double check the currency table, I'm not confident the JPY entries are right.",
    "I can take the currency table check, I've got the spreadsheet from the last audit anyway.",
    "Great, Sofia has the currency table.",
    "Can we talk about the launch date itself for a second?",
    "Sure, what's up?",
    "Marketing wants to send the announcement email on the Wednesday, the thirtieth, so the feature needs to be at a hundred percent by then.",
    "The plan says a hundred percent on October first.",
    "Right, and that's a day late for the email. Can we go to a hundred on Tuesday instead?",
    "If the reconciliation and idempotency stuff land next week, technically yes.",
    "Okay, let's move the hundred percent to Tuesday the twenty-ninth then.",
    "Tuesday is tight for the final QA pass on the address form though.",
    "Hmm. Actually, no, let's not. Scrap Tuesday, we keep October first and marketing shifts the email a day.",
    "Okay, I'll go back to marketing and ask them to move the email to Thursday the first.",
    "Thanks. Sorry for the flip-flop.",
    "Load testing. Marcus, where are we?",
    "I ran a load test on Tuesday, five hundred checkouts a minute, everything held.",
    "p99 latency on the payment call was about nine hundred milliseconds, which is fine, but the tax lookup was the slow part.",
    "Black Friday is going to be more than five hundred a minute though.",
    "Yeah, we should test at two thousand. But the staging tax API rate-limits us above about eight hundred."
  ],
  "statement": "Someone leaves this meeting owing a piece of work because of this line.",
  "when_true": "the line hands work out, asks for it, takes it on, or repeats back what was just agreed: 'Marcus, add the upsell event this week', 'I'll send the write-up tomorrow', 'understood, idempotency before we widen the rollout', 'on it', 'I can take that', 'someone needs to file a ticket'",
  "when_false": "nobody picks up work here: a greeting or handing the floor over ('Dev, you're up'), a question, a warning, a report on work already finished, a decision about what to build, or an end-of-meeting recap of what everyone already agreed to"
}
DM1_REQUEST