Judge whether received inputs are fit for the delivery line
Packaged know-how that tells an agent how to do a job well.
You might say…
“The checklist shows everything as received but the data file they sent is in a format the method can't process — and I only find out when we try to run step one.”
What it does
Reviews each received input against the method's format and quality requirements — checking file types, data completeness, date ranges, and structural conformance — and flags items that are present but unusable.
Trigger: Use after the completeness reconciliation confirms all items are received, to verify that what arrived is actually fit for the method to consume.
I/O: Received inputs + method format/quality requirements → format fitness report (usable / unusable / needs conversion per item) with specific issues flagged
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation