# AISLE local operator kit

A mirror of the public shelf plus the production contract, installed on your own
machine. It is the part of a Local Setup that keeps working when the hosted site
is capped, offline, or behind a bad connection: the rows, prices, teardowns,
formats, scoring config and the brief template all live as files you control.

Read the whole thing before you hand it to a team. Five minutes here saves a
week of "why did the agent invent that hook".

## What is installed

| Path | What it is |
| --- | --- |
| `skill.md` | The production skill: formats, gates, and the acceptance contract |
| `llms.txt` | Agent-readable map of the whole site |
| `data/products.json` | Product rows with scores and source posts |
| `data/rows.json` | Full measured row set |
| `data/prices.json` | Retail prices with the page they were read from |
| `data/research_index.json` | Product, niche and creator index |
| `data/teardowns.json` | Short teardowns with hooks, beats and reasons |
| `data/formats.json` | The format library with beat timings |
| `data/library.json` | Skill and playbook manifest |
| `data/rates.json` | Measured benchmark rates |
| `data/stack.json` | Vendor and model comparison data |
| `brief.template.md` | The shoot-ready brief, with all seven gates |
| `acceptance-criteria.json` | The same gates as machine-readable pass/fail rules |
| `config.json` | Your base URL, niches, brands and seat count |

## Install

Windows (PowerShell):

```powershell
.\install.ps1 -Into C:\work\aisle-local
```

macOS / Linux:

```bash
chmod +x install.sh
./install.sh https://sauce-ops.appskins-studio.workers.dev ./aisle-local
```

Both installers fetch every file from `manifest.json`, check that each one has
the expected minimum size, copy the templates, write `config.json`, and print
`LOCAL SETUP VERIFIED`. A short or missing file is a hard failure, not a warning.
To aim at another deployment, pass its URL as `-Base` (PowerShell) or as the
first argument (bash).

## Run without the hosted site

1. Point your agent at this folder, not at the website. `skill.md` is the
   instruction file; `data/*.json` is its evidence.
2. Pick a niche in `config.json`. The `niches` array is the allowlist: a brief
   outside it is a bug, not creativity.
3. For each row you want to remake, fill `brief.template.md` from the local
   JSON. Never fill a field from memory. If the source row cannot be found
   locally, stop and record the gap.
4. Run the seven gates in `acceptance-criteria.json` before you call a brief
   done. A brief that fails a gate is a draft.
5. Keep the JSON files in version control beside your briefs. That is what makes
   a decision auditable three months later.

## The seven gates

A brief passes only when all seven pass. They are deliberately boring:

1. **source** — a real row id and a reachable source URL
2. **hook** — the first-frame line is present and under 20 words
3. **beats** — at least three timed beats, in order
4. **proof** — the proof shot is described, not implied
5. **mechanism** — the product claim is stated in one sentence
6. **price** — a price and currency, with where it was read
7. **criteria** — a pass/fail check that a shooter can run on set

## Boundaries

This kit reads and remakes measured organic posts. It does not place ads, hold
a wallet, scrape a new platform, or guarantee a result. It does not contain
client secrets. Keep your own model keys in your own environment, never in
`config.json`.

A Local Setup engagement installs and validates this kit on your machines,
wires your niches and brands, and hands over a runbook your team can follow
without the founder in the room. The download is the same contract in a
self-serve form.
