PAT-0370
Redundant Declaration
A structural condition where multiple declarations produce equivalent structural effect without semantic differentiation.
Primary Lenses
Normalization Lens
Transforms structurally equivalent variants into a canonical form to prevent false divergence.
Lens Application
The Normalization Lens is a primary inspection mechanism for Redundant Declarations because it examines whether multiple declarations collapse into the same canonical structure. When variants normalize to equivalent form without meaningful semantic distinction, the lens strongly supports inspection for redundant declaration behavior.
Inspect For
- Declarations that normalize to the same canonical structure
- Repeated structural effects with no semantic distinction
- Variant forms that create apparent but not meaningful divergence
- Canonicalization exposing duplicate declaration roles
Avoid
Treat normalized equivalence as an inspection signal, not as proof that the declaration is redundant in every semantic context.
Conflict Lens
Detects mutually incompatible constraints, claims, states, or declarations that cannot be simultaneously satisfied.
Lens Application
The Conflict Lens is a primary inspection mechanism for Redundant Declarations when repeated declarations appear structurally equivalent but introduce tension in constraint priority, interpretation, or operational effect. It helps identify whether redundancy masks incompatibility rather than harmless repetition.
Inspect For
- Equivalent declarations with different implied authority
- Repeated constraints that cannot both be applied cleanly
- Duplicate claims producing divergent downstream behavior
- Ambiguous priority between structurally similar declarations
Avoid
Treat repetition as an inspection signal only when the declarations create incompatible effects; repetition alone does not establish conflict or redundancy.
Secondary Lenses
Compression Lens
Reduces structural graphs into stable minimal representations for comparison, redundancy detection, and diffing.
Lens Application
As a secondary lens, the Compression Lens can support inspection of Redundant Declarations by collapsing declaration structures into stable minimal representations. This may help reveal where separate declarations normalize to similar graph effects, especially during comparison or diffing, while leaving semantic interpretation to other checks.
Inspect For
- Declarations that compress to matching structural forms
- Repeated graph effects across separate declaration sites
- Minimal representations with little or no differentiating structure
- Diff results that show structural sameness despite separate declarations
Avoid
Treat compressed similarity as a supporting inspection signal, not as confirmation that the declarations are redundant.
Primary Issue Matches
Duplicate Fields With Same Meaning
The AI returns multiple fields, labels, sections, or structured elements that carry the same meaning and create ambiguity about which one should be used.
Duplicate Output Sections
The AI repeats sections, headings, blocks, or output areas in a way that creates redundancy, confusion, or downstream handling problems.
Multiple Policies Say the Same Thing
Multiple policies, rules, or guidance documents express the same requirement, creating redundancy and uncertainty about which one governs.
Repeated Constraints Create Confusion
Repeated constraints, instructions, limits, or exclusions make the task harder to interpret instead of clearer.
Same Rule Declared in Multiple Places
The same rule, constraint, instruction, or policy appears in multiple places, creating redundancy and possible drift.
Same Workflow Check Happens Twice
The same review, validation, approval, routing, or safety check occurs more than once in the workflow without a clear reason.
Supporting Issue Matches
Old Output Expectations Survive Migration
Expectations from a prior model, prompt, schema, tool, or workflow survive a migration and continue shaping review or downstream handling after they should be replaced.
Single Field Carries Too Many Obligations
One field, label, score, status, or structured value is expected to carry too many meanings, decisions, or workflow obligations.