Editorial use
How to interpret a coverage result
The Capability Gap Tracker answers one narrow question: for each of the eight capital priorities in the Dependency Atlas, how many entries in the Claw & Talon research database currently look like they address that priority? The answer is produced by deterministic rules — sector weights and keyword patterns that are published with the dataset — rather than by judgment calls made out of view. That design choice matters more than any individual count. When a company appears under a priority, the correct response is not to treat it as vetted; it is to open the match criteria, see which sector weight and which keyword produced the match, and then decide whether the underlying evidence supports the connection.
Coverage bands are deliberately coarse. Uncovered means no database entry matched the published criteria. Thin means fewer than five did. Moderate covers five to fourteen, and Dense means fifteen or more. The bands compress a noisy signal into something a reader can compare across priorities, but the compression cuts both ways: a Dense band can hide the fact that most matches are early-stage or weakly verified, and a Thin band can hide one genuinely strong company. The per-priority density score and the entity-type and sector breakdowns exist so that readers can look underneath the band before quoting it.
The most tempting misreading is to treat a gap as an opportunity. A priority with thin coverage is not automatically a place where capital would be well spent. The gap may exist because the capability is supplied by established industrial companies that sit outside a startup-oriented database, because the work happens inside government programs that never appear in public sources, or because the economics of the niche are genuinely poor. Equally, the gap may be an artifact of this database's composition: the collection skews toward cybersecurity, defense, and deep tech, so civilian categories can look thinner than the real economy warrants. A gap is a prompt for a specific research question — who actually supplies this capability today, and on what terms — not a conclusion that nobody does.
Dense coverage deserves equal suspicion in the opposite direction. A crowded band tells you the database has many entries whose public descriptions match the priority's criteria. It does not tell you whether those companies compete in the same layer, whether any of them has qualified production capacity or paying customers, or whether the priority's real bottleneck is even addressable by the kind of company a database like this tracks. The useful move with a dense band is comparative: filter by entity type to separate private startups from public companies and acquired assets, filter by sector to see which bucket carries the count, and then follow the profile links to check sources and verification status one company at a time.
Results should also be read against the date of the underlying data. Company status, product direction, and public evidence change quickly, and the Atlas priorities themselves are re-scored as new source data arrives. The tracker is a map of where the research record currently shows activity against a published strategic thesis. It is a starting point for diligence questions — never a substitute for them, and never a current verification report.