CrewWhy an item is not proven
Not proven means Crew cannot confirm the evidence for an item marked Done. It does not mean Crew has established that the work failed.
For an ordinary code item, Crew needs the listed commits and a version build or current project revision to check them against. Every listed commit must be included in that revision. An unchecked commit remains unproven.
Common reasons include:
- No commits were recorded for the item.
- Crew has no build or current revision to check.
- A listed commit is not included in that revision, or has not been checked yet.
- Git is unavailable, cannot read the folder, or the folder is not its own repository.
These Git conditions are different. A folder without a repository does not prove that Git needs installing. Use the reported reason rather than assuming that installing tools will fix every case.
Documentation items use a recorded link as their evidence. Historical releases explicitly recorded under the legacy rule retain that rule's treatment; they are not reinterpreted as new work.
Changing a status word does not supply missing evidence. Until the evidence is available, Crew leaves the item out of its proven-done count.