The platform · five parts

A device becomes a platform when every part of it is accountable.

Midas 1 is one machine with five parts, each with its own screen, record, and named owner. The point is being able to say afterwards exactly what happened.

01

What does the firm's work

Jobs queue, run, retry, and pause for a person — each following a named, numbered workflow.

Runtime →

02

What may leave the building

The one doorway to the internet — everything that leaves is written down, and your most-sensitive list is refused.

Boundary →

03

Custody of your systems

The sign-ins to your systems — locked to the machine itself, never held by us.

Credentials →

04

Whose name is on the work

Every job signs in under its own named account, owned by a person in your firm.

Identity →

05

Where it stops

Before anything is sent outside the firm, the machine stops and waits for a named person.

Approval →

one accountable party

Five parts, one service, one number to call.

  • One machine, one service — the parts are not sold separately.
  • Every part writes to the same record, so each job reads as one story.
  • Settings are changed at the machine, by your administrator — never by us from afar.
  • We can see the box is healthy — we cannot read a document or move a stop.
Book the showroom →

Part 01 · Runtime

The part that actually does the firm's work.

Every job follows a named workflow with a version number — nothing is improvised.

RUNTIME · SCHEDULER

workers 15 · queued 14 · parked 3 · idle 1

WORKFLOW · VERSION · STATE · ATTEMPT

  • shortlist_role_brief v7 running 1/3
  • reference_chase v3 running 2/3
  • cv_parse_batch v11 running 1/3
  • pack_to_client v4 parked · gate —
  • offer_letter v6 parked · gate —
  • crm_hygiene_sweep v2 running 1/3
  • timesheet_reconcile v5 running 1/3
  • brief_digest v9 done · 03:12 —

DURABILITY

retry policy
3 attempts, backoff
on portal change
halt, notify
on power loss
resume from step
parked runs
wait indefinitely
batch window
22:00–06:00

A paused job never times out and carries on by itself. It waits for a person.

the machine's job board, as it appears on screen

workflow libraries

Named, numbered, and not written by you.

Thirty-one recruitment workflows come with the machine, built around your actual portals and templates. No one in your firm has to write or update one.

Browse the workflow atlas →
  • Each workflow states which systems it uses, what it produces, and where it must stop.
  • A new version runs alongside the old one, watched, before it takes over.
  • The machine has read everything you gave it — that reading is a tool, not the product.
  • The hardest thinking steps can go through Hybrid Reasoning — only if you switch it on.
  • It learns overnight from your team's corrections, and what it learns stays on your machine.

8–15

jobs at once — set by what the machine can do, not by how many seats you pay for.

1–2k

tasks a day, with the heavy volume work done overnight.

31

ready-made recruitment workflows, kept and numbered on your machine.

Next: what the machine is allowed to send outside the building. 02 · Boundary →

Part 02 · Boundary

One way out, and it keeps a receipt.

One doorway to the internet, and it writes down everything that passes through. Behind it, a hard stop refuses anything you have marked most sensitive.

Egress ledger

STEP 01 · LOCAL · 03:41:19 HKT

The question, as the user typed it 

            Between Priya Raman and Wai-kit Cheung, who fits the Head of
Compliance role at Meridian Partners? Budget is HK$1.85M and
the client wants someone who has taken an SFC Type 4 licence
through a first inspection.

NOTHING

The question never leaves the machine in this form. It is only used to search your own files.

Local · 0 bytes out Session opened, map empty

1 / 5

STEP 02 · LOCAL RETRIEVAL · 03:41:20 HKT

What the machine found in your own files 

            4 documents, 11 passages, all resident on the appliance:

  · CV — Priya Raman (2024-11).pdf              p.1–2
  · CV — Wai-kit Cheung (2025-02).pdf           p.1, 3
  · Meridian — role brief, Head of Compliance.docx
  · Placement notes — Meridian, Q1.md           §2

Retrieval: BGE-M3 · Qdrant · in-memory · 380ms

NOTHING

All of this searching happens inside the machine. No filename or passage is sent anywhere.

Local · 0 bytes out 11 passages held in memory

2 / 5
Boundary

STEP 03 · OUTBOUND · 03:41:22 HKT · 1,204 BYTES · LOGGED

Exactly what left the machine, in full 

            Between Priya Raman and Wai-kit Cheung, who fits the Head of
Compliance role at Meridian Partners? Budget is HK$1.85M and
the client wants someone who has taken an SFC Type 4 licence
through a first inspection.

(Toggle to "What we sent" to see what actually left the machine.)

CODE WORDS

Code words only — no name, figure, filename or firm. The key that links code words back to real names never leaves the machine.

1,204 bytes out · logged Tripwire: pass · ZDR, no-training terms Frontier cost: US$0.015

3 / 5

STEP 04 · INBOUND · 03:41:24 HKT

The outside AI’s answer, still in code words 

            The outside AI answers about [PERSON_11] and [PERSON_12]. It
has no way of knowing who they are.

OUTLINE

Reasoning and judgement, but no facts about your firm. The machine swaps your real details back in during the next step.

Inbound · 812 bytes · logged No identities present

4 / 5

STEP 05 · LOCAL COMPOSITION · 03:41:25 HKT

The answer the user actually sees 

            Priya Raman is the stronger fit for Head of Compliance at
Meridian Partners.

She carried an SFC Type 4 licence through a first inspection
at her 2021 firm [CV — Priya Raman (2024-11).pdf, p.2] and
has 11 years in asset management [ibid., p.1].

