One production change. Watch the system walk the graph.
Pick a scenario and watch Olivine trace the ripple in plain English. The animation is the point: you see the system traverse connected records, discover blockers, surface operational gaps, and summarize exactly what broke and why.
Scenarios
Choose a guided cascade story.
Watch the edges draw left-to-right as the scan walks each record.
OOH billboard spec added to the delivery package.
Talent buyout does not cover OOH usage.
No OOH deliverable asset exists yet.
No bid line item covers OOH production.
What surfaced
Plain-English outcomes
The labels are the story. Nothing here is a raw ontology identifier or SHACL message. Each line is the thing a producer now needs to know.
Red
Blockers
Emma Yates' deal covers Broadcast, Cable, OLV, and Social. Not OOH. The $73K buyout needs renegotiation before this asset can use her likeness.
Orange
Warnings
No warning-only findings surfaced in this scenario.
Blue
Downstream effects
Editorial needs a new cut, a new QC pass, and a new master before the package can ship.
There is no budget line, PO, or allocation for OOH production, so the added scope is currently unplanned cost.
System walk
How the scan traversed the project
Each path below is the chain the animation just walked: source change, intermediate records, then the discovered outcome.
Emma Yates' deal covers Broadcast, Cable, OLV, and Social. Not OOH. The $73K buyout needs renegotiation before this asset can use her likeness.
Editorial needs a new cut, a new QC pass, and a new master before the package can ship.
There is no budget line, PO, or allocation for OOH production, so the added scope is currently unplanned cost.
This public route is a guided walkthrough. The operator monitor runs the same kind of cascade reasoning on live project graphs, branch drafts, and submission packages.