Hierarchos Native's creator claims its released Rust and Vulkan backend supports training and inference across 143 canonical Transformer architectures without CUDA or PyTorch, potentially broadening hardware-portable model execution.

state: watchingheat: lowuncertainty: mediumknownscott: lowvulkan-inference portable-llm-runtimes ai-infrastructurenecat101PhysicsDisastrous462

What is this?

Hierarchos Native is described in the supplied case as a creator-built Rust/Vulkan backend claiming training and inference support for 143 canonical Transformer architectures without CUDA or PyTorch; the case lists necat101 and PhysicsDisastrous462, but the snippets do not establish their respective roles. The directly relevant search hit is a Reddit post titled “Hierarchos Alpha v0.30: Toward a Vulkan-Native …,” describing a backend being designed around forward propagation, backpropagation, gradient accumulation, batching, and optimizers. That development-oriented wording does not verify the claimed released coverage: the supplied snippets establish neither working support for all 143 architectures nor tested hardware portability or performance.

Why it matters to Scott

The portability claim repeats a direction already held in Scott’s Hardware-aware local inference and Sovereign Software Assurance pages, with a concrete dependency connection to gamepc’s CUDA/PyTorch stack. However, the supplied evidence establishes neither usable replacement coverage nor tested portability or performance, so it does not yet change his runtime choices; the radar tracks related alternatives, not this specific development.

dev:concept.hardware-aware-local-inferenceip:framework.sovereign-software-assurancedev:project.gamepcdev:technology.cudaradar:concept.inference-runtimesradar:voxgen-vulkan-amd-ttsradar:cuda-amd-windows-reproducible-stack

queries asked of Scott's wikis

local inference runtime selection hardware portability
CUDA dependency GPU vendor lock-in model sovereignty
Rust Vulkan GPU compute projects
portable training backends fine-tuning workflows
model runtime compatibility correctness benchmarks

Measured heat

now 0 pts/hpeak 13 pts/hcomments 0/hpeers p0momentum: steady2 platformsage 592h

points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion

How the heat travelled

09-17 00:22 (minted)	⭐ origin echo-reconstructed	The creator's cross-posts describe a native Rust and Vulkan training and inference backend covering 143 canonical Transformer architectures necat101 on github (echo) · attributed from reddit.post.1widomo, reddit.post.1widush · published time unknown	—
09-16 23:43	first on r/LocalLLaMA · published · lag ?	I built a native Vulkan training backend for 143 modern Transformer architectures — no CUDA or PyTorch required PhysicsDisastrous462	—
09-16 23:50	first on r/singularity · published · lag ?	I built a native Vulkan training backend for 143 modern Transformer architectures — no CUDA or PyTorch required PhysicsDisastrous462	—
09-16 23:43	amplified on r/LocalLLaMA 👑	reddit.post.1widomo PhysicsDisastrous462	peak 38 · 31 comments · 54% of case engagement
09-16 23:50	amplified on r/singularity	reddit.post.1widush PhysicsDisastrous462	peak 13 · 1 comments · 11% of case engagement
09-30 14:25	amplified on r/LocalLLaMA	reddit.post.1wu6cbl PhysicsDisastrous462	peak 9 · 1 comments · 8% of case engagement
09-30 14:41	amplified on r/singularity	reddit.post.1wu6qta PhysicsDisastrous462	peak 18 · 2 comments · 16% of case engagement
10-07 23:34	amplified on r/LocalLLaMA	reddit.post.1x0bttq PhysicsDisastrous462	peak 1 · 3 comments · 3% of case engagement
10-07 23:35	amplified on r/singularity	reddit.post.1x0bupe PhysicsDisastrous462	peak 1 · 9 comments · 8% of case engagement
09-17 00:20	our radar first saw it · lag ?	discovery anchor: reddit.post.1widomo	—

pace: p67 vs 1032 stories at the 336h mark (now 592h old) — ahead of maccconc-kernel-race-testing (1.0x), behind applied-compute-training-serving-platform (1.0x)

Evidence (7) — ⭐ canonical anchor

source	object	author	score	comments
🟠 reddit	I built a native Vulkan training backend for 143 modern Transformer architectures — no CUDA or PyTorch required LocalLLaMA	PhysicsDisastrous462	37	31
🟠 reddit	I built a native Vulkan training backend for 143 modern Transformer architectures — no CUDA or PyTorch required singularity	PhysicsDisastrous462	13	0
🟧 echo.github ⭐	The creator's cross-posts describe a native Rust and Vulkan training and inference backend covering 143 canonical Transformer architectures	necat101	—	—
🟠 reddit	Follow-up: my native Rust + Vulkan Transformer training backend — 14 days later, now 14 parity-verified architectures and full PEFT LocalLLaMA	PhysicsDisastrous462	8	1
🟠 reddit	Follow-up: my native Rust + Vulkan Transformer training backend — 14 days later, now 14 parity-verified architectures and full PEFT singularity	PhysicsDisastrous462	18	1
🟠 reddit	Follow-up: my native Rust + Vulkan Transformer backend now qualifies on both an Intel Gen9 laptop and an AMD RDNA 3 handheld from the same build — the GPU vendor is no longer what picks the reduction shape LocalLLaMA	PhysicsDisastrous462	0	3
🟠 reddit	Follow-up: my native Rust + Vulkan Transformer backend now qualifies on both an Intel Gen9 laptop and an AMD RDNA 3 handheld from the same build — the GPU vendor is no longer what picks the reduction shape singularity	PhysicsDisastrous462	0	9

