REVIEWABLE WORKFLOW ACTIVITY
Trust isn't a feeling. It's a record.
Aptoria is designed to make supported agent-assisted work inspectable: what the workflow prepared or handled, what it asked you to approve, and what remains reserved for a human. Each supported action records the available source facts, policy, approval state, and outcome so your team can review it after the fact.
Reviewable action record
Hash-chained
Exportable review record
Source and policy context
Supported decisions land in one lane
What it handled. What it routed. What remains human.
Supported agent workflows resolve into one of these lanes when the policy engine has enough context, and each supported lane records available policy and review state.
THE AGENT ACTED
Handled on its own
For a supported, configured workflow inside your thresholds, the agent can handle a routine task such as preparing a tenant reply or coordinating maintenance. Provider-backed payments and dispatches have their own setup and approval conditions. The action record captures the policy, inputs, and review state so the work can be inspected later.
THE AGENT ASKED
Surfaced to you
When a decision falls outside your thresholds — a fee above your cap, a maintenance bid over your approval-rule limit, a message it isn't sure about — it stops and routes the item to your queue with the full context. Your approve/deny is recorded next to what the agent proposed.
HUMAN-REQUIRED FLOOR
Held for an accountable person
Eight defined action classes — including eviction filings, applicant denials, lease terminations, deposit deductions, rent-increase notices, and cross-landlord pricing signals — are not autonomously executed through supported Aptoria workflows. The product can prepare context while the authorized person retains the decision and any required external process. This product boundary is not legal advice or a compliance certification.
THE RECORD
One reviewable record per supported action.
Supported agent actions record the decision, policy context, lane, available source facts, approval state, and content hashes. For workflows that currently write hash-chain metadata, exports can be checked against available recorded hashes. Records are operational review artifacts, not complete legal records.
Supported decision records preserve available policy, source, and review context
Policy changes can snapshot BEFORE/AFTER where that workflow records them
"What was the configured dispatch cap on March 5?" has a reviewable answer where available fields record it
Illustrative row. Field names map to real columns; values are an example.
How we measure
Numbers with a published method.
We measure supported metrics from available design-partner snapshots and publish aggregate data only after the k-anonymity floor is met. Published rates and deltas are weighted by current unit count and gated by a three-partner floor so no single account can be reverse-engineered from them.
Methodology
At baseline capture, Aptoria calculates available metrics from the preceding 12-month window and records when no prior history exists. After the minimum tenure gate, the weekly cohort job recomputes metrics from the available trailing 90-day window and compares supported deltas with that recorded baseline. Published aggregates are weighted by current unit count and require at least three design partners. Source data comes from workspace payment, lease, and work-order records; missing history is not filled with synthetic outcomes.
Your record starts the day you sign up.
Availability depends on the workflow, provider setup, and your configured policy. Review product availability and test a bounded workflow before relying on it in production.
Start free trial
See the safety architecture