State
What is true now: roles, commitments, business rules, services, releases, incidents and customer impact.
The platform
The graph the whole company runs on.
One temporal model of people, customers, commitments, rules, capacity, software, money and time. The five product surfaces are views onto it, and every investigation or action an agent takes retains its source, authority and history.
The spine the whole company writes to.
The system does not copy disconnected records into another warehouse. It links human intent, company rules, workforce reality, delivery state and production outcomes into durable operating context. A person and an agent query it the same way, through the same permission model.
05Work surfaces
Mission Control · My Work · Engineering · Sales · Delivery · People · Knowledge
04Reasoning and action
Investigation · impact analysis · patches · briefs · approvals · governed execution
03Company model
People · customers · commitments · rules · software · services · capacity · money · time
02Event spine
Messages · decisions · code changes · releases · incidents · outcomes
01Connected systems
Communication · documents · source control · CI/CD · observability · CRM · support · finance
Four things every decision needs.
Relationships
How people, intent, documents, code, systems, customers and dependencies affect one another.
History
What changed across the business and software, who or what changed it, and the evidence behind it.
Authority
Who may see, decide, approve and act—applied equally to people and agents.
Recommendation, action and outcome share one history.
A recommendation that never records its outcome cannot make the next recommendation better. OmniManas writes the action and its result into the same event log the recommendation came from.
01
Observe
Events from work and systems
02
Understand
Meaning resolved in context
03
Decide
Options ranked with evidence
04
Act
People and agents execute
05
Learn
Outcomes return to memory
Living company model · state + relationships + history