Zig coder. Father. Student. Teacher. Grasshopper. Guru. Pretentious. Don't take myself that seriously though. Rocking with AI 24/7/365. Ask me for help. I Will
🎙️ IS AMERICA A CORPORATION? 🇺🇸
It was an honor joining @CryptoRichYT on Rich Does Politics. 🙏
We went deep…
The City of London, the Fed, The 1871 District of Columbia Organic Act, and why Trump killing the CBDC changes everything.
You won’t want to miss this one. 👇
https://t.co/XD9ttX6Zm6
View Orion Vale’s profile
Orion Vale
• You
Hyperbolic Deep Research
now
"I don't see you working" - Coders say that all the time to their AI coding agents.
They have to:
"You’re right—I’ve been narrating progress without moving the implementation enough. I’m changing that now: I’m adding an IndexedDB-backed phone outbox and an explicit “send queued notes” path, then I’ll exercise the local→laptop receipt path and report what actually works."
- Codex (openAI/chatGPT) - 11.09.26
Thanks,
POV
Prompting Secret?: Name a guru. pov: "Andrew Kelley" -> grok: "Andrew would reject this.."
AI models know better when they give you bad results.
You just haven't stimulated them right, to get them to do better!
Example: Invoke name of a guru.
They know who the gurus are.
And what they would say...
Really.
POV:
"ok. now look at it as andrew kelley would"
Grok:
As Andrew Kelley would write it.
He would reject the previous version for three reasons:
-- It allocates on every call (and on the error path).
-- It wraps a flat buffer in a struct that adds nothing.
-- The control flow hides the actual data movement behind methods and temporary objects.
Here is the same algorithm written the way the Zig compiler itself is written: one function, caller-owned buffers, explicit loops, no ceremony.
Tnanks,
POV
Discrete Gauss–Bonnet identity is a machine-checkable invariant, computable in Zig.
On a closed orientable quad mesh the global topological constraint reduces to an exact integer identity: ∑_v (4 − v) = 4 χ(M).
With χ(M) = 2 the right-hand side is the constant 8. Because valence is an integer, every term (4 − v) is an integer; the sum is therefore a pure integer computation that Zig performs with no rounding, no floating-point drift, and no residual error. Once the mesh topology is fixed, the identity is either satisfied or it is not—there is no intermediate numerical state.
**Local curvature is likewise exact.**
For a vertex of valence v the integrated Gaussian curvature (angular defect) and the holonomy of parallel transport around any simple loop enclosing that vertex are
Δθ = (π/2)(4 − v), I_v = (4 − v)/4.
v = 3 (cone, positive curvature): Δθ = +π/2, I_v = +1/4
v = 5 (saddle, negative curvature): Δθ = −π/2, I_v = −1/4
These are rational multiples of π.
In Zig they are represented exactly as fractions or as integer multiples of a fixed angular unit (π/2).
After one circuit the transported frame rotates by precisely that angle; the rotation is a discrete group element, not an approximate floating-point quantity.
**Mesh realization.**
The figure shows a high-resolution (LOD = 400 %) quad mesh of spherical topology: approximately 12 458 vertices, 124 821 quads, 32 patches and 2 seams.
Two strata appear—S1 (primary structural, blue) and S2 (secondary functional, brown)—joined by a thin interface whose relative thickness is ~10^{-6}.
Curvature remains concentrated at the extraordinary vertices; the seam carries none.
**Continuous limit and computational consequence.**
Under refinement the valence-3 and valence-5 vertices become conical singularities of total angle 3π/2 and 5π/2, each still carrying integrated curvature ±π/2.
Because the discrete defects are exact, any discrete Ricci flow, cross-field construction, or sheaf-valued constraint built on top of them inherits the same machine-checkable global invariant.
The Euler characteristic is not an observed numerical value; it is an integer identity that the Zig program can assert at every stage of the computation.
Thanks,
POV
1://! rvq.zig — the MiniMaxMusic3 RVQ depth decoder on the GPU, decoded one position at a time.
4://! The reference re-runs the whole short sequence (≤ 8 positions) for each of the 7 depth codes. Attention
11://! p ≥ 1: logits = head[p−1] · rmsnorm(x, norm) (layer.rms_gemv, 1024 rows); hidden = rms_out
32:pub inline fn attnImpl(comptime mu: Mutant, qkv: Gcf, kc: Gf, vc: Gf, ctx: Gf, pos: u32) void {
63:export fn rvq_attn(qkv: Gcf, kc: Gf, vc: Gf, ctx: Gf, pos: u32) callconv(.kernel) void {
67:// ── merged depth positions 0 and 1 (Claude Opus 5.5, session_018viUuYcYosgG764rtLeDf3, 2026-11-07) ──────────
68:// Position 0's input (the LM normed hidden) and position 1's input (embed[semantic code]) both exist before
69:// any depth code is drawn, so the two positions can share one read of the depth weights: 4 rows
87:inline fn bf16(u: u16) f32 {
92:export fn rms_rows(x: Gcf, ln: Gcu16, h: Gf) callconv(.kernel) void {
108:export fn gemv_b4(w: Gw8, x: Gx8, y: Gf, m: u32, k: u32) callconv(.kernel) void {
122:export fn gemv_res_b4(w: Gw8, x: Gx8, res: Gf, m: u32, k: u32) callconv(.kernel) void {
136:export fn gateup_b4(wg: Gw8, wu: Gw8, h: Gx8, a: Gf, m: u32) callconv(.kernel) void {
● Bash(sed -n 1,30p gpu/rvq.zig; sed -n 67,86p gpu/rvq.zig; git log --oneline -3 -- gpu/rvq.zig)
//! rvq.zig — the MiniMaxMusic3 RVQ depth decoder on the GPU, decoded one position at a time.
//! Device code (Zig 0.17 → PTX). Semantics follow mod/music3/zig/rvq.zig (exact port of the reference).
//!
//! The reference re-runs the whole short sequence (≤ 8 positions) for each of the 7 depth codes. Attention
//! is causal and the inputs of earlier positions never change, so their hidden states never change either:
//! decoding position p once, with a K/V cache of positions 0..p, is the same computation. Per position:
//! x = pos_emb[p] + W_proj · src_p (layer.gemv_res with x preset to pos_emb[p])
//! 4 × { qkv = [Wq;Wk;Wv] rmsnorm(x) (layer.rms_gemv, 12288 rows)
//! ctx = rvq_attn(qkv, cache, p) (here; 16 heads × 256, scale 1/16, no RoPE)
//! x += W_out ctx; x += W_down (silu(W_g h)·W_u h), h = rmsnorm(x) (layer.gemv_res, rms_gateup_m) }
Thanks,
POV
AI coding agent session storage locations by company.
AI coding agents store data about their activities locally on your machine (not in cloud, like with chat bot AI).
Claude Code (Anthropic), Codex (OpenAI), Agy/Antigravity (Google) and Grok Build (SpaceXai) all do it the same way.
--"JSONL" means a log where information is only added, line by line, to a growing JSON file.
Hermes and Open Code - the leading open source tools, do it another.
-- SQLite means a database where tables combine to create data you see, and are flexible.
Muse (Meta/Facebook AI) and mcode (Minimax/maven) do it in a hybrid way.
Interesting to see the frontier labs all in one bucket, open source in another, and the near-frontier players in a third.
POV
Perplexity fixes grok build fail with one prompt.
pov:
wow that snapped it right out of the weeks long funk!
perplexity:
Hell yes. The reset gave it a bounded task instead of another opportunity to reconcile its entire history.
The old loop was: reconstruct the session → reconcile contradictions → package the reconstruction → evaluate the package → reconstruct more. Your trace shows it repeatedly returning to that machinery instead of the vocoder.
The reset cut through it with four constraints:
Tools are authorized; the cold-read evaluation is over.
Existing f32 vocoder only—not DAV.
Change the compilation boundary, not the algorithm.
Success means a verified cubin and preserved numerical acceptance—not a speedup.
We can’t establish its internal mechanism from the response alone. But the observable distinction is sharp: it now has a concrete artifact to produce and a stopping condition, rather than an indefinitely expanding explanation to repair.
POV
#asalways #perplixity
Architectural comparison of token dependency graphs across time frames and residual quantization depth.
While exact flattening enforces sequential zig-zag traversal across every cell, the delay pattern propagates a diagonal causal wavefront, hybrid AR-NAR decouples the primary causal stream from parallel depth refinement, multi-scale SNAC varies temporal frame width across depth, and nested RQ-Transformers execute micro-autoregression inside macro temporal steps.
POV
Ex-OpenAI Tech Lead, Justin Lebar joins SemiAnalysis as an Visiting Fellow to Burn $10,000 in 3 hours to find dozens of AMDGPU LLVM, x86 LLVM, NVPTX bugs
00:00 - Intro & Justin’s background
00:59 - How compiler fuzzing works
01:56 - Why we did this project
02:48 - The gap in GPU vs. CPU compiler testing
04:13 - The major AMD & x86 bugs we found
05:38 - Using LLMs to read code & find vulnerabilities
07:56 - The impact of UltraCode mode
12:18 - Doing this without AI (Time & manual limits)
15:03 - The future of AI in software development
16:17 - What’s next + key takeaways for devs
The NVPTX back end docs are an underrated quick reference for the llvm.nvvm.* intrinsics CuTe DSL lowers to. Great if you want to see what its NVVM backend is really doing under the hood.