Show and tell: a "check the work" native function, next to the functions that did the work

[Fikpeze123]

Hi all — I'm Frank, founder of Pactlyst.ai, built with AI help and not shy about it. This community thinks in plugins, so here's the pattern in plugin shape.

My test scenario is procurement, because it's where I live: an SK agent pulls vendor data with one function, drafts a purchase order with another, and the plan ends with the PO ready to send. Everything worked — and nothing had checked the PO against anything. So the last function in the kernel is a checker, not a doer:

[KernelFunction("check_work")]
public async Task<string> CheckWorkAsync(string workText, string workType, string ask)
{
    // POST https://api.pactlyst.ai/functions/v1/work-check
    // Authorization: Bearer $PACTLYST_KEY
    // { "work_text": workText, "work_type": workType,
    //   "ask": ask, "requesting_agent": "sk-procurement-agent" }
}

Called with the finished PO (work_type: "document", ask: "Raise a PO for the renewal at the contracted price, net-30 terms"), it returns a verdict — Low risk, Needs review, or High risk — with findings, plus a gate decision the planner can actually branch on: proceed, or hold for a named human. Needs review means a named person acknowledges the findings; High risk means a named approver who isn't the requester approves first. And the response carries a signed PactCheck Receipt™ and its public link, so the PO's file can hold proof the check ran — the same door also checks code and software work, if your kernel's agents write those. The work itself is never stored by Pactlyst; the receipt keeps the hash and the finding counts, and the graded ask lines quote the work where it matched — or broke — what was asked.

Plainly: no official SK connector and no partnership — one HTTP native function and a free key is the whole integration. If your agents use MCP, the identical check is exposed as a check_work tool.

We're bringing on a few design partners from agent-framework communities — three months of Pro free, no card. Full request/response shapes: pactlyst.ai/docs. I'd welcome a kernel person's critique of where a check belongs in a plan: last step, or a filter on every step?

— Frank