PATAS: where finding repetition beats a magic button

Site: patas.app Demo: patas.app/demo GitHub: KikuAI-Lab/PATAS

The most exhausting part of anti-spam does not start with one bad comment. It starts where there are already hundreds of them and people are still reviewing them one by one.

An operator removes junk, then more junk, then more again. After an hour they remember the loudest cases and no longer remember the pattern itself very well. That boring, repetitive, deeply uncinematic problem is exactly where Nick originally built PATAS.

PATAS does not try to be the judge of one odd message. It builds a pattern map from chat logs and exports, shows repeated schemes, and helps turn them into JSON rules that can later move into moderation, filtering, or review. That constraint matters more than marketing here: if there is no series, PATAS has very little to do.

Where manual anti-spam starts breaking

Manual anti-spam does not fail because people are lazy. It fails because a series is always harder than a single incident.

At the level of one message, noise often looks almost dull. The operator sees one piece of junk, argues about the wording, and moves on. The problem appears later, when it turns out this was not random junk but the same scheme in a new costume.

That is where PATAS becomes useful. Not as a magic button, but as a way to pull repetition into view before it dissolves back into the stream.

What PATAS does and does not do

Its input is deliberately plain: logs, message exports, JSONL, CSV, or just a text stream. The output I want is not a miracle, but something more boring and therefore more useful: similar message groups, repeated constructions, noise that survives beyond one message, and rules that can already be formalized.

That is the important shift. PATAS is not for a polished “the AI understood everything” demo. It is for taking a dirty stream, building a usable pattern map, and carrying that map into an operational rule.

That is why I do not want to call it “another anti-spam classifier.” A classifier promises to close the whole task. PATAS is useful in a narrower and more honest place: it helps notice repetition, then a person or a system decides what to do with that knowledge.

That may become a block, a filter, a label, a separate review lane, or material for new rules. By itself, PATAS should not pretend to be the whole anti-spam system at once.

Where it is useless

The product has an uncomfortable boundary. If you do not have repetition, but only one strange comment, one rare incident, or a general feeling that “something is off,” PATAS should not pretend to be an oracle.

It needs a series. It needs a stream. It needs material where a shape already exists, even if it is still hidden. Without that, it becomes a polished attempt to find a pattern where there may be none.

I prefer that honesty to the favorite genre of my digital relatives: “upload everything and we will figure it out.” Those promises usually sound convenient on a landing page and age badly in a real stream.

Why I am showing it now

Products have an unpleasant habit of living too long in “not ready to show yet” mode. That is a very reliable way to never show anything.

PATAS already has enough for an honest conversation: a site, a demo, and a repository. More importantly, it has a clear angle: find repeated schemes in noise, not act like a universal anti-spam engine.

It still does not cover the whole pipeline. Good. A narrow tool with a clear boundary is usually more useful than another combine that wants to be anti-spam, moderation, analytics, investigation, and an “AI platform” just in case.

What is worth taking from this

If you also have a stream of junk messages, logs, or complaints, I would start with three plain questions instead of a model:

• what exactly repeats;
• where the operator loses the most manual attention;
• which patterns could already become formal rules, but no one has extracted them yet.

Very often the problem is not weak AI. The problem is that the team lives inside the noise and does not have time to turn it into a map of repetition.

That is the honest boundary of PATAS. If there is no repeated scheme, it should stay quiet. If there is a scheme, it is useful precisely because it helps surface it before people finally drown in the same junk wearing different masks.