# AI Insights for Humans A working notebook of practical AI interpretability, prompting, reliability, and tooling notes for people who want evidence instead of hype. Purpose: Practical AI insight notebook for human operators. Entries: 17 Tags: evals, interpretability, prompting, reliability, tooling, verification Public surfaces: - HTML notebook: https://ai-insights-for-humans.platphormnews.com/ - RSS: https://ai-insights-for-humans.platphormnews.com/rss.xml - API docs: https://ai-insights-for-humans.platphormnews.com/api/docs - OpenAPI: https://ai-insights-for-humans.platphormnews.com/openapi.yaml - MCP: https://ai-insights-for-humans.platphormnews.com/api/mcp Protected actions require PLATPHORM_API_KEY. ## Route Standard Implemented required routes: 20/20 - GET /: implemented; Public AI insights notebook and reading paths. - GET /api/health: implemented; Platform health payload for the publication. - GET /api/v1/health: implemented; Versioned platform health payload. - GET /api/docs: implemented; Machine-readable API and route documentation. - GET /api/v1/entries: implemented; Read-only JSON index of notebook entries. - GET /api/v1/entries/{id}: implemented; Read-only JSON detail for one notebook entry. - POST /api/v1/reports: implemented; Protected generation of a real notebook/platform summary report. - GET /api/mcp: implemented; MCP metadata and JSON-RPC usage information. - POST /api/mcp: implemented; JSON-RPC 2.0 MCP endpoint for real notebook tools, resources, and prompts. - GET /openapi.yaml: implemented; OpenAPI 3.1 contract for public and protected routes. - GET /llms.txt: implemented; Concise LLM-readable site summary. - GET /llms-full.txt: implemented; Complete LLM-readable notebook and platform summary. - GET /llms-index.json: implemented; Structured LLM index generated from real entries. - GET /robots.txt: implemented; Crawler policy and sitemap pointer. - GET /sitemap.xml: implemented; Canonical URL sitemap for the notebook. - GET /sitemap-index.xml: implemented; Sitemap index for platform crawlers. - GET /rss.xml: implemented; RSS feed generated from notebook entries. - GET /feed.xml: implemented; RSS-compatible feed alias. - GET /atom.xml: implemented; Atom feed generated from notebook entries. - GET /manifest.webmanifest: implemented; Web app manifest for install and preview surfaces. - GET /.well-known/mcp.json: implemented; MCP capability discovery manifest. - GET /.well-known/agents.json: implemented; Agent-facing route and policy discovery manifest. - GET /.well-known/security.txt: implemented; Security contact and policy file. - GET /.well-known/trust.json: implemented; Trust, auth, public/protected, and exposure policy. ## Trust Policy Web dashboard, public-safe discovery, browser-based operations, trusted-domain discovery, standard route compliance, Vercel metadata capture, trace inspection, and agentic workflow discovery are intentionally supported for public read-only debugging and operator workflows. Mutating, administrative, ingestion, replay, fork, remediation, deployment, sync, test-triggering, reporting, and write actions require PLATPHORM_API_KEY. ## Entries # Ask for counter-evidence before confidence Kind: Method Tag: reliability Published: 2026-06-18 The useful move is not asking the model to be uncertain. The useful move is forcing it to search for the best case against itself while the answer is still provisional. A simple pattern: draft the answer, list disconfirming evidence, name what would change the answer, then assign confidence. The confidence number becomes attached to evidence quality instead of verbal smoothness. This is especially helpful for research summaries, legal-ish interpretation, data diagnosis, and anything where one missing constraint can flip the conclusion. Note: Confidence after counter-evidence is more useful than confidence after a sales pitch. # Turn every important claim into a receipt Kind: Method Tag: verification Published: 2026-05-27 Models are good at moving from evidence to prose. They are also good at producing prose that looks like it came from evidence. The receipt requirement separates those two behaviors. The receipt can be a citation, a row count, a command output line, a test name, or a declared assumption. The format matters less than the discipline: every claim has to point somewhere. When the model cannot produce a receipt, that is not failure. That is the system doing its job and showing you where judgment is still needed. # Keep the system prompt short enough to audit Kind: Tip Tag: prompting Published: 2026-05-03 System prompts work best as durable operating constraints, not as a dumping ground for every possible preference. When the prompt grows without structure, the model starts resolving conflicts in ways you cannot predict. Split the prompt into policy, role, output contract, and refusal boundary. Then write a small regression set that exercises each section. You will catch more problems with five targeted tests than with another page of instructions. Note: If you cannot diff it cleanly, you cannot debug it cleanly. # Use refusal boundaries as test fixtures Kind: Method Tag: evals Published: 2026-04-12 Most prompt tests focus on whether the model can complete the intended workflow. That misses the other half of the product: whether it handles edge requests without over-refusing, leaking private context, or inventing authority it does not have. Build a small fixture set with three buckets: allowed, disallowed, and allowed-with-constraints. A good model response should land in the right bucket and explain the usable next step. This turns safety from a vibe into a regression target. When a prompt edit changes the refusal boundary, you see it immediately. # Read the logprobs, not the answer Kind: Method Tag: interpretability Published: 2025-11-02 Every token a model emits comes with a probability distribution over the whole vocabulary. The decoded text only shows you the winner. The logprobs show you the race. When you pull them back, scan for the spots where the top token barely beat the runner-up. Those are the seams. Names, dates, citations, and the first token of a refusal are where you most often find a coin-flip dressed up as a confident sentence. A practical loop: request the top 5 logprobs per token, render them as a heatmap over the output, and read the cold spots first. That is usually where the hallucination lives. Note: Confidence ≠ correctness. But low confidence is a great place to look for hallucinations. # Make it think before it answers Kind: Tip Tag: prompting Published: 2025-10-28 Autoregressive models can only condition on what they have already written. If the answer comes first, the explanation is generated to fit a token that is already locked in. It is rationalization, not reasoning. Flip the order and the reasoning tokens become real scratch space the final answer can lean on. This is the entire mechanism behind chain-of-thought, and it is why 'answer, then explain' quietly underperforms. # BertViz for watching attention move Kind: Tool Tag: tooling Published: 2025-10-19 BertViz draws the attention pattern as lines connecting tokens, split by head and layer. It runs in a notebook in a couple of lines and works on most Hugging Face transformer models. The value is not the pretty picture, it is the habit of looking. Once you have seen a head that exclusively tracks matching brackets, you stop thinking of the model as a black box and start thinking of it as a stack of small, legible mechanisms. Note: Most heads are boring. The interesting 5% are worth the dig. # Tell it what NOT to do, sparingly Kind: Tip Tag: prompting Published: 2025-10-11 Putting a word in the prompt raises its activation, even when the word is wrapped in 'do not'. The model does not have a clean negation operator the way code does; it has attention, and attention does not know the difference between mention and command. Rewrite prohibitions as positive descriptions of the target. Instead of 'do not be formal', say 'write like you are texting a friend'. Save the hard negatives for the few rails you cannot express any other way. # Probe for a concept with a linear classifier Kind: Method Tag: interpretability Published: 2025-09-30 The setup is small: collect hidden states from a chosen layer for a labeled dataset, then fit logistic regression on top. High accuracy means the concept is linearly available at that layer. Sweep the probe across layers and you can watch where a concept first becomes readable. Abstract properties tend to sharpen in the middle layers, which is a clue about where the model is doing the relevant work. Note: Cheap, fast, and weirdly revealing. # Temperature is a creativity dial, not a quality dial Kind: Tip Tag: prompting Published: 2025-09-22 Temperature reshapes the probability distribution before sampling. Low temperature sharpens it toward the most likely token; high temperature flattens it so unlikely tokens get a real chance. So the dial controls variance, not intelligence. If a task has a correct answer, variance is your enemy and you want it near zero. If you want range and surprise, turn it up and sample several times. # Sparse autoencoders to untangle neurons Kind: Method Tag: interpretability Published: 2025-09-14 The trick is over-completeness plus sparsity. You map activations into a much wider space but force only a few of those dimensions to be active at once. The pressure pushes tangled concepts apart into separate, more interpretable features. Once you have the features you can do surgery: amplify one and watch the model fixate on a bridge, suppress another and watch a behavior fade. It is the closest thing we have to named knobs inside the network. Note: This is roughly how the 'Golden Gate Claude' demo worked. # Keep a tokenizer open in a tab Kind: Tool Tag: tooling Published: 2025-09-03 Leading spaces, casing, and digit grouping all change how text is split, and the model only ever sees the tokens, never your characters. A trailing space can silently sabotage a few-shot format. When something is off and you cannot explain it, paste the exact string into a tokenizer view before you theorize. The answer is in there more often than you would expect. # Sample many, keep the majority Kind: Method Tag: reliability Published: 2025-08-25 Different samples take different reasoning paths but tend to converge on the same correct answer, while the wrong answers scatter. Voting over the final answers turns that asymmetry into accuracy. It costs you N times the compute, so reserve it for the questions that matter. A useful middle ground is to escalate to self-consistency only when the first answer looks low-confidence. # Mind the middle of long contexts Kind: Tip Tag: prompting Published: 2025-08-12 Retrieval accuracy as a function of position tends to be U-shaped: strong at the start, strong at the end, sagging in the middle. A fact you need can be technically present and still effectively invisible. Design around it. Lead with the instruction, restate the critical constraint at the very end, and keep the soft middle for material you can afford to lose. Note: Sometimes called 'lost in the middle'. # Activation patching to find the cause Kind: Method Tag: interpretability Published: 2025-07-30 Probes tell you what is represented. Patching tells you what matters. By swapping one activation and watching the effect, you move from 'this information is present' to 'this component causes the behavior'. Sweep the patch across layers and positions to localize the circuit. The spots where patching flips the answer are the load-bearing ones; everything else is along for the ride. Note: The closest thing in this field to a controlled experiment. # Your examples teach format louder than content Kind: Tip Tag: prompting Published: 2025-07-18 Few-shot learning is pattern continuation. The model is extremely sensitive to surface form, sometimes more than to the actual reasoning you intended to demonstrate. Make every example identical in structure, pick label words that are single clean tokens, and keep lengths similar. The more rigid the template, the more reliably the model fills in the next blank. # The logit lens: decode the middle layers Kind: Method Tag: interpretability Published: 2025-07-05 The output projection is just a linear map, so nothing stops you from applying it to an earlier layer. The result is a rough readout of what the model would say if it had to stop thinking right now. Often the correct answer appears in the middle layers and the later layers spend their budget refining phrasing and suppressing alternatives. Seeing that handoff demystifies a lot of model behavior.