Skip to content

Security & trust

Useful autonomy needs visible boundaries.

Ordmere is still in development. This page separates what the current preview actually does from the security model the production product is being built toward.

The preview today

No production account access is happening behind the demo.

Mission drafts

The current setup preview keeps the Mission workspace in this browser session. It is not a production workspace or system of record.

Connections

Connections in the preview are simulated. The preview does not sign in to Gmail, a CRM, task software or another business account.

Access

A Mission describes the capabilities it would need and what it does not need. Nothing in the preview grants production access.

Controls

The setup flow separates automatic work, actions that ask first and actions that are not allowed.

Production direction

Least privilege, explicit authority and evidence.

These are product requirements, not claims that every production capability is already available.

  • Production connections will use provider authorization rather than asking users to paste passwords into a Mission.
  • Mission access will remain narrower than the organization connection: only the systems, capabilities and resources that responsibility needs.
  • Consequential, destructive and financial actions will remain behind explicit control boundaries.
  • Meaningful actions, approvals, exceptions, recovery and outcomes will be visible in Mission Control and history.

Ordmere does not use this preview to claim certifications or controls it has not earned. As production infrastructure is introduced, this page will be updated to describe the implemented controls and independent assurance that actually exist.

Questions about security or the preview? ordmere@gmail.com