Verifier model clarifies when execution evidence is complete or missing
Evidence Coverage for Intent-Bound Execution: Scope, Obligations, and Cutoff Reasoning
Cryptography and Security
Summary
Sometimes, checking all available records about how a task was done doesn’t prove that the story is complete. The authors created a clear way to decide if all the needed evidence for a task is there, based on rules about what evidence was supposed to show up and when. They also show how to handle late evidence or missing pieces, and how to report if the evidence is complete, incomplete, or unknown at a certain point in time. This helps people understand and trust that what they see about task results really covers what should be known.
What this means in practice
- •For security auditors: Evaluate if all necessary evidence for system actions is available and justified during audits to confirm completion or identify gaps.
- •For cloud operations teams: Use the model to monitor service execution records and detect missing reports or late updates for incident validation and root cause analysis.
Authors
Mengting Wu, Lin Wang, Yong Zhang, Jiang Deng
Abstract
A verifier may authenticate every available record and still lack grounds to call an execution account complete. Such a claim requires a justified account of which records were due for the execution being assessed. We present an analytical model for retrospective coverage of declared execution-evidence obligations. Its scope binds a structured Intent, an exact Candidate, a selected analytical attempt, an execution and evidence boundary, a stage horizon, a fixed record-obligation profile, a named verifier, and an assessment cutoff. Branch and trigger premises determine obligation instances; source competence, content, integrity, and object and stage bindings determine admissibility. We distinguish closure of the obligation inventory from closure of the relevant verifier view, and define three reporting results: COMPLETE_WITHIN_SCOPE, INCOMPLETE, and UNKNOWN. These results concern current coverage of obligations due at the cutoff. Execution progress, external outcome knowledge, and historical delivery timeliness are reported separately. Constructed service-principal-disablement cases demonstrate complete dispatch and refusal branches, a due but missing final-result record, subsequent coverage after late delivery, and the limits of extending one selected attempt's coverage to all attempts. The contribution is an execution-specific composition of scope, branch, horizon, obligations, admissibility, view, and cutoff. Completeness remains conditional on the declared profile and assessment premises.