Proof Desk · Field Dispatch 14
One question, one instrument
Dispatch 14Composite marketsOct 2026

One question.
One instrument.

“Did a goal happen before ETH crossed $3,000?” reads like one question. Run by hand, it is a fresh specification and a fresh resolution every time anyone asks it. Compile it once and it becomes an instrument: it has an address, it executes against the feeds, and it knows the exact moment its answer became final.

human ↔ machinereads
Will a goal be scored before ETH crosses $3,000?
01
Ask
Two conditions and one way to join them.
A
op
B
02
Compile
A canonical spec, addressed by its own content.
03
Execute
One market hour of feeds. The answer locks when it is known.
Day 01 · market hour 00:00 to 60:00
…
01 · Ask it in any order

Same question, same instrument.

An instrument should not care how a person phrased it. “Rain and gas” and “gas and rain” compile to one specification and one address, so two markets on the same question are the same market. Order still matters where it means something: rain before gas is not gas before rain.

02 · Settled before the bell

Most answers are final long before close.

The question you built in the instrument, run across thirty different market hours. Each dot is the moment its answer became final. A person resolving at close waits for the bell every time. An instrument settles the second the outcome is known.

03 · The catalogue

Markets multiply. The work does not have to.

Every new feed can be joined with every other one. Specified and resolved by hand, composite markets cost work for each pair. Compiled, each feed is described once and each way of joining them is written once.

Feeds described
6
Two-feed composite markets
78
Work by hand
156
Work compiled
10
04 · How it decides

Four ways to join a question.

True the moment A happens, if B has not happened yet. False the moment B happens first. A tie is not “before”. If neither happens, it is false at close. A · finalB
True when the second of the two happens. False the moment either one becomes impossible, which is at close for events, or earlier inside a window. AB · final
True the moment the first of the two happens; the second no longer matters. False only when both have run out of time. B · finalA
True the moment A happens inside the window. False the moment the window closes without it, even if the market stays open longer. window · finalA, too late
The bottleneck is turning human-readable conditions into executable instruments.
Paraphrasing Fermah, Oct 13, 2026: across 100,000+ resolved markets, each composite still required fresh specification and resolution work.
05 · Method

The instrument is open. Build your own question.

composite-sim
Compose a question from events and thresholds, read it back as English, compile it to a canonical content-addressed spec, and execute it against a market hour. Ten tests, including 480 random questions checked by stepping through every second of the hour.
# four questions on one market hour
npm run demo

# semantics, ids, the catalogue
npm test

Feeds on this page are generated from a seed and shaped like their real counterparts: a price walk, a gas series with spikes, a view counter, and events that arrive when events do. They are not market data. The composite counts are a model of two-feed questions with four ways to join them; they illustrate how the catalogue grows, not Fermah’s numbers. Fermah’s figure of 100,000+ resolved markets is their stated number.

Sources

  1. Fermah on composite markets scaling when conditions can be executed rather than interpreted, and on fresh specification work for each composite. @fermah_xyz, Oct 13, 2026.
  2. Fermah on content-addressed programs and onchain handoff turning one output into the next action’s input. @fermah_xyz, Oct 17, 2026.
  3. Kernel, the Protocol Agency Engine. fermah.xyz
  4. The model behind every result on this page. composite-sim

This dispatch is an independent model built by this desk. It is not published by Fermah and describes their thesis, not their implementation.