Governance in context
Ownership, sensitivity, source authority and permissions sit alongside the data relationships.
Security & Governance
The agent should know the rule before it sees the data.
Deca10 keeps meaning, provenance and policy in the same graph used to answer the request.
Permission path
Fraud can see it. Marketing cannot.
The policy node stays in the path, so the decision is inspectable.
Control
Three things that have to be true.
Provenance by default
The answer can carry where it came from and which relationships were used.
Customer-controlled deployment
The organizational graph and policy layer are designed to remain inside the customer’s chosen boundary.
Sovereignty
Your map of the business is sensitive too.
The provider can change. The organizational model stays yours.
FAQ
Direct answers
Does Deca10 replace our warehouse or lakehouse?
No. It sits above existing systems and creates a governed semantic layer across them.
Do we need to move all of our data?
No. The product is designed to connect to existing systems rather than require a wholesale migration.
Can humans use the same layer?
Yes. People and agents resolve against the same organizational meaning.
What does sovereign mean here?
The customer controls the graph, governance and deployment boundary that represent its internal knowledge.
Talk to us
Ask us how the rule travels with the path.
If agents are about to touch sensitive knowledge, the permission has to live on the graph.