--- question: What are the core terms of the ABI platform? kind: guide --- # Platform ABI (Agentic Brain Infrastructure) is the open-source AI Operating System. It grounds language models in your organization's ontology, so the agents built on it work from what your organization knows. ABI is the core of Naas, an AI Network as a Service: the [Introduction](/) says how it fits. Under the hood, a kernel loads modules. An agent is a model, a system prompt, and tools. Everything else in a module is a class of tools that agent uses. Surfaces talk to the kernel. They are not the kernel. The surfaces are Nexus (the web UI), the [REST API](/api), and the [`abi` CLI](/user-guide/reference/cli). `config.yaml` enables a module. Adapters sit under the kernel. They are not modules. You run the same source yourself (MIT, no license key), or Naas runs it with you. There is no hosted signup. This sidebar group is that shell: Auth, Accounts, Workspaces, Organizations, Modules, Home, Search, Chat, and Code. Repositories and Installation live under Get started. The diagram, how a call moves, and the longer account are [Overview](/architecture/overview). ## Terms | Term | Meaning | |---|---| | Project | Directory from `abi new project`. Holds `config.yaml`, `.env`, and `src/`. The git repos are [Repositories](/user-guide/platform/repositories). | | Module | Extension unit. Remote: own process, imports `naas-abi-sdk`, not listed under `modules:`. In-engine: loaded by the engine, listed under `modules:`, imports `naas_abi_core`. | | Agent | Model + system prompt + tools. Unit of work. | | Workflow | Intent to execution. The engine can expose it as a tool and as an API route. | | Pipeline | External data into RDF triples. | | Integration | One external API or system. | | Ontology | OWL in Turtle (BFO, CCO, or a domain). Loaded into the schema graph. | | App | UI a module ships (`apps//manifest.json`), shown in Nexus when the workspace turns it on. Nexus itself is an app of `naas_abi`. | | Tool | What the agent calls. | | Skill | A tool class the agent uses. | | Organization | Nexus tenancy above workspaces. Membership roles: owner, admin, member. Set on [Organization settings](/user-guide/platform/organization-and-members). | | Business workspace | Nexus collaboration space under an organization. Roles: owner, admin, member, viewer. The UI word Workspace means this. See [Workspaces](/user-guide/platform/business-workspaces). Settings: [Workspace settings](/user-guide/platform/workspace-settings). | | Code workspace | Coder runtime. Forgejo holds Repo and Branch. The Code section needs `--with-coding`. See [Code](/user-guide/platform/code-workspaces). | | Marketplace | Package `naas-abi-marketplace`: AI providers, application integrations, domain modules, and a `__demo__` tree to copy. | | Super admin | `is_superadmin`. Opens [Platform settings](/user-guide/platform/platform-settings). Independent of organization role and workspace role. The generated `admin@example.com` is one. | ## What the kernel binds Adapters sit under the kernel: models (OpenAI, Claude, Gemini, or local such as Ollama), a graph (Oxigraph locally; other SPARQL stores in production), a store (Postgres, object storage, Redis), and a bus (local or cloud). Adapters are not modules, and they are not a sidebar feature. `config.yaml` still names every kernel service and picks an adapter for it: agent, model registry, triple store, ontology, object storage, vector store, secret, cache, key-value, bus, document, email, event, and activity log. Module components and data stores are under **Application building** and **Knowledge & Data** in Capabilities. [Services](/capabilities/platform-services/overview) is email, events, the message bus, and secrets. See the [Configuration Reference](/capabilities/get-started/configuration). Files, maps, documents, sheets, and slides are module components or kernel services. They are not pages in this group. Chat and Code are dock sections documented here. Since 3.0 a project runs on NATS. `abi dev up` starts `nats-server`, Oxigraph, the API, Nexus web, and remote modules. The Docker stack adds PostgreSQL, Fuseki, Qdrant, MinIO, Redis, Caddy, and the MCP server. Dagster and RabbitMQ are the legacy path (`--without-nats`). See [NATS](/user-guide/get-started/nats). A new project enables OpenRouter and expects `OPENROUTER_API_KEY`. Local models are Ollama. Canonical ids: `services.model_registry.default_chat_model` and `default_embedding_model`. ## Auth Nexus sign-in is a password or an email code, chosen by `nexus_config.auth_password_enabled`. Self-registration is off. The seeded user is `admin@example.com`. The password is `NEXUS_USER_ADMIN_EXAMPLE_COM_PASSWORD` in `.env`. Engine routes (`/agents`, `/workflows`, `/pipelines`, `/tools`) use `ABI_API_KEY`. There is no built-in MFA, SAML, or OpenID Connect. See [Auth](/capabilities/platform/auth). ## In this group | Page | What it is | |---|---| | [Auth](/capabilities/platform/auth) | Sign-in, sign-in method in config, and engine API key. | | [Accounts](/capabilities/platform/account) | The account menu: profile, appearance, and links to organization and platform settings. | | [Workspaces](/user-guide/platform/business-workspaces) | The Nexus collaboration space. Settings: [Workspace settings](/user-guide/platform/workspace-settings). | | [Organizations](/user-guide/platform/organization) | The Nexus tenancy above workspaces. Settings and members: [Organization settings](/user-guide/platform/organization-and-members). | | [Modules](/user-guide/build/modules/overview) | Extension packages: remote vs in-engine, jobs, and the marketplace. | | [Home](/capabilities/platform/home) | The workspace desk. Dock layout: [Orientation and navigation](/capabilities/get-started/orientation). | | [Search](/capabilities/platform/search) | Topics, workspace features, and web scopes. Tasks: [Run a search](/capabilities/platform/run-a-search), [Choose search scopes](/capabilities/platform/choose-search-scopes). | | [Code](/capabilities/platform/code-workspaces) | Coder runtime vs business workspace. | | [Chat](/capabilities/platform/chat) | Chat dock section; agent threads on [Chat with an agent](/capabilities/build/agents/chat-with-an-agent). | | [Organization settings](/user-guide/platform/organization-and-members) | The organization, its users, and which workspace features each role can use. | | [Workspace settings](/user-guide/platform/workspace-settings) | Settings for this workspace, including which apps are shown. | | [Platform settings](/user-guide/platform/platform-settings) | The super-admin screen for the platform itself. | The tasks you can do from more than one interface have their own pages, with Web UI, CLI, REST API and Config tabs: [Create an organization](/user-guide/platform/create-an-organization), [Create a workspace](/user-guide/platform/create-a-workspace), [Invite an organization member](/user-guide/platform/invite-an-organization-member) and [Invite a workspace member](/user-guide/platform/invite-a-workspace-member).