blueMoat screens prior art for a disclosure you paste in. Each finding should carry a validated source quote, an independent second opinion, and a tamper-evident receipt you can keep for diligence files.
The customer app is bluemoat-app (desktop or web build — your onboarding email names the channel).
Install
- Download bluemoat-app from the link in your MOBLUEHQ onboarding email, or clone the repo if your agreement is source-based.
- Install dependencies only if you are on a developer build (
npm installthennpm run devor the command in the repo README). - Launch the app and activate this device when asked. Your license allows a fixed number of machines; see Activation and licensing.
First run
- Open New screening (or equivalent).
- Paste a short disclosure or claim text — start with a paragraph, not a full application, to learn the UI.
- Submit and wait for the run to finish. blueMoat judges on the Blue substrate; large inputs take longer.
- Review the landscape view: each row should show a source quote and confidence or dissent markers where enabled.
Where results and receipts appear
| Output | Location |
|---|---|
| Screening report | In-app results table or landscape view |
| Source quotes | Per-finding detail drawer |
| Second opinion / dissent | Tagged on findings where council disagreed |
| Signed receipt | Export receipt or Evidence menu — JSON or PDF depending on build |
Export the receipt before you close the session if your policy requires a permanent record. For export options in other products, see Export receipts.
If something fails
- Stuck run — Check MOBLUEHQ status; dispatch issues may affect backend lanes.
- License error — Activation and licensing
- Missing quotes — Note the finding ID and use in-app Report; see Support