# How the five products fit together.

> How the five Boltcliq products fit together: the layers, what each product gives and gets, the rules that keep them from overlapping, one request traced end to end, and how teams adopt them.

Canonical URL: https://www.boltcliq.com/products/stack
Part of: https://www.boltcliq.com/llms.txt

Zeus models the business, Odin decides who may act, Monolith governs what agents know and do, Argus runs them, and Cyclopes observes all of it. One ontology, one identity system, one audit trail.
- Each product has one job. Nothing keeps a private copy of what a customer, an account or a shipment is, and every access decision goes through one place.
### What each product gives the others
- Zeus
- Odin
- Cyclopes
- Monolith
- Argus
- Zeus
- Zeus: — | Odin: Business meaning | Cyclopes: KPI context | Monolith: Objects and relationships | Argus: Workflows and apps
- Odin
- Zeus: Access decisions | Odin: — | Cyclopes: Audit events | Monolith: Agent permissions | Argus: Workload identities
- Cyclopes
- Zeus: KPI views and lineage | Odin: Records only | Cyclopes: — | Monolith: Evaluation results | Argus: Telemetry storage
- Monolith
- Zeus: Governance over access | Odin: Agent policy | Cyclopes: Gateway evidence | Monolith: — | Argus: Memory access rules
- Argus
- Zeus: Runs workflows, stores the ontology | Odin: Hosts Odin | Cyclopes: Session recordings | Monolith: Hosts memory and agents | Argus: —
- Rows give. Columns receive.
### Boundaries, stated plainly
- Several products touch the same ideas, so we wrote the rules down. They are the part most likely to go wrong in a platform, and the part buyers should ask about first.
- Odin is the only place identity and policy decisions are made. Monolith and Argus never run their own login or permission engine. They ask Odin. Monolith decides and Argus stores and runs: Argus hosts memory, and Monolith governs access to it and what gets written. Zeus is the single source of business meaning, and other products refer to its objects by identifier. Cyclopes observes and never blocks. Blocking is the job of Odin and Monolith.
- Odin: the only policy decision point.
- Monolith decides what an agent may know and do. Argus stores and runs.
- Zeus owns business meaning. Nobody keeps a private copy of “customer”.
- Cyclopes records and explains. It does not decide.
### One request, traced
**Identify**
- A loan officer asks an agent to review a late application. Odin authenticates the officer and issues the agent a short-lived credential, scoped to this task and tied to her name.
- Delegated scope: read applications for one branch.
**Model**
- Zeus resolves what the request is about. The application is an object linked to an applicant, an account and a set of rules. The agent receives meaning, not a raw table.
- Application, Applicant, Policy rule
**Assemble context**
- Monolith decides what the agent may see for this purpose. It retrieves the right objects and notes, redacts fields the officer cannot see, and refuses the rest.
- Income shown, national ID masked
**Run**
- Argus executes the agent in an isolated sandbox with controlled network access. Memory for the task is hosted on Argus and written only as Monolith policy allows.
- Sandbox with no default egress
**Decide**
- The agent proposes an action through a Zeus workflow: request missing documents. Approving it is a human step, so the officer reviews and confirms.
- Approve: request payslip
**Record**
- Cyclopes stores the decision record: inputs, rule, proposal, approver and cost. Odin controls who may read it. An auditor can replay the case later.
- Decision record with approver
### How teams adopt it
**Start with one use case**
- Pick a single decision that matters, such as late loan applications or stock-outs at clinics. Our forward deployed engineers model it in Zeus, run it on Argus and prove it end to end before anything else is touched.
**Add trust and control**
- Once an agent does real work, add Odin for identity and Monolith for governance. Permissions become explicit, memory gets retention rules, and every agent appears in one registry with an owner.
**Widen with observability**
- Cyclopes turns the record into evaluation. You test agent changes against past cases, watch cost per task and quality, and give auditors and regulators exports they can read without help.