The agent coordinates supported work inside configured limits, brings exceptions to you, and keeps published consequential action categories human-required.
In this article
01
Autonomy with a ceiling
02
The approval queue is where you stay in control
03
The floor that never moves
04
The point is that the limits can widen
Autonomy with a ceiling
"Autonomous" gets used to mean everything from drafting to external execution. Bounded autonomy is the useful middle: eligible supported steps may proceed up to configured thresholds, while exceptions and consequential decisions route to a person.
Per-task thresholds are one mechanism. A routine repair route below a configured cap may be eligible to proceed through policy, provider, acknowledgement, and safety-window checks; an over-cap or unsupported case routes for review. A threshold is not blanket authority.
The approval queue is where you stay in control
Everything that crosses a threshold lands in one place: an approval queue. Each item comes with the context to decide quickly — what the agent wants to do, why, and what it will cost — so approving or denying is a glance, not an investigation.
For eligible hard-to-reverse actions using the soft-commit workflow, a short cancellation window precedes execution. It creates an intercept point for supported pending steps, but does not undo completed or externally settled actions.
Spend caps: a dollar limit per task type — under it the agent acts, over it it asks.
Approval queue: exceptions surface for a fast approve or deny.
Cancellable window: a short interceptable delay for eligible soft-commit actions.
Emergency stop: pauses new Aptoria autonomous execution; completed and provider actions are not undone.
The floor that never moves
Some decisions carry legal or financial weight and warrant human ownership. Aptoria treats published categories as a human-required floor: in supported workflows, ordinary threshold settings do not authorize autonomous execution of those actions.
Applicant denials, eviction filings, lease terminations, security-deposit deductions, and large single transfers can carry jurisdiction-specific duties. The agent may gather available facts or prepare supporting material, but a person owns the decision and external action. This product boundary is not legal advice or a compliance certification.
The point is that the limits can widen
Bounded does not mean frozen. The reason to set explicit limits is so you can loosen them deliberately as the routine cases prove themselves, rather than flipping a single all-or-nothing switch. You start conservative, watch what the agent does, and widen the thresholds you are comfortable widening.
That progression is the goal, and it is yours to set — there is no promised schedule. Eligibility still depends on the workflow, provider, policy, and jurisdiction, and supported decisions recorded through the current ledger retain available attribution and review context.