Issue
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.
What This Looks Like
A single field, status, label, score, category, or structured value is used to represent too many things at once. It may carry display meaning, workflow routing, approval state, risk severity, parser behavior, and review outcome together, making it hard to know what the field actually governs.
Why It Matters
Overloaded fields create fragile workflows. A small change to the field value can affect multiple downstream obligations at once. Users and systems may treat the same value differently because it is being used for too many purposes.
Structural Signal
Too much meaning is concentrated in one structural field. The issue is not simply that the field is important; it is that the field carries multiple obligations that should be separated or more explicitly governed.
Common Triggers
- One status field controls both display and workflow routing
- A score is used for risk, confidence, review, and escalation
- A category label also acts as an approval signal
- Schema design collapses several meanings into one value
- Prompts ask the AI to encode multiple decisions into one field
- Downstream systems reuse a field for purposes it was not designed to support
When to Use This Issue
Use this Issue when one field or structured value carries too many meanings, decisions, or workflow obligations for reliable use.
When Not to Use This Issue
Do not use this Issue when a field has one clear purpose and is merely important. Do not use it when the problem is a wrong field type or missing required field.
Category
Primary Pattern
Declared Patterns
Density Spike
A structural condition where nodes, edges, dependencies, decisions, or effects concentrate sharply within a localized region beyond declared thresholds.
Redundant Declaration
A structural condition where multiple declarations produce equivalent structural effect without semantic differentiation.
Schema Breakage
A structural condition where an instance, graph, payload, or object violates the type, shape, or rule requirements of a declared schema.
Derived Primary Lenses
Compression Lens
Reduces structural graphs into stable minimal representations for comparison, redundancy detection, and diffing.
Conflict Lens
Detects mutually incompatible constraints, claims, states, or declarations that cannot be simultaneously satisfied.
Interface Contract Lens
Compares declared interface structure to observed runtime structure to detect contract deviations.
Invariant Lens
Verifies that declared invariants are structurally enforceable and not contradicted by observed structure.
Normalization Lens
Transforms structurally equivalent variants into a canonical form to prevent false divergence.
Variance / Entropy Lens
Measures structural variability across repeated or comparable evaluations and identifies divergence beyond expected bounds.
Derived Secondary Lenses
Search Intents
- single field carries too many obligations
- AI field overloaded
- one field has too many meanings
- structured output field carries too much
- status field overloaded
- AI output field used for too many decisions