Production reality changes.
A location moves. A crew plan changes. A permit expires. A payroll assumption no longer matches the job. The production changes first.
Product
The layer that validates the production itself.
Existing systems validate their own output. Olivine verifies whether the production state itself is still coherent across payroll, permits, insurance, safety, budget, and operations.
Knowledge + relationships + graph state.
Olivine follows the chain across people, places, paperwork, money, and rules so the production can see the cascade while it is still manageable.
Decision-ready consequences with next actions.
Teams get a grounded picture of what broke, which departments are affected, and what has to happen next before the change becomes real.
Authoritative knowledge
The product is not just structure. It is the encoded rates, fringes, permit logic, insurance dependencies, labor rules, and production business logic that teams rely on.
Consequence mapping
Olivine shows what a change touches across departments before each team discovers the fallout on its own timeline.
Cross-domain visibility
Creative, operational, financial, and compliance realities share one graph, which is why a location change can surface payroll and budget consequences immediately.
Decision memory
Every scenario stays attached to its rationale, so the production can remember why a decision was made and what changed because of it.
Branchable what-if scenarios
Teams can inspect options before they become reality, which makes expensive choices less speculative and easier to approve with confidence.
One shared operating picture
Producers, payroll, studio teams, and production company owners can all work from the same graph instead of reconciling different versions of the truth.
Why this layer matters
The ontology is what lets the consequence map itself.
The value is not just that Olivine stores facts. It stores the relationships between the facts, which is why one change can surface many downstream effects in one move.
Node
Every person, place, document, and budget assumption becomes an addressable entity.
Edge
Every real dependency becomes a relationship the production can inspect.
Cascade
When one node changes, the graph shows the affected chain before teams find it by hand.
Decision
The output is operational: what broke, what moved, and what now needs attention.