# Explicit Scope & Known Limitations

1. **Enforcement Boundary**: Apodictic enforces invariants on traffic routed through `@apodictic/sdk`, `@apodictic/mcp-verifier`, or the PostgreSQL proxy. Direct database connections bypassing the gateway require database-level network/credential isolation.
2. **Database Concurrency**: Multi-process atomic transaction tests in this repository were executed against SQLite WAL (`BEGIN IMMEDIATE`). Live PostgreSQL multi-process contention requires a dedicated PostgreSQL server.
3. **Formal Model Scope**: `formal-specifications.smt2` (`QF_LRA`) models financial reserve floors, 24-hour velocity caps, and tax parity. Both the native Rust compiler (`noesis-symbolic-sql`) and Python enclave recursively unwrap CTEs (`WITH`), `DO $$ ... $$` PL/pgSQL blocks, stored function bodies, and dynamic `chr()`/`hex` `EXECUTE` statements on gateway-routed traffic; arbitrary runtime triggers executed directly inside an external PostgreSQL daemon bypassing the proxy are outside the proxy boundary.
4. **External Validation**: Independent third-party penetration testing, blind external test corpora, and bare-metal Linux `/dev/kvm` Firecracker escape testing require external infrastructure/auditors.
