Artifacts: Pages That Refresh Themselves
Artifacts: Pages That Refresh Themselves
When Artifacts Are Wrong: The Probe-First Habit
Artifacts that call connectors break when the underlying API shape drifts.
Three weeks ago you built a live pipeline page. It laid out every open deal from your CRM by stage and value, and refreshed itself every time you opened it. It worked beautifully, so you stopped checking it.
This morning you open it before a forecast call. The "stage" column is blank for half the rows, and the total is twenty percent low. Nothing changed in the page. You didn't touch the prompt.
Your first instinct is that Cowork broke.
It didn't. Someone on your ops team renamed a field in the CRM last week ("Stage" became "Deal Stage") and the page is still asking for the old name, getting nothing, and quietly showing a hole where data used to be.
The page didn't fail. The assumption it was built on did. The fix isn't a cleverer prompt; it's a small habit you do before you build.