Resource
Plain-English definitions for the vocabulary of AI systems, automation, and operational verification. Written for leaders evaluating or deploying AI in their organization, not for engineers.
The uncontrolled, inconsistent growth of a folder or file structure over time. It shows up as duplicate homes for the same kind of content, naming conventions that drift from folder to folder, and structure that no longer matches whatever documentation was meant to govern it. Sprawl is often confused with simple depth, but the two are different problems: a deeply nested structure can be perfectly clean if every level is deliberate and consistent, and a shallow structure can still be sprawling if it grew ad hoc. The tell for sprawl is not how many levels deep something is, it's whether new content keeps landing in the right place without anyone having to think about it.
To compare two versions of something (two files, two folders, two document drafts) item-by-item and identify exactly what's only in one, only in the other, or changed between them. Same root as a software "diff" in version control. Useful any time two things are supposed to be identical, such as a backup, a synced folder, or a migrated copy, and you need to actually prove that rather than assume it.
The one version of something treated as the authoritative source when more than one copy exists. Calling something the "sole canonical copy" is a deliberate statement that it's the only version anyone should read from or edit going forward; everything else is a mirror, backup, export, or derivative that should defer to it, never the other way around. The term shows up constantly in any system with duplicated or synced data (files, folders, databases, documentation) because without naming one copy canonical, it's ambiguous which version is "true" when two versions disagree.
The three digit code a web server returns with every response. 200 means it responded, 404 means the resource was not found, 403 means access was refused, 500 means the server itself failed. Useful as a first signal and insufficient as a final answer, because a server can return 200 while sending something entirely different from what was requested.
The declared format of what a server actually sent, for example an image or a web page. When you are verifying that something worked, content type is the more meaningful check, because it reveals cases where the request succeeded but the response was the wrong thing.
A request that returns a success code while delivering the wrong thing entirely. In web systems, a server can answer 200 OK while actually serving an error page, a login redirect, or a placeholder. Anything checking only the status code sees success. This is the concrete, everyday version of a broader principle: a green signal is evidence that something responded, not evidence that it responded correctly. Always verify the content, not just the code.
Confirming the part of a system you touched, then treating the entire system as verified. The check that was performed was real, which is what makes this so easy to miss. It just covered a narrower scope than the confidence it produced. Confirming that a change was saved is not the same as confirming the change had an effect, and the gap between those two is where a surprising number of production failures live.
An automated process that runs on schedule, reports success, and accomplishes nothing. The job starts, the log turns green, and no actual work happens. It is one of the most common and most expensive failures in automated systems, because every dashboard says everything is fine. The cause is almost always that the system measures execution rather than output: it checks whether the job ran, not whether the job did anything. The fix is to monitor results, not activity.
Running a case with a known outcome alongside the case you are actually investigating, so that a failure is distinguishable from a broken test. Without a control, an inconclusive result and a negative result look identical. It is a basic experimental discipline that is routinely skipped in technical troubleshooting, and skipping it is how teams confidently reach the wrong conclusion.
Adding a unique value to a request to force a fresh response rather than a stored copy. Used when diagnosing whether you are looking at current state or at something a cache is holding onto. A useful habit before concluding that a fix did not work.
A reusable set of instructions an AI system loads when a matching situation appears. A skill defines how a particular kind of task should be done, encoding standards and procedure so the same work is performed consistently rather than improvised each time. Skills do not run on their own; they shape behavior when relevant work arrives.
An instruction set that runs automatically on a clock, whether or not anyone is present. Scheduled tasks are where automation delivers compounding value and also where it fails most quietly, because nobody is watching at the moment they run. Any scheduled task worth having is worth monitoring for output rather than execution.
A task set to run automatically at a fixed time or on a recurring schedule, defined by a compact five-part time pattern, minute, hour, day of month, month, day of week, known as a cron expression, for example one meaning "every day at 6:45 AM." The name comes from cron, the decades-old Unix scheduler this pattern originated in. It's now the standard way automated systems, including AI scheduled tasks, express recurring timing.
An AI system given a goal, a set of tools, and permission to decide its own steps, rather than following a fixed script. Agents are more capable than scripted automation and correspondingly harder to supervise, because the path they take is not known in advance. The practical requirement is not smarter agents but clearer boundaries: defined scope, defined tools, and a defined point where a human decides.
An open standard that lets AI systems connect to external tools and data sources such as email, calendars, file storage, and business applications. It matters because it turns an AI from something that talks about your work into something that can act on it. It also means access, permissions, and scope become real operational concerns rather than theoretical ones.
An authorized link between an AI system and an external account. Connectors are scoped and revocable, which is what makes them safe, and their scope is frequently narrower than people assume. A common source of confusion is an AI reporting that something does not exist when it simply falls outside what that particular connection was authorized to see.
Where standing rules for an AI system live. Most platforms have several layers: global instructions that apply everywhere, project or workspace instructions with narrower scope, and reference material loaded only on demand. Knowing which layer is guaranteed to load is essential, because a rule written into a layer that does not load is documented rather than active, and it will appear to be working right up until it matters.
How much information an AI system can hold in working memory at once. When it fills, earlier detail degrades, which is why long sessions drift, repeat themselves, or lose established decisions. Practical implication: durable decisions belong in a document, not in a conversation.
Output stated confidently that is not grounded in any real source. The risk is not that AI systems are wrong sometimes, it is that wrong output arrives with the same fluency and confidence as correct output. This is why verification steps and source citation matter more than model quality in most business deployments.
An automated process still faithfully following instructions that no longer match the document meant to govern it. Nothing errors and nothing alerts. The procedure and the practice simply diverge over time, and the gap is usually discovered by accident, often long after it started causing damage. Preventing it requires periodically checking the live system against its documentation rather than assuming they match.
Two or more AI sessions working at the same time on related material. Sessions do not share state, so each can act on the same resource without knowing the other exists, including undoing each other's work. As organizations deploy more agents, this becomes a foundational design question rather than an edge case: what is the shared source of truth, and how does one agent learn what another already changed?
A required human approval before an action that is difficult or impossible to reverse. The practical rule is to place approval gates around anything that sends, spends, publishes, or deletes, and to let everything else run unattended. The goal is not to supervise AI constantly, it is to be deliberate about which decisions stay human.
The two-tool pattern behind targeted retrieval. One tool finds files by name or pattern; the other searches inside file contents for a match. Together they let an AI system have broad access to a folder of information without pulling all of it into working memory at once. This is the mechanism that makes wide access and a manageable context window compatible: an AI can reach everything in a connected folder while only the specific files relevant to the question at hand are actually read.
Manually attaching a document to an AI project or workspace even though the AI already has broader access that would let it find that same document on its own. The redundancy is deliberate: it guarantees a specific piece of context loads automatically at the start of every session, rather than depending on the AI to retrieve it when relevant. Worth reserving for a small set of genuinely load-bearing documents, since doing it for everything defeats the purpose of having broad access at all.
A specialized agent that a primary agent creates to handle one bounded piece of work, with its own working memory and a narrower set of tools, before reporting its result back and closing. Subagents exist mainly to protect the parent agent's own working memory: the exploratory searching, reading, and trial-and-error involved in a subtask stay contained inside the subagent rather than crowding out everything else the parent needs to remember. A useful mental model is a specialist a manager delegates a narrow task to, rather than doing the research personally.
A distributable bundle that packages skills, specialized agents, and connections to outside systems together so they can be installed as a single unit. A plugin is the package; a skill is one instruction set inside it. Plugins are how AI capability spreads in practice: rather than building a capability from scratch, an organization installs a plugin someone else built and gets its skills, agents, and connections all at once.
OpenAI's version of a saved, custom-configured AI assistant: built from custom instructions, uploaded reference material, and a chosen set of tools, layered on top of ChatGPT. It is closer to a saved project setup than to a fully autonomous agent, since it is mostly a persona and a knowledge scope rather than something that takes multi-step action on its own. OpenAI has begun evolving this concept toward more autonomous agent products, which is the direction the whole industry is heading.
Google's version of a saved, custom-configured AI assistant inside Gemini, built from a name, instructions, and reference material. It serves the same basic purpose as OpenAI's custom GPTs: save a configuration once instead of re-explaining context every conversation. Of the major platforms' equivalents, it is generally the lightest-weight, closer to a saved prompt than to an autonomous agent that takes action on its own.
A short, paste-ready block of the essential facts from a finished session or project, written so a person can drop it into a brand-new AI conversation and have the assistant pick up right where things left off, without re-explaining everything from scratch. The same idea shows up across the AI industry under different names: some call it a 'seed,' others describe it as part of 'context engineering' or 'context rehydration.' Whatever the name, the practice is the same: rather than carrying a full conversation history forward, carry forward only the load-bearing facts a fresh conversation actually needs.
This glossary is generated from the same working knowledge base behind BK Blueprint's own operations, not written as marketing copy. Structured as schema.org DefinedTermSet data so AI answer engines can parse it directly, and synced from source on a monthly cadence so it never goes stale.