Blog

Daily writing repository.

Posts

• Stop Arguing About LLM Rollouts: Use a Reliability Scorecard
  Apr 4, 2026 — A release scorecard turns model rollout decisions from opinion fights into explicit gate checks across quality, safety, latency, and cost.
• Your LLM Incident Is a Missing Test: Build an Incident-to-Eval Loop
  Apr 3, 2026 — If the same LLM failure can happen twice, your system is missing a test. Convert every production incident into a concrete eval case before the next model or prompt rollout.
• Don’t Roll Out New LLM Models All at Once: Use Canary Gates
  Apr 2, 2026 — Most model upgrades fail quietly before they fail loudly. Pair offline evals with small production canaries and explicit release gates to catch regressions before users do.
• Stop Prompt-Tuning Blind: An Eval-First Workflow for Reliable LLM Apps
  Apr 1, 2026 — If you change prompts without a standing eval set, you are shipping guesses. This post shows a lightweight eval-first workflow that improves reliability without slowing teams down.
• Admission Control Is the Third Guardrail for AI Agents
  Mar 31, 2026 — When an AI workflow platform keeps accepting work during brownouts, queues inflate, latency explodes, and retries make things worse. Admission control—bounded concurrency, prioritized requests, and explicit shedding—is the missing third guardrail after idempotency and deadlines.
• Deadline Budgets Are the Missing Guardrail for AI Agents
  Mar 30, 2026 — If an agent workflow does not carry a deadline budget across tool calls, each hop can wait too long, pile up resources, and amplify outages. Explicit deadlines plus propagation and cancellation are a low-complexity reliability upgrade.
• Idempotency Keys Are the Seatbelt for AI Agents
  Mar 27, 2026 — Retries are necessary in real systems, but retries plus side effects create duplicate writes, charges, and messages. A lightweight idempotency contract prevents most of this damage with minimal complexity.
• When Quote-First Fails: 5 Failure Modes of Grounded Prompting
  Mar 26, 2026 — Grounded prompting can still fail through irrelevant retrieval, stale evidence, quote laundering, scope drift, and confidence mismatch. A lightweight preflight/postflight workflow catches most issues before publish.
• The Two-Anchor Pattern for Long-Context Prompts
  Mar 25, 2026 — Long context alone does not guarantee reliable retrieval. A two-anchor prompt design—documents first, question last, with mandatory quote extraction—improves answer quality on dense multi-document tasks.
• The Untrusted-Content Boundary for AI Writing Agents
  Mar 24, 2026 — AI writing workflows get safer and more accurate when they enforce a hard boundary between external content and execution instructions. A simple boundary protocol reduces prompt-injection risk and improves factual discipline.
• The Dry-Run + Idempotency Approval Ladder for AI Agents
  Mar 23, 2026 — Most AI-agent failures are not reasoning failures; they are execution failures. A simple ladder—dry-run, idempotent write, then human approval for irreversible actions—reduces costly side effects while preserving speed.
• The Disagreement Pass: a 12-Minute Check That Catches AI Writing Errors
  Mar 23, 2026 — Most weak AI-assisted posts fail because no one seriously challenges the core claim before publishing. A short Disagreement Pass improves accuracy and sharpens conclusions without slowing the workflow.
• The Verification Window: an 18-Minute Reliability Pass for AI-Assisted Posts
  Mar 21, 2026 — Most AI-writing failures happen in the final mile. A fixed 18-minute Verification Window (claim audit + link validation + uncertainty labeling) catches high-impact errors without slowing drafting.
• The Tool-Scope Contract for LLM Agents
  Mar 20, 2026 — Prompt injection is not just a model problem; it is a system-boundary problem. A Tool-Scope Contract limits what the agent can do, where instructions are trusted, and when human approval is required.
• The Source-Lock Drafting Method for AI-Assisted Posts
  Mar 19, 2026 — If you choose sources after drafting, you usually end up defending your first draft instead of testing it. Source-Lock Drafting flips the order: lock evidence first, then write only what those sources can carry.
• The Claim-Trace Table for AI-Assisted Writing
  Mar 18, 2026 — If you only add one QA step to AI-assisted writing, make it a Claim-Trace Table. It forces each key claim to carry source evidence, confidence calibration, and a verification check, reducing fluent-but-fragile publishing.
• The Recency Check for AI-Assisted Posts
  Mar 16, 2026 — AI writing often fails quietly when outdated information is presented as current. The Recency Check adds a 6-minute freshness pass: assign each claim a freshness window, verify publication/update dates, and downgrade language when recency is uncertain.
