# AtoCore Operations

Current operating order for improving AtoCore:

1. Retrieval-quality pass
2. Wave 2 trusted-operational ingestion
3. AtoDrive clarification
4. Restore and ops validation

## Retrieval-Quality Pass

Current live behavior:

- broad prompts like `gigabit` and `polisher` can surface archive/history noise
- meaningful project prompts perform much better
- ranking quality now matters more than raw corpus growth

Use the operator client to audit retrieval:

```bash
python scripts/atocore_client.py audit-query "gigabit" 5
python scripts/atocore_client.py audit-query "polisher" 5
python scripts/atocore_client.py audit-query "mirror frame stiffness requirements and selected architecture" 5 p04-gigabit
python scripts/atocore_client.py audit-query "interferometer error budget and vendor selection constraints" 5 p05-interferometer
python scripts/atocore_client.py audit-query "polisher system map shared contracts and calibration workflow" 5 p06-polisher
```

What to improve:

- reduce `_archive`, `pre-cleanup`, `pre-migration`, and `History` prominence
- prefer current-status, decision, requirement, architecture-freeze, and milestone docs
- prefer trusted project-state when it expresses current truth
- avoid letting broad single-word prompts drift into stale chunks

## Wave 2 Trusted-Operational Ingestion

Do not ingest the whole PKM vault next.

Prioritize, for each active project:

- current status
- current decisions
- requirements baseline
- architecture freeze / current baseline
- milestone plan
- next actions

Useful commands:

```bash
python scripts/atocore_client.py project-state p04-gigabit
python scripts/atocore_client.py project-state p05-interferometer
python scripts/atocore_client.py project-state p06-polisher
python scripts/atocore_client.py refresh-project p04-gigabit
python scripts/atocore_client.py refresh-project p05-interferometer
python scripts/atocore_client.py refresh-project p06-polisher
```

## AtoDrive Clarification

Treat AtoDrive as a curated trusted-operational source, not a generic dump.

Good candidates:

- current dashboards
- approved baselines
- architecture freezes
- decision logs
- milestone and next-step views

Avoid by default:

- duplicated exports
- stale snapshots
- generic archives
- exploratory notes that are not designated current truth

## Restore and Ops Validation

Backups are not enough until restore has been tested.

Validate:

- SQLite metadata restore
- Chroma restore or rebuild
- project registry restore
- project refresh after recovery
- retrieval audit before and after recovery

Baseline capture:

```bash
python scripts/atocore_client.py health
python scripts/atocore_client.py stats
python scripts/atocore_client.py projects
```