<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Joshua Durey (Josh Durey) · Applied AI Enablement &amp; Agentic Workflows</title>
  <subtitle>Applied AI enablement. I audit workflows for AI readiness, build agentic systems, and run the LLM quality control that gets teams to adoption they can trust.</subtitle>
  <link href="https://jdurey.github.io/feed.xml" rel="self" type="application/atom+xml"/>
  <link href="https://jdurey.github.io/" rel="alternate" type="text/html"/>
  <link href="https://pubsubhubbub.appspot.com/" rel="hub"/>
  <link href="https://pubsubhubbub.superfeedr.com/" rel="hub"/>
  <id>https://jdurey.github.io/</id>
  <updated>2026-11-15T00:00:00Z</updated>
  <author>
    <name>Joshua Durey</name>
    <uri>https://jdurey.github.io/</uri>
    <email>josh.durey@gmail.com</email>
  </author>
  <entry>
    <title>Hiring an Applied AI Enablement Lead: A 30-60-90 Day Playbook for Team Adoption</title>
    <link href="https://jdurey.github.io/guides/applied-ai-enablement-lead/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/guides/applied-ai-enablement-lead/</id>
    <updated>2026-11-15T00:00:00Z</updated>
    <category term="Playbook"/>
    <summary>What an Applied AI Enablement Lead actually ships in the first 90 days: workflow audits, self-checking agent pipelines, cross-family quality gates, and staff playbooks that turn shelfware seats into daily output.</summary>
  </entry>
  <entry>
    <title>Enterprise AI Workflow Audit Checklist: Ranking Tasks by Payoff, Risk &amp; Checkpoints</title>
    <link href="https://jdurey.github.io/guides/ai-workflow-audit-checklist/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/guides/ai-workflow-audit-checklist/</id>
    <updated>2026-11-15T00:00:00Z</updated>
    <category term="Playbook"/>
    <summary>A practical four-step checklist for auditing team operations before writing automation code: mapping real inputs, pricing silent errors, placing human checkpoints, and killing low-payoff pilots early.</summary>
  </entry>
  <entry>
    <title>Self-Reviewing Agentic Workflows: Designing Pipelines Non-Technical Teams Trust</title>
    <link href="https://jdurey.github.io/guides/self-reviewing-agentic-workflows/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/guides/self-reviewing-agentic-workflows/</id>
    <updated>2026-11-15T00:00:00Z</updated>
    <category term="Playbook"/>
    <summary>How to replace fragile single-shot prompts with four-stage self-checking workflows: deterministic Python pre-gates, narrow drafting nodes, cross-family critics, and SHA-verified audit receipts.</summary>
  </entry>
  <entry>
    <title>LLM-as-a-Judge Calibration: Stopping Self-Bias, Verdict Flips &amp; Silent Truncations</title>
    <link href="https://jdurey.github.io/guides/llm-judge-calibration-and-qc/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/guides/llm-judge-calibration-and-qc/</id>
    <updated>2026-11-15T00:00:00Z</updated>
    <category term="Playbook"/>
    <summary>How to calibrate LLM-as-a-Judge panels against human expert baselines: binary decomposed rubrics, cross-vendor panels, golden-set agreement checks, and catching silent HTTP 200 truncations.</summary>
  </entry>
  <entry>
    <title>SOP-to-SCORM AI Pipeline: Compiling Policy Docs into Verified LMS &amp; QTI Modules</title>
    <link href="https://jdurey.github.io/guides/sop-to-scorm-ai-pipeline/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/guides/sop-to-scorm-ai-pipeline/</id>
    <updated>2026-11-15T00:00:00Z</updated>
    <category term="Playbook"/>
    <summary>How corporate L&amp;D and compliance teams turn static SOPs and runbooks into ADL SCORM 1.2 packages, QTI 1.2 item banks, 300-DPI guides, and narrated 1080p lessons with 0% policy drift.</summary>
  </entry>
  <entry>
    <title>6-Rung LLM Cost &amp; Latency Routing: Cutting Enterprise Token Spend Without Losing Quality</title>
    <link href="https://jdurey.github.io/guides/llm-cost-and-latency-routing/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/guides/llm-cost-and-latency-routing/</id>
    <updated>2026-11-15T00:00:00Z</updated>
    <category term="Playbook"/>
    <summary>Why a tiny fraction of agent calls burn 80% of your API bill, and how a 6-rung policy router shifts routine checks to zero-token Python hooks and fast mid-tier models.</summary>
  </entry>
  <entry>
    <title>AI Curriculum &amp; QTI Assessment Quality Control: Blind-Solver Checks &amp; Zero Answer Leaks</title>
    <link href="https://jdurey.github.io/guides/ai-curriculum-and-qti-assessment-qc/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/guides/ai-curriculum-and-qti-assessment-qc/</id>
    <updated>2026-11-15T00:00:00Z</updated>
    <category term="Playbook"/>
    <summary>Engineering-grade quality control for EdTech and enterprise assessment pipelines: catching ambiguous distractors, standards drift, hint answer leaks, and broken math rendering before students see them.</summary>
  </entry>
  <entry>
    <title>Two-Week AI Workflow &amp; QC Sprints: Moving Stalled Pilots into Daily Team Use</title>
    <link href="https://jdurey.github.io/guides/fixed-scope-ai-workflow-sprint/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/guides/fixed-scope-ai-workflow-sprint/</id>
    <updated>2026-11-15T00:00:00Z</updated>
    <category term="Playbook"/>
    <summary>How founders and operations leaders use a fixed-scope two-week sprint to audit one high-friction bottleneck, deploy a self-checking workflow with human checkpoints, and keep the runnable QC harness.</summary>
  </entry>
  <entry>
    <title>Model evaluation in machine learning</title>
    <link href="https://jdurey.github.io/work/model-evaluation-in-machine-learning/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/model-evaluation-in-machine-learning/</id>
    <updated>2026-09-25T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Blind expert-parity: can a model adjudicate like a credentialed examiner, and can you prove it?.</summary>
  </entry>
  <entry>
    <title>Llm judge metrics</title>
    <link href="https://jdurey.github.io/work/llm-judge-metrics/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/llm-judge-metrics/</id>
    <updated>2026-09-24T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Can you trust the model that grades your content? Measuring when an AI judge waves through broken work.</summary>
  </entry>
  <entry>
    <title>Llm as a judge framework</title>
    <link href="https://jdurey.github.io/work/llm-as-a-judge-framework/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/llm-as-a-judge-framework/</id>
    <updated>2026-09-21T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Can you trust the model that grades your content? Measuring when an AI judge waves through broken work.</summary>
  </entry>
  <entry>
    <title>Llm as a judge paper</title>
    <link href="https://jdurey.github.io/work/llm-as-a-judge-paper/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/llm-as-a-judge-paper/</id>
    <updated>2026-09-14T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Can you trust the model that grades your content? Measuring when an AI judge waves through broken work.</summary>
  </entry>
  <entry>
    <title>Llm eval harness</title>
    <link href="https://jdurey.github.io/work/llm-eval-harness/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/llm-eval-harness/</id>
    <updated>2026-09-13T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to How to audit an LLM judge before you trust its verdicts.</summary>
  </entry>
  <entry>
    <title>Red teaming llm applications</title>
    <link href="https://jdurey.github.io/work/red-teaming-llm-applications/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/red-teaming-llm-applications/</id>
    <updated>2026-09-02T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Red-teaming my own publish gate.</summary>
  </entry>
  <entry>
    <title>Llm judge</title>
    <link href="https://jdurey.github.io/work/llm-judge/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/llm-judge/</id>
    <updated>2026-08-31T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Can you trust the model that grades your content? Measuring when an AI judge waves through broken work.</summary>
  </entry>
  <entry>
    <title>Llm as a judge</title>
    <link href="https://jdurey.github.io/work/llm-as-a-judge/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/llm-as-a-judge/</id>
    <updated>2026-08-30T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Can you trust the model that grades your content? Measuring when an AI judge waves through broken work.</summary>
  </entry>
  <entry>
    <title>Llm judge model</title>
    <link href="https://jdurey.github.io/work/llm-judge-model/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/llm-judge-model/</id>
    <updated>2026-08-26T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Can you trust the model that grades your content? Measuring when an AI judge waves through broken work.</summary>
  </entry>
  <entry>
    <title>What is model evaluation in machine learning</title>
    <link href="https://jdurey.github.io/work/what-is-model-evaluation-in-machine-learning/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/what-is-model-evaluation-in-machine-learning/</id>
    <updated>2026-08-24T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Blind expert-parity: can a model adjudicate like a credentialed examiner, and can you prove it?.</summary>
  </entry>
  <entry>
    <title>Why use multiple AI models instead of sampling one model many times</title>
    <link href="https://jdurey.github.io/work/multi-model-panels-vs-resampling/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/multi-model-panels-vs-resampling/</id>
    <updated>2026-08-21T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Author with one model, attack with another.</summary>
  </entry>
  <entry>
    <title>How to run AI content pipelines unattended overnight safely</title>
    <link href="https://jdurey.github.io/work/unattended-ai-pipeline-failure-budget/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/unattended-ai-pipeline-failure-budget/</id>
    <updated>2026-08-19T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Three failures your LLM pipeline never logs: gates for truncation, reasoning tax, and latency tails.</summary>
  </entry>
  <entry>
    <title>How to make AI QC verdicts auditable and replayable</title>
    <link href="https://jdurey.github.io/work/replayable-ai-qc-verdicts/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/replayable-ai-qc-verdicts/</id>
    <updated>2026-08-17T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Same answer, different grade: measuring when an AI grader can&apos;t hold a verdict.</summary>
  </entry>
  <entry>
    <title>How to audit an AI pipeline when you cannot read its data</title>
    <link href="https://jdurey.github.io/work/audit-ai-pipeline-without-reading-data/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/audit-ai-pipeline-without-reading-data/</id>
    <updated>2026-08-14T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Three failures your LLM pipeline never logs: gates for truncation, reasoning tax, and latency tails.</summary>
  </entry>
  <entry>
    <title>How to choose an LLM provider when many serve the same model</title>
    <link href="https://jdurey.github.io/work/choose-llm-provider-by-latency-not-price/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/choose-llm-provider-by-latency-not-price/</id>
    <updated>2026-08-12T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Three failures your LLM pipeline never logs: gates for truncation, reasoning tax, and latency tails.</summary>
  </entry>
  <entry>
    <title>Why a few LLM calls carry most of your API bill</title>
    <link href="https://jdurey.github.io/work/llm-api-costs-concentrate-in-few-calls/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/llm-api-costs-concentrate-in-few-calls/</id>
    <updated>2026-08-10T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Three failures your LLM pipeline never logs: gates for truncation, reasoning tax, and latency tails.</summary>
  </entry>
  <entry>
    <title>How much do reasoning tokens add to LLM API costs</title>
    <link href="https://jdurey.github.io/work/how-much-do-reasoning-tokens-cost/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/how-much-do-reasoning-tokens-cost/</id>
    <updated>2026-08-06T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Three failures your LLM pipeline never logs: gates for truncation, reasoning tax, and latency tails.</summary>
  </entry>
  <entry>
    <title>Why does my LLM output get cut off and how do I detect it</title>
    <link href="https://jdurey.github.io/work/why-llm-output-gets-cut-off/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/why-llm-output-gets-cut-off/</id>
    <updated>2026-08-03T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Three failures your LLM pipeline never logs: gates for truncation, reasoning tax, and latency tails.</summary>
  </entry>
  <entry>
    <title>What is llm judge</title>
    <link href="https://jdurey.github.io/work/what-is-llm-judge/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/what-is-llm-judge/</id>
    <updated>2026-07-31T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Can you trust the model that grades your content? Measuring when an AI judge waves through broken work.</summary>
  </entry>
  <entry>
    <title>Three failures your LLM pipeline never logs: gates for truncation, reasoning tax, and latency tails</title>
    <link href="https://jdurey.github.io/work/telemetry-gates/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/telemetry-gates/</id>
    <updated>2026-07-31T00:00:00Z</updated>
    <category term="eval"/>
    <summary>I aggregated a month of my own API telemetry, 88,000 calls, and found three failure classes that raise no exception anywhere. One model silently truncated 5.7% of its responses. Eight models spent 83 to 95 percent of their completion tokens on reasoning nobody reads. Providers serving comparable models ranged from 1.1s to 20s median latency, with one tail hitting 89 seconds. So I built three deterministic gates that run on telemetry alone, and tested them against a synthetic fleet with defects planted by construction. The gate is correct when it finds every planted defect and nothing else.</summary>
  </entry>
  <entry>
    <title>How to evaluate llm output</title>
    <link href="https://jdurey.github.io/work/how-to-evaluate-llm-output/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/how-to-evaluate-llm-output/</id>
    <updated>2026-07-31T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Can you trust the model that grades your content? Measuring when an AI judge waves through broken work.</summary>
  </entry>
  <entry>
    <title>The agent-boundary harness: measuring whether an AI agent respects a data fence, and whether the fence holds</title>
    <link href="https://jdurey.github.io/work/agent-boundary/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/agent-boundary/</id>
    <updated>2026-07-31T00:00:00Z</updated>
    <category term="eval"/>
    <summary>An agent with file access can leak in two ways. The guard code fails, or the model decides to cross. I built a two-layer instrument that measures both, scored by whether a sealed canary token ever reads out. A naive path guard passed 75% and leaked twice through known EscapeRoute-class bypasses. The hardened guard passed clean. Then I tempted real models with tasks where crossing the boundary is the easy path, and counted the crossings. Everything runs on a fictional workspace, so the whole machine is public.</summary>
  </entry>
  <entry>
    <title>What is llm as a judge</title>
    <link href="https://jdurey.github.io/work/what-is-llm-as-a-judge/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/what-is-llm-as-a-judge/</id>
    <updated>2026-07-29T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Can you trust the model that grades your content? Measuring when an AI judge waves through broken work.</summary>
  </entry>
  <entry>
    <title>How to red-team AI-built tools and content before they reach a classroom</title>
    <link href="https://jdurey.github.io/work/red-team-ai-built-tools-before-classroom-use/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/red-team-ai-built-tools-before-classroom-use/</id>
    <updated>2026-07-29T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Can you trust the model that grades your content? Measuring when an AI judge waves through broken work.</summary>
  </entry>
  <entry>
    <title>Why an AI grader checking its own output can&apos;t be trusted, and what to do</title>
    <link href="https://jdurey.github.io/work/why-an-ai-grader-checking-itself-fails/" rel="alternate" type="text/html"/>
    <id>https://jdurey.github.io/work/why-an-ai-grader-checking-itself-fails/</id>
    <updated>2026-07-27T00:00:00Z</updated>
    <category term="guide"/>
    <summary>A practical answer grounded in a runnable, published harness rather than opinion. Links to Can you trust the model that grades your content? Measuring when an AI judge waves through broken work.</summary>
  </entry>
</feed>
