{
  "host": "scan",
  "cell": "java-jni/vma/pool",
  "classification": "rejected role-identity evidence; no latency imported",
  "source_commit": "141f550ad3b45d0aa84187dfa8ca4cdfe085da97",
  "runtime_build_source": "3e4de53c752b3b3b478038c2c615171b9cc440d6",
  "evidence": "/tmp/libhft-pool-cells-20260910-lE99Tb/java-jni-vma-pool/pool/java-jni/vma/attempt-u_8nnjr0/run",
  "publication_driver_interrupted_utc": "2026-09-10T01:29:08Z",
  "publication": "Driver explicitly interrupted before import after repeated live role-identity violations. The bounded harness subsequently finished and its JVMs exited. The previous matrix row is unchanged.",
  "startup_and_live_readbacks": [
    {"role": "coordinator", "pid": 592698, "tid": 592744, "requested_cpu": 19, "actual_cpu": 19, "observed_name": "hft-pool-coord"},
    {"role": "VMA maintenance", "pid": 592698, "tid": 592749, "requested_cpu": 14, "actual_cpu": 14, "observed_name": "hft-pool-coord"}
  ],
  "live_pinning_samples": {"VIOLATION": 17, "INCONCLUSIVE": 2},
  "cause": "JNI named the coordinator before the listener's Bind initialized VMA. Linux child threads inherit their creator's name, so the maintenance thread acquired the same application-role identity despite its separate correct affinity.",
  "source_correction": "Retain the pre-bind affinity gate; establish and verify the coordinator name only after transport initialization, before publishing the bound port or starting workers. Do not exempt duplicate coordinator identities from the live audit.",
  "regression": {
    "fixture": "engine/java/src/test/native/test_acceptor_poll_failure.cpp",
    "scope": "actual JNI pool binding with inert transport, helper created by Bind, no JVM/VMA/socket; housekeeping cores only",
    "previous_source": "fails inherited creator-name assertion (exit 134; core dumps disabled)",
    "corrected_source_ssl_disabled": "PASS",
    "corrected_source_ssl_enabled": "PASS",
    "placement_formatter_and_call_order_tests": 2,
    "unchanged_live_pinning_tests": 23,
    "evidence": "/tmp/libhft-jni-coordinator-name-20260910-T9qGyl"
  },
  "hashes": {
    "live_pinning_log": "260be0826b1af6c8089da5d6efa9814492a032356249d39a99c99af2d46fc166",
    "interrupted_sweep_json": "e54608cbe213879dc9c4e4a13733589a8031e0fd34085c47bc8c8bd5110209b5",
    "corrected_ssl0_test_log": "457ea3599967287eec3102820eeac38acad313386a3d5de6a21851a59dabff0c",
    "corrected_ssl1_test_log": "680543a41b91e079fd78d9e0a45f20ea028ab70394269d9a09a623a0ce602981"
  },
  "limitations": [
    "This corrects thread-role identity, not the separate intermittent VMA payload stall or latency variation.",
    "Source tests passed; rebuilt installed JNI and a new live run are still required.",
    "The current canonical driver checks startup readbacks but does not automatically consume the separate live watcher; this attempt was stopped manually before import."
  ]
}