In a dispute, delivery records may conflict with correspondence, transcripts may differ from written accounts, and legal authorities may support competing interpretations. A coherent narrative is not enough: the system must surface disagreements, preserve each source’s standing, apply authorized precedence rules, and route unresolved material for professional review. section 5.6
Consistency governs conflict and acceptable variation across deterministic and probabilistic components. It does not require identical model wording across executions; it requires defined variation boundaries and rules for conflicts the enterprise is authorized to resolve. section 5.6
Table 5.6 Verifying and managing agentic data quality
|
Quality dimension
|
What you should verify and manage
|
|
Accuracy
|
Reconcile source data with authoritative records, test
transformation fidelity, and run versioned evaluation datasets against
retrieval, grounding, factual claims, tool use, and expected outcomes.
|
|
Completeness
|
Test whether required fields, sources, evidence,
exceptions, and policy inputs are present for the decision surface.
|
|
Timeliness
|
Monitor freshness, effective dates, supersession, pipeline
delay, retrieval-index lag, and context expiry.
|
|
Consistency
|
Detect conflicting values, duplicates, incompatible
formats, broken relationships, and disagreement across sources.
|
|
Traceability
|
Connect sources, transformations, retrieval, model and
tool activity, policy decisions, and the final decision episode.
|
|
Privacy and confidentiality
|
Discover, classify, mask, redact, and restrict personal,
privileged, confidential, or regulated information.
|
|
Compliance
|
Evaluate policy conditions, processing restrictions,
evidence requirements, approval routes, and control outcomes.
|
Use the consistency row to check for conflicting values, duplicates, incompatible formats, broken relationships, and disagreement across sources. section 5.6



























