# Parallel Agent Strategy

GeoIntel can use multiple Codex agents only when their work areas do not conflict.

## Safe parallel tracks

### Track A — Backend foundation

Allowed paths:

- `backend/`
- `tests/backend/`
- database docs when needed

Do not touch frontend except API contract comments.

### Track B — Frontend shell

Allowed paths:

- `frontend/`
- `tests/frontend/`
- UI docs when needed

Do not change API contracts without coordination.

### Track C — Documentation/runbooks

Allowed paths:

- `docs/`
- `prompts/`
- `skills/`
- `checklists/`

Do not change implementation code.

### Track D — Fixtures/tests

Allowed paths:

- `tests/fixtures/`
- `fixtures/`
- `scripts/`
- test docs

Do not alter production services except to expose stable test hooks.

## Unsafe parallel work

Do not run parallel agents on:

- database schema plus API schemas unless coordinated;
- API contracts plus frontend client generation unless coordinated;
- storage paths plus dataset manager unless coordinated;
- detection output schemas plus QA/QC engine unless coordinated.

## Worktree naming convention

```text
worktrees/
  geointel-backend-foundation
  geointel-frontend-shell
  geointel-qaqc-engine
  geointel-docs-control
```

## Merge order

1. governance/docs updates;
2. database/domain foundation;
3. backend APIs;
4. frontend API client;
5. UI pages;
6. tests/fixtures;
7. polish.

## Parallel agent completion report

Every agent must report:

- branch/worktree name;
- files changed;
- contracts touched;
- tests run;
- merge risks;
- required follow-up from other tracks.