Merlin

Merlin

This page explains what Merlin is and the principles that govern it — not a feature list or a status report. For what Merlin can actually do today, and how thoroughly each surface has been validated, see Capabilities.

What Merlin Is

Merlin is not a chatbot added to KEEP. It's the single AI identity inside KEEP — the same name, the same authority model, and the same voice wherever it appears, so a Director or technician never has to learn a new mental model of what Merlin is allowed to do when it shows up on a new screen. (Source: Merlin architecture documentation)

Merlin exists to make the person who's already responsible for a decision faster and better-informed at making it — not to make the decision itself. That's consistent with KEEP's own positioning: KEEP is not a certification authority and does not substitute for human judgment, and Merlin inherits that constraint directly. (Source: Merlin architecture documentation)

Philosophy

One line, true on every surface Merlin appears on: Merlin discovers. The Director decides. The corollary governs every interaction without exception: Merlin is an advisor by default, and an executor only when a human authorizes it. (Source: Merlin architecture documentation)

Independent of Any Single AI Provider

Merlin is KEEP's governed orchestration and policy layer — not the underlying language model. The AI provider behind Merlin's reasoning is a replaceable implementation detail, not part of Merlin's identity. Replacing that provider never changes Merlin's identity, governance, authority, or the fact that every action it takes is logged. (Source: Merlin architecture documentation)

Where Merlin Shows Up

Merlin currently appears on three surfaces: reviewing a device's incident and event history to produce a plain-English diagnosis; reviewing a new client's onboarding scan results to produce a prioritized remediation brief; and reading an incident's full thread to suggest next steps and keep a Director informed. For current status and how each has been validated, see Capabilities.

How Merlin Is Governed

Merlin's reasoning never receives a password, key, or credential. When a human authorizes an action that actually requires one, the credential is entered directly into KEEP and used by KEEP's own server code — Merlin's reasoning and any credentialed action are always two separate steps. (Source: Merlin architecture documentation)

Merlin has no standing authority of its own. It only ever acts within whatever the requesting or authorizing person is already permitted to do — it never assumes broader access than that, and a Director decides, surface by surface, how much authority Merlin is granted. (Source: Merlin architecture documentation)

Some actions — altering or deleting an audit record, for example — Merlin is never permitted to take, regardless of who asks or what authority they hold. (Source: Merlin architecture documentation)

Every action Merlin performs is logged as part of KEEP's permanent record — no exception. (Source: Merlin architecture documentation)

Frequently Asked Questions

Is Merlin a chatbot?No. Merlin is an identity that appears across KEEP's existing screens — it doesn't compete with the rest of the product as a separate way of working, it reasons about the same real state those screens show.

What AI does Merlin use, and can that change?The underlying provider is an implementation detail that can change without changing what Merlin is, how it's governed, or what it's allowed to do. (Source: Merlin architecture documentation)

Can Merlin take action on my network without my approval? No. Merlin is an advisor by default and only ever executes an action when a human has authorized it. (Source: Merlin architecture documentation)

Does Merlin ever see my passwords or keys?No. Merlin's reasoning only ever receives descriptive information — never a credential. (Source: Merlin architecture documentation)

What can Merlin do today? See Capabilities for the current, conservatively classified list.

For the architecture behind KEEP as a whole, see How KEEP Works. (Source: KEEP architecture documentation)

Continue to Capabilities

For what Merlin and the rest of KEEP can do today, and how thoroughly each capability has been validated, see Capabilities.