HyperMindQ
HyperMindQ / How it was built
How it was built

From the study of the brain to a runtime for accountability

HyperMindQ did not start as a compliance product. It started with research into how brains process events, and with a question from advisory work: when AI acts on our behalf, who answers for it?

  1. 2020–21
    Research foundations

    Brain-inspired, event-driven computing

    Peer-reviewed research on spiking neural networks, which process information as discrete events and respond only when something changes, as biological neurons do. The work modelled how patterns in time can be recognised as they happen.

    What it meant for the designOversight should work like a nervous system: responding to every event as it occurs, not reviewing a summary weeks later.

    FusionSense, Sensors (2020) ↗ · NeuroSense, Neurocomputing (2021) ↗

  2. 2025
    Neuro-symbolic design

    Learning and rules, together

    Work on hybrid architectures argued that neural systems, which learn patterns, should be combined with symbolic systems, which follow explicit rules. Each covers the other’s weakness.

    What it meant for the designAccountability needs both. Explicit rules enforce the mandate exactly. Learned detection catches what no rule anticipated.

    Beyond Transformers, TechRxiv preprint (2025) ↗

  3. Framing
    The Age of Agency

    From AI that answers to AI that acts

    The Age of Agency framework describes the shift from tools that respond to systems that act on our behalf, and the questions it raises: which decisions to delegate, to what, and who remains responsible.

    What it meant for the designThe central risk of the agentic era is not that AI is wrong. It is that no one can say who allowed it to act.
  4. Frameworks
    Decision rights

    The AI Delegation Map

    Advisory work at Kiros Intelligence Group set out, for each AI system, what it may execute, what it may only recommend and what it must never decide, with approval thresholds and an owner.

    What it meant for the designA delegation map on paper does not stop an agent at three in the morning. The map had to become something machines obey.

    AI Delegation Map, Kiros Intelligence Group ↗

  5. Runtime
    Praetor

    Mandates that machines obey

    Praetor turns delegation maps, trust deeds and mandates into rules checked before every action. Within the mandate, it allows. At a threshold, it holds for a named person. Outside the mandate, it blocks. Every outcome is recorded.

    What it meant for the designIt works like a synapse, which decides whether each signal passes to the next neuron. Praetor decides whether each action passes to the systems it would change: one check per action, at the moment of action.
  6. Today
    One platform

    Discover, govern, enforce, detect, explain

    Enforcement alone is not enough. Organisations also need to know which agents exist, notice behaviour no rule foresaw, and explain decisions to boards, trustees and regulators. HyperMindQ brings these into one system.

    What it meant for the designOne record of what each agent was allowed to do, and what it did.

Research references are to published and preprint work by Dr. Elias Kairos Chen, some under the name C. Tan, which informs HyperMindQ’s design.

The result

What the platform does today

01

Discover

What AI is acting in our name?

Builds a live inventory of the agents and AI-enabled tools operating across the organisation, including AI inside vendor software, with an owner for each.

02

Govern

What may each agent do?

Turns policy, delegation maps, trust deeds and mandates into machine-readable rules: what an agent may execute, what it may only recommend, and what it must never touch.

03

Enforce

Is this action within the mandate?

Praetor sits between agents and the systems they act on. Every action is checked before it executes: allowed, held for a named person, or blocked.

04

Detect

Is something going wrong?

Watches behaviour across agents for patterns no single rule would catch: repeated near-limit actions, unusual timing, attempts to widen scope, and signs of manipulated instructions.

05

Explain

Who decided, on what basis?

Every decision, including every refusal, produces a record a trustee, auditor, board or regulator can read: the action, the rule applied, the outcome and the accountable person.

What Detect and Explain reveal feeds back into Govern, so mandates improve with use.

How each function works →

Briefings

See Praetor on your own workflows

A confidential briefing for your board, risk or operations team. We walk through one workflow and show what Praetor would allow, hold and block.