FUA wing · Door 02

A block was served. Nobody can show what your automation did in the next second.

Block-and-Stop Audit

The problem

A publisher, a platform, or a counterparty served a block. The question that follows is never whether the block existed — it is what your system did once it arrived. Logs that record requests do not record restraint.

What the reading shows

• Whether the block appeared in the observed sample.
• Whether collection resolved to a stop under the disclosed protocol.
• Whether any alternate-route retry was observed after the block.

What it does not establish

• Whether the block was validly served or legally binding.
• Whether conduct outside the disclosed sample behaved the same way.

Where this door goes

Path: M01

The twelve are doors into one nine-module instrument, not twelve separate products. Every engagement begins with the sealed M01 baseline; the modules enter only where the defined question requires them.

M02, M03, M04 and M09 consume M01. M05-M08 require M03. M03 requires M02. M02 requires M01.

Module composition is how the work is built, not how it is priced or sold. There is one way in and it is the briefing.