Seven specific reasons decision quality is failing
Each one named, each one mapped to an architectural answer.
Decision quality fails for seven specific reasons. Each compounds the next. A single-future plan becomes more dangerous when its parameters are stale. Both become more expensive when there's no margin awareness at the order line. The cumulative cost is impossible to govern without an explicit risk posture. When risk is modeled, it's modeled as binary. The optimization targets the plan, not the policy that produces it. And the plan is committed without ever being stress-tested. Each of those failure modes maps to a specific architectural answer VYAN provides.
Throughout this book we ground the diagnosis with Meridian Industrial Components — MIC — a $1.2B industrial manufacturer with three product families, roughly 3,000 active SKUs, two production plants, four distribution centers, and a supplier network of about 140 active vendors. MIC is fictional but representative. Every named scenario uses MIC's customers (Customer-Alpha, Customer-Bravo), its SKUs (SKU-A-2891), its supplier (Taiwan FPGA), and realistic industrial-scale numbers. The MIC scenarios are illustrations — we don't have public customer references yet, and we won't pretend we do.
Each of the next seven nodes walks one failure end-to-end: the named scene at MIC, why the current architecture produces it, and VYAN's answer at a conceptual level. Forward references point at the architecture chapters where each answer becomes concrete.