-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Nick edited this page Nov 21, 2025
·
21 revisions
Pattern-Adaptive Transmodal Anti-Spam System
PATAS Core technical documentation. This wiki contains technical documentation for integration and deployment.
- Quick Start Guide - Installation and basic usage
- Architecture - System architecture and design principles
- Code Overview - Code structure and navigation guide
- Configuration - Configuration reference and environment variables
- Configuration Examples - Example configurations for different deployment scenarios
- Scaling & Cost Design - How PATAS handles millions of logs efficiently
- Comparison and Positioning - PATAS vs traditional approaches
- Roadmap - Development roadmap and future enhancements
- Migration Guide - Database migration instructions
- Safety Profiles - Conservative, Balanced, and Aggressive profiles
- Custom Profiles - Define custom aggressiveness profiles
- LLM Usage - LLM integration and privacy guarantees
- Threshold Calibration Guide - How to calibrate thresholds for your use case
- Engineering Notes - Technical overview for engineering teams
- Safety Guide - Safety profiles and enforcement model
- API Reference - Complete API endpoint documentation
- API Quickstart - Quick start guide for API usage
- API Enhancements v2.1 - New API features: filtering, explanations, risk assessment
- Privacy and Data Protection - Privacy modes and data handling
- Security - Security considerations and best practices
- Security Audit Checklist - Comprehensive security checklist
- Production Deployment Guide - Production deployment and maintenance
- Scaling Guide - Horizontal scaling strategies
- Distributed Locks - Multi-instance coordination
- Checkpointing - Resume pattern mining from checkpoints
- Performance Guide - Performance benchmarks and optimization
- Load Testing Guide - Load testing tools and procedures
- Alerting - Alert rules and AlertManager configuration
PATAS is an autonomous pattern discovery and rule management system for anti-spam operations. It analyzes historical message logs, automatically discovers spam patterns, generates safe blocking rules, and evaluates their effectiveness before deployment.
Key Characteristics:
- Signal engine, not enforcement - PATAS provides patterns and metrics that inform anti-spam decisions
- On-premise deployment - Designed for deployment within your infrastructure
- Two-stage processing - Fast scanning + deep analysis for 70-90% cost reduction
- Deterministic and rule-based - Core engine is deterministic; ML/LLM is optional
- Safety-first design - Multiple safety profiles with clear risk boundaries
- Ingest - Load historical message logs into PATAS
- Discover - Automatically identify recurring spam patterns (two-stage: fast scan + deep analysis)
- Generate - Create safe SQL rules from discovered patterns
- Evaluate - Test rules on historical data (shadow mode)
- Promote - Activate rules that meet safety thresholds
- Monitor - Track rule performance and deprecate underperforming rules
Architecture and Design:
- Start with Architecture for high-level understanding
- Review Code Overview to understand codebase structure
- See Configuration for setup and tuning
Scaling and Performance:
- Scaling & Cost Design - How PATAS scales efficiently
- Scaling Guide - Horizontal scaling strategies
- Distributed Locks - Multi-instance coordination
- Checkpointing - Resume long-running operations
Integration & Safety:
- Start with Engineering Notes
- Review Safety Guide
API and Operations:
- Review API Reference for integration
- See Configuration and Quick Start for deployment
- See Production Deployment Guide for production setup
- See Alerting for observability
- GitHub: kiku-jw/PATAS