The company owns the release.
A sponsor can distribute a playbook but cannot activate a local workflow or override local approvers.
Trust at Ordinal
Ordinal is being designed so authority, data boundaries, human decisions and evidence are explicit—not buried in a policy document.
Product principles
A sponsor can distribute a playbook but cannot activate a local workflow or override local approvers.
Tools, data, thresholds and consequential actions are explicitly allowed, gated or blocked.
The workflow creates a usable control record as the work happens, not as a retrospective exercise.
Ordinal supports customer-defined controls. It does not determine obligations or guarantee compliance.
Evidence by design
Receipts connect the approved workflow to execution, human judgement, exceptions and customer-defined outcomes.
EVIDENCE RECEIPT
CLM-2048 / 01429d2a…c71fCapability status
Ordinal is in its design-partner stage. This table describes the intended pilot scope and current build status; it is not a certification statement.
Operational cases remain in the portfolio company boundary.
Named local approvers release each workflow version.
Explicit permissions constrain what the agent may access and do.
Structured run evidence connects approvals, actions and outcomes.
Granular permissions for sponsor, company and assurance roles.
No SOC 2 or ISO 27001 certification is currently claimed.
Security conversations
Design partners receive a detailed data-flow, responsibility and control review before any operational pilot.