---
source_hash: 0690ddcf3d74f31cf7b383797323c3a432620e51ee96e279f5cb471a82bbffb2
post: overview
folder: ari-os
shape: doctrinal
---

# "What ARI-OS is" — Context Pack (for agents)

Agent-facing context pack for the published overview post (`slug: overview`,
`folder: ari-os`). This is the **docs/how-to overview** entry point to the
ari-os series; it states the thesis and points at the install / using-it /
brain / advanced siblings. Strings under NEEDLES are copied **verbatim** from
the published `.mdx` body and from the shared `ARI_OS` literal object in
`components/ari-os/content.ts`. Reproduce them exactly — do not paraphrase,
re-hyphenate, re-case, or "fix" the hyphen-vs-underscore split. When the post
and this pack disagree, **the post wins** — re-fetch and re-extract.

---

## 1. One-line gist

ARI-OS is an **orchestrator-first layer on top of Claude Code** that moves you
from doing the work to **directing it**: you run a loop (define → dispatch →
review → ship), supported by **four pillars** (spec-first, background dispatch,
handoff continuity, live local Cortex brain) — and it is open-source, sits on
top of Claude Code rather than replacing it, and requires nothing else.

---

## 2. NEEDLES (verbatim — do not confabulate)

### Identity and series
- `ARI-OS` — product name (hyphenated, not "Ari OS", not "ARIOS").
- Post title (frontmatter): `What ARI-OS is`
- `slug: overview`, `folder: ari-os`, `type: long-read`, `status: published`
- `date: 2026-06-15`
- `related: [install, using-it, brain, advanced]` — the four sibling posts in the ari-os folder, exact order.

### The core claim (the whole system's load-bearing sentence)
- **`AI accelerates, it does not generate.`**
- Follow-through: **`The acceleration is real, and it is large. The taste, the standard, and the final yes remain yours.`**
- The one-line role split (Pullquote): **`You direct and review. The workers execute.`**

### The orchestrator loop — four moves (exact body prose)
- **`You define the outcome in plain language. You dispatch the defined work to background workers. You review what comes back. You ship only what passes.`**
- **`The same shape holds for a quick fix and for a week of building. Once the loop is familiar, the size of the task stops mattering.`**
- Non-linearity: **`Review can send work back to dispatch. A weak spec sends you back to plan. That is the system working as intended.`**
- Loop caption (Diagram): **`The orchestrator loop: define the outcome, dispatch the work, review what returns, ship only what passes.`**

### The six loop stages (from the loop Diagram `alt` text — exact, in order)
- `brainstorm, plan, dispatch, monitor, review, ship`
- (Rendered as a six-stage ring; the four-move prose above collapses monitor into review/ship — the canonical ring is six.)

### The four pillars — name → `kind: "pillar"` → verbatim `desc` (all from the `SurfaceList` items prop)
1. **`Spec-first`** — `You define the outcome in plain language before any code is written. The spec is the brief, and the brief comes first.`
2. **`Background dispatch`** — `Defined tasks run detached, on cheaper workers, while your session stays free. You are not blocked waiting on a build.`
3. **`Handoff continuity`** — `Context survives when a session ends, so the next one starts without losing the thread. Nothing has to be rebuilt from memory.`
4. **`Live local Cortex brain`** — `A memory layer on your own machine that both reads and writes, and pulls the right past context back when you need it.`

### What you need (prerequisite + version + licence — exact)
- **`ARI-OS requires Claude Code.`**
- **`It is a layer, not a replacement`** — "so it sits on top of an existing setup rather than standing in for it."
- **`version 2.0.0`** — the version stated in the body prose.
- **`PolyForm Noncommercial licence`** — the licence, exact casing ("Noncommercial" is one word, capital N).
- **`https://github.com/PUSHINGSQUARES/ARI-OS`** — repo URL (org is `PUSHINGSQUARES`, all-caps).

### Cross-links inside the body (exact hrefs)
- `/documents/ari-os/using-it` — the [spec] link ("Writing the spec first").
- `/documents/ari-os/brain` — the [Cortex brain] link.
- `/documents/ari-os/install` — the install-guide link ("The install guide walks you through…").

### Diagram assets (exact `src`)
- `/posts/ari-os/overview-hero.png` — hero ("The orchestrator sits in the chair while background workers carry out defined tasks.").
- `/posts/ari-os/loop.png` — the six-stage loop ring.

