WHAT CAUSES THIS?
Why it breaks in production
No stable contract around the legacy operation.
- Side effects are not idempotent.
- Read and write models disagree.
- UI automation is used where a controlled adapter could expose a safer boundary.
problem_kicker
Add AI around legacy systems without pretending the legacy system is stateless.
Legacy applications often encode critical business rules in database procedures, batch jobs, UI workflows and undocumented side effects. AI integration fails when those constraints are hidden behind a thin tool wrapper.
Legacy integrationExplicit contractsAdapter layerIncremental migrationVerifiable state
DEMAND LANGUAGE / REAL-WORLD PROBLEM
Does this sound familiar?
“It works in the demo — but will it work in daily operations?”
“How do we measure whether the problem is actually solved?”
architecture_for AI LEGACY SYSTEM INTEGRATION
engineering
We identify stable business capabilities and wrap them with narrow, observable contracts. AI stays outside the source-of-truth boundary; adapters own validation, idempotency and state verification.
authority
Separate read and write capabilities, constrain service identities and prevent model-generated input from bypassing domain validation.
critical
Measure adapter latency, legacy saturation, queue depth and batch interaction. Backpressure and bounded concurrency protect systems that were not designed for agent-scale request patterns.
vendor
legacy systems · APIs · adapters · AI agents · integration
failure_kicker
anti_title
- Let the model generate arbitrary SQL.
- Automate screens without detecting state drift.
- Replace the whole system before validating integration value.
- Assume retries are safe.
measure_kicker
verify_title
verify_intro
- Contract tests against representative legacy states.
- Idempotency and duplicate-delivery tests.
- Read-back verification after writes.
- Load tests that include legacy resource limits.
CTO / CIO FAQ
faq_title
Do we need to modernize first?
Not always. A controlled integration boundary can create value and evidence before a larger modernization decision.
Is RPA the same architecture?
No. RPA can be one adapter mechanism, but production integration still needs contracts, state verification, identity and recovery semantics.
Can an agent write directly to the database?
That is usually a high-risk shortcut because it bypasses application invariants and audit semantics. Prefer explicit domain operations.
connected