Meeting commitments

A meeting produces useful follow-up when each agreed commitment has an owner and date. Meeting commitments takes the checklist you enter and connects its tasks to the stored meeting, so the team can trace the work back to its source.

Complete your first checklist

Enable Meeting commitments in Plugins, then open /admin/meeting-commitments. You need an authorized workspace, a stored meeting and valid task assignees. The plugin starts disabled and has no extra provider credentials or public settings.

1. Select the stored meeting that the work belongs to.
2. Enter one to ten tasks, each with a title, description, due date and assignee.
3. Preview the plan and check the source, dates and owners. Submit that exact version for approval.
4. Approve it through the shared action queue, then inspect the execution result and the created tasks.

For a fictional example, prepare two tasks: send the agreed summary and confirm the next appointment. After successful approval execution, expect two assigned tasks linked to the selected source. A preview or pending proposal has not created them yet. The demo uses the actual admin components with session-local fictional data.

Use it through AI

The registered tools prepare_meeting_commitments and propose_meeting_commitments use the same workflow as the interface. Preparation returns a reviewable plan; proposing uses that plan's digest and a stable request identity. The assistant cannot approve its own task creation.

At execution, the host checks the workspace, the enabled plugin, the source, the assignments, and the approved plan all over again, right before it commits anything. If any of those facts changed since you reviewed the plan, it asks for a fresh one rather than running a stale decision, which is what keeps the created tasks attached to the decision you made, not one that has since gone out of date.

What this example teaches you to build

Build another source-to-task workflow using the same preview, approval and task-creation services. This version takes the tasks you enter; automatic extraction from a transcript would be an additional capability to implement and verify.

The workflow source produces a bounded plan. The shared host owns permissions and business writes. You can change the business-specific plan while reusing the approval queue, task records and execution receipts.

Costs, disabling and recovery

Checklist preparation and task creation are both deterministic and make no paid model or provider request on their own. Hosting and database costs still apply as usual, and any AI chat you have around the workflow uses your workspace's configured model.

Disabling the plugin in Plugins blocks any later execution, including approvals that are already pending, while existing tasks and receipts stay exactly where they are. Use the normal task controls to edit or complete whatever work was already created before you disabled it.

If the source or an assignee is missing, correct the input and preview it again. When a result comes back uncertain, inspect the original receipt and reuse its request identity for a retry, rather than submitting a fresh request just to route around the uncertainty. A code or policy upgrade can invalidate an existing preview too, in which case it simply needs a fresh review.

The developer guide covers the contracts and npm run test:business-workflows. Controlled tests and fictional demo behavior are distinct from verification of your own workspace permissions and database.