Identity and permissions
Use authenticated identities, least privilege, and organization-scoped access. Validate permissions for every sensitive operation and test cross-organization access boundaries.
Security and trust
Make execution inspectable and bounded.
Nexus is designed around explicit authorization, organization-scoped operations, evidence records, and human review where a system cannot independently establish an outcome.
Evidence and provenance
Evidence integrity and provenance can improve traceability. A cryptographically intact record does not independently prove that the represented physical-world event happened.
Human oversight
Policy checks can flag missing or inconsistent information. Keep review and verification states explicit; do not silently convert incomplete evidence into a verified result.
Production operations
Use HTTPS, secret management, backups, dependency monitoring, and tested restore procedures. Keep payment movement disabled until a production provider and the relevant controls are validated.
Current deployment
Readiness depends on configuration.
The public homepage does not certify a particular deployment. Check its readiness endpoint, review the release's operational guide, and complete the production certification checks for the actual environment before connecting sensitive workloads.