Coverage
Coverage is the central measure in Auwai. It is not the same as reading every byte into one prompt.
First-party scope
A file is first-party when it belongs to the service or tool and can be changed by a human or an agent.
Included by default:
- source code in any supported language;
- tests and fixtures;
- documentation such as README and design pages;
- configuration such as TOML, YAML, JSON, and INI;
- infrastructure such as Terraform, Helm, Kubernetes, and Puppet;
- migration and schema files;
- build and packaging files that describe the project.
Excluded with a reason:
- vendor, third_party, external, and dependency directories;
- node_modules, virtual environments, and package caches;
- generated files, source maps, minified assets, and lock files;
- build output such as dist, build, target, and obj;
- binary and archive files;
- the
.gitand.auwaidirectories.
The exclusion list is in skills/auwai/scripts/scope.py.
A project can add a reason in the future scope policy file.
The current implementation records the reason in the ledger.
Coverage states
| State | Meaning |
|---|---|
| indexed | The chunk exists in the index |
| mapped | The chunk has a partition and a deterministic label |
| read | The chunk body was returned by a read segment |
| finding | At least one finding is attached to the chunk |
| stale | The source changed after the indexed read |
A chunk can be read without a finding. The coverage report separates the two so a read that taught nothing is visible.
Coverage certificate
auwai fullread verify reports the first-party chunks that remain unread.
A complete pass has no unexplained unread chunk.
The report includes the plan, the coverage counts, and the unread list.
The certificate does not claim that the model understood the code. It claims that every first-party chunk was scheduled and read or skipped with a reason.