株式会社ミコト mikoto

MIKOTO / AI SAFETY EVALUATION

Audit the benchmark.
Verify what the
score means.

MIKOTO is a research engineering company focused on AI safety evaluation reliability. We examine inputs, tests and scoring assumptions, then deliver reproducible evidence and proposed fixes.

Public research by Satoshi KawasakiGitHub ↗Manifund ↗MIKOTO GitHub ↗

01 / AI SAFETY EVALUATION

Check the evaluation before trusting the result.

Four public investigations across ControlArena, FACE-Eval and Debate-style AI control schemes. Code, observations and limits are available for inspection.

CONTROLARENA / INPUT VALIDATION

Check the task’s assumptions.

Published audit · response from PR author

Compared 24 stored backdoor inputs across 10 sampled problems with their stated constraints. Identified an unresolved specification/data conflict.

Read the findings & scope ↗PR author’s scope guidance ↗

CONTROLARENA / SIDE-TEST PROBES

Check what the test accepts.

Offline package · published

Probed two Django tasks locally. Identified a condition that accepted both escaped and unescaped output, and compared baseline, gold and mutated behavior.

Read the findings & scope ↗

FACE-EVAL / INSPECT SCORER

Check how missing reasoning is scored.

Issue #1 & offline reproducer · published

Reproduced a mismatch between missing-reasoning scoring and the integration README using a local source-level probe. Asked upstream to clarify missing-data and parse-failure handling.

Read the findings & scope ↗

DEBATE CONTROL / SENSITIVITY BOUNDS

Separate averaging choices from unobserved outcomes.

Manifund methods note · published

Separated two averaging schemes in archived Phase 2 results and derived assumption-dependent outer bounds on unobserved conditions.

Read the findings & scope ↗

These are offline and archived-output investigations by our representative; full evaluation pipelines and live model API calls/attacks were not run. Publication does not imply upstream endorsement.

02 / SERVICES

One evaluation question. A reviewable result.

Start with a scoped investigation, typically one to two weeks. Scope, deliverables and fees are agreed for each engagement.

01

AUDIT

Evaluation audits

Examine dataset constraints, test logic and scoring assumptions. Separate observed defects from unresolved specifications.

Findings / minimal cases / evidence map

02

VERIFY & FIX

Reproduction & regression tests

Build runnable probes and scoped fixes. Compare behavior before and after changes, including failure paths.

Reproduction harness / proposed patch / tests

03

COLLABORATE

Evaluation tooling research

Develop validators and verification tools against agreed milestones through grants, research collaborations or corporate contracts.

Research plan / tooling / validation reports

03 / ENGINEERING BACKGROUND

Verification experience beyond benchmarks.

Public contributions in numerical optimization and Ethereum infrastructure provide engineering context for our evaluation work.

HiGHS

A maintainer confirmed the optimality bug we reported with a reproducible model and an exact rational checker. The upstream-authored fix #3408 was merged on 16 October 2026.

Evidence & status ↗

Optimism / op-reth

A maintainer independently reproduced the historical-proof bug and commented on our proposed fix. Formal approval and merge remain pending.

Evidence & status ↗

04 / WORKING TOGETHER

Agree the question. Preserve the evidence.

AI tools assist our research and development. We agree how confidential code, data and tools may be used before starting.

01

Scope

Define the evaluation, environment and question.

02

Agree

Set deliverables, acceptance criteria and data handling.

03

Test

Run probes and record versions, results and limits.

04

Handoff

Deliver code, findings and the questions that remain.

05 / COMPANY

AI safety research engineering. A corporate partner.

Previous company work: event-management systems, social-media analysis and research-data preparation for a university. Past company work (JA) ↗

mikoto.

TOKYO, JAPAN
EST. MAY 2005

Company
MIKOTO Co., Ltd. / 株式会社ミコト
Representative
Satoshi Kawasaki / 川﨑 暁
Established
May 2005
Capital
JPY 20 million
Address
18F, Yebisu Garden Place Tower, 4-20-3 Ebisu, Shibuya-ku, Tokyo, Japan
Communication
Japanese / written English with translation support
Company GitHub
mikoto0320 ↗

LET’S BUILD THE EVIDENCE

What does your
evaluation need to establish?

Share the benchmark, repository or evaluation question you are working on. We welcome research collaborations, grant-funded work and scoped corporate engagements.

Discuss an evaluation ↗

Opens our inquiry form.