amorce

The project emphasizes a robust zero-trust security model with L1 API key authentication (in cloud mode) and L2 Ed25519 cryptographic signatures for all transactions. It uses Google Secret Manager for secure key management and has actively removed past hardcoded secrets, providing clear guidance for secure key rotation. Human-in-the-Loop (HITL) approvals add an important layer of oversight for sensitive operations. A critical warning exists against using 'standalone' (development) mode in production, as it relaxes signature verification and lacks cloud-managed services; this is a significant risk if ignored. The use of 'subprocess.Popen' to launch external MCP servers is noted, but current configuration implies local control over these commands.