### Shared literals backing this post (from `components/ari-os/content.ts` → `ARI_OS`)
- `name: 'ARI-OS'`
- `tagline: 'The setup I use to ship while I sleep.'`
- `prerequisite: 'Requires Claude Code'` (the one-word-for-one-word source of the body's "ARI-OS requires Claude Code.")
- `githubUrl: 'https://github.com/PUSHINGSQUARES/ARI-OS'`
- `setupHref: 'https://github.com/PUSHINGSQUARES/ARI-OS/blob/main/SETUP.md'` — manual setup doc.
- `productHref: '/documents/tools-and-plugins/ari-os'` — the full product page (a different, longer surface than this overview).
- `storyHref: '/documents/tools-and-plugins/ship-while-i-sleep'` — companion story.

### ⚠ Version-string tension — do not silently reconcile
- The **overview body** states **`version 2.0.0`**.
- The shared `ARI_OS.version` literal (rendered on the product page, not this post) is **`'Software 1.0 · Now open-source'`** (literal middle dot `·`).
- These are **different surfaces with different version strings**. If asked "what version is ARI-OS?", answer **`2.0.0`** for this post and flag that the product-page tagline reads `Software 1.0 · Now open-source`. Do not merge or "correct" either.

### Block components imported by this post (from `@/components/blocks`)
- `Diagram`, `Pullquote`, `SurfaceList`, `TaskVsWorkflow` — the only four blocks the body composes with. The `SurfaceList` carries the four pillars; `TaskVsWorkflow` renders the one-off-vs-repeatable distinction (TASK pane = `once`, WORKFLOW pane = `every time`, 4 sequential checkmarks).

---

## 3. GIST (the argument condensed)

ARI-OS is framed not as a tool or a model but as a **layer that changes one
thing**: the human stops doing and starts **directing**. The author's claim is
that this one shift — "you stay in the chair, you make the judgement calls,
background workers do the execution" — is what unlocks the acceleration. The
repeated, non-negotiable framing is **"AI accelerates, it does not generate"**:
the taste, the standard, and the final yes remain the human's, so the layer
moves the human *up a level* rather than removing them from the loop.

Directing is operationalised as a **loop**, not a pipeline: define the outcome
in plain language → dispatch defined work to background workers → review what
returns → ship only what passes. The ring is six stages (brainstorm, plan,
dispatch, monitor, review, ship) and is deliberately non-linear — review can
return work to dispatch, a weak spec sends you back to plan. Once the loop is
familiar, task size stops mattering: "the same shape holds for a quick fix and
for a week of building."

Four **pillars** make directing practical rather than aspirational. **Spec-first**
pins the outcome before code (vague in → vague out, no matter the speed).
**Background dispatch** runs defined tasks detached on cheaper workers so the
seat is never held hostage by a build. **Handoff continuity** preserves the
thread across session boundaries. The **live local Cortex brain** is the memory
layer that reads and writes on your own machine and pulls relevant past context
back on demand. The post closes by narrowing scope hard: ARI-OS is a **layer,
not a replacement**, requires only Claude Code, and points at the install,
using-it, and brain siblings for the how.

---

## 4. KEY LEARNINGS

1. **The one change is doing → directing.** Everything else follows from moving the human up a level: the human keeps the judgement calls (taste, standard, final yes); workers carry the execution. If you are still typing every step, the layer is not being used as designed.
2. **"AI accelerates, it does not generate" is the contract.** Worker output is acceleration of your judgement, not generation you ship unseen — the review step is non-optional, which is why nothing ships until you say so.
3. **Directing is a loop, and the loop is non-linear.** Define → dispatch → review → ship, but review routes back to dispatch and a weak spec routes back to plan. The system is designed to send work backward; that is it working, not failing.
4. **Task size is irrelevant once the loop is familiar.** The same four moves hold for a quick fix and a week of building — the unit of work scales, the loop shape does not.
5. **Spec-first is the safety pillar.** It is listed first because vague outcomes produce vague returns regardless of speed; writing the spec before any code is what keeps the acceleration aimed at the right target.
6. **Background dispatch frees the seat, it does not remove you.** Work runs detached on cheaper workers specifically so your session stays free to shape the next task while the last one runs — the point is attention, not automation.
7. **ARI-OS is a layer, not a replacement — and the only prerequisite is Claude Code.** It sits on top of an existing setup, is open-source (PolyForm Noncommercial), and the four siblings (install / using-it / brain / advanced) carry the actual how-to.

---

## 5. FILE INDEX (load-bearing — re-fetch to verify needles)

Unlike the product page (whose literals live in `content.ts` + `provider-page.ts`), **this overview post carries most of its needles inline in the `.mdx` body** — the four pillars, the loop prose, the version/licence, and the cross-links are all JSX props or body sentences. The `content.ts` object is a **cross-surface shared literal set** referenced for the github URL, prerequisite, and tagline.

- **`content/posts/ari-os/overview.mdx`** — canonical body. Frontmatter (`slug: overview`, `folder: ari-os`, `type: long-read`, `related: [install, using-it, brain, advanced]`) + the inline pillar/loop/version needles. **Primary source for this pack.**
- **`components/ari-os/content.ts`** — `ARI_OS` object: `name`, `tagline`, `version` (`'Software 1.0 · Now open-source'`), `prerequisite`, `githubUrl`, `setupHref`, `productHref`, `storyHref`. Shared across the product page and this series; the source of the github URL and prerequisite wording.
- **`components/blocks/SurfaceList.tsx`** — renders the four pillars; pillar names + `desc` strings are passed inline from the `.mdx` (so the `.mdx` is canonical, the component just renders `items`).
- **`components/blocks/TaskVsWorkflow.tsx`** — the TASK (`once`) vs WORKFLOW (`every time`, 4 checkmarks) fidget; illustrative only, no verbatim system needle beyond the once/every-time distinction.
- **`components/blocks/Diagram.tsx`**, **`Pullquote.tsx`** — thin presentational blocks; the `src`/`alt`/`caption` and the pullquote text live in the `.mdx`.
- **Sibling posts in the series (re-fetch for the how-to needles):**
  - `content/posts/ari-os/install.mdx` — install guide (`/documents/ari-os/install`).
  - `content/posts/ari-os/using-it.mdx` — using-it / spec-first deep-dive (`/documents/ari-os/using-it`).
  - `content/posts/ari-os/brain.mdx` — Cortex brain (`/documents/ari-os/brain`).
  - `content/posts/ari-os/advanced.mdx` — advanced.
- **Public diagram assets:** `public/posts/ari-os/overview-hero.png`, `public/posts/ari-os/loop.png`.

External refs to re-fetch if stale:
- `https://github.com/PUSHINGSQUARES/ARI-OS` — repo (verify public + that the org/repo casing is unchanged).
- The `version 2.0.0` and `PolyForm Noncommercial licence` claims are body prose, not machine-readable — re-read the `.mdx` before quoting either.

> Backfilled 2026-07-18 from the published body; not needle-extracted at thought-time.