Integration demos for instrument and research-software makers

Stage: after at least one lab reaches stage 3 on a given instrument or software stack. This is not a lead source on its own; it widens a workflow that already works. Buyer pages: validation docket · reproducibility bundle · workflow fit.

We approach a camera, microscope or DHM maker, or a research-software project (acquisition or analysis software), with one concrete integration demo on a workflow that already ran end to end — not a broad partnership pitch.

The gate (all must be true before any contact)

1. A validated workflow on that maker's instrument or that software's output: at least one lab's own frames from it reconstructed (stage 2) and the lab's reference measurement committed (stage 3).
2. The lab's written permission to mention that their setup was used (or the demo uses only our own or public frames, and says so).
3. The maker is not a production-line or do-not-approach organisation (pages 15, 29).
4. Operator go, logged.

No validated workflow → no approach. Log the idea as integration candidate and wait.

Demo recipe (one page, one script, one ZIP)

1. Input: a frame exported exactly as the maker's instrument or software writes it (their file format, bit depth, metadata fields).
2. Mapping: a short table of which of their metadata fields map to our request fields (wavelength, pixel pitch, distance, geometry) — run through the fit check, saved.
3. Call: a ≤20-line script (Python or curl, with the form-token step on the public endpoint) that takes their exported file and returns our result ZIP.
4. Output: the result ZIP opened at the evidence record and methods supplement; the result ID re-derived on a second run.
5. Limits slide: the validation docket's "not measured" list, verbatim.

Run it end to end yourself the day before; record the result ID.

The approach (plain text, to a named product or developer contact)

Subject: A working export -> reconstruction-record demo for <product> files

Dear <Name>,

A lab using <product> sent us frames exported as <format>. We mapped the
export's metadata fields to our hosted reconstruction and every result now
carries a re-computable evidence record and a methods supplement. The full
demo is one page and a 20-line script; I can show it in 20 minutes or send it
to try on your own sample file.

This is a specific, narrow thing; we are not proposing a partnership or any
commitment. It is research tooling with published limits:
https://api.apertureapi.com/docs/validation-docket

<your name>

What not to promise

• No co-marketing, logos, bundling, revenue share, reseller or OEM terms — the operator decides those, if ever.
• No accuracy, agreement, speed or throughput figures; no "validated for " — one lab's comparison is one rig.
• No on-prem, embedded or in-instrument version, and no roadmap dates.
• Nothing that implies the maker's endorsement.

Artifact: the demo bundle (page, script, ZIP, result ID) filed; the approach email sent; outcome logged as integration demo shown or declined.