Coverage

AppThentic does not claim to know your whole business. It shows coverage: how much of each area has an owner, an approved reason, and current evidence.

What coverage shows

For each area (a service, a domain, a team):

• Rules found, and how many are Approved, Inferred, Disputed, Stale or Unknown.
• Rules with a single knowledgeable person: the places where one departure would leave nobody able to explain.
• Rules nobody owns.
• Rules changed since approval.

Why it matters

A sample is not the whole. If 15 of 50 services have approved rules, AppThentic says 15 of 50, not “understood”. Leaders see exactly where the risk sits instead of trusting a summary.

Research on open-source projects found that 46% of popular GitHub projects depend on a single developer for most of their knowledge, and 28% on just two (Avelino et al., 2016). Most companies have never measured the same thing in their own systems. Coverage is how you measure it.

Using coverage

• Plan where AppThentic asks next: high-change areas with low coverage first.
• Plan offboarding: rules that only a leaving person can explain. See When someone leaves.
• Report honestly to auditors and leadership. See Audit and compliance.