ivyxivyx
← All ivy-agents
IVYXSTUDIO · IVY AGENT
M

Meeting Actions

ivy.agent.meeting-actions · v1.0.0

ivyx

Has a model pull the action items out of meeting notes, checks each one has an owner and a task, and writes them as a table.

Steps

In the order the agent's file lists them, each with where its inputs come from and the values the file fixes. A branch or a loop is a step too.

  1. 01
    Extract the action items

    List the action items in these meeting notes. An action item is something a named person agreed to do. For each one give owner (the person's name), task (what they will do, in a few words) and due (the date or day the notes give, or an empty string when none is given). Leave out decisions and remarks that nobody has to act on.

    takes
    context from the agent's input, notes
    Model turn
  2. 02
    Check each item
    ivy.node.rows-validate

    Checks every row against a JSON Schema and splits the rows into valid ones and invalid ones with their problems.

    takes
    rows from step 1, output.items
    set
    schema {"type":"object","required":["owner","task"],"properties":{"owner":{"type":"string","minLength":1},"task":{"type":"st...
    returns
    actions, rejected
    Ivy Node
  3. 03
    Lay out the table
    ivy.node.markdown-table

    Formats rows as a Markdown table, with the columns in the order given or as they first appear.

    takes
    rows from step 2, valid_rows
    set
    columns ["owner","task","due"]
    returns
    count, markdown
    Ivy Node
  4. 04
    Write the table
    ivy.node.file-write

    Writes text to a file, creating its folder, and returns the absolute path and the number of bytes written.

    takes
    text from step 3, markdown
    set
    path reports/actions.md
    overwrite true
    returns
    path
    Ivy Node

Nodes it brings

Adding this agent in IVYX Studio adds these nodes with it. A node your workspace already has is kept as it is, even at another version.

What it touches

Collected from what each of its nodes declares, plus the model call when a step is a model turn. A declaration is the author's statement, and it is what policy rules select on.

Writes filesCalls a model

Inputs

FieldTypeDescription
notesrequiredstringThe meeting notes, as text.

Outputs

FieldTypeDescription
actionsarrayThe action items that have an owner and a task, as {owner, task, due}.
countintegerHow many action items were written.
rejectedintegerHow many extracted items lacked an owner or a task.
markdownstringThe table that was written.
pathstringThe file the table was written to.

Tests

2 of 2 test cases passed on Oct 4, 2026, in the publisher's own environment, before this version was published. The registry keeps that record; it does not run the cases again.

Requires: python:3.9, a model core

  • weekly-sync

    Three people took a task and one point was a decision: three rows, none about the logo.

    given
    notes Weekly sync, 3 October. Present: Ayla, Bram, Chen. - Checkout bug: Bram will ship the fix by Friday 9 October. - Ayla...
    expects
    count equals 3
    markdown matches Bram[\s\S]*Ayla[\s\S]*Chen|Ayla[\s\S]*Bram[\s\S]*Chen
    path matches reports/actions\.md$
  • design-review

    Other notes give other owners.

    given
    notes Design review. Dana presents the onboarding flow. Decision: keep three steps. Dana to update the mockups by Monday. E...
    expects
    count equals 2
    markdown matches Dana[\s\S]*Erik