Introduction to nondro

A shared operational model#

nondro connects the systems your organization already uses and gives their information a common business meaning. Databases, files, and services become the foundation for typed objects, relationships, governed actions, and focused applications.

An order can be connected to its supplier, the documents that support it, and the decision that moves it forward. People and AI work with those shared definitions instead of reconstructing their meaning for every task. The model is called an ontology.

From sources to decisions#

Start with a connection, define the things that matter, and decide what people may do with them. A source connection and an object definition are separate: connecting a database does not automatically approve every proposed business concept.

nondro connects to source systems in place. Its control plane maintains definitions, object identities, selected indexed properties, knowledge, work, and audit records. Your source systems remain the authoritative homes for operational data.

• Connections make existing systems available to authorized workflows.
• The ontology defines objects, relationships, and their business meaning.
• Actions apply explicit policy before executing changes.
• Applications give teams a focused way to use the same governed foundation.

AI with organizational context#

The built-in conversation uses the definitions, tools, and knowledge available to the signed-in person. It can help explore data and draft changes. Named model profiles let an operator configure supported AI providers, while compatible external agents can connect through scoped credentials.

Knowledge records preserve explanations and decisions with their subjects and attribution. Work threads preserve objectives, progress, and handoffs. Their usefulness depends on the context your team actually records and reviews.

Start with one workflow#

Choose one team, one source, and one decision worth improving. Establish a small set of object types, review the proposed definitions, and build a useful application around them. Expand once the team understands the model and its access boundaries.

The quickstart walks through this first path. The core concepts explain what is being created and which authority each step requires.