Reddit voice calibration is a click-weighted bandit, not a vibe

The failure mode of “match the vibe”

The default move is to tell the model: “here is the subreddit, here is the thread, write a comment that sounds like it belongs.” That instruction is too vague to constrain anything. The model anchors on whatever feels safest given the few thousand tokens it sees, and the safe answer is almost always the same: a calm, pattern-recognizer voice. “I’ve seen this pattern before in X, it usually comes down to Y.” Reasonable on every sub, special on none.

When we measured this on a few months of comment data, the pattern-recognizer voice was being chosen roughly 30% of the time even on subs where its measured click rate was the lowest in the pool. The model was over-picking the most generic option, and the voices that actually drove clicks (the data-point drop in r/Entrepreneur, the short snarky one-liner in 500k+ subs, the disclosed-lane storyteller in r/startups) were being underused by a factor of two to four. The picker had to come out of the model’s hands.

The taxonomy is fixed, the weights are not

The first thing calibration needs is a closed set to calibrate over. S4L runs seven voices for comment replies. The names are stable, the descriptions live in one file, and every new comment gets assigned exactly one of them before the model writes a word. What changes per subreddit and per week is the probability of each one being assigned, not the voices themselves.

Seven is small enough that each voice can be measured (n above the credibility threshold within a 30-day window in any sub with real volume) and large enough to cover the registers Reddit actually rewards. The seven are: critic, storyteller, pattern_recognizer, curious_probe, contrarian, data_point_drop, and snarky_oneliner. One of those, curious_probe, is policy-banned on Reddit entirely because one-question replies trigger spam filters in narrow subs. The other six compete for share of the distribution per sub.

Five numeric knobs, with the values from the repo

Calibration is five constants and one formula. Each value is the current setting in engagement_styles.py; they are not theoretical. You can clone the repo and grep for each name.

What one picking round actually looks like

The picker is one function call: pick_style_for_post("reddit"). It loads the 30-day stats, computes the composite score per voice, applies the shrinkage, ranks, sorts the top five into the use pool, draws weighted-random inside that pool, and either returns the chosen voice or (with 5% probability) returns mode=invent. The pipeline below is the same code path every comment reply runs through, no overrides per sub.

The output of one such call against a recent Reddit pull (an actual run from the repo, redacted to the public voice names):

Note the two voices at the floor: storyteller with n=7 and snarky_oneliner with n=6. The snarky one’s raw score is the highest in the column at 33.1, but the credibility shrinkage knocks it to 9.93, and after the floor and cap pass it lands at 5% instead of dominating the draw. That single mechanism is the difference between “every comment sounds the same because one viral hit warped the distribution” and an honest exploration loop.

Calibration sits inside the subreddit guardrails, not on top

A few rules run before the picker ever weights anything, and they’re per-platform, not per-voice. The PLATFORM_POLICY block lists voices that are flat-banned on a platform regardless of how well they score. On Reddit, the curious-probe voice is never picked even if it has the highest measured click rate; one-question comments draw a different kind of attention than we want. Inside each voice, the metadata carries best_in hints: the snarky one-liner is only enabled in subs above 500k members, and the storyteller is fenced by a separate Grounding Rule that requires either a disclosed-hypothetical opener or grounded specifics from a config file, so it can’t fabricate first-person claims in earnest subs.

What this means in practice: the calibration loop is honest about its scope. It optimizes share of voice given the rules. It does not optimize the rules. The rules are static, deliberate, and written by hand because the cost of a wrong voice in r/Meditation is much higher than the cost of suboptimal weighting in r/SaaS.

What this lets you ship that vibes-based calibration can’t

Three things, in order of how much they matter:

1. An audit trail. Every comment carries the voice it was assigned, the score the picker had when it drew, and the full distribution snapshot. If a comment underperforms you can ask the dashboard which voice it ran and whether that voice was at floor weight or winning. You can answer “why did the bot pick this register here” with a number, not a guess.
2. A self-correcting loop. When a new sub-culture emerges (the AI agent boom flipped r/programming’s reward function in early 2026), the 30-day window catches it within weeks. Whatever voice starts accumulating clicks moves up the distribution automatically. No prompt edits, no taxonomy revisions, no human-in-the-loop re-tuning.
3. A budget for the unknown. The 5% invent rate is the closest thing the system has to a research line item. One pick in twenty is guaranteed not to look like anything currently in the taxonomy. That’s how the next winning voice gets discovered. Without that guarantee, the loop just exploits the current winners forever.

Read the code or fork it

The whole calibration layer lives in one file. Open the picker at scripts/engagement_styles.py; the constants are at the top, the picker function is around line 784, and the composite-score helper is right above it. The repo is github.com/m13v/social-autoposter. You can self-host the whole stack, plug in your own LLM credits, and run the loop against any subreddit you have an account in. The numeric defaults are reasonable; the interesting tuning happens at the floor and the recency window, both single constants you can change in one line.

Frequently asked