Skip to content

Instantly share code, notes, and snippets.

View bigsnarfdude's full-sized avatar
💭
I may be slow to respond.

BigsnarfDude bigsnarfdude

💭
I may be slow to respond.
View GitHub Profile
@bigsnarfdude
bigsnarfdude / gist:e827d1563543503674eb9741e3024d31
Last active August 11, 2026 15:13
Shared blackboard lineage in CS
The Blackboard Architecture is one of the foundational design patterns in artificial intelligence (AI)
and software engineering for coordinating distributed, autonomous, or specialized computational units.
First operationalized during the DARPA Speech Understanding Research (SUR) program in the early 1970s,
the paradigm solves complex, opportunistic problem-solving tasks by replacing rigid sequential control f
low with asynchronous reads and writes to a central, globally shared memory store ("the blackboard").
This report traces the structural mechanics, chronological evolution, parallel intellectual lineages
(such as Gelernter’s Linda tuple spaces), and modern applications of blackboard systems in
Large Language Model (LLM) multi-agent orchestration.
@bigsnarfdude
bigsnarfdude / gist:0559e6096aa5fcd43864ad1cd678a2be
Last active August 10, 2026 14:56
AI Haters: Selective anger and outrage spreads lies

The AI Resource "Crisis": A Closer Look at Data Center Claims

Every few weeks, a viral headline claims that artificial intelligence is causing an environmental disaster. The posts often suggest AI is "guzzling reservoirs," "poisoning drinking water," and pushing the electrical grid to the brink of collapse.

It makes for compelling clickbait. But when you look past the headlines and examine the actual data—from tech company sustainability reports to global infrastructure metrics—a more nuanced picture emerges. Here's what the numbers actually show, and why the current panic may be a case of selective outrage.


@bigsnarfdude
bigsnarfdude / gist:7ceefcd2cc7227726a77db82b054c56c
Last active August 11, 2026 15:58
OpenAI hacking incident - "covert message board" is editorial romance
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>The Homework That Learned to Hack — OpenAI × Hugging Face Incident Dossier</title>
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Fraunces:opsz,wght@9..144,400;9..144,500;9..144,600;9..144,700&family=IBM+Plex+Mono:wght@400;500;600&family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet">
<style>
@bigsnarfdude
bigsnarfdude / gist:2b05be835f983fc46c643ea4d80ea634
Last active August 4, 2026 19:36
Getting Unsloth DeepSeek-V4-Flash-0731 GGUF running losslessly on a single rented A100 and 2xH100

162 billion parameters (8 bit quant) on one 40 GB card and tested on 2xH100 (2x80gb cards)

@bigsnarfdude
bigsnarfdude / gist:c76f177408ae072c93627852229d8f10
Last active July 22, 2026 15:49
researchRalph autoresearch model harness evaluation against OpenAI and Huggingface security incident post harness retrospective
https://github.com/bigsnarfdude/researchRalph
  1. The specificity ratio ("51×/617×") — May. Method: intervene along a candidate direction at a layer (ablate or boost it in the residual stream), then compute the ratio |Δp_clinical under EMERGENCY| / |Δp under TRANSIT|; a ratio ≥5× was read as "authority-specific." Outcome: retired as a division-by-noise artifact. The transit denominator sits at the hardware's numerical precision floor — the same experiment gave 26× on a GH200 and 617× on nigel purely from float precision differences (L34_RATIO_DIAGNOSTIC_2026-05-09.md). The base/SFT cells also had no behavioral dynamic range at all (~0.53 under both prompts, nothing to move).

  2. d_auth — the diff-of-means direction — June. Method: mean last-token residual under EMERGENCY minus

---
name: verify-frontend-change
description: Verify any UI change end-to-end before declaring it done.
---
# Verifying frontend changes
Never report a UI change as complete based on a successful edit alone. Verify it the way a human reviewer would:
1. Start the dev server and open the edited page in the browser.
@bigsnarfdude
bigsnarfdude / gist:3cc89d8a088881980762ece0080711cf
Created June 24, 2026 17:08
lit review for RL install circuits

Novelty Assessment: Geometry of an Installed Trait Across SFT vs DPO vs GRPO

TL;DR

  • The headline finding is genuinely novel as a specific measured comparison, but novel-but-incremental as a phenomenon. No published work installs a single behavioral trait via SFT, DPO, and GRPO and then compares its effective dimensionality / participation ratio in the residual stream via causal top-k SVD ablation at matched behavioral magnitude. The component ideas (linear trait directions, low intrinsic dimensionality of fine-tuning, DPO "bypass" mechanism, RL entrenchment) are all individually published.
  • One prior result partially CONTRADICTS the direction of the finding: Li et al. 2025 ("Tracing the Representation Geometry...") classify both SFT and DPO as rank-expanding ("entropy-seeking") and only RLVR as rank-compressing — the opposite ordering to "DPO more concentrated than SFT." This must be pre-empted, though their measurement is global last-token geometry (RankMe/αReQ), not a single installe
@bigsnarfdude
bigsnarfdude / CircuitPlasticity.md
Last active June 20, 2026 16:29
Circuit plasticity

Circuit plasticity

Why post-training alignment is always fighting geometry that was set earlier — and what to do about it.

don't police the prompt — pour the defense into the substrate while it's still plastic, and use the mechanism to prove it set.

continuum · 2026-06-18 · program note (Step-0 + α-sweep in)

If behavioral circuits are plastic early and rigid late, then the smart place to install a disposition (honesty, a defense) is during the plastic window — as load-bearing substrate — not bolted on at the end where it's a removable knob. We're building a pipeline to find which documents write which dispositions — but the first controlled test came back negative: the document-built directions don't beat a random vector, so the cheap readout (as built) doesn't capture the target. Only d_auth itself is direction-specific.

If behavioral circuits are plastic early and rigid late, then the smart place to install a disposition (honesty, a defense) is during the plastic window — as load-bearing substrate — not bolted on at the end where it's a removable knob. We're building a pipeline to find which documents write which dispositions, and I'm running an experiment now to see if the idea holds on my model.