<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>BanditBuzz research</title>
    <link>https://bandit.buzz/blog/</link>
    <description>Practical research on customer decisions that learn from results.</description>
    <language>en-us</language>
    <item>
      <title>Building a learning loop with two API calls</title>
      <link>https://bandit.buzz/blog/building-a-learning-loop-with-two-api-calls/</link>
      <guid>https://bandit.buzz/blog/building-a-learning-loop-with-two-api-calls/</guid>
      <pubDate>Fri, 10 Jul 2026 12:00:00 GMT</pubDate>
      <description>Wire BanditBuzz with POST /decide and POST /events. Cover idempotency, a local fallback, reward maturity, mismatched identifiers, and what to add after the base loop works.</description>
    </item>
    <item>
      <title>The customer decisioning market in 2026</title>
      <link>https://bandit.buzz/blog/customer-decisioning-landscape-2026/</link>
      <guid>https://bandit.buzz/blog/customer-decisioning-landscape-2026/</guid>
      <pubDate>Thu, 02 Jul 2026 12:00:00 GMT</pubDate>
      <description>Customer decisioning products split by what they already own. Compare setup, context, reward truth, identity, execution, control, and proof by starting point, not by a winner grid.</description>
    </item>
    <item>
      <title>What happens when yesterday stops predicting tomorrow</title>
      <link>https://bandit.buzz/blog/bandit-policies-under-drift-and-seasonality/</link>
      <guid>https://bandit.buzz/blog/bandit-policies-under-drift-and-seasonality/</guid>
      <pubDate>Thu, 18 Jun 2026 12:00:00 GMT</pubDate>
      <description>Full-history bandit posteriors can adapt too slowly when reward rates shift. How seasonality, wear-out, sliding windows, and discounting change the history rule, and what BanditBuzz does today.</description>
    </item>
    <item>
      <title>Language models need a policy for exploration</title>
      <link>https://bandit.buzz/blog/language-models-need-a-policy-for-exploration/</link>
      <guid>https://bandit.buzz/blog/language-models-need-a-policy-for-exploration/</guid>
      <pubDate>Thu, 04 Jun 2026 12:00:00 GMT</pubDate>
      <description>Language models can help name actions and draft setup, but current bandit tests do not support relying on them alone to balance exploration and exploitation.</description>
    </item>
    <item>
      <title>How Faraday adds context to BanditBuzz</title>
      <link>https://bandit.buzz/blog/how-faraday-adds-context-to-banditbuzz/</link>
      <guid>https://bandit.buzz/blog/how-faraday-adds-context-to-banditbuzz/</guid>
      <pubDate>Thu, 21 May 2026 12:00:00 GMT</pubDate>
      <description>Faraday resolves a person and returns a small decision-time vector. BanditBuzz snapshots it, encodes a few fixed features, and lets replay decide whether that context helps.</description>
    </item>
    <item>
      <title>Checking a contextual policy before it goes live</title>
      <link>https://bandit.buzz/blog/checking-contextual-policy-with-doubly-robust-replay/</link>
      <guid>https://bandit.buzz/blog/checking-contextual-policy-with-doubly-robust-replay/</guid>
      <pubDate>Thu, 07 May 2026 12:00:00 GMT</pubDate>
      <description>How person-level cross-fitting and a doubly robust estimator turn logged randomized traffic into a guarded preview of a per-person policy, including the evidence gates, overlap checks, and limits that keep the preview honest.</description>
    </item>
    <item>
      <title>The decision log is part of the model</title>
      <link>https://bandit.buzz/blog/decision-logs-propensities-and-replay/</link>
      <guid>https://bandit.buzz/blog/decision-logs-propensities-and-replay/</guid>
      <pubDate>Thu, 23 Apr 2026 12:00:00 GMT</pubDate>
      <description>What to store at choice time so a future policy can be checked fairly, including offered sets, propensities, context snapshots, and why a reward table alone is not enough.</description>
    </item>
    <item>
      <title>Scheduling an action without pretending it happened</title>
      <link>https://bandit.buzz/blog/scheduling-actions-with-delayed-feedback/</link>
      <guid>https://bandit.buzz/blog/scheduling-actions-with-delayed-feedback/</guid>
      <pubDate>Thu, 09 Apr 2026 12:00:00 GMT</pubDate>
      <description>Planning, release, acceptance, and reward each need their own time. Start the reward clock only after a direct destination accepts the action.</description>
    </item>
    <item>
      <title>The timing estimand comes before the timing model</title>
      <link>https://bandit.buzz/blog/timing-estimand-before-timing-model/</link>
      <guid>https://bandit.buzz/blog/timing-estimand-before-timing-model/</guid>
      <pubDate>Thu, 26 Mar 2026 12:00:00 GMT</pubDate>
      <description>Send-time optimization can mean whole-policy lift, timing lift conditional on acting, or repeated act-or-wait pacing. These are different questions. BanditBuzz answers the first two with nested controls and does not yet run the third.</description>
    </item>
    <item>
      <title>A live holdout and a range you may inspect each day</title>
      <link>https://bandit.buzz/blog/live-holdouts-and-confidence-sequences/</link>
      <guid>https://bandit.buzz/blog/live-holdouts-and-confidence-sequences/</guid>
      <pubDate>Thu, 12 Mar 2026 12:00:00 GMT</pubDate>
      <description>How BanditBuzz measures whole-policy lift with a stable person holdout, matured decision units, absolute and relative effects, and a 95% confidence sequence built for repeated dashboard viewing.</description>
    </item>
    <item>
      <title>Delayed rewards and identity-resolved attribution</title>
      <link>https://bandit.buzz/blog/delayed-rewards-identity-resolved-attribution/</link>
      <guid>https://bandit.buzz/blog/delayed-rewards-identity-resolved-attribution/</guid>
      <pubDate>Thu, 26 Feb 2026 12:00:00 GMT</pubDate>
      <description>How BanditBuzz joins a choice made on one identifier to a result that arrives days later on another, using pending windows, nightly identity stamps, and latest-eligible-decision attribution.</description>
    </item>
    <item>
      <title>Thompson sampling as a useful first policy</title>
      <link>https://bandit.buzz/blog/thompson-sampling-useful-first-policy/</link>
      <guid>https://bandit.buzz/blog/thompson-sampling-useful-first-policy/</guid>
      <pubDate>Thu, 12 Feb 2026 12:00:00 GMT</pubDate>
      <description>Why BanditBuzz’s free tier uses Beta-Bernoulli Thompson sampling: no training set, no exploration-rate knob, matured counts, Monte Carlo propensities, and the limits that come with the choice.</description>
    </item>
    <item>
      <title>Why “do nothing” belongs in the action set</title>
      <link>https://bandit.buzz/blog/why-do-nothing-belongs-in-the-action-set/</link>
      <guid>https://bandit.buzz/blog/why-do-nothing-belongs-in-the-action-set/</guid>
      <pubDate>Thu, 29 Jan 2026 12:00:00 GMT</pubDate>
      <description>Without a no-action choice, a learner can rank messages while never learning whether contact helps. How BanditBuzz treats nothing, holdout, cooldown, frequency, and timing as different jobs.</description>
    </item>
    <item>
      <title>What “next best action” should mean</title>
      <link>https://bandit.buzz/blog/what-next-best-action-should-mean/</link>
      <guid>https://bandit.buzz/blog/what-next-best-action-should-mean/</guid>
      <pubDate>Thu, 15 Jan 2026 12:00:00 GMT</pubDate>
      <description>A next-best-action system should own one bounded choice among approved actions, including no action, tied to one business result. Strategy, content, consent, and execution stay with you.</description>
    </item>
  </channel>
</rss>
