Security & Planning
Security architecture, compliance boundaries, and the architectural decisions still open for resolution.
| Page | What It Covers |
|---|---|
| Security Architecture | Authentication, authorisation, mTLS, audit trail, and regulatory compliance boundaries |
| Open Questions | Eight architectural decisions still open — LLM provider, Temporal Cloud vs self-hosted, monorepo vs polyrepo, and more |
Design Philosophy on Compliance
Anchita treats compliance boundaries as engineering constraints, not policy flags. The distinction matters:
- A policy flag can be turned off by a configuration change or a bug
- An engineering constraint is enforced by the type system, the workflow interface, and the signal definition
The submitBSAAttestation signal requires an AttestationRecord with a userId validated against the BSA_OFFICER role. There is no force_approve: true parameter. There is no admin override. The compliance boundary is the API.