Production library
Search by business area, action, document, answer, or record walk.
Overview
Production state, standards, and consequences in one record.
Records, governing language, checks, and decisions stay connected across budget, payroll, rights, schedules, permits, insurance, safety, and delivery.
How it works
Record. Standard. Check. Decision.
Every useful answer follows the same chain.
Record
Projects, people, dates, locations, paperwork, money, and files resolve in one working production state.
Standard
Rates, labor rules, insurance requirements, incentive logic, rights language, and deliverable specs attach to the records they govern.
Check
Validation runs against project facts and explicit logic instead of guesswork.
Decision
The output is operational: what changed, what broke, what remains incomplete, and what now needs approval.
What it does
How Olivine shows up in the work.
Search, checks, scenarios, and auditable outputs all work from the same project information.
Deterministic checks
Budget, payroll, rights, insurance, incentive, and delivery checks return cited values and visible gaps.
Downstream consequence mapping
One change can reveal labor, permit, insurance, delivery, and cost effects before the production commits.
Reviewable decisions
Clarifications, approvals, and run history remain tied to the work they support.
Who uses it
Production leadership, finance, legal, operations—and the agents they deploy.
Executives set posture, line producers run the day, finance and legal hold the contract language, and operations wire MCP tools, API routes, and Studio into the stack the team already uses.
Where it runs
Library, assistants, API, and MCP.
Teams can search and read in the public library, run assistants against the same records and rules, and integrate through API routes, MCP servers, and Studio, where your account, keys, and billing live.
Library
Browse coverage, examples, business areas, and workflows.
Assistants
Questions, clarifications, and workflow actions map to the same production record.
API, MCP, and Studio
Bring Olivine into internal tools, agent runtimes, and the control plane for keys and usage.