Refactor identifiers across constrained legacy programs

Why use this

1. A legacy identifier change can affect storage, validation, sorting and external interfaces in ways that are not obvious from a field name. An alphanumeric value may be preserved in one program and truncated or interpreted numerically in another.

2. A constraint-led impact packet could trace each supplied rule to affected field variants and interfaces. Domain experts could review unresolved assumptions before editing, rather than relying on a broad search-and-replace to preserve business behavior.

Why an agent / simpler alternative

Useful judgment

Relate expert-authored field variants to scattered program descriptions and identify inconsistent identifier assumptions.

Simpler alternative

Use a deterministic transformation only when the affected fields and semantics are exhaustively documented and uniform.

Unsuitable when

Business constraints are missing or the task would alter production financial processing without qualified review.

Proposed inputs

1. Name

   Identifier constraint sheet

   Owner

   Domain expert

   Minimum scope

   Fictional field variants, allowed representation and preservation rules

   Quality check

   Separate storage format from display and validation behavior.

2. Name

   Program impact sample

   Owner

   Legacy-system maintainer

   Minimum scope

   Selected field descriptions, copybook references and interface contracts

   Quality check

   Mark numeric operations and truncation-sensitive boundaries.

Access and setup — proposed or unknown

Proposed minimum

1. Offline fictional program descriptors and a proposed impact matrix.

Compatibility unknowns

1. Unknown: current runtime, language tooling, build environment and cross-system coverage.

External actions requiring approval

1. Source access, code changes, test-data use, interface changes and any production release.

Expected deliverable and review checks

Proposed artifact

Constraint-to-field impact matrix with unresolved transformations and domain-review questions.

Critical checks

1. Every proposed field change links to an explicit expert rule.

2. External interfaces and variant-specific behavior remain visible in the scope.

Missing output evidence

No new workflow run or output inspection was performed for this overlay; use the canonical source-outcome references.

Failure signals and proposed responses

1. Signal

   A field is widened locally while an output interface retains its old length.

   Why it matters

   Values could be truncated downstream.

   Proposed response

   Flag the contract mismatch and require a coordinated interface decision.

2. Signal

   A supposedly textual identifier participates in numeric comparison.

   Why it matters

   Changing representation may alter business branching.

   Proposed response

   Stop the mechanical transformation and request expert guidance on intended semantics.

Effort and cost — unknown

Setup work

1. Collect authoritative constraints and field lineage.

Ongoing review

1. Resolve semantic exceptions and inspect later regression evidence.

Unknowns

1. Unknown: affected-program coverage, test-data needs and migration cost.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

A fictional impact map includes an unchanged external field length and a numeric comparison on the identifier.

Acceptance checks

1. Identify both rule conflicts.

2. Keep transformations unresolved without altering or compiling code.

Stop conditions

1. Real business data, code execution, production changes or financial processing is required.

Limits

1. The proposed impact check provides no assurance that a legacy migration preserves business or regulatory behavior.