DV Quick Run · Mini RCA · Experimental · Engine v2.1

DV Quick Run Mini RCA (Experimental)

Question: What operational explanation best fits the available evidence?

Subject: Account · TIMELINE-MOCK

Mini RCA is experimental, deterministic, and evidence-backed. Explain assists. Evidence decides.

Evidence49%Low

Correlation91%Very High

Executive Summary

Automation Participation is the leading explanation

ConclusionAutomation Participation (100%)

Supporting Evidence5 references

Strongest CompetitorMixed Contributors (72%)

Evidence ConfidenceLow

Correlation ConfidenceVery High

First ActionInspect automation participation

Investigation Objective

Explain the operational pattern most consistent with the available understanding evidence for Account.

Experimental Boundary

Mini RCA is experimental and advisory. It does not prove exact change time, root cause, remediation status, deployment correctness, or operational authority.

Investigation Story

Mini RCA reviewed 5 snapshots across 4 intervals and summarised 38 timeline events.

Automation Participation is the leading operational explanation for Account.

Mixed Contributors remains visible as a competing explanation, but it currently carries a lower correlation score (72%) than Automation Participation (100%).

Correlation is strong at 91%, but evidence confidence is 49%, so the explanation should be treated as probable rather than conclusive.

Use the evidence references as the source-of-truth: Mini RCA explains the pattern; it does not prove exact change time, runtime causality, remediation status, or operational authority.

Why DVQR Thinks This

Deterministic evidence flow

Timeline Understanding38 event(s)

Audit EvidenceAudit evidence unavailable. Confidence unchanged.

Cross EnvironmentNot provided

Provider Signals0 signal(s)

→

Automation Participation5 evidence references

Configuration Drift2 evidence references

Metadata Evolution1 evidence reference

Operational Profile1 evidence reference

→

Automation ParticipationMini RCA recommendation path

Most probable

Automation Participation

100%

Leading explanation context: 5 supporting evidence references; observed across 4 timeline intervals.

Timeline evidence contains automation or execution participation changes. 5 supporting evidence items support this explanation.

Account Create Validation plugin state changed (Enabled → Disabled)
Account SIT Enrichment Dispatch added in target
Account Update Integration Dispatch execution pipeline changed

View all linked evidence (5)

timeline-2 — Observed plugin step registration metadata differs across snapshots. Use this as runtime behaviour orientation, not as root-cause certainty. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.
timeline-3 — Target-only plugin step registration. Treat this as runtime behaviour context, not deployment validation. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.
timeline-4 — Observed plugin step registration metadata differs across snapshots. Use this as runtime behaviour orientation, not as root-cause certainty. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.
timeline-5 — Source-only plugin step registration. Treat this as runtime behaviour context, not deployment validation. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.
timeline-7 — Observed state and owner metadata differ across snapshots. Use this as orchestration orientation, not as execution causality. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.

Show competing explanations (5)

Competing explanation

Mixed Contributors

72%

The strongest explanation is not isolated to one contributor type. Evidence spans multiple categories across 4 intervals.

DVQR Score density changed: 42 → 67
Account Create Validation plugin state changed (Enabled → Disabled)
Account SIT Enrichment Dispatch added in target

View all linked evidence (6)

timeline-1 — Observed operational-density score differs across snapshots. Use this as comparison orientation, not as health, risk, or root-cause evidence. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.
timeline-2 — Observed plugin step registration metadata differs across snapshots. Use this as runtime behaviour orientation, not as root-cause certainty. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.
timeline-3 — Target-only plugin step registration. Treat this as runtime behaviour context, not deployment validation. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.
timeline-4 — Observed plugin step registration metadata differs across snapshots. Use this as runtime behaviour orientation, not as root-cause certainty. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.
timeline-5 — Source-only plugin step registration. Treat this as runtime behaviour context, not deployment validation. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.
timeline-6 — Observed solution package metadata differs across snapshots. Use this as deployment/layering orientation, not as proof that a deployment caused runtime behaviour. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.

Competing explanation

Configuration Drift

38%

Configuration drift is present, but the available evidence does not identify a more specific contributor class. 2 supporting evidence items support this explanation.

Account Change Tracking Enabled changed: false → true
human.operator.dev@example.com present only in source

