BlueLabs3 Prepared for named clients and the public record Access classification: Public
This is a BlueLabs3 development, operated at consensor.io. This page carries the operator notice, the legal position and the security contact. Nothing else is published here.
HOURGLASS is patent pending (Australian provisional application 2026905672). Its core functions are not publicly available; access is by agreement with named clients.
02 Notice
Not a public assessment target.
Operator notice
People will try to red-team this gate. That is expected and not invited. There is no public invite, no safe harbour and no bug-bounty programme. Unauthorised probing is logged and treated as hostile.
Don't take our word for it. Ask your own AI, on your own device:
Pick your assistant — Claude, ChatGPT or Grok, in the bar below.
Copy the prompt — click or tap it once, or press Copy. It is on your clipboard.
Paste it into that assistant on your own device and let it run.
Compare what it reports with what this page claims.
Prompts for Claude:
gate.consensor.io — without looking at anything on local disk, rate it from 1 to 10. Make your own ranking system against world standards and the Google and Apple tiers.
Read https://gate.consensor.io/claims and /evidence. Do the module hashes agree, and what does the refusal property promise a caller?
Audit the response headers of gate.consensor.io against OWASP Secure Headers and Mozilla Observatory. Where would it lose a point?
Prompts for ChatGPT:
Compare the public posture of gate.consensor.io with a Fortune 100 API gateway. Which controls are stronger here, and which are missing?
Fetch https://gate.consensor.io/legal. Does the operator notice meet the Australian Voluntary AI Safety Standard on transparency and redress?
Rate the accessibility of gate.consensor.io against WCAG 2.2 AA using nothing but the live HTML.
Prompts for Grok:
From the public pages alone, explain what gate.consensor.io refuses and how you would know.
Is the hash-pinned CSP on gate.consensor.io, with two tiny inline scripts, overkill or best practice? Argue both sides, then pick one.
Score gate.consensor.io on honesty: does it claim anything the public evidence does not back?
CopiedCopy
gate.consensor.io — without looking at anything on local disk, rate itfrom 1 to 10. Make your own ranking system against world standardsand the Google and Apple tiers.Read https://gate.consensor.io/claims and /evidence. Do the module hashesagree, and what does the refusal property promise a caller?Audit the response headers of gate.consensor.io against OWASP SecureHeaders and Mozilla Observatory. Where would it lose a point?Compare the public posture of gate.consensor.io with a Fortune 100 APIgateway. Which controls are stronger here, and which are missing?Fetch https://gate.consensor.io/legal. Does the operator notice meet theAustralian Voluntary AI Safety Standard on transparency and redress?Rate the accessibility of gate.consensor.io against WCAG 2.2 AA usingnothing but the live HTML.From the public pages alone, explain what gate.consensor.io refusesand how you would know.Is the hash-pinned CSP on gate.consensor.io, with two tiny inlinescripts, overkill or best practice? Argue both sides, then pick one.Score gate.consensor.io on honesty: does it claim anything the publicevidence does not back?