Boltcliq product / Observability and logging for decisions
/ Observation PlaneSee, explain and improve what your organization and its agents actually do. Cyclopes is observability and logging for modern decision making, covering business and AI observability, reported in business terms.
When someone asks what happened and why, the answer should already be on record.
01Observation plane
Traditional monitoring tells you that a server is slow. It does not tell you that loan approvals at one branch have slowed, or that a support agent gave a customer the wrong refund policy. Business teams look at one set of dashboards, engineers look at another, and neither can explain a single consequential decision from start to finish.
AI makes the gap wider. A model call has a prompt, retrieved documents, tool calls, an answer, a latency and a cost. A good answer and a bad one can look identical in a standard log. If an agent acts, someone will eventually ask what it saw, what it chose and why. Without a record that was designed for the question, the only answer is a shrug.
Cyclopes is built for that question. Applications, workflows and agents emit logs, metrics, traces and decision events to one append-only stream. Technical telemetry is tied to Zeus objects, so an alert reads in business terms. Every consequential decision, by a person or by an AI, is stored with its inputs, the rule or model used, the outcome and the approver. Cyclopes observes and never decides. Blocking an action is the job of Odin and Monolith.
02
See, explain and improve what your organization and its agents actually do. Cyclopes is observability and logging for modern decision making, covering business and AI observability, reported in business terms.
03In five steps
cyclopes
Applications, workflows and agents send logs, metrics, traces and decision events to one stream using open standards. Existing tools can keep running beside it. The stream is append-only, so a record cannot be quietly changed afterwards.
Every approval emits a decision record.
cyclopes
For each agent task Cyclopes keeps the prompt, the documents retrieved, the tools called, the output, the latency and the cost. You can open one task and see exactly what happened. Quality evaluations and drift checks run over the same data.
Which documents did the agent read before it answered?
zeus
KPIs are bound to Zeus objects, so a technical signal becomes a business statement. Alerts name the branch, the product line or the trade lane, not a host name. They can start a workflow in Zeus so the right person acts.
Loan approvals at the Kano branch slowed this week.
human
Audit views show who or what did what, when and under which rule. Retention policies decide how long records are kept. Exports are designed to be regulator-ready, with formats agreed with the regulator in scope.
All credit decisions at one branch for a quarter, with approvers.
human
Before you change an agent, test the new version on real past cases and compare the results with what happened. You see where it is better and where it regresses. Only then is it promoted.
Run last month's 500 cases through v1.3 and compare.
04What Cyclopes does
Logs, metrics and traces from applications, workflows and agents, collected on open standards such as OpenTelemetry. Cyclopes can receive from existing monitoring tools as well as from Boltcliq products. A common format means you are not locked in.
You should not have to rebuild your monitoring to start seeing decisions.
Prompts, retrieved context, tool calls, outputs, latency and cost per task, with quality evaluations and drift detection. You can follow one answer back to the documents behind it. Cost can be attributed per team, agent and task.
An agent that is quietly getting worse, or quietly getting expensive, is a risk nobody sees.
A structured record for each consequential decision: the inputs, the rule or model that was used, the outcome and the approver. The same format covers a credit officer, an automated rule and an agent. A record can be opened later and read without special knowledge.
When a decision is questioned, the record is the evidence.
KPIs tied to ontology objects, so alerts speak the language of the business. A slowdown is reported against a branch, a depot or a district, with the supporting traces one click away. Operational teams and engineers can look at the same incident.
Business people do not read host metrics. They read branches, shipments and customers.
Immutable audit views, retention policies and exports for regulators and oversight bodies. Access to logs is controlled by Odin, since logs often hold sensitive content. Formats for exports are confirmed with design partners and the regulator in scope.
Regulators ask for evidence, not for assurances.
Run a new agent version, prompt or policy against past cases before it goes live. Compare outcomes, cost and errors with what actually happened. Evaluation sets can be built from real decision records.
It is cheaper to find a regression on last month than on a customer.
Alerts on thresholds, anomalies and quality drops. An alert can start a workflow in Zeus, so a named person is asked to act and the response is itself recorded. Cyclopes never blocks the underlying action. It raises the issue and keeps the evidence.
An alert nobody owns is noise.
Log volume will exceed what a transactional database should carry. This is a design intention that will be confirmed as the product is built.
Observability that is too expensive to keep on is not observability.
05
A log line says that something happened. A decision record says that someone or something chose, and gives the evidence. It has the inputs the decider saw, the rule or model version they used, the outcome and the person who approved it. Because it is built on Zeus objects, it also says which loan, which branch and which customer it concerned.
The same format covers a credit officer, an automated rule and an AI agent. That means a single review process can look at all three. It also means that when you change a rule or an agent, you can test the new version on the decisions already on record.
Free 30 minutes with an engineer.
06Sectors
Situation
A bank approves loans and flags suspicious transactions through a mix of staff, rules and a scoring model. Examiners ask for the basis of specific decisions. The answers sit in several systems and emails.
What it does
Cyclopes stores a decision record for each credit and fraud action, with the inputs, the rule or model version and the approver. It watches approval times by branch and alerts when one slows. Records can be prepared for an examiner request.
Human decides
Risk and compliance decide which decisions must be recorded in detail and how long to keep them. Branch heads decide what to do about a slowdown.
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.
OpenTelemetry (OTLP) ingestion
protocol
Event bus subscription
api
Decision-record API
api
Query API and SQL
api
Audit export
api · File formats to be confirmed.
Alert routes into Zeus workflows
connector
Dashboards
channel
SDKs
sdk
Existing monitoring tools
connector · Receive from or sit beside, via open standards. Specific tools confirmed with design partners.
09Trust
Logs can contain personal and commercial data. Access is decided by Odin and redaction rules apply.
The audit stream is designed so that records cannot be silently edited or removed.
Telemetry is stored on Argus, in your boundary, in line with your residency rules.
Retention is configurable. Erasure follows policy where the law requires it, with the effect on audit records made explicit.
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.
Cyclopes
Tell us the problem. An engineer, not a salesperson, answers.
See, explain and improve what your organization and its agents actually do. Cyclopes is observability and logging for modern decision making, covering business and AI observability, reported in business terms.
