Independent Matrix Slices and Epoch-Checked Hierarchical Merge in a Solana Transformer Runtime

Parallel arithmetic does not by itself imply parallel transaction execution when workers share writable result accounts or a fee payer. This report examines an implemented partition protocol in the public `staccDOTsol/break-solana-chat` fork. A Qwen3-8B-shaped runtime assigns fixed matrix slices to separate result accounts and fee payers, collects them into sixteen lane accounts, and advances a shared session through an epoch-checked merge. An ordinary full matrix wave contains 96 slice transactions; a feed-forward down-projection wave contains 256. These are source-derived instruction counts, not measured throughput. Seven existing client tests were rerun unchanged in isolation and passed, checking account metadata, payer separation, collector construction and scheduler ordering or failure. The production Rust library also passed a locked host compilation check. The original SBF benchmark could not be rerun because exported model shards, their manifest and the compiled program ELF were absent from the recovered public tree. We distinguish these fresh findings from historical project receipts, including a partial matrix-wave report that explicitly records no complete reply. Commit comparison also corrects the catalogue chronology: the September implementation has independent lanes, while independent within-lane slice accounts and completion bits first appear in the recovered public history in October. The result is a reproducible component study of execution partitioning and result admission, with explicit cost, configuration and verification limits. This component report addresses catalogue account C07 and distinguishes the historical September lane implementation from the October independent-slice implementation. Manuscript text is CC BY 4.0; upstream source retains its original notices and license markers. Jarett Dunn, independent researcher. Technical report, version 1.0. Preprint, not peer reviewed. Codex assisted source recovery, analysis, test orchestration and writing. Report text is CC BY 4.0; upstream software retains its licenses and attribution.