{"schemaVersion":"0.1","generatedAt":"2026-10-09T19:41:29.212Z","entry":{"knowledgeKey":"what-meshqu-is-not","kind":"limitation","entityKey":"product","locale":"en","primaryQuestion":"What is MeshQu not, and which problems does it deliberately not solve?","questionVariants":[{"question":"Is MeshQu a rules engine?"},{"question":"Can MeshQu replace our permissions system?"},{"question":"Does MeshQu score risk?"},{"question":"Is MeshQu a KYC or screening tool?"}],"title":"What MeshQu is not","answer":"MeshQu is a standalone service that assesses a decision against policy and records the result. It is not a rules engine you embed, not an execution layer, not a permissions system, not a real-time data feed, not a scoring or risk engine, and not an explainability tool. It is not a screening, KYC or data provider, and it does not interpret regulation for you: the rules remain your organisation’s. The documentation states its exclusions as non-goals rather than gaps.","explanation":"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.","applications":[{"value":"Answer a scoping question directly, without implying a capability MeshQu does not offer."},{"value":"Check a proposed use against the documented audience before an integration is designed."},{"value":"Give a reviewer the exclusions in the documentation owner's own words, rather than a paraphrase that softens them."}],"limitations":[{"value":"This entry states scope, not readiness. What is available in a particular deployment is a separate question, answered by what-meshqu-does and the verified-claims register."},{"value":"The exclusions are the documentation's as at 11 September 2026. They are a published scope statement, not a permanent commitment."},{"value":"Stating what MeshQu is not says nothing about how well the things it does do are evidenced. That is a separate axis."},{"value":"Calling MeshQu through the MCP server or the API is offered within research, evaluation and design-partner availability. No general availability or named vendor integration is claimed."}],"nextStep":{"label":"Concepts overview: explicit non-goals","href":"https://docs.meshqu.com/concepts/overview"},"claims":[{"claimKey":"explicit-non-goals","statement":"The documentation lists MeshQu's exclusions explicitly: it is not a rules engine you embed, not an execution layer, not a permissions system, not a real-time data feed, not a scoring or risk engine, and not an explainability tool.","qualification":"Each exclusion is the documentation owner's own heading. The list is quoted rather than summarised so no exclusion is softened in restatement."},{"claimKey":"non-goals-not-gaps","statement":"These exclusions are stated as deliberate scope, not as features that are missing or planned.","qualification":"A scope statement can be revised by its owner. This records what the documentation says on the date it was captured."},{"claimKey":"bounded-audience","statement":"The documentation also bounds who the product is for: it is not intended for feature flagging, application permissions, or consumer-facing rule evaluation.","qualification":"This is a statement about intended use, and it is stated on the documentation index rather than in the non-goals list."},{"claimKey":"no-hierarchical-governance","statement":"MeshQu does not offer tiered or hierarchical governance, and the documentation instructs that it must not be described that way.","qualification":"The constraint is stated as a copy rule on the documentation's own governance field, so it binds public wording as well as product description."},{"claimKey":"logs-are-the-gap","statement":"The documentation frames logs as the thing MeshQu is not: logs record what happened, and recording what happened is not the same as establishing policy compliance.","qualification":"This is the documentation's own statement of why the product exists. It is a scope statement, not a comparison against any named logging product."},{"claimKey":"not-a-provider","statement":"MeshQu does not interpret regulation for you and does not replace your screening, KYC or data providers. The rules remain your organisation’s.","qualification":"A scope statement. MeshQu assesses and records; your systems orchestrate the case."},{"claimKey":"mcp-or-api","statement":"Bring your own agent through MeshQu’s OAuth-secured MCP server or documented API.","qualification":"Stated on the MeshQu website. The public documentation does not yet describe the MCP server. Offered within research, evaluation and design-partner availability; production availability and support are agreed per engagement."}],"statementKind":"product-description","availability":"not-applicable","evidenceStrength":"source-reported","publicSources":[{"title":"MeshQu docs - Concepts overview","url":"https://docs.meshqu.com/concepts/overview","context":"The documentation owner's 'Explicit non-goals' list, which is the substance of this entry."},{"title":"MeshQu docs - Documentation index","url":"https://docs.meshqu.com/index","context":"The intended-use boundary, and the statement of what logs do not settle."},{"title":"MeshQu docs - Decision assurance","url":"https://docs.meshqu.com/concepts/decision-assurance","context":"The instruction that MeshQu must not be described as offering tiered or hierarchical governance."}],"revision":"83cceb00b4211b779de0d6fc0b3cbac275cff71a48745c2bec162c1c94e6fa96","updatedAt":"2026-10-09T11:40:34.303Z","canonicalUrl":null,"related":[{"key":"what-meshqu-does","url":"https://www.meshqu.com/knowledge/what-meshqu-does.json"},{"key":"responsible-ai-evidence","url":"https://www.meshqu.com/knowledge/responsible-ai-evidence.json"},{"key":"limits-of-verification","url":"https://www.meshqu.com/knowledge/limits-of-verification.json"},{"key":"enhanced-due-diligence","url":"https://www.meshqu.com/knowledge/enhanced-due-diligence.json"}]}}