Criterion
What approved standard or rule should have governed the action?
Evidence-based examination
Execution Integrity Diagnostic
The Execution Integrity Diagnostic reconstructs one defined workflow and period using actual records. It is designed to distinguish a documented control from evidence that the control can be shown to operate.
Scope
One workflow. One period. One defensible question.
The diagnostic is bounded deliberately. It does not claim to certify an enterprise or establish population-wide prevalence from one reconstructed path.
Condition
What did the workflow records show actually occurred?
Consequence
Why does any gap matter to the organization, customer, member, regulator, or operation?
Recommendation
What remediation or evidence requirement should be considered?
Evidence map
The diagnostic follows the path, not a single system.
Evidence may be distributed across documents, emails, tickets, vendor records, workflow tools, approvals, logs, and systems of record.
Approved criteria
Authority record
Workflow events
Exception path
Final action
Preserved evidence
The diagnostic reports what can be supported by the records examined and identifies where evidence is missing or insufficient.
Outputs
A finding should be traceable to both the criterion and the evidence.
The output is designed to support remediation and a validation re-run, not merely describe risk at a high level.
- Defined scope and evidence inventory
- Workflow reconstruction
- Observed findings
- Cross-framework implications where supported
- Evidence gaps and limitations
- Recommended remediation path
- Proposed validation criteria
Important boundary
The diagnostic tests conformance to the criteria in force. It does not determine whether the criteria themselves are wise, fair, or legally sufficient unless that question is separately included in scope.
Select a workflow whose evidence matters.
A historical workflow can establish the fact base before the organization commits to integration or runtime governance.