PENGO Workbench
Workbench / Issues / Same Rule Declared in Multiple Places

Issue

Same Rule Declared in Multiple Places

The same rule, constraint, instruction, or policy appears in multiple places, creating redundancy and possible drift.

What This Looks Like

The same rule, policy, instruction, constraint, or requirement appears in more than one place. It may be repeated in a prompt, schema, policy file, workflow step, tool instruction, rubric, or documentation. The repeated versions may match at first, but over time they can drift.

Why It Matters

Rules declared in multiple places are harder to maintain. Users and systems may not know which copy is authoritative, and updates can change one copy while leaving another behind. This creates ambiguity, stale instructions, and hidden conflicts.

Structural Signal

A single governing rule is represented by multiple declarations instead of one stable authority. The issue is not that the rule is wrong; it is that redundant declarations create overload and drift risk.

Common Triggers

  • A rule is copied into prompts, docs, schemas, and workflow instructions
  • The system lacks a canonical rule location
  • Old versions remain after migration or refactoring
  • Examples repeat requirements as if they were separate rules
  • Tool instructions and policy instructions restate the same constraint
  • Updates are applied to one copy but not the others

When to Use This Issue

Use this Issue when the same rule is declared in multiple places and that duplication creates ambiguity, maintenance risk, or conflicting behavior.

When Not to Use This Issue

Do not use this Issue when related rules are distinct and intentionally layered. Do not use it for ordinary emphasis unless duplicated rule declarations affect governance or output behavior.

Category

Duplication & Overload

Primary Pattern

PAT-0370 — Redundant Declaration

Declared Patterns

PAT-0370

Redundant Declaration

A structural condition where multiple declarations produce equivalent structural effect without semantic differentiation.

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-0270

Density Spike

A structural condition where nodes, edges, dependencies, decisions, or effects concentrate sharply within a localized region beyond declared thresholds.

Derived Primary Lenses

LEN-0140

Compression Lens

Reduces structural graphs into stable minimal representations for comparison, redundancy detection, and diffing.

LEN-0150

Conflict Lens

Detects mutually incompatible constraints, claims, states, or declarations that cannot be simultaneously satisfied.

LEN-0170

Convergence Lens

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

LEN-0230

Normalization Lens

Transforms structurally equivalent variants into a canonical form to prevent false divergence.

LEN-0270

Reconciliation Lens

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

LEN-0290

Variance / Entropy Lens

Measures structural variability across repeated or comparable evaluations and identifies divergence beyond expected bounds.

Derived Secondary Lenses

LEN-0180

Determinism Lens

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

LEN-0190

Escalation Gradient Lens

Measures structural growth or intensification across sequential executions, states, or transitions.

Search Intents

  • same rule declared in multiple places
  • duplicate AI rules
  • same instruction appears twice
  • policy duplicated in multiple places
  • repeated rule creates confusion
  • same constraint declared more than once