/minutes-x1-closeout

Turn one clear meeting outcome into a proposed closeout for one existing X1 coordination thread. Minutes supplies the source. X1 supplies identity, authority, review, disposition, and the household record.

Required connections

This workflow needs both the local Minutes MCP and the official X1 MCP. If X1 isn't connected, stop after identifying the meeting outcome and direct the user to X1's official connection instructions. Don't invent an endpoint, credential, account, thread ID, or local substitute.

Workflow

1. Call Minutes get_meeting_insights with include_restricted: false to find an explicit or strong decision or commitment that supports the closeout the user requested. The logged restricted-source override is forbidden for this cross-service handoff. Use only an insight released by that bounded call. Don't use agent.annotation, a raw path, a transcript fragment read outside Minutes, or a model-written summary as source proof.

2. Use X1 find_coordination_threads or list_my_coordination_threads, then get_coordination_thread, to resolve exactly one open thread the signed-in X1 actor can read. If zero or multiple threads plausibly match, ask the user to choose. Never select a hidden, closed, or guessed target.

3. Ask the user to choose the X1 outcome if they haven't already: resolved, escalated_elsewhere, deferred, or no_longer_relevant. Meeting language that money was sent, a wire was approved, or a payment was discussed doesn't prove settlement. Keep the work open unless the user explicitly chooses a non-settlement closeout.

4. Build sourceProposal from the exact released Minutes insight: