Timeline Findings Summary

This report summarises changes first observed between selected evidence snapshots.

SubjectAccount

EnvironmentTIMELINE-MOCK

Timeline range

May 25, 2026, 3:27 PMJun 16, 2026, 5:40 PM

Snapshots analysed5

Intervals compared4

Timeline events34

Timeline visual summary

Snapshot-bounded intervals

Visual orientation only. Intervals are bounded by adjacent snapshot captures; counts show events first observed in that capture window.

Interval timeline

4 intervals

May 25, 2026, 3:27 PMJun 16, 2026, 5:40 PM

Interval 1 28 events Interval 2 2 events Interval 3 2 events Interval 4 2 events

Intervals are bounded by snapshot captures. Counts show timeline events first observed in each capture window.

Provider and significance distribution

Provider-owned findings

Findings by provider

Plugin Step Diff

Workflow / Automation Participation Diff

Operational Profile Diff

Solution Participation Diff

Entity Configuration Diff

Relationship Metadata Diff

Identity Participation Diff

Column Metadata Diff

Operational significance mix

High

Medium

Low

Timeline trust

Unverified — 1 of 5 selected snapshots are legacy or unverified. Timeline reconstruction can continue only as inspect-only evidence.

3 verified 1 modified 1 legacy / unverified 0 invalid

Warnings

Timeline is inspect-only

1 of 5 selected snapshots are legacy or unverified. Timeline reconstruction can continue only as inspect-only evidence.

Timeline Findings Summary

34 timeline events first observed across 9 providers.

Plugin Step Diff changed 6 findings, 4 high, 2 medium

6 findings first observed.
First observed between May 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM
Workflow / Automation Participation Diff changed 6 findings, 1 high, 2 medium, 3 low

6 findings first observed.
First observed between May 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM
Operational Profile Diff changed 3 findings, 1 high, 2 medium

3 findings first observed.
First observed between May 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM
Solution Participation Diff changed 4 findings, 1 high, 1 medium, 2 low

4 findings first observed.
First observed between May 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM
Entity Configuration Diff changed 2 findings, 1 high, 1 medium

2 findings first observed.
First observed between May 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM
Relationship Metadata Diff changed 2 findings, 1 high, 1 medium

2 findings first observed.
First observed between May 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM
Identity Participation Diff changed 9 findings, 6 medium, 3 low

9 findings first observed.
First observed between May 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM
Column Metadata Diff changed 1 finding, 1 medium

1 finding first observed.
First observed between May 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM
Choice / Option Set Diff changed 1 finding, 1 low

1 finding first observed.
First observed between May 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM

Top Timeline Events

Highest signal

High Account Change Tracking Enabled changed: false → true
Entity Configuration Diff

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-05-25T05:27:12.006Z → 2026-06-16T06:20:23.405Z.

First observedMay 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM6 evidence references
High DVQR Score density changed: 42 → 67
Operational Profile Diff

Observed operational-density score differs across snapshots. Use this as comparison orientation, not as health, risk, or root-cause evidence. First observed between 2026-05-25T05:27:12.006Z → 2026-06-16T06:20:23.405Z.

First observedMay 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM4 evidence references
High Account Create Validation plugin state changed (Enabled → Disabled)
Plugin Step Diff

Observed plugin step registration metadata differs across snapshots. Use this as runtime behaviour orientation, not as root-cause certainty. First observed between 2026-05-25T05:27:12.006Z → 2026-06-16T06:20:23.405Z.

First observedMay 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM4 evidence references
High Account SIT Enrichment Dispatch added in target
Plugin Step Diff

Target-only plugin step registration. Treat this as runtime behaviour context, not deployment validation. First observed between 2026-05-25T05:27:12.006Z → 2026-06-16T06:20:23.405Z.

First observedMay 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM2 evidence references
High Account Update Integration Dispatch execution pipeline changed
Plugin Step Diff

Observed plugin step registration metadata differs across snapshots. Use this as runtime behaviour orientation, not as root-cause certainty. First observed between 2026-05-25T05:27:12.006Z → 2026-06-16T06:20:23.405Z.

First observedMay 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM6 evidence references
High Legacy Account Background Sync removed from target
Plugin Step Diff

Source-only plugin step registration. Treat this as runtime behaviour context, not deployment validation. First observed between 2026-05-25T05:27:12.006Z → 2026-06-16T06:20:23.405Z.

First observedMay 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM2 evidence references
High Relationship removed: lk_accountbase_modifiedby (Account → SystemUser, ManyToOne)
Relationship Metadata Diff

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-05-25T05:27:12.006Z → 2026-06-16T06:20:23.405Z.

First observedMay 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM7 evidence references
High Power Pages Runtime Core changed from Managed → Unmanaged
Solution Participation Diff

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-05-25T05:27:12.006Z → 2026-06-16T06:20:23.405Z.

First observedMay 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM5 evidence references
High Account Sync Realtime state changed (Deactivated → Activated)
Workflow / Automation Participation Diff

Observed state and owner metadata differ across snapshots. Use this as orchestration orientation, not as execution causality. First observed between 2026-05-25T05:27:12.006Z → 2026-06-16T06:20:23.405Z.

First observedMay 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM5 evidence references
Medium Category (accountcategorycode) Is Audit Enabled changed
Column Metadata Diff

Observed column metadata differs across snapshots. Review the captured metadata and verify externally before drawing deployment or schema conclusions. This property is treated as a higher-signal column metadata change because it can affect query, create/update, or lookup interpretation. First observed between 2026-05-25T05:27:12.006Z → 2026-06-16T06:20:23.405Z.

First observedMay 25, 2026, 3:27 PMJun 16, 2026, 4:20 PM6 evidence references

Evidence boundary

This report summarises changes first observed between selected evidence snapshots.

It does not prove the exact time, actor, cause, remediation status, or operational authority of any change.

Snapshot evidence remains workspace-owned. DV Quick Run organises and presents investigation evidence; it does not create historical certainty.