Тема
Governed capture smoke — 2026-08-08
ИСТОРИЧЕСКОЕ ДОКАЗАТЕЛЬСТВО. Описанный standalone recorder, replay и sweep сняты 2026-08-22. Числа ниже сохранены как датированный факт прежнего прогона, но не задают текущий профиль, команду или критерий приёмки.
This record is the operational evidence for OpenSpec change capture-completeness-and-bounded-recording. It is not profitability evidence.
Validated run
| Field | Result |
|---|---|
| VPS session | 1786215056338-1 |
| Bounds | 180 s / 1 GiB current pair / 64 GiB free reserve |
| Stop | duration, exit 0 |
| Event records | 280,792 |
| Coverage markers | 4 |
| Gamma pages | 8 |
| Referenced / hydrated tokens | 2,584 / 2,684 |
| Engine-events bytes | 108,604,091 |
| Gamma bytes | 16,258,692 |
| Pair bytes | 124,862,783 |
| Remaining filesystem bytes | 121,843,920,896 |
| Observed pair rate | about 2.33 GiB/hour |
The terminal seal carried reason=duration and gamma_bytes=16258692, equal to the sidecar size. Both artifacts were deploy:deploy. The trading engine remained running with unchanged StartedAt=2026-08-07T23:41:10.832339636Z and its binary hash remained a3d6df912b426b9a97eea872aa57f5ff37f037a978b3f459830ea04d10e9b037.
Two baseline replays against the read-only live harvester-engine-v2 config processed 269,147 frames / 268,959 decisions and produced the same determinism hash 06141ade3d65218df05c1be6284bc8337b6207883da64f776212f3916c41c3e4. Both had zero orders and fills, so this short pair proves replay acceptance and determinism but is explicitly insufficient for parameter tuning or EV claims.
Disconfirming run and correction
The preceding sealed smoke session 1786214101160-1 was rejected by the strict validator: an exchange-global NewMarket outside tag 104596 referenced a condition absent from the filtered Gamma discovery sidecar. The recorder was corrected to admit NewMarket / MarketResolved only when their outcome is already inside the ordered captured universe. The validator was not weakened.
Production follow-up
At the observed rate, 12 hours projected to about 27.9 GiB. The initial production follow-up therefore used a 12-hour duration, 32 GiB current-pair cap and 64 GiB free-space reserve. Session 1786215591756-1 started in the separate weather-sealed directory at 2026-08-08T18:59:51Z; sweep remains blocked until a sealed representative pair validates and baseline replay has non-zero expected orders/fills.
That follow-up stopped at 2026-08-09T05:31:11Z after about 10.5 hours with 34,360,835,420 bytes across the pair: effectively the configured 32 GiB cap, not the requested 12-hour boundary. The operator subsequently required the production limit to be raised from 32 GiB to 64 GiB and the observation window to cover a full day. The versioned profile therefore now uses 24 hours / 64 GiB pair / 64 GiB reserve. CaptureBounds refuses startup unless the whole pair cap fits above the reserve; storage must be freed or expanded before that profile can start, rather than silently producing another short recording.
Сама запись удалена 2026-08-21
Решением оператора накопленные пары сняты: локальные три сессии (879 МБ, включая 1786215056338-1 из таблицы выше) и каталог записей на VPS. Числа в этом документе — единственное, что от того прогона осталось; переигрывать или перепроверять его нечем. Механизм записи pm-engine --capture-only и его профиль после решения 2026-08-22 удалены.