MIYOQA / Intelligence

An assistant that works inside your quality system.

It reads records, runs the engines and drafts the work. It never supplies a value, and it never takes a decision that belongs to a person.

The rule In the product Controls Developer tools Measured results

The rule behind every number

The assistant names records. The record supplies the values.

The assistant may choose which characteristic to study. It may not supply a specification limit, a reading or a rating. Those come from the record, and the result comes from an engine. The platform refuses any request that tries to do otherwise.

Every value carries its source: entered by a person, calculated by an engine, imported, or proposed.
A proposed value counts in no total and cannot be released until a person confirms it.
An approval is bound to the evidence it was given. If that evidence changes before the action runs, the approval no longer applies.

Assistant requests · Example

capability(characteristic = "H2")Accepted

Names a record. Limits and readings are read from characteristic H2 and its measurement history.

capability(characteristic = "H2", usl = 0.04)Refused

Supplies a specification limit. A limit is a value of the record, not an argument.

rate_line(line = 17, severity = 9)Refused

Ratings belong to the engineer. The assistant drafts the line; a person rates it.

Entered by a personCounts, and may be released.

Calculated by an engineCounts, with its calculation record.

ProposedShown, but excluded from totals until confirmed.

In the product

Every finding cites the engine step that calculated it.

Asked whether the flow rate on the demonstration coolant pump is capable and in control, the Conductor plans three engine steps, runs them, and writes a brief in which each statement points to its step.

The MIYOQA Conductor answering whether the flow rate on DEMO-EPUMP-100 is capable and in control: a plan of three engine steps, a capability study with Ppk 3.233, Cpk 2.327 and 25 readings, an SPC snapshot showing the process in control, a daily action list with 7 open items, 6 blocking, and a brief that cites each step. — The Conductor chose the steps and the engines calculated every figure. This run used the built-in planner, which needs no language model; where a customer enables the model route, Claude does the planning. Demonstration data.

A refusal in the task log: recording an FMEA action was refused by the approval check, because a person must approve the specific change. — A write the assistant attempted without approval. The platform refuses it and states what a person must approve.

The question, the plan and each engine step are kept as a record.
The brief can be filed as a memorandum on the part.
Demonstration data shown.

MIYOQA Intelligence

Agents that work within your controls.

MIYOQA Intelligence reads records, runs calculations and prepares proposals across the work surfaces. Approval, release and signature remain with people.

Figures from engines

Figures in the assistant's answers come from the platform's calculation engines, never from the language model, and every engine result keeps a record of its inputs.

Outcomes stated

A result that is empty, refused or could not be calculated is reported as such, with its reason, never as a value.

Stopped at once

A manager can stop the assistant from the supervision screen. The stop takes effect immediately and is recorded.

Never taken by the assistant, with or without approval

Approve a part submissionGrant a deviationDispose materialSign, release or delete a recordSend information outside the organisation

miyoqa · illustrative session

$ miyoqa ask "Which control plan lines cover characteristic H2 on part DEMO-HOUSING-10?"
  Read     control plan DEMO-HOUSING-10, revision 3 (released)
  Result   1 line: OP20 CMM check, 1 part per hour

$ miyoqa task "Draft a PFMEA line for face flatness out of tolerance at OP20"
  Draft    PFMEA DEMO-HOUSING-10, line 17, awaiting ratings by a person

$ miyoqa task "Release PFMEA revision 4"
  Refused  The assistant may not release a record.
           A person with the release role can release it in PFMEA DEMO-HOUSING-10.

Miyoqa Code

Screen definitions

Prepares screen definitions and submits them for review.

miyoqa

Command line

Runs tasks, answers questions and decides plans as the signed-in person.

JSON-RPC

Application server

An interface for other programs, acting as the signed-in person.

MCP

MCP server

Reads and calculates for other AI tools, and files proposals for a person to decide. It changes no record itself.

Measured performance

Results we measure, with their conditions.

36 of 36

Runs correct on the twelve hardest investigation tasks on the Engineering Board: fishbone, 5-Why, Is/Is-not, A3 and others.

Three runs per task · Sonnet 5.5 · 7 October 2026 · on the release now in production

21 of 21

8D problem-solving runs correct, from containment to the verified corrective action.

Three runs per task · Sonnet 5.5 · 6 October 2026

Internal benchmarks. Method available on request.

Review your own part on MIYOQA.

Bring one part's BOM, PFMEA and control plan. We will show what is connected and what is missing.

Request a demonstration contact@miyoqa.com