# Carried benchmark patch and attribution review — 2026-10-04

This is source-file and licence/attribution review, not an engine build,
linked-product licence admission, runtime, timing, physical or release gate.
Existing preparation recipes, candidate defaults, patch bytes and sealed
campaigns are unchanged.

## Reviewed inputs

The source generation is `8c080cb02a4595e665e91b5f4c22476fdfd4fc3f`.
Its complete selected harness contains 752 files, including the three export
templates. The public `patch-provenance.json` records exact patch hashes,
immutable upstream URLs, original target hashes, licence/attribution hashes
and independently calculated expected patched-target hashes.

| Upstream | Reviewed commit | Material inspected |
|---|---|---|
| Fix8 | `fd6a550685ed9addbdccb27e605eb11e5ff949e0` | Patched header, `LICENSE`, `COPYING`, `AUTHORS`, `CONTRIBUTORS` |
| libtrading | `9cf4dfa58fd7201935f7bf7e9046d78653e041d3` | Patched header and `LICENSE` |
| NanoFIX | `0f79bae0ad141653c80cf01c60c807649a6adf7b` | Patched source and `LICENSE` |
| Aeron compatibility dependency | `920c266acc79f0bab642b83aeddd720875faa0b5` | `LICENSE` |

These are ten declared upstream files, not whole engine source archives.
The upstream target files and licence/attribution files are retained only in
the private sealed archive. The committed declaration links to the exact
upstream material. Matching these individual files does not attest an older
cached source tree's whole commit. The local cached libtrading header matches
the reviewed patched target; the cached Fix8 and NanoFIX targets match their
reviewed originals. Existing cached inputs were read only.

Fix8's target header explicitly grants LGPL version 3 or later; its `COPYING`
contains LGPL v3 and `LICENSE` incorporates GPL v3. libtrading retains its BSD
copyright, conditions and disclaimer. NanoFIX retains its MIT copyright and
permission/disclaimer; the inspected Aeron licence is Apache 2.0. The harness
notice now makes clear that its Apache licence does not replace upstream terms
on patch context and modified source. Linked or distributed products still
need review of the actual components and linking form.

## Original HP refusal

HP's host slot and running processes were inspected before the job. The
outer foreground check obtained `shared` at high priority. GNU `patch` was
absent, so the first patch operation could not start. No engine was built or
run. Its exact outer log, original runner and failure receipt remain in
[the original evidence](evidence/patch-review-20261004/qualification/result.json)
and [lease log](evidence/patch-review-20261004/hp-lease.log). This is not a pass
and is not overwritten by the local result.

## Local source-file completion

The same original checks ran locally with GNU patch 2.8 after process and memory
inspection. This subsecond file check added no heavy build or suite beside the
other session's JVM. The sole runner changes select a distinct local output and
materialization directory. No assertion or patch command changed.

All fifteen patch operations pass their expected exits: for each of three
patches, dry run and real application succeed without fuzzy context, a second
dry-run application refuses, and reverse dry run plus reversal restore the
original target bytes. Actual patched hashes equal the separately computed
edit results. Every other supplied file stays unchanged. There is also one
successful Git initialization of the unrelated enclosing parent; the stripped
archive never borrows its inputs. No patch operation is skipped.

The [local receipt](evidence/patch-review-20261004/qualification-local/result.json)
retains all sixteen command/exit records and byte comparisons. Both streams of
each real command remain verbatim. The full harness's 752 file bytes and modes,
all declared upstream input bytes and the foreign-parent sentinel are unchanged.
The local materializations are removed. Both hosts verify all 56 sealed archive
files and the seal itself. The failed HP materialization and both owning cache
capsules are now removed after their exact bytes were checked against that
archive. The first cleanup guard incorrectly expected the locally written
`hp-lease.log` in the remote capsule, and refused before deleting anything.
Its exact reproduced stderr and original checker remain separate; correcting
that sole host-local inventory expectation preserves every content/mode check.
The corrected cleanup receipts identify only this generation's owning paths.

No SDK compilation, native-library load, codec/converted-value qualification,
session pair, measurement, Stage 5 or release admission is supplied. Public
release still requires whole source pins, dependency/runtime inventories and
the distribution review for every enabled driver.

## Retention

`~/archive/libhft/patch-review-20261004` retains the whole harness archive,
the ten upstream input files, independent expected edits, both actual runner
sources, original refusal, local output and environment. The
[private archive receipt](evidence/patch-review-20261004/private-archive.json)
identifies its seal. Committed evidence contains hashes, command streams and
receipts, rather than upstream target source copies or SDK products.