Why v2 Exists

MapPrism v1 grew around direct n8n webhooks. Each new pipeline meant another workflow, another webhook endpoint, and another place where logic lived. It worked, but it didn't scale well. Pipelines were hard to evolve, observability was limited, and small changes often meant duplicating entire flows.

MapPrism v2 introduces Ordo as a thin orchestration layer between the frontend and n8n. The goal isn't to change how the product feels — it's to make the backend easier to reason about and evolve.

With Ordo:

• Pipelines are defined as composable steps instead of one-off workflows
• Job state is centralized and queryable
• Progress reporting becomes deterministic
• n8n stays focused on execution, not coordination

From the frontend's perspective, almost nothing changes. You still upload to MinIO, trigger processing, and poll for progress. The difference is that the system behind it is now structured enough to support more complex processing without accumulating operational debt.

For the full migration guide including API changes and v1→v2 recipe mapping, see 08-migration/v1-to-v2.md.