Guides

Task-shaped walkthroughs: each one starts from something you are trying to do and ends with it done. The system documentation is the other half — it explains how Watchdog works rather than what to do with it.

From GitHub App to your first baseline
Connect a repository and read the result — what the first number means, and what it does not.

A finding is a work packet
How to hand a finding to whoever fixes it, with enough context that they do not have to re-derive it.

Code rots even when no one commits
Why a scheduled survey and a daily security watch answer different questions.

Architecture drawn from the code
C4 containers, boundaries and coupling, derived rather than declared.

Security is not a CVE list
What a repository-level security read adds to dependency scanning.

Which gate to add first
Sequencing CI checks by what the measurement says, not by what is easiest to switch on.

Read-only as a design principle
What a security reviewer will ask, and the answers.