Auwai

Workspace workflow

A workspace is a virtual repository made of several repositories.

Create

./auwai workspace init /path/to/workspace --name demo --target /path/to/workspace/target
./auwai workspace add /path/to/repo-a /path/to/repo-b --workspace demo

Each repository keeps its own .auwai index. The workspace stores its manifest under .auwai/workspace.

Survey

./auwai workspace survey --workspace demo --context-window 262144
./auwai workspace survey --workspace demo --context-window 262144 --json

The survey prints the virtual tree and the segment plan. A segment can span repositories. A chunk id is qualified with the repository name.

Full read

The workspace has its own plan and coverage ledger. It never duplicates the per-repository indexes.

./auwai workspace fullread plan --workspace demo --context-window 65536
./auwai workspace fullread next --workspace demo
./auwai workspace fullread read --workspace demo --segment read-1
./auwai workspace fullread done --workspace demo --segment read-1 \
  --summary "read the workspace segment"
./auwai workspace fullread status --workspace demo
./auwai workspace fullread verify --workspace demo

A plan is refused when an unfinished plan exists unless --force is passed. --force resets the workspace coverage ledger. A read segment cannot be done until every planned chunk has complete workspace coverage. A synthesis segment has no source bodies and closes after the findings review.

State lives in .auwai/workspace/fullread.json and .auwai/workspace/coverage.sqlite. Chunk ids are qualified with the repository name at the workspace boundary.

Work

./auwai workspace status --workspace demo
./auwai workspace brief --workspace demo
./auwai workspace map repo-a repo-b --workspace demo
./auwai workspace search "session token" --workspace demo
./auwai workspace read repo-a:ID --workspace demo
./auwai workspace record --batch findings.jsonl --workspace demo
./auwai workspace decide --batch decisions.jsonl --workspace demo

The workspace brief is the handoff digest. It contains the decisions, the findings, and the next reads.

Current limits

Cross-repo categories are tags, not separate nodes. The workspace ledger records virtual coverage; each repository ledger remains authoritative for its own reads. The runner does not call a model. The agent or a harness drives the read loop.