# Introduction

> A persistent home for your relationships, built for the agents that work with you.

## A little context goes a long way

A useful relationship is more than a name in a list. It is the conversation you had, the work you are doing together, and the small details you want to remember next time.

Orbit gives your agents a persistent, structured place for that context. Create a contact once, find it in another conversation, and keep building on what you already know.

## Built for the way agents work

**One shared source of context.** Your records live in your private workspace, independently of any agent session.

**A small, explicit interface.** Agents connect through the Model Context Protocol (MCP). Every tool has a defined purpose, validated inputs, and an authenticated caller.

**You stay in control.** Orbit stores records and enforces permissions. Your agents provide the reasoning and decide how to help, within the permissions you give them.

> **Headless by design**
> CRM operations happen through MCP. The [owner interface](/docs/account) provides account and agent-access management; server provisioning and advanced administration remain command-line responsibilities.

## Your first conversation

Once [Hermes is connected](/docs/connect-hermes), ask it to start with the workspace context and look for a contact before creating one:

```text
Search Orbit for Maya Chen. If there is no matching contact,
create one with maya@example.com and the tag “collaborator”.
Remember the contact ID so we can retrieve it next time.
```

Hermes can use `contacts_search`, `contacts_create`, and `contacts_get`. Orbit attributes any creation to the authenticated agent and keeps the result available after the conversation ends.

## What you can do today

The **0.4 CRM** supports contacts, organisations, projects, affiliations, participants, sourced activity, assigned tasks with expiring claims and outcome-backed completion, structured briefs, reusable tags, and typed custom fields. Mutable records use revision checks and archive/restore. It includes reader and contributor permissions, duplicate candidate warnings on creation, safe mutation retries, and an audit trail.

Administrator export and audited activity redaction are available through the CLI. Live deployment acceptance and production backup/recovery verification remain pending. See the [release roadmap](/docs/roadmap) for the full picture.