Interpretation history

2026-10-08T00:27:04Z
The creator's third follow-up adds a first-party portability milestone — a single build now qualifies on Intel Gen9 and AMD RDNA 3 after fixing kernel shapes wrongly baked into the portable path — upgrading the portability claim from AMD-only to demonstrated vendor-agnostic execution, though still entirely self-graded. Verified architecture coverage is unchanged at 14/143, and engagement has collapsed to ~zero (1 pt / 0 comments per cross-post), so this remains a low-heat cadence watch on a single-actor project whose decisive unknowns are performance vs CUDA/ROCm and any independent validation.
2026-10-08T00:26:04Z
evidence attached: reddit.post.1x0bupe — Same creator's follow-up: one build now qualifies on Intel Gen9 and AMD RDNA 3 with full PEFT — direct progress evidence on the portability claim.
2026-10-08T00:26:04Z
evidence attached: reddit.post.1x0bttq — Follow-up from the same Rust+Vulkan transformer backend project showing cross-vendor (Intel Gen9, RDNA 3) qualification and a portability fix bears directly on its portability claim.
2026-09-30T16:07:28Z
The creator's own 14-day follow-up reframes the headline: parity-verified training coverage stands at 14 of the advertised 143 architectures (up from 7) with full PEFT, checked against a pinned Hugging Face Transformers oracle — a rigorous but entirely self-graded harness. The case is now a cadence-tracking story on a single-actor project with zero third-party validation, not a community-validating one.
2026-09-30T15:27:10Z
evidence attached: reddit.post.1wu6qta — First-party follow-up from the same creator confirming parity-verified architecture growth and PEFT support on the Rust+Vulkan training backend.
2026-09-30T15:27:10Z
evidence attached: reddit.post.1wu6cbl — Same creator's follow-up showing 7→14 parity-verified architectures plus full PEFT is direct progress evidence for the open 143-architecture claim.
2026-09-17T00:25:31Z
grounded: known/low — The portability claim repeats a direction already held in Scott’s Hardware-aware local inference and Sovereign Software Assurance pages, with a concrete depende
2026-09-17T00:22:29Z
case created — The linked backend is a concrete systems artifact distinct from existing cases; both cross-posts belong to one episode and do not independently validate its advertised coverage.

Decision trace

10-11 21:10review_screenjev screen: no material development (noul=0.15)
10-08 23:33sensor_dirtycomment_update
10-08 11:32attention_routeThe editor compared this story and chose to keep watching.
10-08 11:27attention_candidatematerial_reprice
10-08 11:27repriceThe creator's third follow-up adds a first-party portability milestone — a single build now qualifies on Intel Gen9 and AMD RDNA 3 after fixing kernel shapes wrongly baked into the portable path
10-08 11:26attention_candidateattach
10-08 11:26attachSame creator's follow-up: one build now qualifies on Intel Gen9 and AMD RDNA 3 with full PEFT — direct progress evidence on the portability claim.
10-08 11:26attachFollow-up from the same Rust+Vulkan transformer backend project showing cross-vendor (Intel Gen9, RDNA 3) qualification and a portability fix bears directly on its portability claim.
10-08 11:26propose_attachSame creator's follow-up: one build now qualifies on Intel Gen9 and AMD RDNA 3 with full PEFT — direct progress evidence on the portability claim.
10-08 11:24propose_attachFollow-up from the same Rust+Vulkan transformer backend project showing cross-vendor (Intel Gen9, RDNA 3) qualification and a portability fix bears directly on its portability claim.
10-01 02:07repriceThe creator's own 14-day follow-up reframes the headline: parity-verified training coverage stands at 14 of the advertised 143 architectures (up from 7) with full PEFT, checked against a pinned H
10-01 01:27attachFirst-party follow-up from the same creator confirming parity-verified architecture growth and PEFT support on the Rust+Vulkan training backend.
10-01 01:27attachSame creator's follow-up showing 7→14 parity-verified architectures plus full PEFT is direct progress evidence for the open 143-architecture claim.
10-01 01:24propose_attachFirst-party follow-up from the same creator confirming parity-verified architecture growth and PEFT support on the Rust+Vulkan training backend.
10-01 01:22propose_attachSame creator's follow-up showing 7→14 parity-verified architectures plus full PEFT is direct progress evidence for the open 143-architecture claim.
09-18 01:23review_screenThe added comments are opinions, implementation suggestions, and questions about unverified RDNA 2 compatibility; they provide no new test result, release, contradiction, or other consequential eviden
09-17 22:20sensor_dirtycomment_update
09-17 18:25review_screenThe new comments express interest and ask about a potential feature but provide no implementation result, validation, contradiction, or other material evidence about the backend's claimed coverag
09-17 11:21sensor_dirtycomment_update
09-17 10:25groundThe portability claim repeats a direction already held in Scott’s Hardware-aware local inference and Sovereign Software Assurance pages, with a concrete dependency connection to gamepc’s CUDA/PyTorch
09-17 10:22createThe linked backend is a concrete systems artifact distinct from existing cases; both cross-posts belong to one episode and do not independently validate its advertised coverage.