LEN-0230 - Normalization Lens

Primary Pattern Matches

• PAT-0370 - Redundant Declaration

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

Secondary Pattern Matches

• PAT-0250 - Circular Dependency

  A structural condition where two or more elements depend on each other in a closed loop without an independent base condition or declared resolution mechanism.

• PAT-0150 - Interface Mismatch

  A structural condition where observed interface behavior, shape, or exchange differs from the declared interface contract.

Related Issues

• Agent Cannot Choose Tool Without Tool Result

  The agent needs a tool result to choose the right tool, but cannot obtain that result without choosing a tool first.

• Agent Gets Conflicting Tool Authority

  An agent receives conflicting authority signals about whether, when, or how it may use a tool, connector, function, or integration.

• Agent Never Settles on Final Answer

  The agent keeps revising, rechecking, planning, or branching instead of converging on a final answer or completed result.

• AI Output Breaks Parser

  The AI output causes a parser, validator, importer, or structured-output consumer to fail.

• Approval Depends on Output That Needs Approval

  A required approval depends on an AI output or workflow result that itself cannot be produced or trusted until approval is granted.

• Citation Points to Wrong Source

  A citation, reference, link, or source pointer is present, but it points to the wrong source, wrong passage, wrong document, or unsupported evidence.

• 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.

• Fallback Authority Is Missing

  The system does not declare who or what has authority when the primary owner, rule, tool, source, or decision path is unavailable or inconclusive.

• Invalid JSON Output

  The AI returns malformed JSON or structured output that cannot be parsed.

• Model and Workflow Disagree on Next Step

  The AI model recommends or selects a next step that conflicts with the workflow state, required handoff, routing rule, or process sequence.

• Multiple Policies Say the Same Thing

  Multiple policies, rules, or guidance documents express the same requirement, creating redundancy and uncertainty about which one governs.

• Nested Fields Do Not Match

  The AI returns nested structured fields whose internal shape, hierarchy, parent-child relationship, or contained values do not match the expected structure.

• 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.

• Output Breaks the Next Step

  The AI output looks acceptable by itself but cannot be used by the next tool, workflow step, parser, reviewer, or downstream consumer.

• Policy Decision Depends on Itself

  A policy decision requires the outcome of the same policy decision before it can be made.

• Prompt Changed but Workflow Did Not

  A prompt changes but the workflow, parser, review step, routing rule, or downstream expectation still assumes the old prompt behavior.

• Repeated Constraints Create Confusion

  Repeated constraints, instructions, limits, or exclusions make the task harder to interpret instead of clearer.

• Review Escalates Without Stop Condition

  A review process keeps escalating, re-reviewing, or adding scrutiny without a declared condition for stopping.

• Routing Path Cycles Back to Start

  A routing path sends the case back to the starting point or an earlier step without resolving the condition that caused the route.

• Same Contract Name Has Different Meanings

  The same prompt, schema, field, policy, tool, or workflow contract name is used in different places with different meanings.

• 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.

• Schema Reference Loops Without Base Case

  A schema, field, type, object, or structured reference points through a loop without a base case that allows validation or interpretation to resolve.

• 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.

• Tool Call Contract Mismatch

  The AI or agent calls a tool with names, arguments, types, modes, or shapes that do not match the declared tool interface.

• Tool Can Act Without Responsible Authority

  A tool, connector, function, or integration can perform an action without a declared responsible authority for that action.

• Tool Exists but Required Inputs Are Missing

  A usable tool or integration exists, but the AI or agent does not have the required inputs, permissions, fields, identifiers, or context needed to call it correctly.

• Tool Result Not Integrated Correctly

  The AI receives a tool result but misreads, ignores, overwrites, misplaces, or fails to incorporate it correctly into the final output or workflow state.

• Tool Rules and Prompt Rules Conflict

  Tool, connector, function, or MCP rules conflict with prompt instructions, causing the AI or agent to face incompatible requirements.

• Workflow Loops Through Review Without Resolution

  A workflow repeatedly sends work through review, repair, or escalation without reaching an approved, rejected, or otherwise resolved state.

• Workflow Waits on Step That Waits Back

  A workflow step waits for another step that also waits on the first step, creating a blocking loop.

• Wrong Field Types

  The AI returns fields with values whose types do not match the expected schema, such as strings where numbers, booleans, arrays, objects, or enums are required.

Ontology Metadata

Code

LEN-0230

Version

[email protected]

Ontology release

0.1.0

Updated

2026-05-10T00:00:00Z

History

• 0.1.0 — 2026-05-10T00:00:00Z — Created

  Promoted reviewed Lens ontology entry: Normalization Lens.

  Receipt impact: None

View full ontology changelog