> For the complete documentation index, see [llms.txt](https://docs.solcis.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solcis.ai/the-business-problem-we-solve.md). # The business problem we solve The Solcis Policy Engine evaluates the actions your AI systems take against your controls before they run, returning decisions; receipts are recorded in the evidence ledger in Compliance Studio. Your organisation is putting AI systems into production: AI-powered software, agents, and models that act in your name. Agents are the sharpest case. They act in milliseconds, at volume, across systems that were not designed for autonomous software. Your compliance programme still relies on a control library, an audit programme, and point-in-time reporting. The gap between those cadences is where the risk sits. **The Solcis Policy Engine evaluates each action your AI systems take against your controls before it happens. Each decision's receipt goes to the evidence ledger in Compliance Studio, which an auditor can verify independently.** ## The five questions you will be asked Boards, regulators and procurement teams are starting to ask the same five questions about agents. Each one has to be answered with evidence, not a policy document. 1. **Which agents are in scope?** A register of the agents you run, with the boundary of what is governed made explicit. 2. **Which obligations apply to each one?** The laws, frameworks, and policies you operate under, mapped to the controls that implement them. 3. **What is each agent permitted to do?** Authority and delegation stated in advance, as controls, not inferred afterwards from logs. 4. **How is each action decided?** A check against those controls before the action executes, with a defined outcome. 5. **What did each agent do, and can you prove it?** A record for every decision that internal audit, external assurance or a regulator can verify independently. The first three are governance questions. The last two are enforcement and evidence questions. Most organisations can partly answer the first three. Almost none can answer the last two for agents, because the tools that exist were built for a different problem. ## What Solcis is The Solcis Policy Engine answers the enforcement questions; Compliance Studio answers the evidence questions, and its coverage map and agent discovery help with the first: which agents are in scope. The Policy Engine sits between your AI systems and the actions they take. When an action is attempted, it evaluates the action against your controls and returns `Allow`, `Deny` or `Escalate`, each with a severity rating. The Solcis Policy Engine writes a compliance receipt for each decision; Compliance Studio's tamper-evident universal evidence ledger collects receipts from every enforcement point. Each receipt identifies the control and framework clause that drove the decision. Compliance Studio and the Solcis Policy Engine run in your infrastructure, under your certifications, with a model you host. Sovereign by construction explains the deployment and data-handling boundaries. ## What Solcis does not do Solcis is not a network firewall. The Solcis Gateway sits in the path of AI calls, but it decides on actions against your controls, not on packets or connections. Solcis applies compliance controls to what your AI systems do. The Solcis Policy Engine governs the AI systems you connect to it. Compliance Studio discovers agents, can take input from the discovery tools you already use, and shows exactly where coverage begins and ends. Understand your coverage sets out the edges. Solcis does not make you compliant with any framework. It enforces the controls you define and evidences that it did. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.solcis.ai/the-business-problem-we-solve.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.