Frequently asked questions
Common questions about how Scryable works, how metrics are calculated, and what to do when something looks unexpected.
Churn ratio rises when recently-written code gets rewritten or deleted shortly after being committed. The most common causes are: AI-generated code that needed immediate correction, a codebase in active refactoring, or early-stage exploratory work where direction changes frequently.
Before treating a high churn ratio as a problem, compare it against your pre-AI baseline. If churn was already elevated before AI adoption, the current figure may reflect the nature of the work rather than AI tool quality. If churn has risen significantly since your baseline date, that's worth investigating.
Scryable does not read source code, so it cannot identify AI-generated lines directly. What it measures is the statistical patterns associated with AI-assisted development: changes in commit volume, churn rates, burst patterns, and line change velocity, all compared against your pre-AI baseline. These patterns don't identify individual AI-authored lines, but they do surface whether AI adoption has changed your team's output in measurable ways.
The most common causes of unexpected figures are: the date range not covering the period you intended; the outlier filter including or excluding commits you didn't expect; branch filters that include feature branches with unusual patterns; or a pre-AI baseline date set after AI tools were already in use, which compresses the comparison.
Check the date range display at the top of the sidebar and the active filter counts next to each section. If the issue persists, email support@scryable.ai with a description of what you're seeing.
Developers whose commits appear in a connected repository can request access to their own data directly from Scryable. This is a right under UK GDPR and applies regardless of whether their employer has given them access to the dashboard. See the privacy page for how to make a request.
Whether developers have live access to the dashboard is controlled by the account holder. Workspace access is managed in Settings.
For each metric, the baseline is calculated using the same date range length as your current selection, ending on your baseline date. If you're viewing a 30-day window, the baseline shows the 30-day period immediately before your baseline date. The comparison is always between periods of equal length, regardless of which preset you've selected.
Commits can be excluded for a few reasons: they fall outside the selected date range; they are on a branch that is currently deselected; or they were made by an author who is deselected. If the outlier filter is active, commits above the P95 or P99 threshold are excluded from charts and aggregate stats, though they remain visible in the commit explorer.
If you've checked all filters and commits are still missing, it's possible the initial import didn't complete fully. Contact support and we'll investigate.
Scryable syncs connected repositories on a regular schedule. New commits typically appear within a few minutes of being pushed. The data freshness indicator in the top bar shows when the last sync completed.
Disconnecting a repository removes its data from your dashboard within 30 days. Closing your account removes all associated data within 30 days, except billing records retained for 7 years as required by UK tax law. Full details are in the privacy policy.
Email support@scryable.ai. We update this documentation based on the questions that come in, so if something is missing it's useful to know.