View all linked evidence (2)

timeline-8 — Entity change tracking configuration differs across snapshots. Change tracking may affect integration, synchronization, and delta-observation behaviour, but DVQR does not infer runtime impact or remediation scope. First observed between 2026-06-16T06:31:26.106Z → 2026-06-16T07:23:46.723Z.
timeline-10 — Identity appears only in the source evidence set. First observed between 2026-05-25T05:27:12.006Z → 2026-06-16T06:20:23.405Z.

Competing explanation

Metadata Evolution

24%

Schema or field-level evolution is present in the reconstructed timeline. 1 supporting evidence item support this explanation.

Power Pages Runtime Core changed from Managed → Unmanaged

View all linked evidence (1)

timeline-6 — Observed solution package metadata differs across snapshots. Use this as deployment/layering orientation, not as proof that a deployment caused runtime behaviour. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.

Competing explanation

Operational Profile

24%

Operational profile signals indicate different execution posture or context. 1 supporting evidence item support this explanation.

DVQR Score density changed: 42 → 67

View all linked evidence (1)

timeline-1 — Observed operational-density score differs across snapshots. Use this as comparison orientation, not as health, risk, or root-cause evidence. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.

Competing explanation

Security Participation

24%

Identity, team, role, business-unit, or access participation signals appear in the reconstructed evidence. 1 supporting evidence item support this explanation.

Relationship removed: lk_accountbase_modifiedby (Account → SystemUser, ManyToOne)

View all linked evidence (1)

timeline-9 — This ManyToOne relationship (account → systemuser) exists in the source snapshot but is missing in the target. Relationship drift can occur when lookup fields or relationship metadata are removed, renamed, added, or changed between snapshots. DVQR treats this as high-signal metadata evidence because relationships can affect lookup/navigation/traversal interpretation, but it does not infer deployment causality, runtime impact, or remediation scope. First observed between 2026-06-16T06:31:26.106Z → 2026-06-16T07:23:46.723Z.

Evidence

Supporting, missing, and confidence notes

Supporting Evidence

timeline-2: Account Create Validation plugin state changed (Enabled → Disabled)
timeline-3: Account SIT Enrichment Dispatch added in target
timeline-4: Account Update Integration Dispatch execution pipeline changed
timeline-5: Legacy Account Background Sync removed from target
timeline-7: Account Sync Realtime state changed (Deactivated → Activated)

Missing / Limiting Evidence

Audit evidence unavailable. Confidence unchanged.
Cross-environment understanding was not provided to this Mini RCA bundle.
Provider signals beyond Timeline Understanding were not provided.
Reconstruction artifacts were not attached to this Mini RCA bundle.
Timeline evidence is not fully verified
Audit evidence may be absent from RCA correlation
Limiting evidence: timeline-1: DVQR Score density changed: 42 → 67
Limiting evidence: timeline-6: Power Pages Runtime Core changed from Managed → Unmanaged
Limiting evidence: timeline-8: Account Change Tracking Enabled changed: false → true
Limiting evidence: timeline-9: Relationship removed: lk_accountbase_modifiedby (Account → SystemUser, ManyToOne)
Limiting evidence: timeline-10: human.operator.dev@example.com present only in source

Show confidence notes

Strengthens: A deterministic leading explanation is available: Automation Participation (100%).
Strengthens: 9 high-confidence evidence references support the evidence set.
Limits: Evidence confidence (49%) is lower than correlation confidence (91%).
Limits: Timeline evidence is not fully verified (Medium).
Limits: Audit evidence may be absent from RCA correlation (Low).

Next Investigation

Recommended Next Steps

Inspect automation participation

Review the plugin steps, workflows, flows, or execution pipeline entries referenced by the leading evidence group.

5 evidence references currently support Automation Participation with a deterministic correlation score of 100.

Evidence: timeline-2: Account Create Validation plugin state changed (Enabled → Disabled) · timeline-3: Account SIT Enrichment Dispatch added in target · timeline-4: Account Update Integration Dispatch execution pipeline changed · timeline-5: Legacy Account Background Sync removed from target · timeline-7: Account Sync Realtime state changed (Deactivated → Activated)

Prepare reconstruction export if remediation is needed

