Inventory operating knowledge. The audit exposes what lives only in someone's head, lacks a backup, or has gone stale.
The bundled inventory contains four supplied knowledge rows. At the ninety-day threshold one is head only, two have no named backup, two are stale and two pass the source readiness predicate. Bars share one hundred pixels per row and compare four total rows with two ready rows. Adding one plus two plus two flags gives five, but they overlap on the same records and do not mean five distinct processes. These flags inspect entered strings and ages, not actual access, knowledge quality or employee performance. The saved ninety-day threshold marks ages one hundred twenty and two hundred ten stale, giving two rows. Raising the entered threshold to one hundred twenty leaves only the two hundred ten-day row stale, giving one. Bars share one hundred seventy pixels per stale row. Exactly one hundred twenty is not stale under the greater-than condition. The contractor record still lacks a backup, so removing its stale flag does not alone make it ready. A chosen age threshold is a rule of this audit, not proof of current operational reliability. Ready requires the location not be head only, a nonempty backup and age at or below threshold. If the two unready bundled rows are hypothetically entered with shared locations, named backups and thirty-day verification ages, the count changes from two to four. Bars share one hundred pixels per row. This counterfactual clears source flags, but entering a backup name does not demonstrate that person can access or perform the work. Inventory completeness, record quality, automation feasibility and business value remain outside this audit.