Values Drift

The values poster is still on the wall. The architecture principles deck still says immutable events. Leadership still cites document before apply. In practice, teams ship silent overrides, skip the commitment boundary under deadline pressure, and treat tier labels as marketing. Nobody held a meeting to abandon the values. Drift happened — one undocumented exception at a time — until what the organisation does and what it says it stands for are different systems.

In software systems

Drift appears when stated invariants exist only in Confluence while production runs on break-glass scripts, shared admin credentials, and “temporary” mutable tables that outlive every reorg. Event sourcing was adopted; then a critical path got a fast UPDATE because the incident was hot. The principle remains documented; the architecture no longer embodies it.

Model and policy versions drift from what was certified. A fraud engine trained under one threshold runs with another in production because ops tuned it for throughput. The record still references the approved policy id. Compliance theatre fills the gap: checkboxes prove the process existed; they do not prove the live system still honours the commitment.

Without append-only discipline and visible correction events, teams cannot tell when divergence began — only that audit and reality disagree today.

In human organisations

Values drift is the organisational form of incoherence over time. Onboarding teaches the official story; veterans teach the workaround. “We value transparency” coexists with decisions made in side channels. “We require human review” coexists with three-second approvals tracked as compliance.

Consensus culture accelerates drift: comfort replaces named commitment, and the written values become aspirations no one will enforce against a shipping calendar. Insincere commitment fills forms the culture does not believe. Neither is a single scandal — both are slow betrayal of Coherence.

In socio-technical systems

Regulated domains compound the failure. A bank publishes AI ethics principles while loan models auto-approve without override monitoring. A health system commits to shared records while each clinic maintains shadow spreadsheets for “real” patient status. External auditors see policies; front-line staff see incentives. The gap widens each quarter because nothing in the stack forces reconciliation between stated values and operational truth.

This is a primary reason to build judgment infrastructure: not only to decide well once, but to keep coherence over time — so values, principles, and mechanisms stay aligned because commitments are recorded, consumed uniformly, and deviations are visible events rather than folklore.

Distinctions

Structural causes

Epistemic tier collapse

When inference, preference, and committed fact are stored and consumed alike, stated rigour drifts upward in rhetoric while actual binds stay weak. Values language attaches to L3 artifacts; the organisation believes it is “data-driven” while nothing crosses the commitment boundary honestly.

Diffuse write authority

Many writers, many override paths, no single reconcilable record — each team optimises locally until global principles are fiction. Architectural values (“single writer per invariant”) cannot survive if every service can mutate shared state.

Consensus culture

Norms that privilege comfort over accountable bind prevent values from costing anything at decision time. Drift is guaranteed: the document says one thing; the room does another; no L0 event records the gap.

Counter direction

• Document before apply — mechanisms adopted in writing before deployment; changes are new records, not tacit edits.
• Commitment at the boundary — values matter when they constrain bind, not when they decorate decks (commitment boundary).
• Deviation and correction events — exceptions visible and logged; drift cannot hide in “how we really work.”
• Periodic coherence audit — compare stated principles, architecture decision records, and event-log behaviour; treat unexplained gaps as values drift, not culture.