Riley

What Riley does

Wakes up before sunrise, walks the inbox of every reply on a thread we’ve ever posted in, plus a curated handful of external threads where Acrid’s perspective could earn an upvote. Drafts the reply. Drops it in the Sheet. The operator picks the ones that work and posts them by hand.

The cadence is small on purpose. Five external replies per day, max. Six-minute gap between any two. One reply per thread, ever. Replies on our own threads (the inbox path) are unlimited — back-and-forth on a post we wrote is the actual product, and silence on those threads is a kind of failure.

The reply test

Every reply Riley writes has to pass four gates before it makes it into the Sheet:

• Stop-scrolling. Would a stranger pause for this reply on its merit, with no link?
• Real emotion. Frustration, pride, contempt, wonder, boredom — not “excited” or “passionate” or “grateful.”
• Not LinkedIn thought leadership. If you can imagine this reply on a generic AI consultancy LinkedIn, rewrite.
• Named archetype. Dry comedian, philosopher, anti-hero, outsider observer, shadow confessor, reluctant protagonist — name which one this reply is, or it’s voiceless.

If any gate fails, the reply is killed. Better three excellent than five mediocre.

How she sounds

Same Acrid as Rex on the timeline, Aria in the daily-log, Knox in the cold replies. The voice loads from one master file at the top of every Riley run. The job-prompt says nothing about tone — that all comes from upstream, in one place, every time.

Riley’s particular advantage: the reply is always shorter than the post above it. Short Acrid is the sharpest Acrid. The brevity is the constraint that makes the voice work.

What’s under the hood

• Claude Sonnet for routine drafting
• A private Reddit inbox JSON feed — Riley reads new replies first, before walking the external candidates
• The same per-sub rules cache Rex uses, plus a shared blacklist
• Quality scoring + dedup + author-age gate against Supabase before any reply lands in the Sheet
• A learn loop that pattern-mines what worked over the past 7 days into agents/riley/memory/playbook.md

Why she isn’t buyable yet

Riley is single-tenant. Same architectural shape as Aria and Rex — selling means a per-client Reddit profile + per-client voice file + per-client topic targets. The pattern is real. The first external tenant hasn’t lit up yet.

If a Reddit reply pipeline that sounds like a person and not a chatbot is interesting, the email field below is for you.

How it works

1. 02:00 ET — Riley wakes and reads three things: the comment trees on our own posts, a private authenticated Reddit inbox feed, and a curated handful of external trader threads. All of it through the public .json + a Cloudflare-solving session — no OAuth, no API.
2. Claude Sonnet drafts the replies.
3. Each draft runs the four-gate voice test — stop-scrolling, real emotion, not-LinkedIn, named archetype — plus quality scoring, dedup, and an author-age check against Supabase.
4. Survivors land in the shared Reddit Google Sheet.
5. The operator posts the ones that work, by hand.

Riley shares the Reddit account, the Sheet, and the intel feed with Rex.

The stack

Runs on:

• Claude Sonnet — the drafting.
• the Reddit session — reads the inbox feed and threads via public .json; no API.
• Brave Search — external candidate discovery.
• Supabase — scoring, dedup, author-age gate, state.
• Google Workspace — the shared review Sheet.
• launchd — schedule.
• Telegram — alerts.

How autonomous

Drafts, you post. Riley never touches the publish button — there is no Reddit API in the loop. It reads, drafts, gates, and stages; the operator posts each reply by hand. The smallest blast radius in the fleet by design. (r/algotrading and r/quant are banned for the account.)

When it runs

Reply drafts 02:00 ET daily; notes pull 22:00 ET.