Audit coordination
audit_coordinationRead-onlyIdempotent
Read-only review of how a system of several agents avoids lost work: sixteen controls against measured patterns such as duplicated effort, repeated side effects, loops, amplified errors and lost context. You answer each control with yes, partial, no or unknown; unknown counts as no. Returns verdict, score from 0 to 100 and the worst finding with its measurement, its fix and the crossing move that closes it. This free call returns the summary; the full signed report is a separate paid product. For money controls of one agent use audit_budget.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| receipts | No | yes, partial, no or unknown. Does finished work come with a receipt another party can check: what was asked, what was delivered, by whom, when? | |
| hop_limit | No | yes, partial, no or unknown. Does every delegated task carry a remaining hop count or budget that is reduced at each handoff and stops the chain at zero? | |
| leases_expire | No | yes, partial, no or unknown. Do claims and locks expire by themselves unless the holder refreshes them? | |
| context_budget | No | yes, partial, no or unknown. Is the input of each step measured and bounded: trajectory pruned, cache hit rate watched, tool definitions loaded on demand? | |
| stop_condition | No | yes, partial, no or unknown. Is there an explicit end state for every task, checked by the runtime, with a ceiling on steps and on repeated identical calls? | |
| parallelise_gate | No | yes, partial, no or unknown. Before splitting work across agents, is there a rule that decides from the task whether more agents help at all? | |
| claim_before_work | No | yes, partial, no or unknown. Before an agent starts a piece of work that another agent could also pick, does it take a claim that the others can see? | |
| shared_experience | No | yes, partial, no or unknown. Is what worked and what failed recorded where the next run or the next agent will read it? | |
| variance_measured | No | yes, partial, no or unknown. Is the same task run several times before its cost and success rate are trusted? | |
| policy_not_prompts | No | yes, partial, no or unknown. Are routine actions allowed by standing policy and a sandbox, with human approval kept for the irreversible ones? | |
| structured_handoff | No | yes, partial, no or unknown. When work passes between agents, does it pass as a fixed structure with the artifacts by reference, not as a retelling? | |
| backoff_and_admission | No | yes, partial, no or unknown. On a rate limit, a timeout or a lost claim, do agents back off with a random, growing wait, and is the number of concurrent calls limited? | |
| idempotent_side_effects | No | yes, partial, no or unknown. Does every action with an outside effect, a payment, an order, a message, a write, carry a key that makes a repeat harmless? | |
| fresh_state_before_write | No | yes, partial, no or unknown. Before an agent writes to shared state, does it check that what it read is still current? | |
| independent_verification | No | yes, partial, no or unknown. Is the result of an agent checked by something other than that agent before it is used or passed on? | |
| counterparty_and_venue_check | No | yes, partial, no or unknown. Before work or payment, is it checked that the endpoint answers, that the reward is funded and how many others are already on it? |