Glossary
The vocabulary of execution intelligence.
Definitions for the core concepts behind InteliG. Plain English, no marketing.
-
Autonomous Intelligence
The category InteliG is building. A system that reads engineering execution, derives strategy from it, and explains it back to the business without anyone maintaining metadata.
Read the definition -
Execution Intelligence
The platform category InteliG occupies. Platforms that read engineering reality where it lives — commits, pull requests, deployments, meetings — and reason across all of it.
Read the definition -
Initiative Discovery
An InteliG capability that reads a codebase's commit and pull-request history and proposes a structured strategy — themes, initiatives, workstreams — without requiring any manual declaration.
Read the definition -
Atomic Code Linking
The InteliG capability that automatically attributes every commit to its corresponding initiative, without requiring developers to maintain ownership rules, tickets, or labels.
Read the definition -
DORA Metrics
Four measures of software delivery performance: deployment frequency, lead time for changes, change failure rate, and time to restore service. They benchmark how well a team ships, not whether it ships the right work.
Read the definition -
Cycle Time
The elapsed time from the first commit on a unit of work to the moment it reaches production. A flow metric for delivery speed that says nothing about what was built or whether it mattered.
Read the definition -
Bus Factor
The number of people who would have to leave a project before it stalls for lack of knowledge. A low number signals dangerous knowledge concentration, but the raw figure is only meaningful with team size as context.
Read the definition -
Lead Time for Changes
Lead Time for Changes is the elapsed time from a code change being committed to that change running in production. It is one of the four DORA metrics and measures how long it takes work to travel from a developer's keyboard to live users.
Read the definition -
Deployment Frequency
Deployment Frequency is how often a team ships code to production over a given period. It is one of the four DORA metrics and a common proxy for delivery throughput.
Read the definition -
Change Failure Rate
Change Failure Rate is the share of deployments to production that cause a failure requiring remediation, such as a hotfix, rollback, or patch. It is one of the four DORA metrics and a measure of release stability.
Read the definition -
Mean Time to Recovery (MTTR)
Mean Time to Recovery (MTTR) measures how long it takes to restore service after a production failure, from the moment an incident starts to the moment normal operation returns. It is one of the four DORA metrics and a proxy for how resilient your delivery system is under failure.
Read the definition -
Code Churn
Code churn measures how much recently written code gets rewritten, reworked, or deleted within a short window after it was first committed. It is a signal of code that is not settling.
Read the definition -
Pull Request Throughput
Pull Request Throughput is the number of pull requests a team or individual merges in a given period. It is a count of completed review-and-merge units, used as a proxy for delivery pace.
Read the definition -
Work in Progress (WIP)
Work in Progress (WIP) is the count of units of engineering work that have been started but not yet finished, such as open branches, unmerged pull requests, and tickets in active development. It measures how much work the team is carrying at once rather than completing.
Read the definition -
Flow Efficiency
Flow Efficiency is the percentage of total cycle time that a unit of work spends being actively worked on versus sitting idle in queues, waiting on reviews, builds, or handoffs.
Read the definition -
Code Review Coverage
Code Review Coverage is the share of merged code changes that passed through a human review before reaching the main branch. It tells you how consistently changes are inspected, not whether the review caught anything that mattered.
Read the definition -
Sprint Velocity
Sprint velocity is the amount of work, usually measured in story points or completed tickets, that a team finishes within a fixed sprint. It is used to forecast how much a team can take on in the next sprint based on its recent average.
Read the definition -
Story Points
A story point is a unitless number a team assigns to a backlog item to estimate its relative effort before work begins. It measures perceived size, not value delivered or strategic fit.
Read the definition -
Code Ownership
Code ownership describes who is responsible for a given part of a codebase, typically measured by which contributors author and review the changes to specific files, directories, or services. It is a way of mapping people to the code they create and maintain.
Read the definition -
Technical Debt
Technical debt is the accumulated cost of code, architecture, and tooling shortcuts that make future changes slower and riskier than they need to be. It is interest the team pays on every change that passes through the affected code.
Read the definition -
Commit Frequency
Commit Frequency is the rate at which contributors push commits to a repository over a given period, usually counted per author, per day, or per week.
Read the definition -
Time to First Review
Time to First Review is the elapsed time from when a pull request is opened to when a reviewer leaves the first substantive comment or approval. It measures how quickly code waiting on a human gets a first response.
Read the definition