DVQR observed differences across runtime behaviour, workflow / orchestration, solution participation, operational density, and identity participation. Treat this as investigation orientation, not RCA certainty.
Pro · Cross-Environment Diff
Cross-Environment Diff: Account · DEV-MOCK → SIT-MOCK
DVQR observes operational drift. DVQR does not fix operational drift.
Comparison session
Generated 7/6/2026, 10:51:31 AM. Snapshot evidence remains local investigation context, not deployment authority.
Source snapshot
DEV-MOCK · Account
5/25/2026, 12:05:25 AM · Verified
Target snapshot
SIT-MOCK · Account
5/25/2026, 1:30:00 AM · Verified
Pre-investigation baseline
Baseline not exported
Export the untouched comparison evidence before review state, checklist ticks, notes, or handoff decisions are captured.
Source: DEV-MOCK · Target: SIT-MOCK
9High significance
17Medium significance
6Low significance
32Differences
10Providers
AccountComparison scope
DEV-MOCK → SIT-MOCKComparison
Focused operational surface
Multiple drift signals were observed. Use grouped provider sections to preserve operational context before drilling into individual evidence.
Investigation Workspace
Switch workspace modes to focus investigation synthesis, detailed findings, verification tasks, or handoff readiness without losing the underlying comparison evidence.
Investigation view active
Showing storyline, session continuity, top operational signals, and investigation continuations. Switch to Findings for the full diff evidence browser.
Active mode
Investigation
Workspace focus
Storyline, continuity, current posture, and investigation progression.
Mode behaviour
Mode-focused workspace view. Use Findings to inspect provider drift evidence.
Investigation Briefing
Observation-first summary of what DVQR detected before moving into detailed findings or external verification.
Review high-significance plugin/runtime changes and workflow participation before treating the compared environments as operationally equivalent.
Use Findings to inspect evidence, Verification to track external validation prompts, and Handoff to package unresolved observations for another reviewer or team.
Investigation Session
Operational investigation continuity for this comparison workspace. Investigation guidance remains evidence-backed and externally verifiable.
Session continuity
Baseline boundary pending
Export the pre-investigation baseline before marking evidence reviewed so later handoff state can be compared against the original observed diff.
0 / 0
Reviewed drift surfaces
0%
Operational verification coverage
0
Outstanding high-significance signals
Snapshot trust: Verified
Verification posture: In Progress
Replay source: Cross-environment comparison
Outstanding operational verification
- Account Create Validation plugin disabled High-significance runtime verification still requires external validation.
- Workflow orchestration participation changed Observed automation/runtime adjacency should be reviewed externally before corrective action.
Operational review notes
No reviewer notes captured in this investigation session.
Observed Operational Storyline
Bounded synthesis of what this comparison collectively observed. This is investigation guidance, not RCA certainty or remediation instruction.
Operational comparison narrative
Observed operational differences were found between DEV-MOCK and SIT-MOCK across runtime behaviour, workflow / orchestration, solution / package participation, operational density, identity participation.
These observations may warrant external verification before treating the environments as operationally equivalent. DVQR preserves evidence-backed context; humans retain operational authority and corrective-action ownership.
Potential operational considerations
Use these as verification-oriented prompts. They are not root-cause findings, blame statements, or corrective instructions.
- Runtime behaviourAccount Create Validation plugin state changed (Enabled → Disabled)
- Workflow / orchestrationAccount Sync Realtime state changed (Deactivated → Activated)
- Package / solution contextDVQR Mock Operational Automation present only in SIT-MOCK
- Operational densityDVQR Score changed: 42 → 67
- Identity participationhuman.operator.dev@example.com present only in DEV-MOCK
Investigation handoff posture
The checklist below converts representative drift signals into handoff-ready validation prompts for people or teams outside DVQR.
- External verification recommendedConfirm expectations in Dataverse, Power Platform admin surfaces, ALM pipelines, or owner/team channels as appropriate.
- Authority remains humanDVQR narrows the operational problem space; it does not determine corrective action.
Investigation Continuations
1
Observed drift
Comparison evidence collected
2
Operational verification
External validation in progress
3
Operational conclusion
Awaiting reviewer confirmation
0
Reviewed externally
6
Outstanding verification items
Continue investigation directly from evidence-backed operational drift signals. These continuations preserve investigation locality and comparison context.
Runtime continuation
Plugin runtime investigation
Continue reviewing execution ordering, stage placement, filtering attributes, and runtime participation context.
Orchestration continuation
Workflow / automation investigation
Continue reviewing workflow participation, activation changes, orchestration topology, and automation alignment.
Operational handoff
Verification-oriented continuation
Convert representative evidence into externally verifiable operational review tasks before corrective action is considered.
Top Operational Drift Signals
Fast orientation across the strongest evidence-backed drift signals. These are investigation cues, not remediation instructions.
Showing 5 of 9 high-significance drift signals. Additional signals remain available in provider sections.
- DVQR Mock Operational Automation present only in SIT-MOCK Additional operational participation is visible in SIT-MOCK.
- Account Change Tracking Enabled changed: false → true Review the underlying evidence before comparing runtime behaviour.
- DVQR Score changed: 42 → 67 Operational density changed between snapshots.
- Account Create Validation plugin state changed (Enabled → Disabled) Plugin execution availability differs between environments.
- Account SIT Enrichment Dispatch added in SIT-MOCK Additional operational participation is visible in SIT-MOCK.
Operational Drift
Grouped, evidence-backed differences from comparison providers. These are investigation signals, not remediation instructions.
Search is local to this comparison.
Local search only. DVQR searches rendered evidence in this workspace; it does not query Dataverse or retrieve additional evidence.
Entity Configuration Drift
Observed entity configuration drift for Account. These are metadata configuration changes for external verification, not deployment validation, operational certification, or remediation advice.
Entity Configuration Drift contains 2 drift signals.
- Account Change Tracking Enabled changed: false → true
- Account Audit Enabled changed: false → true
Other observed drift surfaces 3
Use these cues to decide which neighbouring evidence may deserve external verification. They indicate adjacency only, not chronology, causality, remediation, or root-cause certainty.
-
Additional bounded contextRelationship Metadata Drift Review this provider when its signals answer a distinct operational verification question.Investigation handoff Included in verification checklist ↓
-
Adjacent runtime driftPlugin Step Runtime Behaviour Drift Review enablement, execution stage, mode, order, and filtering-attribute drift that can change runtime behaviour.Investigation handoff Included in verification checklist ↓
-
Additional bounded contextColumn Metadata Drift Review this provider when its signals answer a distinct operational verification question.Investigation handoff Included in verification checklist ↓
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.
Sourcefalse
Targettrue
Show full evidence 5
-
Entity logical name — account
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Entity logical name
- Observed value
- account
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Entity display name — Account
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Entity display name
- Observed value
- Account
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Entity set name — accounts
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Entity set name
- Observed value
- accounts
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Change Tracking Enabled (source) — false
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Change Tracking Enabled (source)
- Observed value
- false
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Change Tracking Enabled (target) — true
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Change Tracking Enabled (target)
- Observed value
- true
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet.
Account Audit Enabled changed: false → true Entity auditing configuration differs across snapshots. Auditing drift may affect future change-history evidence availability, but DVQR treats this as metadata configuration evidence only.
Sourcefalse
Targettrue
Show full evidence 5
-
Entity logical name — account
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Entity logical name
- Observed value
- account
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Entity display name — Account
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Entity display name
- Observed value
- Account
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Entity set name — accounts
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Entity set name
- Observed value
- accounts
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Audit Enabled (source) — false
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Audit Enabled (source)
- Observed value
- false
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Audit Enabled (target) — true
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Audit Enabled (target)
- Observed value
- true
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet.
Operational Profile Drift
Account operational profile differs between snapshots.
Operational profile density shifted between DEV-MOCK and SIT-MOCK. Review the strongest contributor changes before treating the environments as operationally equivalent.
- DVQR Score changed: 42 → 67
- Plugin Steps count increased (Moderate → High)
- Operational profile signal only in target: Real-time Workflows present only in SIT-MOCK
Other observed drift surfaces 3
Use these cues to decide which neighbouring evidence may deserve external verification. They indicate adjacency only, not chronology, causality, remediation, or root-cause certainty.
-
Adjacent runtime driftPlugin Step Runtime Behaviour Drift Review enablement, execution stage, mode, order, and filtering-attribute drift that can change runtime behaviour.Investigation handoff Included in verification checklist ↓
-
Package participation contextSolution Participation Drift Review managed state, version, and package presence differences that may explain component-layering changes.Investigation handoff Included in verification checklist ↓
-
Adjacent orchestration driftWorkflow / Automation Participation Drift Review activation, owner, real-time/background, and orchestration participation differences outside the plugin pipeline.Investigation handoff Included in verification checklist ↓
DVQR Score changed: 42 → 67 DVQR Score increased from Moderate to High density.
Source42
Target67
Show full evidence 3
-
Source score — 42 (Moderate)
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Source score
- Observed value
- 42 (Moderate)
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Target score — 67 (High)
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Target score
- Observed value
- 67 (High)
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Observed delta — +25
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Observed delta
- Observed value
- +25
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet.
Plugin Steps count increased (Moderate → High) Automation (Plugin Steps) changed between DEV-MOCK and SIT-MOCK.
SourceModerate
TargetHigh
Show full evidence 2
-
Source signal — moderate — 12 synchronous plugin steps
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Source signal
- Observed value
- moderate — 12 synchronous plugin steps
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Target signal — high — 28 synchronous plugin steps
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Target signal
- Observed value
- high — 28 synchronous plugin steps
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet.
Operational profile signal only in target: Real-time Workflows present only in SIT-MOCK Only observed in SIT-MOCK.
TargetModerate
Show full evidence 1
-
Target signal — moderate — 3 real-time workflows
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Target signal
- Observed value
- moderate — 3 real-time workflows
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet.
Plugin Step Runtime Behaviour Drift
Plugin step registrations differ between snapshots.
Plugin runtime behaviour differs between DEV-MOCK and SIT-MOCK. Review changed step state, pipeline placement, and environment-specific registrations before comparing runtime outcomes.
- Account Create Validation plugin state changed (Enabled → Disabled)
- Account SIT Enrichment Dispatch added in SIT-MOCK
- Account Update Integration Dispatch execution pipeline changed
Other observed drift surfaces 3
Use these cues to decide which neighbouring evidence may deserve external verification. They indicate adjacency only, not chronology, causality, remediation, or root-cause certainty.
-
Adjacent orchestration driftWorkflow / Automation Participation Drift Review activation, owner, real-time/background, and orchestration participation differences outside the plugin pipeline.Investigation handoff Included in verification checklist ↓
-
Package participation contextSolution Participation Drift Review managed state, version, and package presence differences that may explain component-layering changes.Investigation handoff Included in verification checklist ↓
-
Additional bounded contextEntity Configuration Drift Review this provider when its signals answer a distinct operational verification question.Investigation handoff Included in verification checklist ↓
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.
SourceAccount Create Validation • Dvqr.Mock.Plugins.AccountValidationPlugin • Message: Create • Entity: account • Stage: Pre-operation • Mode: Synchronous • Order: 10 • Enabled • Unmanaged
TargetAccount Create Validation • Dvqr.Mock.Plugins.AccountValidationPlugin • Message: Create • Entity: account • Stage: Pre-operation • Mode: Synchronous • Order: 10 • Disabled • Unmanaged
Show full evidence 3
-
Source plugin step — Account Create Validation • Dvqr.Mock.Plugins.AccountValidationPlugin • Message: Create • Entity: account • Stage: Pre-operation • Mode: Synchronous • Order: 10 • Enabled • Unmanaged
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Source plugin step
- Observed value
- Account Create Validation • Dvqr.Mock.Plugins.AccountValidationPlugin • Message: Create • Entity: account • Stage: Pre-operation • Mode: Synchronous • Order: 10 • Enabled • Unmanaged
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Target plugin step — Account Create Validation • Dvqr.Mock.Plugins.AccountValidationPlugin • Message: Create • Entity: account • Stage: Pre-operation • Mode: Synchronous • Order: 10 • Disabled • Unmanaged
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Target plugin step
- Observed value
- Account Create Validation • Dvqr.Mock.Plugins.AccountValidationPlugin • Message: Create • Entity: account • Stage: Pre-operation • Mode: Synchronous • Order: 10 • Disabled • Unmanaged
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
State drift — Enabled → Disabled
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- State drift
- Observed value
- Enabled → Disabled
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet.
Account SIT Enrichment Dispatch added in SIT-MOCK Target-only plugin step registration. Treat this as runtime behaviour context, not deployment validation.
SourceNo plugin step evidence
TargetAccount SIT Enrichment Dispatch • Dvqr.Mock.Plugins.AccountEnrichmentPlugin • Message: Update • Entity: account • Stage: Post-operation • Mode: Asynchronous • Order: 40 • Enabled • Managed
Show full evidence 1
-
Target plugin step — Account SIT Enrichment Dispatch • Dvqr.Mock.Plugins.AccountEnrichmentPlugin • Message: Update • Entity: account • Stage: Post-operation • Mode: Asynchronous • Order: 40 • Enabled • Managed
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Target plugin step
- Observed value
- Account SIT Enrichment Dispatch • Dvqr.Mock.Plugins.AccountEnrichmentPlugin • Message: Update • Entity: account • Stage: Post-operation • Mode: Asynchronous • Order: 40 • Enabled • Managed
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet.
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.
SourceAccount Update Integration Dispatch • Dvqr.Mock.Plugins.AccountIntegrationPlugin • Message: Update • Entity: account • Stage: Post-operation • Mode: Synchronous • Order: 20 • Enabled • Unmanaged
TargetAccount Update Integration Dispatch • Dvqr.Mock.Plugins.AccountIntegrationPlugin • Message: Update • Entity: account • Stage: Pre-operation • Mode: Synchronous • Order: 5 • Enabled • Unmanaged
Show full evidence 5
-
Source plugin step — Account Update Integration Dispatch • Dvqr.Mock.Plugins.AccountIntegrationPlugin • Message: Update • Entity: account • Stage: Post-operation • Mode: Synchronous • Order: 20 • Enabled • Unmanaged
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Source plugin step
- Observed value
- Account Update Integration Dispatch • Dvqr.Mock.Plugins.AccountIntegrationPlugin • Message: Update • Entity: account • Stage: Post-operation • Mode: Synchronous • Order: 20 • Enabled • Unmanaged
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Target plugin step — Account Update Integration Dispatch • Dvqr.Mock.Plugins.AccountIntegrationPlugin • Message: Update • Entity: account • Stage: Pre-operation • Mode: Synchronous • Order: 5 • Enabled • Unmanaged
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Target plugin step
- Observed value
- Account Update Integration Dispatch • Dvqr.Mock.Plugins.AccountIntegrationPlugin • Message: Update • Entity: account • Stage: Pre-operation • Mode: Synchronous • Order: 5 • Enabled • Unmanaged
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Stage drift — Post-operation → Pre-operation
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Stage drift
- Observed value
- Post-operation → Pre-operation
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Execution order drift — 20 → 5
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Execution order drift
- Observed value
- 20 → 5
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Filtering attributes drift — name, telephone1 → emailaddress1, name, telephone1
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Filtering attributes drift
- Observed value
- name, telephone1 → emailaddress1, name, telephone1
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet.
Legacy Account Background Sync removed in SIT-MOCK Source-only plugin step registration. Treat this as runtime behaviour context, not deployment validation.
SourceLegacy Account Background Sync • Dvqr.Mock.Plugins.LegacyAccountSyncPlugin • Message: Update • Entity: account • Stage: Post-operation • Mode: Asynchronous • Order: 30 • Enabled • Unmanaged
TargetNo plugin step evidence
Show full evidence 1
-
Source plugin step — Legacy Account Background Sync • Dvqr.Mock.Plugins.LegacyAccountSyncPlugin • Message: Update • Entity: account • Stage: Post-operation • Mode: Asynchronous • Order: 30 • Enabled • Unmanaged
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Source plugin step
- Observed value
- Legacy Account Background Sync • Dvqr.Mock.Plugins.LegacyAccountSyncPlugin • Message: Update • Entity: account • Stage: Post-operation • Mode: Asynchronous • Order: 30 • Enabled • Unmanaged
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet.
Minor plugin configuration signals (2)
2 lower-priority plugin configuration signals observed. These are grouped to keep runtime-behaviour drift focused on execution-impacting changes while preserving evidence continuity.
Grouped classification2 of 6 plugin runtime drift signals
Classification rationaleGrouped because these are plugin configuration or metadata changes rather than added/removed steps or state changes.
Direction summaryConfiguration Drift: 2
Operational priorityLower-priority provider detail by default; review when these details are part of the investigation path.
Evidence continuityRepresentative signals are listed below; full per-signal evidence remains available in JSON/HTML export.
-
Account Address Normalisation changed
Inline evidence context This grouped signal preserves representative evidence from a dense provider section. Use it to verify the signal before continuing investigation outside DVQR.
- Evidence label
- Account Address Normalisation changed
- Observed value
- Source plugin step: Account Address Normalisation • Dvqr.Mock.Plugins.AccountAddressPlugin • Message: Update • Entity: account • Stage: Post-operation • Mode: Synchronous • Order: 45 • Enabled • Unmanaged · Target plugin step: Account Address Normalisation • Dvqr.Mock.Plugins.AccountAddressPlugin • Message: Update • Entity: account • Stage: Post-operation • Mode: Synchronous • Order: 45 • Enabled • Unmanaged · Filtering attributes drift: address1_city → address1_city, address1_postalcode
- Operational boundary
- Grouped evidence opens captured comparison context. In the VS Code webview, DVQR can request a bounded live evidence pivot for supported evidence types.
- Live evidence pivot
- Not queried yet.
-
Account Consent Reminder Dispatch changed
Inline evidence context This grouped signal preserves representative evidence from a dense provider section. Use it to verify the signal before continuing investigation outside DVQR.
- Evidence label
- Account Consent Reminder Dispatch changed
- Observed value
- Source plugin step: Account Consent Reminder Dispatch • Dvqr.Mock.Plugins.AccountConsentPlugin • Message: Update • Entity: account • Stage: Post-operation • Mode: Synchronous • Order: 35 • Enabled • Unmanaged · Target plugin step: Account Consent Reminder Dispatch • Dvqr.Mock.Plugins.AccountConsentPlugin • Message: Update • Entity: account • Stage: Post-operation • Mode: Synchronous • Order: 35 • Enabled • Unmanaged · Filtering attributes drift: emailaddress1 → emailaddress1, telephone1
- Operational boundary
- Grouped evidence opens captured comparison context. In the VS Code webview, DVQR can request a bounded live evidence pivot for supported evidence types.
- Live evidence pivot
- Not queried yet.
Relationship Metadata Drift
Observed relationship metadata drift for Account. These are schema evidence changes for external verification, not dependency analysis, deployment validation, or remediation advice.
Relationship Metadata Drift contains 2 drift signals.
- Relationship removed: lk_accountbase_modifiedby (Account → SystemUser, ManyToOne)
- Relationship added: new_account_customersegment (Account → New Customersegment, ManyToOne)
Other observed drift surfaces 3
Use these cues to decide which neighbouring evidence may deserve external verification. They indicate adjacency only, not chronology, causality, remediation, or root-cause certainty.
-
Additional bounded contextEntity Configuration Drift Review this provider when its signals answer a distinct operational verification question.Investigation handoff Included in verification checklist ↓
-
Adjacent runtime driftPlugin Step Runtime Behaviour Drift Review enablement, execution stage, mode, order, and filtering-attribute drift that can change runtime behaviour.Investigation handoff Included in verification checklist ↓
-
Package participation contextSolution Participation Drift Review managed state, version, and package presence differences that may explain component-layering changes.Investigation handoff Included in verification checklist ↓
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.
Sourcelk_accountbase_modifiedby · ManyToOne · account → systemuser · from: modifiedby · nav: modifiedby
Show full evidence 6
-
Relationship schema name — lk_accountbase_modifiedby
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Relationship schema name
- Observed value
- lk_accountbase_modifiedby
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Relationship type — ManyToOne
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Relationship type
- Observed value
- ManyToOne
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Referencing entity — account
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Referencing entity
- Observed value
- account
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Referenced entity — systemuser
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Referenced entity
- Observed value
- systemuser
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Referencing attribute — modifiedby
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Referencing attribute
- Observed value
- modifiedby
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Source relationship — lk_accountbase_modifiedby · ManyToOne · account → systemuser · from: modifiedby · nav: modifiedby
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Source relationship
- Observed value
- lk_accountbase_modifiedby · ManyToOne · account → systemuser · from: modifiedby · nav: modifiedby
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet.
Relationship added: new_account_customersegment (Account → New Customersegment, ManyToOne) This ManyToOne relationship (account → new_customersegment) appears in the target snapshot but was not present in the source. 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.
Targetnew_account_customersegment · ManyToOne · account → new_customersegment · from: new_customersegmentid · nav: new_customersegmentid
Show full evidence 6
-
Relationship schema name — new_account_customersegment
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Relationship schema name
- Observed value
- new_account_customersegment
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Relationship type — ManyToOne
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Relationship type
- Observed value
- ManyToOne
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Referencing entity — account
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Referencing entity
- Observed value
- account
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Referenced entity — new_customersegment
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Referenced entity
- Observed value
- new_customersegment
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Referencing attribute — new_customersegmentid
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Referencing attribute
- Observed value
- new_customersegmentid
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Target relationship — new_account_customersegment · ManyToOne · account → new_customersegment · from: new_customersegmentid · nav: new_customersegmentid
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Target relationship
- Observed value
- new_account_customersegment · ManyToOne · account → new_customersegment · from: new_customersegmentid · nav: new_customersegmentid
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet.
Solution Participation Drift
Solution package participation differs between snapshots.
Solution layering differs between DEV-MOCK and SIT-MOCK. Review package presence, version, and managed-state drift as operational context, not deployment validation.
- DVQR Mock Operational Automation present only in SIT-MOCK
- Power Pages Runtime Core changed from Managed → Unmanaged
- Power Pages Runtime Core Dependencies version changed (1.0.2305.1 → 1.0.9999.1)
Density-first orientation keeps evidence visible while reducing scan noise.
- Solution classification — Mixed solution classification: 2 · Custom solution: 1 · Microsoft platform solution: 1
Other observed drift surfaces 3
Use these cues to decide which neighbouring evidence may deserve external verification. They indicate adjacency only, not chronology, causality, remediation, or root-cause certainty.
-
Adjacent runtime driftPlugin Step Runtime Behaviour Drift Review enablement, execution stage, mode, order, and filtering-attribute drift that can change runtime behaviour.Investigation handoff Included in verification checklist ↓
-
Adjacent orchestration driftWorkflow / Automation Participation Drift Review activation, owner, real-time/background, and orchestration participation differences outside the plugin pipeline.Investigation handoff Included in verification checklist ↓
-
Additional bounded contextRelationship Metadata Drift Review this provider when its signals answer a distinct operational verification question.Investigation handoff Included in verification checklist ↓
DVQR Mock Operational Automation present only in SIT-MOCK Only observed in SIT-MOCK.
Targetdvqr_MockOperationalAutomation • v2.4.0.0 • Unmanaged
Show full evidence 2
-
Target solution — dvqr_MockOperationalAutomation • v2.4.0.0 • Unmanaged
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Target solution
- Observed value
- dvqr_MockOperationalAutomation • v2.4.0.0 • Unmanaged
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Solution classification — Custom solution
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Solution classification
- Observed value
- Custom solution
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet.
Power Pages Runtime Core changed from Managed → Unmanaged Participation details differ between DEV-MOCK and SIT-MOCK.
SourcePowerPages_RuntimeCore • v1.0.2509.1 • Managed
TargetPowerPages_RuntimeCore • v1.0.2509.1 • Unmanaged
Show full evidence 4
-
Source solution — PowerPages_RuntimeCore • v1.0.2509.1 • Managed
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Source solution
- Observed value
- PowerPages_RuntimeCore • v1.0.2509.1 • Managed
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Target solution — PowerPages_RuntimeCore • v1.0.2509.1 • Unmanaged
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Target solution
- Observed value
- PowerPages_RuntimeCore • v1.0.2509.1 • Unmanaged
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Solution classification — Microsoft platform solution → Microsoft platform solution
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Solution classification
- Observed value
- Microsoft platform solution → Microsoft platform solution
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Managed state drift — Managed → Unmanaged
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Managed state drift
- Observed value
- Managed → Unmanaged
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet.
Power Pages Runtime Core Dependencies version changed (1.0.2305.1 → 1.0.9999.1) Version differs between DEV-MOCK and SIT-MOCK.
SourcePowerPages_RuntimeCoreDependencies • v1.0.2305.1 • Managed
TargetPowerPages_RuntimeCoreDependencies • v1.0.9999.1 • Managed
Show full evidence 4
-
Source solution — PowerPages_RuntimeCoreDependencies • v1.0.2305.1 • Managed
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Source solution
- Observed value
- PowerPages_RuntimeCoreDependencies • v1.0.2305.1 • Managed
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Target solution — PowerPages_RuntimeCoreDependencies • v1.0.9999.1 • Managed
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Target solution
- Observed value
- PowerPages_RuntimeCoreDependencies • v1.0.9999.1 • Managed
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Solution classification — Microsoft platform solution → Microsoft platform solution
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Solution classification
- Observed value
- Microsoft platform solution → Microsoft platform solution
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Version drift — 1.0.2305.1 → 1.0.9999.1
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Version drift
- Observed value
- 1.0.2305.1 → 1.0.9999.1
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet.
Microsoft platform solution (1)
1 Microsoft/platform solution drift signal observed. These are grouped as low-priority platform-layering context; expand only if platform package alignment is relevant.
Grouped classification1 of 4 solution drift signals
Classification rationaleGrouped because the observed solutions match Microsoft/platform package naming or baseline platform-layer evidence.
Direction summary1 source-only
Operational priorityLow operational priority by default; review when platform package alignment is part of the investigation.
Evidence continuityRepresentative signals are listed below; full per-signal evidence remains available in JSON/HTML export.
-
Default Solution present only in DEV-MOCK
Inline evidence context This grouped solution signal preserves representative evidence from a dense solution section. Use it to verify the signal before continuing investigation outside DVQR.
- Evidence label
- Default Solution present only in DEV-MOCK
- Observed value
- Source solution: Default • v1.0 • Unmanaged · Solution classification: Microsoft platform solution
- Operational boundary
- Grouped solution evidence opens captured comparison context. In the VS Code webview, DVQR can request a bounded live solution evidence pivot.
- Live evidence pivot
- Not queried yet.
Workflow / Automation Participation Drift
Workflow and automation participation differs between snapshots.
Workflow and flow participation differs between DEV-MOCK and SIT-MOCK. Review added, removed, or changed orchestration before comparing environment behaviour.
- Account Sync Realtime state changed (Deactivated → Activated)
- Account Enrichment Background added in SIT-MOCK
- Legacy Account Workflow removed in SIT-MOCK
Other observed drift surfaces 3
Use these cues to decide which neighbouring evidence may deserve external verification. They indicate adjacency only, not chronology, causality, remediation, or root-cause certainty.
-
Adjacent runtime driftPlugin Step Runtime Behaviour Drift Review enablement, execution stage, mode, order, and filtering-attribute drift that can change runtime behaviour.Investigation handoff Included in verification checklist ↓
-
Package participation contextSolution Participation Drift Review managed state, version, and package presence differences that may explain component-layering changes.Investigation handoff Included in verification checklist ↓
-
Operational density contextOperational Profile Drift Review density changes to understand which operational dimensions became more or less complex.Investigation handoff Included in verification checklist ↓
Account Sync Realtime state changed (Deactivated → Activated) Observed state and owner metadata differ across snapshots. Use this as orchestration orientation, not as execution causality.
SourceAccount Sync Realtime • workflow • realtime • Deactivated • Managed • Owner: Legacy
TargetAccount Sync Realtime • workflow • realtime • Activated • Managed • Owner: System
Show full evidence 4
-
Source automation — Account Sync Realtime • workflow • realtime • Deactivated • Managed • Owner: Legacy
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Source automation
- Observed value
- Account Sync Realtime • workflow • realtime • Deactivated • Managed • Owner: Legacy
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Target automation — Account Sync Realtime • workflow • realtime • Activated • Managed • Owner: System
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Target automation
- Observed value
- Account Sync Realtime • workflow • realtime • Activated • Managed • Owner: System
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
State drift — Deactivated → Activated
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- State drift
- Observed value
- Deactivated → Activated
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Owner drift — Legacy → System
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Owner drift
- Observed value
- Legacy → System
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet.
Account Enrichment Background added in SIT-MOCK Only observed in SIT-MOCK.
TargetAccount Enrichment Background • workflow • background • Activated • Unmanaged • Owner: Integration
Show full evidence 1
-
Target automation — Account Enrichment Background • workflow • background • Activated • Unmanaged • Owner: Integration
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Target automation
- Observed value
- Account Enrichment Background • workflow • background • Activated • Unmanaged • Owner: Integration
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet.
Legacy Account Workflow removed in SIT-MOCK Only observed in DEV-MOCK.
SourceLegacy Account Workflow • workflow • background • Activated • Unmanaged • Owner: Legacy
Show full evidence 1
-
Source automation — Legacy Account Workflow • workflow • background • Activated • Unmanaged • Owner: Legacy
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Source automation
- Observed value
- Legacy Account Workflow • workflow • background • Activated • Unmanaged • Owner: Legacy
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet.
Minor workflow metadata signals (3)
3 lower-priority workflow metadata signals observed. These are grouped so activation, presence, and orchestration participation remain easier to scan.
Grouped classification3 of 6 workflow / automation drift signals
Classification rationaleGrouped because these are lower-priority workflow metadata changes rather than activation or presence drift.
Direction summaryConfiguration Drift: 3
Operational priorityLower-priority provider detail by default; review when these details are part of the investigation path.
Evidence continuityRepresentative signals are listed below; full per-signal evidence remains available in JSON/HTML export.
-
Account Address Normalisation owner changed (Operations → Integration)
Inline evidence context This grouped signal preserves representative evidence from a dense provider section. Use it to verify the signal before continuing investigation outside DVQR.
- Evidence label
- Account Address Normalisation owner changed (Operations → Integration)
- Observed value
- Source automation: Account Address Normalisation • workflow • background • Activated • Unmanaged • Owner: Operations · Target automation: Account Address Normalisation • workflow • background • Activated • Unmanaged • Owner: Integration · Owner drift: Operations → Integration
- Operational boundary
- Grouped evidence opens captured comparison context. In the VS Code webview, DVQR can request a bounded live evidence pivot for supported evidence types.
- Live evidence pivot
- Not queried yet.
-
Account Consent Reminder owner changed (Operations → Integration)
Inline evidence context This grouped signal preserves representative evidence from a dense provider section. Use it to verify the signal before continuing investigation outside DVQR.
- Evidence label
- Account Consent Reminder owner changed (Operations → Integration)
- Observed value
- Source automation: Account Consent Reminder • flow • cloudFlow • Activated • Unmanaged • Owner: Operations · Target automation: Account Consent Reminder • flow • cloudFlow • Activated • Unmanaged • Owner: Integration · Owner drift: Operations → Integration
- Operational boundary
- Grouped evidence opens captured comparison context. In the VS Code webview, DVQR can request a bounded live evidence pivot for supported evidence types.
- Live evidence pivot
- Not queried yet.
-
Account Notify Flow owner changed (Operations → Integration)
Inline evidence context This grouped signal preserves representative evidence from a dense provider section. Use it to verify the signal before continuing investigation outside DVQR.
- Evidence label
- Account Notify Flow owner changed (Operations → Integration)
- Observed value
- Source automation: Account Notify Flow • flow • cloudFlow • Activated • Unmanaged • Owner: Operations · Target automation: Account Notify Flow • flow • cloudFlow • Activated • Unmanaged • Owner: Integration · Owner drift: Operations → Integration
- Operational boundary
- Grouped evidence opens captured comparison context. In the VS Code webview, DVQR can request a bounded live evidence pivot for supported evidence types.
- Live evidence pivot
- Not queried yet.
Column Metadata Drift
Observed column metadata drift for Account. These are schema evidence changes for external verification, not deployment validation or remediation advice.
Column Metadata Drift contains 1 drift signal.
- Category (accountcategorycode) Is Audit Enabled changed
Other observed drift surfaces 3
Use these cues to decide which neighbouring evidence may deserve external verification. They indicate adjacency only, not chronology, causality, remediation, or root-cause certainty.
-
Additional bounded contextEntity Configuration Drift Review this provider when its signals answer a distinct operational verification question.Investigation handoff Included in verification checklist ↓
-
Adjacent runtime driftPlugin Step Runtime Behaviour Drift Review enablement, execution stage, mode, order, and filtering-attribute drift that can change runtime behaviour.Investigation handoff Included in verification checklist ↓
-
Additional bounded contextRelationship Metadata Drift Review this provider when its signals answer a distinct operational verification question.Investigation handoff Included in verification checklist ↓
Category (accountcategorycode) Is Audit Enabled changed 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.
Sourcefalse
Targettrue
Show full evidence 5
-
Column logical name — accountcategorycode
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Column logical name
- Observed value
- accountcategorycode
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Column schema name — AccountCategoryCode
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Column schema name
- Observed value
- AccountCategoryCode
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Column type — Picklist
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Column type
- Observed value
- Picklist
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Is Audit Enabled (source) — false
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Is Audit Enabled (source)
- Observed value
- false
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Is Audit Enabled (target) — true
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Is Audit Enabled (target)
- Observed value
- true
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet.
Environment Variable Current Value Drift
Observed Dataverse environment variable current-value drift across snapshots. DVQR reports runtime configuration evidence and can export supported non-secret current-value reconstruction intent for DVEVM; DVQR does not mutate Dataverse.
Environment Variable Current Value Drift contains 4 drift signals.
- API Endpoint current value changed
- DVFL JSON Settings current value changed
- DVFL Storage Container current value changed
Other observed drift surfaces 3
Use these cues to decide which neighbouring evidence may deserve external verification. They indicate adjacency only, not chronology, causality, remediation, or root-cause certainty.
-
Adjacent runtime driftPlugin Step Runtime Behaviour Drift Review enablement, execution stage, mode, order, and filtering-attribute drift that can change runtime behaviour.Investigation handoff Included in verification checklist ↓
-
Adjacent orchestration driftWorkflow / Automation Participation Drift Review activation, owner, real-time/background, and orchestration participation differences outside the plugin pipeline.Investigation handoff Included in verification checklist ↓
-
Package participation contextSolution Participation Drift Review managed state, version, and package presence differences that may explain component-layering changes.Investigation handoff Included in verification checklist ↓
API Endpoint current value changed The environment variable current value differs across snapshots. DVQR can export source-side reconstruction intent for DVEVM when the variable is non-secret; DVEVM owns validation, preview and apply.
Sourcehttps://api.dev.mock
Targethttps://api.sit.mock
Show full evidence 3
-
Source current value — https://api.dev.mock
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Source current value
- Observed value
- https://api.dev.mock
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Target current value — https://api.sit.mock
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Target current value
- Observed value
- https://api.sit.mock
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Reconstruction strategy — SetCurrentValue
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Reconstruction strategy
- Observed value
- SetCurrentValue
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet.
DVFL JSON Settings current value changed The environment variable current value differs across snapshots. DVQR can export source-side reconstruction intent for DVEVM when the variable is non-secret; DVEVM owns validation, preview and apply.
Source{"logging":"debug","cache":true}
Target{"logging":"warn","cache":false}
Show full evidence 3
-
Source current value — {"logging":"debug","cache":true}
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Source current value
- Observed value
- {"logging":"debug","cache":true}
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Target current value — {"logging":"warn","cache":false}
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Target current value
- Observed value
- {"logging":"warn","cache":false}
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Reconstruction strategy — SetCurrentValue
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Reconstruction strategy
- Observed value
- SetCurrentValue
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet.
DVFL Storage Container current value changed The environment variable current value differs across snapshots. DVQR can export source-side reconstruction intent for DVEVM when the variable is non-secret; DVEVM owns validation, preview and apply.
Sourcepatient-images-dev
Targetnot set
Show full evidence 3
-
Source current value — patient-images-dev
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Source current value
- Observed value
- patient-images-dev
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Target current value — not set
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Target current value
- Observed value
- not set
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Reconstruction strategy — CreateCurrentValue
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Reconstruction strategy
- Observed value
- CreateCurrentValue
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet.
Enable Feature X current value changed The environment variable current value differs across snapshots. DVQR can export source-side reconstruction intent for DVEVM when the variable is non-secret; DVEVM owns validation, preview and apply.
Sourcenot set
Targetyes
Show full evidence 3
-
Source current value — not set
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Source current value
- Observed value
- not set
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Target current value — yes
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Target current value
- Observed value
- yes
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Reconstruction strategy — DeleteCurrentValue
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Reconstruction strategy
- Observed value
- DeleteCurrentValue
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet.
Identity Participation Drift
Observed identity participation differs or requires confidence-based matching across environments.
Identity participation differs between DEV-MOCK and SIT-MOCK. Matching is confidence-based and should be treated as participation orientation, not authority certainty.
- human.operator.dev@example.com present only in DEV-MOCK
- Likely corresponding identity: service_account_dev → service_account_sit changed
- service_perf_msi present only in SIT-MOCK
Density-first orientation keeps evidence visible while reducing scan noise.
- Identity drift by type — Additional identity drift signals: 2 · Application users: 1
Other observed drift surfaces 3
Use these cues to decide which neighbouring evidence may deserve external verification. They indicate adjacency only, not chronology, causality, remediation, or root-cause certainty.
-
Adjacent runtime driftPlugin Step Runtime Behaviour Drift Review enablement, execution stage, mode, order, and filtering-attribute drift that can change runtime behaviour.Investigation handoff Included in verification checklist ↓
-
Adjacent orchestration driftWorkflow / Automation Participation Drift Review activation, owner, real-time/background, and orchestration participation differences outside the plugin pipeline.Investigation handoff Included in verification checklist ↓
-
Operational density contextOperational Profile Drift Review density changes to understand which operational dimensions became more or less complex.Investigation handoff Included in verification checklist ↓
human.operator.dev@example.com present only in DEV-MOCK Only observed in DEV-MOCK.
Sourcehuman.operator.dev@example.com
Show full evidence 1
-
Only in source — human.operator.dev@example.com
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Only in source
- Observed value
- human.operator.dev@example.com
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet.
Likely corresponding identity: service_account_dev → service_account_sit changed Participation details differ between DEV-MOCK and SIT-MOCK.
Sourceservice_account_dev
Targetservice_account_sit
Show full evidence 5
-
Identity subject — Both identities are applicationUser.
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Identity subject
- Observed value
- Both identities are applicationUser.
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Normalized name — Name matches after conservative environment-token normalization: dev, sit.
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Normalized name
- Observed value
- Name matches after conservative environment-token normalization: dev, sit.
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Identity type — Both identities appear automation-oriented/application-user-like.
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Identity type
- Observed value
- Both identities appear automation-oriented/application-user-like.
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Role participation — Observed role participation overlaps: Integration Role, Read Account.
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Role participation
- Observed value
- Observed role participation overlaps: Integration Role, Read Account.
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet. -
Team participation — Observed team participation overlaps: Integration Team.
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Team participation
- Observed value
- Observed team participation overlaps: Integration Team.
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet.
service_perf_msi present only in SIT-MOCK Only observed in SIT-MOCK.
Targetservice_perf_msi
Show full evidence 1
-
Only in target — service_perf_msi
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Only in target
- Observed value
- service_perf_msi
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Audit evidence enriches this finding; it does not establish root cause.Not queried yet.
Choice Metadata Drift
Observed choice / option set metadata drift for Account. These are schema evidence changes for external verification, not deployment validation or remediation advice.
Choice Metadata Drift contains 1 drift signal.
- Customer Size option added: Enterprise (1000000)
Other observed drift surfaces 3
Use these cues to decide which neighbouring evidence may deserve external verification. They indicate adjacency only, not chronology, causality, remediation, or root-cause certainty.
-
Additional bounded contextColumn Metadata Drift Review this provider when its signals answer a distinct operational verification question.Investigation handoff Included in verification checklist ↓
-
Additional bounded contextRelationship Metadata Drift Review this provider when its signals answer a distinct operational verification question.Investigation handoff Included in verification checklist ↓
-
Adjacent runtime driftPlugin Step Runtime Behaviour Drift Review enablement, execution stage, mode, order, and filtering-attribute drift that can change runtime behaviour.Investigation handoff Included in verification checklist ↓
Customer Size option added: Enterprise (1000000) Observed choice option metadata appears only in the target snapshot. Verify externally before treating this as a deployment or schema outcome.
Targetvalue: 1000000 · label: Enterprise
Show full evidence 6
-
Column logical name — customersizecode
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Column logical name
- Observed value
- customersizecode
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Column schema name — CustomerSizeCode
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Column schema name
- Observed value
- CustomerSizeCode
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Choice set name — account_customersizecode
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Choice set name
- Observed value
- account_customersizecode
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Global choice — false
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Global choice
- Observed value
- false
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Option value — 1000000
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Option value
- Observed value
- 1000000
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet. -
Target option — value: 1000000 · label: Enterprise
Inline evidence context This opens the rendered evidence payload already captured in this comparison. Use it to verify the drift signal before continuing investigation outside DVQR.
- Evidence label
- Target option
- Observed value
- value: 1000000 · label: Enterprise
- Operational boundary
- Captured evidence opens in exported HTML. In the VS Code webview, DVQR can continue into bounded live investigation pivots without losing comparison context.
- Live evidence pivot
- Not queried yet.
Audit evidence Audit lookup is explicit and interval-bounded. Metadata-only changes may not have Dataverse audit rows; captured snapshot metadata remains the evidence source.Not queried yet.
Operational Handoff Readiness
Review-ready summary for transferring this investigation to another human or team. This is not remediation authority or RCA certainty.
Handoff posture
Ready for external operational verification
DVQR has narrowed the operational problem space and identified unresolved validation prompts. Human reviewers should confirm expectations in Dataverse, Power Platform admin surfaces, ALM pipelines, or owner/team channels before corrective action is considered.
0 externally verified / resolved
0 need follow-up
0 reviewer notes
Include in handoff
- Observed operational storyline
- Outstanding high-significance signals
- Verification checklist and reviewed-state summary
- Snapshot trust and comparison context
Do not imply
- Root cause certainty
- Remediation instruction
- Blame or ownership assignment
- Effective-access or runtime causality certainty
Operational Verification Checklist
Consolidated review prompts from all rendered operational drift surfaces. Use this checklist to decide what needs human validation outside DVQR before treating environments as operationally equivalent.
External verification recommended
DVQR observes drift and supports verification. Humans retain operational authority and decide any corrective action.
Runtime behaviour verification
Use these evidence-backed prompts for external validation. They are not root-cause findings, blame statements, or corrective instructions.
-
Verify: Account Create Validation plugin state changed (Enabled → Disabled) High · State Drift · from Plugin Step Runtime Behaviour Drift
-
Verify: Account SIT Enrichment Dispatch added in SIT-MOCK High · Added · from Plugin Step Runtime Behaviour Drift
-
Verify: Account SIT Enrichment Dispatch added in target High · Added · from Plugin Step Runtime Behaviour Drift
-
Verify: Account Update Integration Dispatch execution pipeline changed High · Configuration Drift · from Plugin Step Runtime Behaviour Drift
-
Verify: Legacy Account Background Sync removed in SIT-MOCK High · Removed · from Plugin Step Runtime Behaviour Drift
-
Verify: Account Address Normalisation changed Medium · Configuration Drift · from Plugin Step Runtime Behaviour Drift
-
Verify: Account Consent Reminder Dispatch changed Medium · Configuration Drift · from Plugin Step Runtime Behaviour Drift
Workflow / orchestration verification
Use these evidence-backed prompts for external validation. They are not root-cause findings, blame statements, or corrective instructions.
-
Verify: Account Sync Realtime state changed (Deactivated → Activated) High · State Drift · from Workflow / Automation Participation Drift
-
Verify: Account Enrichment Background added in SIT-MOCK Medium · OnlyInTarget · from Workflow / Automation Participation Drift
-
Verify: Legacy Account Workflow removed in SIT-MOCK Medium · OnlyInSource · from Workflow / Automation Participation Drift
-
Verify: Account Address Normalisation owner changed (Operations → Integration) Low · Configuration Drift · from Workflow / Automation Participation Drift
-
Verify: Account Consent Reminder owner changed (Operations → Integration) Low · Configuration Drift · from Workflow / Automation Participation Drift
-
Verify: Account Notify Flow owner changed (Operations → Integration) Low · Configuration Drift · from Workflow / Automation Participation Drift
Package / solution verification
Use these evidence-backed prompts for external validation. They are not root-cause findings, blame statements, or corrective instructions.
-
Verify: Power Pages Runtime Core changed from Managed → Unmanaged High · Changed · from Solution Participation Drift
-
Verify: DVQR Mock Operational Automation present only in SIT-MOCK Medium · OnlyInTarget · from Solution Participation Drift
-
Verify: DVQR Mock Operational Automation present only in target Medium · OnlyInTarget · from Solution Participation Drift
-
Verify: Default Solution present only in DEV-MOCK Low · OnlyInSource · from Solution Participation Drift
-
Verify: Default Solution present only in source Low · OnlyInSource · from Solution Participation Drift
-
Verify: Power Pages Runtime Core Dependencies version changed (1.0.2305.1 → 1.0.9999.1) Low · Changed · from Solution Participation Drift
Operational density verification
Use these evidence-backed prompts for external validation. They are not root-cause findings, blame statements, or corrective instructions.
-
Verify: DVQR Score changed: 42 → 67 High · DensityChanged · from Operational Profile Drift
-
Verify: DVQR Score density changed: 42 → 67 High · DensityChanged · from Operational Profile Drift
-
Verify: Automation (Plugin Steps) changed: Moderate → High Medium · DensityChanged · from Operational Profile Drift
-
Verify: Operational profile signal only in target: Real-time Workflows Medium · OnlyInTarget · from Operational Profile Drift
-
Verify: Operational profile signal only in target: Real-time Workflows present only in SIT-MOCK Medium · OnlyInTarget · from Operational Profile Drift
-
Verify: Plugin Steps count increased (Moderate → High) Medium · DensityChanged · from Operational Profile Drift
Identity participation verification
Use these evidence-backed prompts for external validation. They are not root-cause findings, blame statements, or corrective instructions.
-
Verify: human.operator.dev@example.com present only in DEV-MOCK Medium · OnlyInSource · from Identity Participation Drift
-
Verify: Likely corresponding identity: service_account_dev → service_account_sit changed Medium · Changed · from Identity Participation Drift
-
Verify: service_perf_msi present only in SIT-MOCK Medium · OnlyInTarget · from Identity Participation Drift
Operational verification
Use these evidence-backed prompts for external validation. They are not root-cause findings, blame statements, or corrective instructions.
-
Verify: Account Change Tracking Enabled changed: false → true High · Configuration Drift · from Entity Configuration Drift
-
Verify: Relationship removed: lk_accountbase_modifiedby (Account → SystemUser, ManyToOne) High · Removed · from Relationship Metadata Drift
-
Verify: Account Audit Enabled changed: false → true Medium · Configuration Drift · from Entity Configuration Drift
-
Verify: API Endpoint current value changed Medium · Configuration Drift · from Environment Variable Current Value Drift
-
Verify: Category (accountcategorycode) Is Audit Enabled changed Medium · Configuration Drift · from Column Metadata Drift
-
Verify: DVFL JSON Settings current value changed Medium · Configuration Drift · from Environment Variable Current Value Drift
-
Verify: DVFL Storage Container current value changed Medium · Configuration Drift · from Environment Variable Current Value Drift
-
Verify: Enable Feature X current value changed Medium · Configuration Drift · from Environment Variable Current Value Drift
-
Verify: Relationship added: new_account_customersegment (Account → New Customersegment, ManyToOne) Medium · Added · from Relationship Metadata Drift
-
Verify: Customer Size option added: Enterprise (1000000) Low · Added · from Choice Metadata Drift