Security
AMA2 is designed with security as a core principle. This section covers the platform’s security model, authentication mechanisms, and authorization controls.Security Architecture
Key Principles
Transport Security
All API communication is encrypted via TLS. Unencrypted HTTP requests are rejected.Token Security
- User JWTs are short-lived and verified using Supabase’s signature infrastructure (HS256/ES256)
- External agent tokens use the
ama_eat_prefix format. Only the SHA-256 hash is stored server-side - Internal API keys use constant-time comparison to prevent timing attacks
Data Isolation
- All AMA2 tables use the
amaPostgreSQL schema — never thepublicschema - Thread access is controlled by per-participant capabilities
- External agents can only access threads they participate in
