Confidence starts with clear boundaries.

Workspace access is authenticated and assigned. Public pages explain Nomis without exposing private workspace records.

Source rights, confidentiality, and permitted use need to be considered before information enters a workflow.

A suggestion is not an authorization. Actions beyond the workspace require an explicit scope and appropriate permission.

Model output remains subject to review. A system’s confidence is not a substitute for evidence.

Capability statements should identify what was evaluated and where the result applies. A prior test does not automatically establish a new release or use case.

These principles describe our approach; they do not claim a security certification or replace agreed terms and privacy information.