deep tier + cited rationale
policy-tuned llm path for the hard 1%. every block ships with a citation pointing at the policy clause that triggered it.
a working document. dates are best guesses. items get added, dropped, and shuffled the moment we learn we were wrong about them.
we haven't shipped the api yet. q2 is about getting all three tiers, the rationale system, and the sdks far enough to put a key in early hands.
policy-tuned llm path for the hard 1%. every block ships with a citation pointing at the policy clause that triggered it.
discord, twitch, reddit. first training run before launch, monthly cadence after.
deterministic regex + lexicon path. targeting ~1ms p99 on the obvious 95% of traffic.
small classifier for the 4% the rules miss. targeting ~30ms p95.
assuming q2 lands, q3 is the first round of things we want right after the api is live: multilingual, batch, and the surfaces that make the api easier to live with.
native, not translated. each language gets its own slang corpus and tuned thresholds. english ships at launch; this is the very next thing we pick up.
10k messages, one call, async return. one of the things we want out the door pretty early after launch.
tune category thresholds. preview against history before deploying. timing depends on how launch lands.
signed deliveries. retries with backoff.
searchable. every decision, every revision.
controls in place. audit window opens q4.
things we want, but where the timeline is honestly fuzzy. anything here can move into next, slip into someday, or get cut entirely.
same shape, different payload. nsfw + violence first. not sure how fast we can get this real — depends on how text lands.
data residency. gdpr-shaped. for scale plans.
second wave after the q3 set. driven by what waitlist teams actually need.
audit window opens. report on request after.
no dates. no commitment. these are conversations we keep having internally and would love to hear opinions on.
streamed transcripts route to the text path. raw clips run through a separate model for nsfw flags. open question: latency budget for live streams.
drop in 1k flagged examples. we fine-tune your slice without leaking it back into the base. open question: pricing model.
wasm bundle. zero server hop for the obvious 95%. open question: keeping the corpus fresh without a chatty update channel.
because eventually a person has to look at the hard 1%. queue, hotkeys, decision audit. open question: build vs partner.
a roadmap is more useful when it includes what's off the table. these are not “yet” — these are no.
we sell the api. you build the workflow. we won't review your queue for you.
not now, not later, not "anonymized." the privacy policy says it; the company is structured to keep it true.
moderation is structured output. chat surfaces lose the structure. wrong tool.
not what we built this for.
tell us what you'd build with us if it existed. we read every reply, and the loud ones move things up the list.