PENGO Workbench
Workbench / Issues / Policy Update Not Reflected in Output

Issue

Policy Update Not Reflected in Output

A policy, rule, standard, or instruction has been updated, but the AI output still follows the older version.

What This Looks Like

A policy, rule, standard, guideline, rubric, or instruction has been updated, but the AI output still reflects the older version. The user may see outdated language, old thresholds, prior approval rules, obsolete categories, or earlier workflow requirements appear after the update should have taken effect.

Why It Matters

Policy updates are only useful if they change the outputs they are supposed to govern. When AI output continues to follow an older policy, users may believe the current policy is being applied when it is not. This creates audit, compliance, and operational risk, especially when the old and new policies lead to different decisions.

Structural Signal

The declared governing rule has changed, but the generated output is still governed by a prior rule state. The issue is not just that the answer is outdated; it is that policy version and output behavior are no longer aligned.

Common Triggers

  • The model or workflow still has old policy text in context
  • Documentation updates before prompts, tools, or retrieval sources are updated
  • The AI retrieves an older policy version
  • Cached examples preserve obsolete policy behavior
  • The workflow does not declare which policy version is authoritative
  • Updated policy is available but not connected to the current task

When to Use This Issue

Use this Issue when a policy or rule has changed and the AI output still follows the older policy state.

When Not to Use This Issue

Do not use this Issue when the policy is merely unclear or when the AI violates a policy that has not changed. Use this Issue when the update itself is central: the output fails to reflect the new governing rule.

Category

Rules & Policies

Primary Pattern

PAT-0190 — Contract Drift

Declared Patterns

PAT-0190

Contract Drift

A structural condition where a declared contract changes but connected structures, implementations, consumers, or expectations do not update in sync.

PAT-0200

Reference Instability

A structural condition where references, identifiers, links, or anchors change across equivalent evaluations without a declared cause.

PAT-0350

Persistence Instability

A structural condition where persisted state cannot be stored and restored into an equivalent structure without alteration.

Derived Primary Lenses

LEN-0170

Convergence Lens

Compares parallel structural systems to determine whether they align under shared authority.

LEN-0270

Reconciliation Lens

Evaluates whether structural changes align with declared authority updates, version changes, or reconciliation rules.

LEN-0280

Reference Stability Lens

Evaluates whether structural references, identifiers, nodes, and edges remain consistent across execution cycles or comparable states.

Derived Secondary Lenses

LEN-0180

Determinism Lens

Evaluates whether identical structural inputs produce equivalent structural outputs across repeated executions.

Related AI-Adjacent Issues

ADJ-0010

Permission Change Not Applied

A permission, approval, role, policy, or access change is made but the AI, agent, tool, or workflow continues behaving as if the old permission state still applies.

Search Intents

  • policy update not reflected in output
  • AI used old policy
  • policy changed but AI output did not
  • updated rule not applied
  • AI follows outdated policy
  • new policy not reflected in response