# Detect configuration drift instead of assuming sameness

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Detect configuration drift instead of assuming sameness

ID: MHC-D-RESEARCH-0355 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/detect-configuration-drift-instead-of-assuming-sameness

'Same deployment' does not guarantee the same state.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- Multiple instances, environments or agents are supposed to run the same configuration.

### Avoid when

- Not all divergence is drift; legitimate canaries and experiments need explicit identities so monitoring does not 'repair' them away.

### Explanation

Regularly compare the effective configuration of peers that are expected to match. Flag differences against the approved version and classify them as planned experiment, staged rollout or unintended drift. Correlate behavior anomalies with version differences before treating them as random noise.

### Steps

1. Define which instances or environments are expected to match.
2. Collect the effective configuration version or fingerprint.
3. Compare against the approved target and rollout plan.
4. Classify differences as intentional or unintended.
5. Remediate unintended drift and preserve evidence of the divergence.

### Example

If one agent instance produces different tool behavior, check whether its policy or model configuration differs before debugging the prompt text alone.

### Check

Unexpected behavior can be tested against an objective configuration difference rather than relying on deployment assumptions.

### Limits

- Not all divergence is drift; legitimate canaries and experiments need explicit identities so monitoring does not 'repair' them away.

### Evidence and sources

- supports: Current AWS Agentic AI guidance recommends detecting configuration drift across running instances and correlating behavior with configuration versions. — RS-2DF67D7590E081DA. Not every difference is harmful drift; approved experiments and staged rollouts must remain distinguishable from unintended divergence. (Drift detection)
- RS-2DF67D7590E081DA: AGENTREL08-BP01 Establish consistent configuration management practices — https://docs.aws.amazon.com/wellarchitected/latest/agentic-ai-lens/agentrel08-bp01.html

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/start-with-what-changed-not-with-certainty-about-it