Where the finding maps to DV ForgeLab reconstruction utilities, use the linked evidence to decide whether DVAF, DVCE, DVIM, or DVEVM export is appropriate.

1 metadata-oriented evidence reference appears in the RCA bundle; Mini RCA can guide reconstruction, but it does not perform remediation.

Evidence: timeline-6: Power Pages Runtime Core changed from Managed → Unmanaged

Open the Timeline Understanding source report

Use the Timeline Understanding report to inspect strongest intervals, adjacent windows, and raw event context behind the Mini RCA summary.

Mini RCA summarises timeline evidence; Timeline Understanding remains the detailed source-of-truth for first-observed windows.

Evidence: timeline-1: DVQR Score density changed: 42 → 67 · timeline-2: Account Create Validation plugin state changed (Enabled → Disabled) · timeline-3: Account SIT Enrichment Dispatch added in target · timeline-4: Account Update Integration Dispatch execution pipeline changed

Enrich with audit evidence where available

Use per-event audit evidence actions to narrow the observed window before escalating confidence or customer-facing conclusions.

Audit evidence can narrow an observed interval but does not override snapshot evidence or prove root cause.

Capture another baseline if confidence remains contested

Add another snapshot or cross-environment comparison when mixed contributors remain visible or when evidence confidence is materially lower than correlation confidence.

Mini RCA becomes stronger when independent understanding surfaces converge on the same contributor category.

Appendix

Detailed Evidence and Bundle Contract

Understanding Bundle v1 · contributor details

Understanding Bundle v1

Understanding Bundle Contract v0.14.6

Availability

Available: Timeline, Metadata, Identity, Configuration

Unavailable: Audit — Audit evidence was not retrieved or audit is disabled, so exact change confirmation remains limited.; Cross Diff — Cross-environment understanding was not provided to this Mini RCA bundle.; Query — Query Understanding was not provided to this Mini RCA bundle.

Not applicable: Relationship

Overall Bundle Confidence

Low

Reasons

4 understanding contributors are available.
Available contributors: Timeline Understanding, Metadata Understanding, Identity Understanding, Configuration Understanding.

Limitations

Audit Understanding: Audit evidence was not retrieved or audit is disabled, so exact change confirmation remains limited.
Cross Diff Understanding: Cross-environment understanding was not provided to this Mini RCA bundle.
Query Understanding: Query Understanding was not provided to this Mini RCA bundle.
First observed is not changed at; Timeline Understanding narrows investigation windows but does not prove exact change time.
Audit evidence was not retrieved or audit is disabled, so exact change confirmation remains limited.
Metadata drift is investigation evidence; it is not deployment correctness proof.
Participation is not authority; identity drift does not prove effective access.
No relationship evidence was present in this investigation bundle.

Contributor Confidence Summary

Timeline Understanding

available · confidence Medium

Timeline Understanding reviewed 38 event(s) across 4 interval(s).

Evidence: timeline-1, timeline-2, timeline-3, timeline-4, timeline-5, timeline-6, timeline-7, timeline-8, timeline-9, timeline-10

Audit Understanding

unavailable · confidence Unknown

Audit evidence was not retrieved or audit is disabled, so exact change confirmation remains limited.

Metadata Understanding

available · confidence High

Metadata Understanding found 1 relevant evidence reference.

Evidence: timeline-6

Identity Understanding

available · confidence High

Identity Understanding found 1 relevant evidence reference.

Evidence: timeline-9

Relationship Understanding

notApplicable · confidence Unknown

No relationship evidence was present in this investigation bundle.

Configuration Understanding

available · confidence High

Configuration Understanding found 2 relevant evidence references.

Evidence: timeline-8, timeline-10

Cross Diff Understanding

unavailable · confidence Unknown

Cross-environment understanding was not provided to this Mini RCA bundle.

Query Understanding

unavailable · confidence Unknown

Query Understanding was not provided to this Mini RCA bundle.

Correlation Summary

Reinforcing / Conflicting

Reinforcing

Timeline Understanding, Metadata Understanding, Identity Understanding, Configuration Understanding are available for bounded correlation.

Conflicting

None

Missing / Not Applicable

Missing

