
Disinformation Observatory
With CIEPS-AIP, Panama
An observatory that studies disinformation in Panama’s digital environment with science and evidence, running on ARPIA.
More in ARPIA LabsA shared layer where people, AI agents and apps work with your organization’s data and systems, safely. It turns every database and every MCP system into business objects with rules, permissions and a history.
Connecting AI to a company’s systems usually means custom work for each one: a connector, prompts that explain what the data means, a set of permissions, and then keeping all of it current as the systems change. Every new agent repeats the job, and every one ends up with its own version of the truth.
The ontology does that work once, in one place. Your teams define what a customer, an order or a risk means for your organization. From then on, every agent, app and person works through the same definitions and the same rules, and everything they do is recorded.
The ontology is made of three pieces.
An agent does not need to know where the data lives or which tool to call. It asks the ontology, in business terms, and the ontology applies your rules on the way in and on the way out.
The rules themselves are written by your teams in plain language: what an active customer is, when an order is at risk, what margin really means. The ontology keeps each one as a definition with an owner and a change history.
Ask in conversation. ORIA answers and acts through the ontology, with the permissions of the person asking.
Apps, dashboards and scheduled flows read and act through the same nodes and actions.
Agents you already use, such as Claude, connect to the ontology over MCP and get the same rules.
A sales director asks ORIA which large customers have orders at risk this month.
The question crosses three systems: orders live in the ERP, accounts in the CRM, open tasks in the project tool. ORIA reads the three nodes through the ontology, joins them by customer, and answers with a table.
Then it proposes a follow-up task for each account owner. Creating tasks is an action that needs approval, so the director reviews the list and approves it. Every read and every task is recorded.
Finally, the director saves the whole thing as a weekly flow. It runs with the same definitions and the same permissions every time.
Most of your systems already speak MCP. Connected directly to an agent, each one arrives as a long list of tools. ARPIA brings them into the ontology instead, next to your databases.
Each MCP server joins as nodes and actions grouped by what they are about: customers, orders, tasks.
The agent loads the business objects its task needs, not every tool of every server. Data is filtered and calculated before it reaches the model.
Reading needs a permission. Writing needs a permission and an approval. Sensitive columns are masked by profile, and credentials never leave the platform.
Every read and every action is logged. When a system adds or changes tools, the ontology notices and the change waits for review or applies with an undo.

With CIEPS-AIP, Panama
An observatory that studies disinformation in Panama’s digital environment with science and evidence, running on ARPIA.
More in ARPIA Labs
With InterFuerza, Grupo ENX
Businesses on InterFuerza connect sales, inventory, collections and accounting to AI through MCP, with governance through Oria by ARPIA.
More in ARPIA LabsBring one business definition your teams argue about. We will show you how it becomes a governed, queryable rule.