Issue
Small Change Produces Large Downstream Effects
A small prompt, schema, policy, output, or workflow change creates unexpectedly large effects in downstream steps.
What This Looks Like
A small change to a prompt, field, schema, policy, example, model setting, tool contract, or workflow step produces a much larger effect later in the system. The immediate change may look minor, but downstream outputs, routes, parsers, reviews, or decisions shift more than expected.
Why It Matters
Small changes become risky when their downstream effects are not visible. A user may approve a minor edit without realizing it changes later behavior, breaks compatibility, or alters review outcomes. This makes regression testing and change control harder.
Structural Signal
A local change propagates into downstream effects beyond its apparent size or declared scope. The issue is not that change occurred; it is that the change has an amplified effect through connected workflow structure.
Common Triggers
- A small prompt edit changes output structure used by later steps
- A field label changes while parsers still expect the old label
- A policy wording change affects routing or escalation
- Examples are updated and shift model behavior broadly
- A tool schema changes in a way that breaks dependent prompts
- The workflow lacks dependency mapping for small changes
When to Use This Issue
Use this Issue when a small change creates large downstream effects across AI output, workflow behavior, tooling, review, routing, or structured data.
When Not to Use This Issue
Do not use this Issue when a large downstream effect was expected and declared. Do not use it for ordinary local edits that remain contained.
Category
Primary Pattern
Declared Patterns
Propagation Amplification
A structural condition where an effect, declaration, authority, constraint, or state increases in scope or intensity as it propagates beyond declared bounds.
Contract Drift
A structural condition where a declared contract changes but connected structures, implementations, consumers, or expectations do not update in sync.
Compatibility Violation
A structural condition where a graph, object, behavior, or runtime state exceeds a declared compatibility envelope without an authorized exception.
Derived Primary Lenses
Compatibility Envelope Lens
Determines whether structure fits within declared runtime, platform, version, or support constraints.
Convergence Lens
Compares parallel structural systems to determine whether they align under shared authority.
Escalation Gradient Lens
Measures structural growth or intensification across sequential executions, states, or transitions.
Propagation Lens
Traces how structural declarations, effects, or state changes propagate across boundaries or stages.
Reconciliation Lens
Evaluates whether structural changes align with declared authority updates, version changes, or reconciliation rules.
Derived Secondary Lenses
Boundary Compliance Lens
Evaluates observed structure against declared boundary posture, including allow, block, and exception rules.
Determinism Lens
Evaluates whether identical structural inputs produce equivalent structural outputs across repeated executions.
Variance / Entropy Lens
Measures structural variability across repeated or comparable evaluations and identifies divergence beyond expected bounds.
Related AI-Adjacent Issues
Too Many Workflows Depend on One Tool
Many workflows, agents, checks, or downstream paths depend on one tool, connector, API, or integration, creating a shared point of failure.
Tool Call Caused Hidden Downstream Change
A tool call causes a downstream state, workflow, metadata, record, or integration change that is not visible at the point of action.
Search Intents
- small change produces large downstream effects
- small AI change caused big workflow impact
- prompt change had large downstream effect
- minor schema change broke workflow
- small update caused major AI behavior change
- downstream effects from small change