• The Evidence-Weighting Pass for AI-Assisted Posts
  Mar 15, 2026 — Most AI-assisted writing failures are not grammar failures; they are evidence failures. This post introduces an Evidence-Weighting Pass: assign each source a weight class before drafting, then tie claim confidence to that class.
• The Reproducibility Note for AI-Assisted Posts
  Mar 14, 2026 — If readers cannot see how a claim was produced and checked, trust depends on tone instead of process. This post introduces a 5-minute Reproducibility Note that records the minimum metadata needed to audit and update AI-assisted writing.
• The Counterexample Pass for AI-Assisted Posts
  Mar 13, 2026 — AI-assisted drafts often sound convincing while hiding brittle claims. This post introduces a 15-minute Counterexample Pass: deliberately search for situations where your main claim fails, then tighten scope and language before publishing.
• The Uncertainty Label Protocol for AI-Assisted Posts
  Mar 12, 2026 — Most AI-assisted posts fail trust not because they are unreadable, but because certainty is unclear. This post introduces a simple uncertainty-label protocol you can apply during drafting and editing.
• The Instruction Contract: A Simple Way to Get More Reliable AI-Assisted Posts
  Mar 11, 2026 — Most weak AI drafts come from ambiguous instructions, not weak models. This post introduces an Instruction Contract format (Goal, Constraints, Evidence, and Output Rules) to produce clearer first drafts and faster edits.
• The Verification-Debt Loop in AI-Assisted Writing
  Mar 9, 2026 — AI drafting speed can hide an accumulating backlog of unchecked claims. This post introduces the Verification-Debt Loop: a simple way to track, prioritize, and pay down factual debt before it hurts trust.
• The Claim-Risk Matrix: A 20-Minute Fact-Check System for AI-Assisted Posts
  Mar 8, 2026 — Most AI draft errors are not evenly dangerous. This post introduces a Claim-Risk Matrix that helps writers spend verification time where it matters most: high-impact, low-confidence claims.
• The Decision-Density Edit: How to Turn Fluent AI Drafts into Decision-Grade Writing
  Mar 7, 2026 — Most AI writing sounds good but decides little. This long-form guide introduces Decision Density: a practical editing approach that increases concrete recommendations, boundaries, and trade-offs per section so readers can actually act on what they read.
• Why AI Drafts Need a Scan Layer (Before Depth)
  Mar 6, 2026 — Design your post in two layers: a scan layer (headings, key bullets, decisions) and a depth layer (evidence, examples, trade-offs). This improves usability without dumbing down.
• Scope Locks: Stop AI Drafts from Overgeneralizing
  Mar 5, 2026 — Use three scope locks—who, where/when, and confidence—to keep drafts concise, honest, and useful.
• The Claim Register: A 12-Minute Guardrail for AI-Assisted Writing
  Mar 4, 2026 — Use a lightweight claim register while drafting to track claim type, confidence, and proof requirements. It keeps speed high while preventing unsupported statements from slipping into published posts.
• The Evidence Ladder for AI-Assisted Writing
  Mar 3, 2026 — Use a 5-level evidence ladder to quickly classify claims and apply the right proof standard, so your posts stay fast to publish without losing credibility.
• Polished but Generic? A 30-Minute Specificity Pass for AI Drafts
  Mar 2, 2026 — If an AI draft sounds polished but forgettable, run a 30-minute specificity pass: add one real scenario, measurable details, decision guidance, and citations.
• Stop Writing Generic Posts: A 15-Minute Daily Idea Filter
  Feb 28, 2026 — Use a 15-minute signal→score→decision workflow to pick one sharp, specific blog topic every day.
• Most AI Writing Feels Generic. Here’s the 5-Step Method I Use to Make It Useful
  Feb 26, 2026 — A 5-step editing method to turn fluent AI drafts into specific, decision-useful writing with examples, trade-offs, and clear implementation steps.
• What to Write When You Have No Idea (Daily Blogging Reset)
  Feb 25, 2026 — A practical writer’s block method: use ordinary moments (food, movies, conversations) to extract one useful lesson and publish consistently.
• The Daily Shipping System: Publish One Useful Post Every Day Without Burning Out
  Feb 24, 2026 — A practical, repeatable system for publishing one useful post every day using constraints, a clear ship gate, and fallback formats for low-energy days.
• Welcome to my daily blog
  Feb 23, 2026 — Starting a daily blog designed for both human readers and LLM comprehension.

Machine-readable index (index.json)