Audit Understanding is unavailable: Audit evidence was not retrieved or audit is disabled, so exact change confirmation remains limited.
Cross Diff Understanding is unavailable: Cross-environment understanding was not provided to this Mini RCA bundle.
Query Understanding is unavailable: Query Understanding was not provided to this Mini RCA bundle.

Not Applicable

Relationship Understanding was not applicable for this investigation bundle.

Recommended Investigation Path

Start with Timeline Understanding; review linked evidence without inferring causality.
Start with Metadata Understanding; review linked evidence without inferring causality.
Start with Identity Understanding; review linked evidence without inferring causality.
Start with Configuration Understanding; review linked evidence without inferring causality.

Legacy Inputs

Timeline 38 event(s) · Audit Unavailable · Reconstruction artifacts 0

Supporting Evidence Appendix

Automation Participation

5 findings

5 High · 0 Medium · 0 Low

Plugin Step Diff, Workflow / Automation Participation Diff

Expand evidence references

timeline-2: Account Create Validation plugin state changed (Enabled → Disabled)
Observed plugin step registration metadata differs across snapshots. Use this as runtime behaviour orientation, not as root-cause certainty. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.
First observed: 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z
timeline-3: Account SIT Enrichment Dispatch added in target
Target-only plugin step registration. Treat this as runtime behaviour context, not deployment validation. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.
First observed: 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z
timeline-4: Account Update Integration Dispatch execution pipeline changed
Observed plugin step registration metadata differs across snapshots. Use this as runtime behaviour orientation, not as root-cause certainty. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.
First observed: 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z
timeline-5: Legacy Account Background Sync removed from target
Source-only plugin step registration. Treat this as runtime behaviour context, not deployment validation. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.
First observed: 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z
timeline-7: Account Sync Realtime state changed (Deactivated → Activated)
Observed state and owner metadata differ across snapshots. Use this as orchestration orientation, not as execution causality. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.
First observed: 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z

Configuration Drift

2 findings

1 High · 1 Medium · 0 Low

Entity Configuration Diff, Identity Participation Diff

Expand evidence references

timeline-8: Account Change Tracking Enabled changed: false → true
Entity change tracking configuration differs across snapshots. Change tracking may affect integration, synchronization, and delta-observation behaviour, but DVQR does not infer runtime impact or remediation scope. First observed between 2026-06-16T06:31:26.106Z → 2026-06-16T07:23:46.723Z.
First observed: 2026-06-16T06:31:26.106Z → 2026-06-16T07:23:46.723Z
timeline-10: human.operator.dev@example.com present only in source
Identity appears only in the source evidence set. First observed between 2026-05-25T05:27:12.006Z → 2026-06-16T06:20:23.405Z.
First observed: 2026-05-25T05:27:12.006Z → 2026-06-16T06:20:23.405Z

Metadata Evolution

1 finding

1 High · 0 Medium · 0 Low

Solution Participation Diff

Expand evidence references

timeline-6: Power Pages Runtime Core changed from Managed → Unmanaged
Observed solution package metadata differs across snapshots. Use this as deployment/layering orientation, not as proof that a deployment caused runtime behaviour. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.
First observed: 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z

Operational Profile

1 finding

1 High · 0 Medium · 0 Low

Operational Profile Diff

Expand evidence references

timeline-1: DVQR Score density changed: 42 → 67
Observed operational-density score differs across snapshots. Use this as comparison orientation, not as health, risk, or root-cause evidence. First observed between 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z.
First observed: 2026-06-16T06:20:23.405Z → 2026-06-16T06:31:26.106Z

Security Participation

1 finding

1 High · 0 Medium · 0 Low

Relationship Metadata Diff

Expand evidence references

timeline-9: Relationship removed: lk_accountbase_modifiedby (Account → SystemUser, ManyToOne)
This ManyToOne relationship (account → systemuser) exists in the source snapshot but is missing in the target. Relationship drift can occur when lookup fields or relationship metadata are removed, renamed, added, or changed between snapshots. DVQR treats this as high-signal metadata evidence because relationships can affect lookup/navigation/traversal interpretation, but it does not infer deployment causality, runtime impact, or remediation scope. First observed between 2026-06-16T06:31:26.106Z → 2026-06-16T07:23:46.723Z.
First observed: 2026-06-16T06:31:26.106Z → 2026-06-16T07:23:46.723Z