Boltcliq product / AI context, memory and governance
/ Control PlaneDecide what every agent may know, remember and do. Monolith is the context, memory, governance and permissions system that makes AI agents safe to trust with real business data.
An agent should know what it needs, remember what it may, and do only what it is allowed.
01Control plane
An AI agent is only as safe as the data and tools it is given. Most teams start by pasting data into a prompt and wiring a few tools to a model. It works in a demo. In production it raises questions that nobody has answered. Which records may this agent read? What does it remember between conversations, and can that memory be erased? Which models may receive customer data? Who can switch it off?
Monolith answers those questions in one place. It registers each agent with an owner, a version, a purpose and a set of permissions. When a task starts, it assembles context: the objects, documents and memories relevant to the task, filtered for both the person asking and the agent. Memory has provenance and retention rules, and it can be forgotten when the law or a customer requires it.
Monolith also sits on the path between agents and everything they touch. Sensitive actions can require human approval, and any agent can be stopped with a kill switch. Monolith governs, and Argus stores and runs. Monolith policy is evaluated through Odin, so there is still only one decision point.
02
Decide what every agent may know, remember and do. Monolith is the context, memory, governance and permissions system that makes AI agents safe to trust with real business data.
03In five steps
human
Every agent is entered in a registry with an owner, a version, a purpose, its permissions and its status. An agent that is not registered cannot get context or call tools. The registry shows at a glance what is in production and who is responsible.
Collections assistant, owned by the Head of Recoveries, v1.2.
monolith
For each task Monolith retrieves the Zeus objects, documents and memories that are relevant. It filters them by what the requesting person and the agent may see. The agent receives a prepared bundle, not a connection to the whole database.
Load this borrower's repayment history, not their medical notes.
monolith
Calls to tools and models go through the gateway. The gateway applies allow-lists, redaction and rate and cost limits, and guardrails check inputs and outputs. Its design is provider-neutral, including open-weight and local models.
Mask national ID numbers before the model call; cap spend per task.
human
Policies define which actions need approval, such as refunds above a limit or messages to customers. The agent pauses and the approver sees what it intends to do. A kill switch can stop one agent or all of them.
Refunds above the limit wait for a supervisor.
cyclopes
Every context request, gateway call, redaction and approval is sent to Cyclopes. Evaluation results flow back, so you can tighten a policy where an agent misbehaved. Memory writes record where each item came from.
Why did the agent send this message? Open the trace.
04What Monolith does
Retrieves the Zeus objects, documents and memories that a task needs. Results are filtered by the permissions of the requester and of the agent, and by data class and purpose. The agent receives only that filtered bundle.
What an agent has never seen, it cannot leak or misuse.
Short-term, long-term and shared memory with retention rules and provenance. Each item records where it came from and who may see it. Items can be forgotten, which supports legal erasure and customer requests. Argus hosts the memory, and Monolith governs access and what gets written.
An agent that remembers everything forever is a liability.
Policy by data class, purpose and region. You can say that national ID numbers never leave the country, or that customer data may be used for service but not for marketing. Policies are written as code, versioned and reviewed.
Data protection law is about purpose and place, not only about who.
Per-agent limits on tools, data, systems and spend. An agent that drafts letters cannot also issue payments. Limits are enforced through Odin, so they apply in every product the agent touches.
Over-permissioned agents are the most common way an AI pilot becomes an incident.
A single controlled path to tools, through MCP and similar protocols, and to language models. The design includes provider routing, fallbacks, open-weight and local models, redaction, rate limits and cost caps. The platform review places the gateway in Monolith.
One path is a path you can watch, limit and switch off.
Checks on inputs and outputs, defences against prompt injection and triggers for human review. No single control is claimed to be sufficient. They work together with least-privilege permissions and approval requirements.
Layered controls fail more gracefully than one clever filter.
The list of every agent, with its owner, version, permissions, status and recent activity. Retiring an agent or rolling back a version is a registry action. Auditors can see in one place what automation the organization runs.
You cannot govern what you cannot list.
Define which actions need a person to approve and who may approve them. Approvals can reach people through the channels they use. A kill switch stops one agent, a class of agents, or all of them, and is enforced through Odin.
Trust grows when people can stop the system quickly.
05
In older systems, access control decided which screens a person could open. With agents, the important decision is what goes into the context: the text and data the model receives for a task. If a record is in the context, the model can repeat it, reason on it or be tricked into sending it elsewhere.
Monolith treats context assembly as a governed step. It does not give an agent a database connection and hope for the best. It builds a bundle for the task, filtered by the person asking, the agent, the purpose and the data class. That bundle is what the model sees, and the bundle is what Cyclopes records.
Free 30 minutes with an engineer.
06Sectors
Situation
A bank wants a customer-service assistant. It must answer account questions but must not see full KYC files, and must not change anything without checks.
What it does
Monolith limits the assistant to account status and recent transactions for the customer on the line. KYC files are not loaded into context. Sensitive actions, such as changing a phone number, need approval, and every call is logged.
Human decides
Compliance decides what the assistant may see and which actions require approval. A supervisor approves or rejects flagged actions.
07Works with
08How you integrate
The lists describe target interfaces and are confirmed per release and per design partner. Nothing on this list is a claim that an integration with a named third party exists today.
Agent registry API
api
Context API
api
Policy as code
api · Authoring and review; evaluated through Odin.
MCP gateway for tools
protocol
Model gateway
protocol · Provider-neutral.
Approval webhooks
api
Email approvals
channel
WhatsApp and messaging approvals
channel
SDK
sdk
09Trust
Agents start with no access and are granted specific tools, data and spend. Limits are enforced through Odin.
Policy controls which data may be sent to which model or tool. Sensitive data can be kept to local models and in-country storage.
Memory has provenance and retention rules, and supports erasure. Memory is hosted on Argus inside your boundary.
Our priorities: prompt injection, over-permissioned agents, exfiltration through tools and runaway cost. A written threat model is a launch requirement.
10
Does
Does not
11FAQ
Experience you can lean on
Immersed in technology and across many different verticals, so the people on your project have done this before.
Monolith
Tell us the problem. An engineer, not a salesperson, answers.
Decide what every agent may know, remember and do. Monolith is the context, memory, governance and permissions system that makes AI agents safe to trust with real business data.
