Home › Evidence › Records › con-0012
⚠ This notebook has stopped taking notes: newest record is 23 days old (eng-0280), against an expected cadence of 14 days.

con-0012

carrying
citable URL: https://halobench.com/records/con-0012/ — this address never moves; the anchor /records/#con-0012 keeps resolving
kind fork · upstream ciru-ai/ROCmFPX
opened 2026-08-23 · https://github.com/ciru-ai/ROCmFPX
carrying — reproducibility hazard: in use but not upstream. Every config listing this id in its divergence runs a fork.
The Kairic Edge Qwen3.8-27B-IU4 build (branch kairic-edge-qwen38-27b-v1.1, commit e1da26bb8) from ciru-ai/ROCmFPX — a vendor-authored fork that binds the ROCmFPX binary (called "TheRock" stack here because the carrier vendor certifies it against TheRock 7.14 / AMD clang 23.0.0) to a custom 4-bit IU4 sidecar layout: a Q4-ish quant GGUF (Qwen3.8-27B-IU4-Kairic-Edge.gguf) + three PROMPTFORGE_* .pfs sidecars (FFN, GDN, GDN-Output) that accelerate the FFN and GDN projector paths on gfx1151, plus a --kairc-edge server flag and a compat mode (KAIRIC_EDGE_COMPATIBILITY_MODE) that enables tool-calling where fast-greedy forbids grammar/tool calls. HK-001 on aihydra rebuilt this at commit e1da26bb8 (binary e121a4d3, model sha 360caf73, sidecar hashes adcbb90a/82f93129/3b07e7b1, gfx1151 / AMD clang 23.0.0). It is a carried fork — results produced with it are fork-specific and must not be attributed to stock llama.cpp, and not to any one bundled patch. Backwards the fixed GDN output path is NOT accelerated (gdn_output_fallback 48) on this aihydra build and the toolchain differs from the vendor-certified one (ROCm 7.1 vs 7.14, LLVM 21 vs AMD clang 23), so the vendor's throughput claims do not transfer; every number must be treated as measured-here on this exact build. [2026-08-24 v1.2 RUNTIME MANDATE — HK-V12-ANNOTATE, per t_b05473c9] The vendor released runtime tag kairic-edge-qwen38-27b-v1.2 @ 205a3e5f (HF repo updated 2026-08-23T14:28:32Z): the v1.1 native IU4 M65 verifier could flip a greedy target token on a low-margin reproduced case; v1.2 defaults to the strict-compact authoritative verify path (unsafe native only via KAIRIC_UNSAFE_NATIVE_M65_VERIFY=1). GGUF + all three .pfs sidecars are byte-unchanged (gguf sha 360caf73…), so throughput records stand. Vendor validation: 6/6 exact-match to frozen no-spec target, draft acceptance 99.73%. ALL FUTURE Kairic Edge box runs MUST build from the v1.2 tag; every HK run recorded to date used v1.1 and carries a comparability annotation on its claim (clm-0116, clm-0118, clm-0119).

Cited by — computed at build time, never stored

claims clm-0116
candidate gate history qwen38-27b