# Chorus Sandboxes

This directory is the **working area for your own Chorus sandboxes**.

Each sandbox is a self-contained knowledge project that you build with the
`chorus-pdf`, `chorus-feed`, `chorus-check`, `chorus-create-project` and
`chorus-strengthen` commands.

## Getting started

```bash
# 1. Provide a corpus (plain text or PDF)
chorus-pdf  my-project  corpus/my-standard.pdf     # optional — PDF extraction
chorus-feed my-project  corpus/001-my-standard.txt # build the knowledge base

# 2. Create a project to validate
chorus-create-project my-project --batch

# 3. Validate the project
chorus-check my-project --all
```

The sandbox directory `my-project/` will be created automatically inside
this `sandboxes/` directory the first time you run `chorus-feed my-project`.

## Sandbox anatomy

```
sandboxes/
  my-project/
    corpus/          ← source documents (numbered NNN-<slug>-text.txt or -vision.md)
    agent/
      chorus/        ← knowledge base org files (index.org + <slug>.org per agent)
      .kb-hash       ← local artefact — not committed
    lib/<Namespace>/
      Agent/<Slug>/
        Helpers.pm   ← generated by chorus-feed
    rules/<slug>/
      R<NN>-<slug>.yml ← YAML rules
    run.pl           ← generated by chorus-check
    projet*.json     ← project files (runtime input)
    README.org       ← sandbox notes
```

## Example sandbox

`demo_en` — timber-frame construction compliance (English)
against BS EN 338, EC5, Building Regulations Part L/B, BS EN 13501-1.

```bash
perl sandboxes/demo_en/run.pl sandboxes/demo_en/project-01.json
```

Agents: `qualification` · `domain` · `fire` · `compliance`

## Notes

- This directory is listed in `.gitignore` — your own sandboxes are **not committed**
  to the Chorus Engine repository.
- Only this `README.md` and the `demo_en/` example sandbox are tracked by git.
