Current public status
Setting limits is available after account setup; changing them requires two-factor sign-in.
The record explains Aptoria’s workflow; it is not a substitute for a customer’s legal, accounting, or regulatory recordkeeping obligations.
A control only applies where the action is run through the supported Aptoria workflow.
What works today
Approval queue: what an enrolled account can use today and what is still planned, checked against the code that runs for accounts. The list updates when a capability ships.
Aptoria doesn’t carry out routine work on its own yet. Today you can set the limits it will work within, and its hardcoded limits are published.
Undo for autonomous actions is planned; nothing runs on its own today.
Acting on routine work on its own (planned)
Undo for autonomous actions (planned)
Planned means not available to accounts yet, even where parts are built.
Controls before use
Configuration, provider setup, and a reviewable record matter more than a feature-page promise.
Actions, policy changes, and approvals are designed to remain reviewable in the workspace.
The system preserves a human-required floor for defined consequential action classes.
When Aptoria pauses
When a record is incomplete, conflicting, or outside policy, the action should pause and be assigned to a human owner.
Do not treat a draft, sample, or activity entry as proof of delivery, settlement, legal validity, or compliance.
Use the Trust Center and Availability pages for the current workflow boundary before enabling a customer-facing process.
Record
Keep evidence with workflow