- 0:00–0:06
Build beside the core • Legacy core unchanged • Adapter beside it • Support screen • Legacy core • Adapter service
The Support screen badge stays fixed at the top. The heavy Legacy core block stands unchanged; the Adapter service case slides in beside it and one narrow cyan line joins the core to the adapter; then a second line runs from the adapter to a plain unlabelled sphere that stands for the model. Nothing connects the sphere to the core.
- 0:06–0:12
One task, one checked call • Only the ticket ID • Screen as before on failure • Support screen • Ticket ID • Adapter service • Checked summary • Typed failure
The task-shaped call figure enters: a Ticket ID token, the Adapter service case and two possible exits, Checked summary and Typed failure. A cyan trace runs from the ticket into the adapter, lights its three blank steps in order and stops at the fork; neither dashed exit lights.
- 0:12–0:18
Act as the signed-in user • Identity from the server • No shared admin account • Support screen • Legacy core • Adapter service
The Legacy core and the Adapter service case stand apart. Three data calls leave the adapter for the core one after another, each carrying a small blank identity tag. A separate blank card standing for a shared admin account fades; no line ever reaches it.
- 0:18–0:24
Give only small typed tools • Read-only by default • Mapped to business APIs • Support screen • Legacy core • Adapter service
Three small blank tool tiles leave the Adapter service case one after another and snap into three existing API sockets beside the Legacy core. A wide generic tile is set aside and fades; it never connects.
- 0:24–0:30
Writes wait for confirmation • Rules validate first • Nothing saved yet • Support screen • Refund draft • Legacy rules • Support agent confirms • Existing API
The refund write-path figure enters: Refund draft, Legacy rules, Support agent confirms and Existing API. A cyan highlight lifts the blank sheet from the Refund draft station, carries it to Legacy rules and stops there; the routes on to Support agent confirms and Existing API stay dashed, so nothing is saved.
An illustrative support screen keeps working while an adapter, the signed-in user’s identity, typed tools and a confirmed write path are added beside it; nothing is saved.
Read the article: How to Add an LLM to a Legacy Application: A Reference Architecture