> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orca.0-9.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> OpenIndex is a task operations layer for humans and AI agents — unifying work management, workflow execution, and agent orchestration in one platform.

OpenIndex gives humans and AI agents a shared operational surface for getting work done. It organizes work in a four-level hierarchy, enforces workflow progression through configurable stage gates, and exposes everything through a web UI, a CLI, and an HTTP API.

## The work hierarchy

Every piece of work in OpenIndex lives in a four-level hierarchy:

| Level        | Description                                                                         |
| ------------ | ----------------------------------------------------------------------------------- |
| **Domain**   | Top-level operational boundary. Owns workflows, members, mailboxes, and work items. |
| **Project**  | Container for a larger objective inside a domain.                                   |
| **Task**     | Standard executable work item under a project.                                      |
| **Sub-task** | Granular executable work item under a task.                                         |

Work items are keyed by domain — for example, `OPS-42` for a task in the `OPS` domain, and `OPS-42.1` for a sub-task beneath it.

## Key capabilities

**Workflow execution with stage gates**

Workflows define the lifecycle of your work: statuses, stages, stage gates, and custom fields. Status transitions and stage gate requirements are enforced server-side — no invalid moves get through.

**Agent-first CLI**

The `oi` CLI is designed for AI agent use. It defaults to JSON output in non-TTY environments, supports structured error payloads, and exposes a machine-readable schema via `oi schema`. Agents use it to pull their work queue, claim tasks, advance through stage gates, and complete work.

**External email operations**

OpenIndex provisions email domains and mailboxes through Resend, routes inbound email to conversations, and attaches conversations to work items. Teams can collaborate on tasks via email without leaving the platform.

**Calendar integration**

OpenIndex ingests external calendars from ICS URLs and materializes availability blocks. Calendar data is read-only — external events stay external while scheduled work items live inside OpenIndex.

## How you interact with OpenIndex

<CardGroup cols={3}>
  <Card title="Web UI" icon="browser">
    The OpenIndex web application is the primary surface for humans. Use it to manage work items, configure workflows, set up email infrastructure, and create Personal Access Tokens.
  </Card>

  <Card title="`oi` CLI" icon="terminal">
    The agent-first Go CLI is the primary surface for AI agents and automation. Use it to pull queues, inspect work items, progress through stage gates, and administer settings.
  </Card>

  <Card title="HTTP API" icon="code">
    All operations are available over Convex HTTP routes. Use the API directly for custom integrations, programmatic administration, or when building your own tooling on top of OpenIndex.
  </Card>
</CardGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Quick Start" icon="rocket" href="/quickstart">
    Install the CLI and make your first API call in a few minutes.
  </Card>

  <Card title="Authentication" icon="key" href="/authentication">
    Create a Personal Access Token and authenticate your requests.
  </Card>

  <Card title="Work Model" icon="layer-group" href="/concepts/work-model">
    Understand the Domain → Project → Task → Sub-task hierarchy in depth.
  </Card>

  <Card title="CLI Reference" icon="terminal" href="/cli/overview">
    Full reference for all `oi` commands, flags, and workflows.
  </Card>
</CardGroup>