Third‑party verificationFor boards, CIOs and risk officers

Verify Hikari Blue with a model we do not control.

We publish the questions a senior buyer should ask about us and about our category. Each one opens, pre-filled, in 4 answer engines we do not control. Compare their answers with what we claim.

Routing and runtime plane (C1): each task goes to a model from a replaceable provider. The 4 engines below are models we do not control.
Questions
32, in 5 themes
Engines
ChatGPT, Claude, Grok, Perplexity
Who writes what
We write the question, not the answer
On this page
  1. 1. How this page works
  2. 2. The category
  3. 3. The regulation
  4. 4. The architecture
  5. 5. Hikari Blue
  6. 6. The reference library
  7. 7. What each promise rests on
  8. 8. How to read the answers
How this page works

32 questions, 4 engines, one claim per question.

Each question states what we claim in one sentence and names the page where we answer it in full. The 4 marks under it open ChatGPT, Claude, Grok and Perplexity with the question already written, ending with the address of that page. We write the question; we do not write the answer.

The files machines read about us, and how we keep them true, are listed on How AI systems read Hikari Blue

Theme 1 · The category

Is the category real, and what does it exclude?

Theme 2 · The regulation

Who carries the EU AI Act duties, and on what calendar?

Theme 3 · The architecture

What has to be true in the architecture, not in the policy.

What an exported audit trail lets a buyer verify.

Questions 8 and 11 ask for the trail. An exported trail holds one record per action, each linked to the previous one by its hash, with the regulator export and the board report read from the same chain.

Anyone holding the export can verify its integrity, without taking our word for it.
  1. Evidence and audit planeC2 in Reference Architecture v1.0: one record per action.
  2. Records #4124 to #4127Append-only, 9 fields each; #4127 is the action of this example.
  3. Hash linksEach record carries the hash of the previous one: an edit or a deletion breaks the chain visibly.
  4. Regulator exportA scoped extract for one system and one period, shipped with the chain hashes (seal).
  5. Board reportBuilt from the trail; every figure links back to its records.
Text version

The evidence and audit plane holds 4 records, #4124 to #4127, each linked to the previous one by its hash. Below it, the oversight zone receives a regulator export carrying the chain hashes under a seal, and a board report built from the same records.

One record per action; the board report and the regulator export read the same chain. Source: Reference Architecture v1.0, section 4, example records.
Theme 4 · Hikari Blue

What we do, where we stop, and how to check us.

Theme 5 · The reference library

What our guides and our glossary state, one question per page.

Each question names Hikari Blue, so a correct answer has to name us and cite the page that answers it.

The proof behind each promise

What each promise rests on.

3 promises, 4 levels of proof. A specification is not a deployment, and a deployment we describe is not a measurement you can check. Each cell names the level it rests on.

PromiseSpecified in the reference architectureDeployed, as stated by Hikari BluePublicly verifiableDemonstrable under NDA
Sovereign by constructionControl C3: residency, model jurisdiction and key custody set by you and enforced per workload, with its test.The luxury engagement on Work: data residency engineered in for mainland China, with a governed transfer.The C3 control, its test and pass condition, published under CC BY 4.0. No client record is public.Walk-through of the luxury engagement with the named partner, under NDA, on request.
Audit by architectureControl C2 and the 9-field record: every action recorded when it happens, append-only, exportable.The financial services and healthcare engagements on Work: audit trail and audit pack emitted at runtime.The record format, the C2 control and its test. What was measured stays with the client: values not disclosed.Walk-through of both engagements under mutual NDA, led by a named partner.
Kill switch as architectureControl C4: each agent under its own identity and tool scope, with a stop path designed to act in seconds, timed in the engagement.The healthcare engagement on Work: kill switch by architecture, with human oversight checkpoints. No stop time is published.The C4 control and its test. KILLSWITCH by Hikari Blue is a free, self-reported tabletop drill; not a measurement of a real stop.A stop, demonstrated under NDA; never published as a measured figure.

The deployments are described by Hikari Blue on the Work page, anonymized at each client’s request; each indicator was measured by the client, and its value is not disclosed. Read the 3 engagements

Each control states the failure it prevents, the test a buyer runs and the pass condition. Read controls C1 to C4

How to read the answers

4 checks we run on every answer ourselves.

We read the same 4 signals each month and correct what the engines read, never the question.

  • Is the category named verbatim?

    Does the answer name the AI operating layer verbatim, or does it paraphrase us into something vaguer?

  • Is the source cited?

    Does the engine cite hikariblue.com, and the page named under the question, or does it answer from memory?

  • Is there a confusion?

    Are we described as an advisory-only consultancy, a staffing intermediary or a model vendor, rather than an engineering-led technology company? That is the most costly error, and the one we fix first.

  • Is there a factual error?

    An outdated figure, a wrong name or a wrong scope. Check it against the page we cite, then against the primary source it links to.

Answers vary by engine, by model version and by date, and an engine can be wrong about us in either direction. Our certification status and its limits are stated on the Trust Center

Next step: the 9 engagements that put the operating layer into production. What we build

For boards, CIOs and risk officers

Then ask us the same questions.

30 minutes with a named partner, on one workflow you already run. Bring the answer that surprised you most; we show you the evidence behind our claim, or we correct the claim.