What MeshQu is not

The scope statement is the documentation owner's own, and it is written as a set of deliberate exclusions rather than a backlog. MeshQu runs as a service your application or agent calls through its documented API or OAuth-secured MCP server, so it is not embedded in your code. It works with the screening, KYC and data providers you already use rather than replacing them. It returns a verdict and never acts on it, so it is not an execution layer. It does not manage authentication or resource access, so it sits alongside your existing identity and permission controls rather than replacing them. It does not produce risk scores or predictions, and it does not account for how a model reached an output. The documentation also bounds the intended audience and states that governance is not tiered: there is one level, and describing MeshQu as offering hierarchical governance would overstate it. The reason the product exists is stated as the same kind of boundary in reverse. Logs record what happened. They do not establish that a decision met the policy that applied to it, and closing that gap is the job MeshQu takes on.