1. Prior art and originality — the highest-risk disclaimer in this portfolio
This disclaimer exists because of something we measured, not something we're guarding against hypothetically: across independent batches of candidates generated by blueMonster, when a real, field-vocabulary literature search was actually run, every single one turned out to already be published or already patented. The reason that's easy to miss is specific: blueMonster gives a mechanism a fresh name, and a search on that name finds nothing — which can look like a new idea until someone searches the field's own vocabulary for the mechanism instead of the tool's name for it.
Short form (shown near every result):
These are hypotheses to verify, not findings. blueMonster does not search for prior art and does not establish that an idea is new. Candidates frequently correspond to work already published or patented under different terminology. Verify independently before relying on anything here.
Long form:
blueMonster generates and stress-tests candidate ideas. Its output is a set of hypotheses for you to evaluate, together with a record of how they were produced.
blueMonster does not perform a prior-art search, a patentability assessment, a freedom-to-operate analysis, or a determination that an idea is new, and its output must not be represented as any of those. In our own testing, candidates that appeared to be original were frequently found to describe mechanisms already published or patented, because the software names a mechanism in its own words rather than the field's. An absence of results for a term coined by this software is not evidence that the underlying idea is new.
Nothing produced by blueMonster is legal, patent, investment, medical, or professional advice. Before relying on any output — and in particular before filing, publishing, disclosing, or investing on the basis of one — have it reviewed by a qualified professional in the relevant field.
2. What a signed receipt proves
A receipt issued by our software is a cryptographic record of what this software did: which inputs it received, which steps it ran, which model or service produced each result, and what it recorded. Anyone can check that record on their own, without our involvement and without trusting us.
A receipt does not establish that any underlying statement is true. It proves that a computation happened as described. It does not certify the correctness, completeness, accuracy, or fitness of the result, and it is not an audit, certification, attestation, or professional opinion. A signed receipt over a wrong answer is a faithful record of a wrong answer.
3. No professional advice — per product
The clause above applies to every product. Each product also carries its own sentence, written by the team that built it, stating specifically where that product stops:
| Product | What it is not |
|---|---|
| blueMonster / blueMonster Premium | Not a patentability opinion, a determination that an idea is new, or a freedom-to-operate opinion. |
| blueMoat (pre-release) | Not a legal opinion, not a clearance search, and not a substitute for an attorney's prior-art review. |
| blueAlibi | A capability-relative provenance verdict. Not a global fact check, and provenance support does not make a claim true. |
| blueFloor | A "sub-floor" result means only that no supplied, enabled, successfully parsed rule is shown to consume a source. It does not mean the source lacks forensic, compliance, operational, or future detection value. Not a security assessment. |
| blueIntent | Not formal verification, not a proof of semantic preservation, and not autonomous repair. |
| blueParity | Equivalence is not correctness. Two systems can agree and both be wrong. Not a migration sign-off. |
| bluePipeline | Answers one question — did the configuration on screen reach the model — and nothing else. Not an observability platform or a model-quality score. |
| blueGlu | Routes among available models and can escalate when you ask it to. Model choice, answer quality, and cost outcomes are not assured. |
These per-product sentences do not cover our healthcare products, which are governed by separate disclaimers appropriate to clinical use.
4. How this fits together
Sections 1–3 are incorporated by reference into our Terms of Service and apply to every product's outputs under that agreement. Our Privacy Policy and Trust page cover what data we collect and who we share it with — a separate question from what our outputs do and don't prove, which is what this page answers.
MOBLUEHQ, Inc., a Delaware corporation, publishes and is responsible for this page; it is governed by the laws of the State of Delaware, consistent with our Terms of Service.
Document version: pending publication · Effective [EFFECTIVE ON PUBLICATION]