Perslis
04 / TOOLS · INSTRUMENT WALL

One console.
Every instrument talking.

A protein databank, a literature index, a variant archive, a chemistry database, a local compute bench, and a hash-chained lab notebook were never designed to speak to each other. The science runtime wires all of them into one console: ask in plain language, and every answer comes back pinned to the database, accession, and URL it came from. Connecting instruments that were never supposed to connect isn't a feature of this lab — it is the product.

Counts on this page are the shipped tool surface of the runtime's research server, exercised end-to-end by its adversarial harness. They are scale and coverage figures — not accuracy, discovery, or clinical claims.

44instruments on one console
19public scientific services
117/117hostile harness scenarios · 0 findings

An instrument is one callable tool exposed by the research server: 33 query instruments across 19 services, plus the compute bench and the 10-instrument WetHands lane. The harness drives the real server over the wire — happy paths, hostile inputs, degraded upstreams — and is scored inverted: a finding earns points, a pass earns zero.

THE INSTRUMENT WALL

Instruments that were never
meant to talk to each other.

Six benches, nineteen services, thirty-three query instruments — plus the native bench on the Airtight chapter. The mono line under each service names the exact tools it powers on the console.

Queried live through each service's public interface under the source contract. Service names belong to their respective owners; the marks above are our own text renderings, and no partnership or endorsement is implied. Variant and clinical instruments are for research use only.

THE BRIDGE

How incompatible instruments
learn one language.

Ask

One question at the console. No per-service query languages, no tab-hopping between nineteen websites.

Route

Lois fans the question across the benches — literature, structures, variants, chemistry, pathways — and gathers what comes back.

Pin

Every result carries its source: database, accession, URL. A result that cannot name its source is refused by construction, not by convention.

Admit

The PEEL gate decides what enters the lab record. Clinical significance stays verbatim; unsupported claims stay out.

The air-gap posture

Live lanes query public interfaces when the wire exists. Everything the lab keeps — topic packs, the scientist ledger, the Peel graph — is local files that keep working with the cable pulled. Evidence is harvested into packs that ship offline, because a lab record has to stand on its own in a disconnected review.

How this stays airtight

SEE IT RUN

The instruments, talking.

A short, unedited capture of a grounded research pass moving across the instrument wall — every fact pinned to its source database. Recorded on a research prototype.

Grounded discovery across the wall

Following typed relationships across services, in one console.

Continue exploringAirtight