Wai-kit Cheung has 8 years and no first-inspection exposure
[CV — Wai-kit Cheung (2025-02).pdf, p.1], so would need
supervisory cover for the first cycle.

HK$1.85M sits at the market range for this seniority
[Placement notes — Meridian, Q1.md, §2].

— 3 claims cited · faithfulness gate passed · 0 orphans

NOTHING

The machine translates the answer back, puts your own names and figures in, and cites every fact to its source. It is checked before you see it.

Local · 0 bytes out Orphan scan: clean Sending this outside the firm requires approval

5 / 5

An illustrative example — no client data. The structure is exactly what really leaves the machine. The key that links code words to real names exists only on the machine.

the ledger your IT team reads

full trace, hop by hop →

A complete record

What left, when, how big, and where it went — exportable for any date range.

A hard stop

A list, kept per client, of the names and numbers that can never leave — even if every other check fails.

No way in

We cannot log in from outside, and updates arrive as sealed packages you verify and install yourself.

claim discipline

Certain where we can be, honest where we can't.

  • For things with a fixed shape — HKID numbers, sums of money — the block is exact, every time.
  • Beyond those, layered checks err on the side of hiding too much — when in doubt, nothing goes.
  • Behind both, a final stop in the machine itself — and zero leaks across all testing to date.
  • We will not say unhackable, provably impossible, or guaranteed private.
Diligence pack →

Next: who holds the keys to the systems the machine works in. 03 · Credentials →

Part 03 · Credentials

Your keys, locked to your own machine.

Jobs work inside your real systems — hiring system, CRM, mail, portals. Every sign-in is locked to the machine itself, and we never hold one.

CONNECTIONS · SEALED STORE

6 connections · sealed to TPM · 0 held off-box

  • ats read + write/gated rotated 12d ok
  • crm read + write/gated rotated 12d ok
  • erp read only rotated 31d ok
  • mail draft only · send gated rotated 7d send held
  • client portal submit gated rotated 9d submit held
  • regulator public register, read rotated — ok

export refused · sealed material cannot leave the appliance

the list of connections, as it appears on the machine

custody, not convenience

The question is not how easy it is to connect. It is who holds the key.

A stolen box gives up nothing — the keys are useless anywhere else. A replacement is set up from your own backup, without us receiving a single secret.

  • Each job gets only the access its workflow has declared in advance — nothing more.
  • Anything that changes a system waits for a person — the stop sits in front of the key itself.
  • You set how often keys change, and every use is written into the record.
  • The keys can never be copied off the machine — not by a job, an administrator, or us.
  • If you leave, every connection is cut and everything the machine has learned is deleted — with proof.

Next: whose name is on the work when a job uses one of those keys. 04 · Identity →

Part 04 · Identity

Every action has a name attached to it.

A job does not act as "the AI". It signs in under its own named account, owned by a person in your firm.

IDENTITY · ROY-4812-a

profile isolated · 37 acts · all attributed

agent
ROY-4812-a
owner
P. Wong · Director, Compliance
desk
financial services
profile
isolated · no shared cookies
scope
ats, crm, client portal
created
on-box · 2026-03-04

ATTRIBUTED ACTS · RUN #4,812

  • 10:16:04 open client portal
  • 10:16:29 fill candidate fields
  • 10:18:41 halt gated action
  • 10:19:07 auth approved by P. Wong
  • 10:19:09 submit accepted MRD-118-S3

no act on this box is unattributed

one named account, and everything done under its name

accountability, not anonymity

An AI with no name is a liability. Ours has an owner.

When a client asks who submitted something at 10:19 on a Tuesday, the answer is a named account, a named owner, and a full record.

  • Each job signs in under its own separate account — nothing carries over between clients or candidates.
  • Every account is owned by a person in your firm — ownership is part of the record.
  • Accounts are created by your administrator — a job can never create one for itself.
  • Remove an owner and their accounts stop with them.
  • A picture-by-picture record of each account's screen is kept in your building, replayable any time.
See a run trace →

Next: the stop that stands in front of every one of those actions. 05 · Approval →

Part 05 · Approval

The machine stops. That is the product.

Before anything is sent outside the firm, the machine stops and waits for a person. The stop is built into the machine itself — it cannot be talked out of stopping.

GATE QUEUE · 3 HELD

nothing sent · nothing submitted

approvals today 7 · all attributed to a named person

expiries none · a held action never times out into being sent

Gate queue

HELD 00:26 · SUBMIT + SEND

Candidate pack — Head of Compliance, Meridian Partners

run #4,812 · ROY-4812-a · 3 claims cited · 0 orphans held for P. Wong · Director, Compliance

  • Offer letter — Cheung, W. HELD 04:11 · OFFER FIGURES
  • Reject notice — 3 candidates HELD 12:38 · REJECTION

approvals today 7 · all attributed to a named person expiries none · a held action never times out into being sent

the phone approves one item at a time — it cannot change where the machine stops.

how the stop behaves

Governed, not convenient.

Approval is slow on purpose. Eight of the thirty-one workflows stop here — exactly the ones a firm gets sued over.

See which workflows stop →
  • The stop sits in front of the key, not in the AI's instructions — so it cannot be skipped.
  • Each approval covers one item, once — never standing permission.
  • Every approval carries a person's name, and the exact document they reviewed is kept alongside it.
  • A no is recorded too, with the reason, and a person finishes the job.
  • Where the machine stops is decided by your compliance lead, at the machine — never by us.

Watch the machine stop mid-job and wait for you.

Half an hour, no slides. Bring a task that ends with something being sent.

Book the showroom →