Organisational knowledge governance
Trusted organisational context, structured at the source.
Origentra is the trusted context layer for your organisation. Record the systems, suppliers, processes, data and policies you depend on — each with an owner, a source, a review date and a history of every change.
Access is arranged directly with the Techvora team.
Every record carries
- Ownership
- Provenance
- Relationships
- Verification
- Review dates
- Change history
The problem
Organisations run on knowledge that nobody can fully vouch for.
What an organisation knows about itself is spread across documents, spreadsheets, inboxes, systems and the memories of the people who have been there longest. Most of it was accurate once. Much of it still is. The difficulty is telling which.
When an auditor, an incident, a new leader or a change programme needs an answer, the same four questions come up — and they can rarely be answered from the place the information lives.
Who owns this?
Accountability is assumed rather than recorded, so nobody is asked to keep the information right.
Where did it come from?
A signed contract, a system export and a remark in a meeting look identical once they are pasted into a spreadsheet.
Is it still current?
Nothing signals that a fact has quietly expired. It simply goes on being repeated.
What depends on it?
Connections live in people’s heads, so the impact of a change is discovered after it happens.
The Origentra approach
Structure the knowledge that matters, not everything that was ever written down.
Origentra does not ingest your documents or claim to understand your organisation for you. Your teams model the entities that matter and connect them with typed relationships, so every fact becomes a record that can be owned, sourced, reviewed and traced.
Entities
Applications, systems, suppliers, partners, processes, datasets, policies, teams, business units, technologies and regulators — with the attributes your organisation needs to record.
Typed relationships
Depends on, hosted on, supplied by, stores data in, governed by, reports to. Each relationship means something specific, which is what makes dependency and impact views dependable.
Governance on every record
Ownership, provenance, verification, review dates and an append-only history apply to each record from the moment it is created — not as a separate process bolted on later.
Relationships read as plain statements
Example recordsPayroll Platform is hosted on Azure Tenant
DependencyPayroll Platform stores data in Payroll Dataset
Data flowPayroll Platform is supplied by Northwind Payroll Ltd
DependencyPayroll Dataset is governed by Data Retention Policy
GovernancePeople Operations reports to Chief Operating Officer
Structure
Start from what you already have. Import existing registers from CSV, with row validation, duplicate warnings and a report of any rows that could not be imported. Search, filter, save views and export to CSV whenever you need to.
01Provenance
Know where every piece of information came from.
Sources are not equally authoritative. A signed contract outweighs a workshop note; the system of record outweighs a spreadsheet someone kept up to date for a while. Origentra records each source with its type, its authority level and a link or evidence file — and can attribute a source to the specific field it supports.
When someone asks why a record says what it says, the answer is on the record.
- Authoritative
- The system or document of record.
- Reliable
- Trustworthy, though not the record itself.
- Indicative
- Useful context that may be incomplete or dated.
- Unverified
- Reliability not yet known.
02Relationships
See how the organisation connects, and what is affected when something changes.
Relationships turn a list of records into a picture of dependency. Trace what a system relies on upstream and what relies on it downstream, then ask the question every change and continuity plan begins with: if this supplier is unavailable, which known records rely on it?
Relationship graphs are deliberately bounded so they stay readable, and every graph has an equivalent list, so the same answer is available to people using keyboards and screen readers.
Origentra shows the dependencies your organisation has recorded. It does not guess at the ones it hasn’t.
03Ownership
Give every record an owner and a steward.
Knowledge without an owner goes stale quietly. Each record names a business owner, accountable for the thing it describes, and a knowledge steward, responsible for keeping the record itself accurate.
Ownership coverage is measured openly, so gaps are visible to the people who can close them rather than discovered in the middle of an audit or an incident.
04Governance
Change knowledge deliberately, with a record of every decision.
Contributors propose; reviewers decide. Changes are submitted for review and then approved, or returned with changes requested. Verification states separate what someone entered from their own knowledge from what has been checked against a source — and make disputed information impossible to miss.
Review dates bring records back for attention before they drift. Nothing is silently deleted: records are archived and remain traceable, and every change is written to an append-only history.
Knowledge health
Plain measures you can check, not a score you have to trust.
Origentra shows how complete and current your organisation’s knowledge is using five measures. Each one is a count — a numerator over a denominator — with an indicator derived from stated thresholds.
Good at 80% or more. Needs attention from 50%. Incomplete below 50%.
| Measure | Records | Indicator |
|---|---|---|
| OwnershipLive records with an active owner | 186 / 204 | Good |
| ProvenanceLive records with at least one attached source | 158 / 204 | Needs attention |
| Review freshnessLive records not past their review date | 171 / 204 | Good |
| VerificationLive records marked Reviewed or Verified | 97 / 204 | Incomplete |
| RelationshipsLive records connected to at least one other record | 149 / 204 | Needs attention |
Intelligence readiness
AI can reason only as well as the context it is given.
Generative AI, automation and analytics all depend on the same foundation: reliable information about how the organisation actually works. Give them knowledge that is unowned, unsourced or out of date, and they will repeat its errors with confidence.
Origentra builds that foundation. Knowledge that is structured, owned, sourced, connected, reviewed and governed is ready to support search, reporting, automation and analytics — and, in future and under your organisation’s control, AI.
Readiness, not automation
The value is in the context itself: records people can rely on, and a clear account of why they can.
Portable by design
Structured records and relationships export to CSV, ready for the reporting and analytics tools you already use.
No AI today
Origentra does not use AI and sends no organisational data to AI providers. Any future use would be your organisation’s decision.
Use cases
One context layer, many landscapes.
Start with the landscape causing the most friction, then connect it to the rest. Relationships across landscapes are where the most useful answers tend to be.
Technology landscape
Applications, systems, services and what they run on.
“What runs on this platform, and who needs to know before it changes?”
Applications, systems, technologies
Supplier landscape
Suppliers and partners, what they provide and what relies on them.
“If this supplier is unavailable, which known systems and processes rely on it?”
Suppliers, partners, applications
Process mapping
How work gets done and what each process depends on.
“Which systems and teams does month-end close depend on?”
Processes, teams, applications
Data landscape
Datasets, where they are stored and how data flows.
“Where is customer data stored, and which systems does it pass through?”
Datasets, systems, business units
Governance and compliance
Policies, standards, regulators, risks and controls.
“Which policies govern this dataset, and when were they last reviewed?”
Policies, regulators, datasets
Organisational structure
Business units, teams and who is responsible for what.
“Who is accountable for this area, and where does it report?”
Business units, teams
What Origentra is not
It is not a wiki, a document repository, a CMDB, a CRM, an ERP, a procurement tool, an HR system or a chatbot. It keeps the owned, sourced and reviewed context about the things those tools manage, and how they connect.
Security
Protections enforced where the data lives.
Organisational knowledge is sensitive by nature. Access rules in Origentra are enforced in PostgreSQL itself, not only in application code.
How Origentra is securedIsolation in the database
Row Level Security is enabled and forced on every table, so one organisation’s knowledge cannot be read by another.
Roles checked twice
Owner, Administrator, Knowledge Steward, Contributor, Reviewer and Viewer permissions are checked on the server and again in PostgreSQL.
Restricted records
Records marked Restricted are visible only to their owner, their steward and roles permitted to see them.
Append-only history
Lifecycle, verification and review changes run through audited database functions and are written to an append-only log.
Hosted in Ireland
Server functions run in Dublin and the database in AWS eu-west-1. Every connection is encrypted.
No AI, no tracking
No organisational data is sent to AI providers. No third-party analytics. Essential cookies only.
Organisational knowledge you can actually trust.
Tell us which landscape you would like to structure first, and we will be in touch about setting up access for your organisation.