Nine objects to know
Enterprise, Workspace, Decision Policy, Decision Twin, SAGE, Canvas, Animations, Order Line, Supply Event.
The object model is nine items. Most planning systems have hundreds; the conceptual ones are the only ones you need to learn to understand how VYAN is shaped.
Enterprise is the tenant boundary — one per customer company. MIC has one. Inside it, Workspaces are the data-isolation boundary — typically one per product family or geography. Each Workspace holds its own Decision Policy, runs its own Decision Twin, has its own SAGE state, and presents its own Canvas surfaces. A customer with three business units typically runs three Workspaces under one Enterprise.
Inside each Workspace, three configuration-and-compute objects. Decision Policy is the versioned behavioral configuration (what risk posture, what objective weights, what constraints, what autonomy thresholds, which solver). Decision Twin is the compute engine that produces decisions under the policy. SAGE is the conversational layer over both. The eight Canvas surfaces (Driver Seat, Decisions, Policy, Frontier, Scenarios, Audit, Risk Events, Platform Admin) are how humans interact with the system. The ninth object is the suite of Animations that make the underlying stochastic compute legible — the Frontier Construction Theater, the Stochastic Run Theater, the Time Travel Studio, the Event Stream Canvas. Chapter 6 walks them.
Two atomic data objects sit at the bottom of the hierarchy. Order Line is the demand atom — every customer order line carries its full attributes (quantity, requested date, customer, SLA terms, price, accepted substitutions, channel, source-location constraints, temporal flexibility, cost-to-serve attributes). Supply Event is the supply atom — every PO, every production order, every STO, with its own pegging chain and its realized cost accumulator. VYAN plans at this grain, not at aggregated buckets (chapter 2.3).
This hierarchy is what gives VYAN its multi-tenancy and its configurability. Customers with multiple business units run multiple Workspaces inside one Enterprise; each can have its own policy and its own twin; SAGE federates across them when a user has cross-Workspace authority.