OntoVana brings together Ontology and Nirvana (Sanskrit nirvāṇa). For us, the name expresses awakening and renewal: knowledge becoming understanding, and people and organizations opening new possibilities as they grow.
An intelligent core for every enterprise. A second brain for every person.
We believe having an agent will become as ordinary as having a website. It should be affordable, easy to set up, and comfortable to use every day. That is why OntoVana is building Kernel: an agent platform for enterprises and individuals, built on digital ontology. Kernel is a digital operating system for individuals and enterprises, built on digital ontology, connecting people and organizations through a collaboration network. Internal operations, management, organizational learning and ongoing development, and external exchange and cooperation, are equally important values that can each stand on their own.
01
Built around a life, not just a task
A task has an ending. A business and a life continue. Beyond completing individual requests, Kernel is designed to keep understanding the people, knowledge, relationships and commitments that give each request its meaning.
We see an enterprise as a living whole, and a personal Kernel as the foundation of a life operating system. Digital ontology gives scattered data a shared frame of reference, so agents can understand the whole, assess a situation and take part in work.
02
Your knowledge. Your coordinates. Your Kernel.
Kernel is a sovereign cognitive counterpart centered on you or your enterprise: a second brain for understanding and remembering, and a second presence through which our agents take part in the world.
The owner of each domain decides who can access its data and which actions agents may take. Understanding connects to real data; action follows granted authority and leaves a verifiable record. A shared platform must not erase these boundaries.
03
Grow through use. Share the foundations.
Implementation should fit into everyday work. Small questions, corrections and verified outcomes can gradually turn knowledge into an evolving digital ontology, rather than demanding that everything be specified in one costly project. Building the ontology is a starting point; making it useful and continually improving it through practice is our goal.
Our direction is self-implementation and growth with human oversight. Our open-source plan includes both product code and industry knowledge packages, so communities can share foundations while keeping private knowledge within its own domain. Public releases and their licenses will be stated explicitly.
04
The bandwidth of thought, beyond one conversation
A person can hold years of experience, yet has limited time and attention to explain it. A digital ontology can preserve the reasons, conditions and context behind their judgments. Our direction is to make that understanding available to more relationships, with the person retaining control.
Network Federation connects sovereign personal and organizational domains, including enterprises, associations and clubs. Its planned functions cover identity and representation, recipient-specific topic permissions, requests and delivery, encrypted transport, receipts and withdrawal. MyKernel and Workbench support private preparation; Shared and Workspace support exchange and joint work. Personal and organizational identities, data and responsibilities stay distinct.
05
A second presence in personal relationships
A digital persona draws on experience, values and feedback. A second presence is its authorized participation in a particular relationship: continuing a discussion, explaining a viewpoint or preparing a shared task when you are unavailable. It identifies itself as delegated, preserves context and returns to you when judgment or new authority is needed. Friends and colleagues may receive different topics and levels of disclosure.
Anyone can present their experience, views, direction and selected relationships through a digital persona, and continue authorized external interactions. Digital Presence is an entry for understanding and contact; second presence is delegated participation in a particular relationship. People can exchange with friends, colleagues, advisers and members, contributing within organizational roles and permissions when joining a company or association.
06
What each member can contribute
Within an organization, members could contribute more than the work they perform in person: their experience, methods and selected connections could help colleagues, customers and partners over time. Leaders can start with a real decision and reflection; every member can add expertise and challenge assumptions. Personal advice becomes organizational knowledge only through review and explicit adoption; an opinion is not an approval.
Business owners and people responsible for development can turn authorized exchanges into meetings, colleague collaboration or company matters. Other members can contribute experience and relationships too. A personal digital persona needs no business role; new disclosure, quotations and commitments follow the relevant authority.
Development direction: node encryption, protocol probes, receipts and platform deployment registration have an experimental Mac/Ubuntu foundation. Complete second presence, social relationships, topic permission matrices and cross-domain collaboration remain in development. The long-term aim is a social and cooperation network built on shared understanding. Hyperbody describes values and experience working naturally within authorization; it is distinct from second presence, and does not claim machine consciousness.
From a lifetime of relationships to an enterprise that learns
Simulated stories: people, companies, figures and events are fictional, illustrating product direction rather than customer results. Complete relationship management, second presence, automatic sharing, live global mapping and autonomous operation still require development and validation. Authorized semantics, real queries and candidate maintenance provide a starting point.
Personal edition / 01
Find the people and experiences behind a lifetime
Functional flow · Open full-size image
Lin is planning science education for rural schools. “Who understands inexpensive experiment kits and would want to help?” Her relationship graph finds Chen: they met during disaster relief ten years ago, later built open sensors together, and Chen once offered to help rural schools. Their shared projects, interests, mutual help and latest conversation provide the context.
Lin writes an idea for experiments using old phones. Within an existing continuing mandate, agents responsible for different relationships choose relevant recipients and disclosure depth: equipment details for Chen, lesson ideas for an alumni group and resource needs for nonprofit partners. Lin can inspect, correct or pause those choices without choosing every recipient again. Relevance and permission are assessed separately.
Chen asks for earlier sensor designs. A delegated second presence can explain public experience and deliver an approved file. Unpublished drawings owned by a former partner stay subject to their source permissions and return to Lin for a decision. Both sides can continue within their own mandates; real progress and corrections update the relationship, supporting sustained personal exchange instead of indiscriminate broadcasts.
General value · Connect people, events, experience and shared goals into lasting relationship context. Move from “Who do I know?” to “Who can help with this?”, with recipient-specific sharing, bounded follow-up and authorized file delivery.
Personal edition / 02
Your experience can participate while you are away
Functional flow · Open full-size image
Zhou is an experienced supply-chain adviser, an industry association member and an alumni mentor. He also advises a small manufacturer each month. He opens different methods and selected experience to each role, with separate subjects, audiences and expiry dates. Joining an organization does not expose his entire personal knowledge.
An association member asks how small buyers can give suppliers predictable demand. His second presence explains his method using approved examples. A manufacturer’s buyer asks which offer to choose; with separately authorized company quotes and schedules, it prepares comparisons and missing questions for the team. Association members cannot see those quotes.
Contractual commitments, private supplier assessments or new representation rights return to Zhou or the company’s authorized decision maker. He later reviews feedback and corrects advice; only explicitly adopted contributions become company knowledge. Even a temporary adviser can contribute continuously while personal material, organizational adoption and formal approvals keep their own owners.
General value · Bring personal knowledge into companies, associations and communities through bounded, revocable representation. Extend its usefulness while preserving human takeover, explicit organizational adoption and responsibility.
Enterprise edition / 03
A chip trader sees one changing business landscape
Functional flow · Open full-size image
Fictional Clearstream Chips receives an order for 20,000 MCUs due in three weeks. CRM holds the promise, ERP lists 8,000 in stock, SRM holds an offer for 12,000, and warehouse records show 3,000 of the stocked parts awaiting inspection. Kernel maps customer, part, lot, offer, stock, payment and schedule into common business meaning, showing source freshness and conflicts. Stock is not automatically deliverable stock.
The owner asks when the whole order can arrive and where cash will be tied up at this price. Within authorized data, the agent compares commitments, usable stock, incoming lots and payment terms. Only 5,000 stocked parts are currently deliverable; the existing supplier offer still leaves a 3,000-part gap. A supplier schedule leaves little margin while customer acceptance delays payment. It presents split delivery, added stock and an alternative supplier, with margin assumptions, cash needs and conditions requiring confirmation for sales, purchasing, warehouse and finance to assess together.
After a decision, the agent prepares purchase requests and schedule updates only through connected, authorized operations. Formal changes follow their approval flow and return receipts. Inspection clearance or a delivery change triggers refresh and reassessment as supported by actual integrations, with stale data visible. Existing systems retain their responsibilities, and unknown information remains unknown.
General value · Turn separate systems into a common, traceable and continually updated business view. People and AI can ask, analyze, decide and act with authorization; actual integration and validation determine freshness, confidence and execution scope.
Enterprise edition / 04
A biopharma team develops shared judgment through questions
Functional flow · Open full-size image
Fictional Clearwell Bio is considering a project’s move to pilot production. R&D calls the process stable; manufacturing says a new raw-material lot has not been tested; quality notes that evidence covers only two small-scale runs. Kernel asks each role what “stable” means: at which scale, under which conditions, supported by which records, and with which unresolved counterexamples?
The answers become source-backed candidate explanations. A schedule discussion reveals competing priorities: commercial timing, learning speed, repeatability and evidence completeness. The team agrees that commitments must state evidence maturity, applicable scale and unresolved risks. This becomes an organizational principle only after review and explicit adoption, rather than a model announcing the company’s position.
On another project, the agent uses the adopted principle to ask different roles and compare outcomes. A material change or larger scale introduces counterexamples; the team revises the principle while preserving versions and scope. Its experience, operating logic and philosophy grow. “Developing a will” means collectively tested aims and tradeoffs; research, quality review and formal release remain with responsible people and processes.
General value · Connect questions across roles, outcomes and counterexamples into organizational learning. Make scattered experience an evidenced, revisable shared judgment; organizational will is a governed direction, not machine consciousness.
Our product
Kernel
An agent platform for enterprises and individuals.
Kernel supports personal assistants and agents governed by companies and organizations, expanding capability through collaboration with clear permissions and responsibilities.
