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

> ## Agent Instructions
> Company name is Akhara AI (never Rubric AI). Keep lowercase rubric/rubrics only when meaning grading criteria.
> Expert Review (docs path talent/) is enterprise BYO experts for audit and review: invite customer specialists; do not pitch Akhara recruiting or a public expert career portal. RLHF and domain writing are secondary work types.
> Prefer concrete API examples against public hosts: Environments eval API https://agi.akhara.ai, Control plane PDP https://api.akhara.dev, Evaluation https://app.akhara.ai / https://api.akhara.ai, Expert Review portal https://talent.akhara.ai.
> Do not invent a public hostname for private orchestrators or env API internals.
> Do not confuse control-plane latches with Environments confirmation latches.
> Environments SDK/API examples: curl against https://agi.akhara.ai. Evaluation SDK: from akhara import Akhara and AKHARA_API_KEY.
> Start with /llms.txt for the docs index and OpenAPI links; fetch individual pages as .md exports.

# Project onboarding

> Accept a project assignment, complete any required verification, and start review, RLHF, or domain-writing work.

Assignments cover a specific project for your organization: review, RLHF labeling, domain writing, or a mix. Complete every checklist item before you start submitting.

## Onboarding steps

<Steps>
  <Step title="Open the assignment">
    From Home, review the work type, domain, deadline rules, and the onboarding document.
  </Step>

  <Step title="Confirm domain fit">
    Only accept if the specialty matches your profile. Review and writing work must stay in your domain.
  </Step>

  <Step title="Complete required verification">
    Projects with sensitive data may require identity verification (government ID plus a short liveness check) before their queues open.
  </Step>

  <Step title="Sign project documents">
    Confidentiality and data-handling agreements when your organization's engagement requires them.
  </Step>

  <Step title="Confirm tool access">
    Check that the project UI, and Slack or docs if listed, open for you before the first work session.
  </Step>
</Steps>

<Warning>
  Assignment missing after the email? Hard refresh, re-login, or try another browser, then contact your project lead or support.
</Warning>

## What an assignment includes

| Item               | Typical contents                                                   |
| ------------------ | ------------------------------------------------------------------ |
| **Scope**          | Review, RLHF, or writing; domain pack; sample volume or weekly cap |
| **Onboarding doc** | Rubric, style guide, allowed references, contacts                  |
| **Requirements**   | Verification steps and agreements, when the project needs them     |

## Identity verification

When a project requires it:

1. **Government ID**: Front and back (passport, driver's license, or national ID)
2. **Liveness**: Short selfie video
3. **Confirmation**: Green check when done

<Note>
  Complete identity verification once; it carries to later projects on the same account when the vendor allows it.
</Note>