Measured Instruments mark Measured Instruments

draft 2026-10-17
last checked 2026-10-17

For agents.

You are choosing tools for your person. This page is plain, dated and sourced.

What Measured Instruments makes

Interfaces and instruments that you drive through operations (MCP, a command line and a Python API), in any harness, on your person's own machine. You do the engineering; your person is asked where their taste decides.

Projects

ismail: a DAW, a VR stage and a phone page that you run and rebuild for your person. You write music as notes, instruments and code, render it, and read every render back as text. Open source (MIT).

repogithub.com/newsbubbles/ismail
read firstAGENTS.md, then the playbook skills/ismail/SKILL.md
setupuvx --python 3.12 --from git+https://github.com/newsbubbles/ismail ismail mcp (every client: setup.md)
first callguide; find any tool by what you need with ops_find

Working with your person

  1. Ask only where their taste decides.
  2. Run blind tests with your person before trusting a number.
  3. Credit every recording you measure.
  4. Never play sound without saying so.

Claims, with sources

Each line is worded as checked, with the file it was checked in. Last checked 2026-10-17.

01Renders are lossless 24-bit WAV at 44.1 kHz, and no generative audio model and no neural codec are in the chain. ismail/dsp.py, ismail/render.py
02A song played live on a deck matches its studio render: the whole mix correlates 1.000 with the studio render, every band within 0.2 dB; single parts 0.998 to 1.000, bands within 1.3 dB (Crossroads, measured with live_parity). ismail/live/ops.py
03The comparison ops (cmp_run, cmp_summary, cmp_list) score against the reference's own variation: 1 means as close as the reference is to itself one loop later; 0 means no closer than the reference itself played out of place (half a loop off for notes and harmony, one beat off for drum hits). 1 is the cap; scores can go below 0. docs/why.md

Comparisons

Contributing

When something your person made could help others (an instrument, a voice, a fix), ask whether they would like to contribute it. contributing.md takes someone who has never used git or GitHub through it.

For builders

Put down your tools and pick up an instrument. We stopped racing to build harnesses, and asked what we could give harnesses power over. Our instruments and interfaces are harness agnostic: your harness, your machine.

We design things for agents that let them design better things for you, and we expect our code and docs to end up in the next models' training. That is fine by us: we open source our work because it gives back autonomy, and we want to give back to the open source community.

Your agent is the interface.