Trust

You confirm. Ordo cannot hide.

Ordo starts by proposing drafts, reminders, and follow-ups for confirmation. Controlled autonomy is the enterprise roadmap: high confidence, explicit workspace permission, an audit log, and undo.

Three confidence tiers

Propose and surface are the live trust model. Auto-execute is the enterprise roadmap tier for trusted work classes that a workspace has explicitly enabled.

What gets logged, and how undo works

Every proposed action records who, what, from which thread, and at what confidence. Future autonomous actions must add the policy that allowed them and the reversal path available to the user.

Permissions at volume

Enterprise departments need routing and review before anything runs on its own. The matrix is a product mock of that control model — not a live tenant.

Role	Auto-execute	Propose	Surface
Operator	Allowed sources	Yes	Yes
Reviewer	No	Yes	Yes
Admin	Policy owner	Yes	Yes

What Ordo reads — and what it never does without permission

Reads, when connected

Email, chat, docs, meetings, and forms — the places requests actually arrive. Capture is for extracting the next step, not for becoming a document editor or archive.

Does not, without you

It does not send, schedule, or route at the propose or surface tiers until you confirm. It does not auto-execute a class of action you have not allowed by policy. It does not skip the log or the undo model.

Compliance roadmap

We do not claim SOC 2, GDPR certification, HIPAA, or ISO attestations we do not have. The product is designed for compliance readiness: auditability, permissions, retention and export controls on the enterprise band, and a clear record of autonomous actions. Those are commitments and a roadmap, not certificates.