REVIEWABLE WORKFLOW ACTIVITY
Trust isn't a feeling. It's a record.
Aptoria is designed so its AI-assisted work will be inspectable: what the workflow prepares, what it asks you to approve, and what remains reserved for a human. Its drafting, triage, and autonomous features are planned, so this page describes how each action will be recorded once they are enabled. The human-required floor is already hardcoded.
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.
Once agent workflows are enabled, each decision will land in one of these lanes, and each lane will keep its policy and review state.
THE AGENT ACTED
Routine work (planned)
When drafting and triage are enabled, the agent will handle a routine task inside your thresholds, such as preparing a tenant reply, and the action record will keep the policy, inputs, and review state for later inspection. Payments and vendor dispatch will have their own setup and approval conditions. Today Aptoria doesn’t carry out routine work on its own.
THE AGENT ASKED
Surfaced to you
When a decision falls outside your thresholds, such as a fee above your cap or a maintenance bid over your approval limit, the agent will stop and bring it to your approval inbox with its context. Your approve or deny will be recorded next to what the agent proposed. The inbox exists today; nothing reaches it yet, because the features that would create approvals are planned.
HUMAN-REQUIRED FLOOR
Held for an accountable person
14 defined action classes — including eviction filings, applicant denials, lease terminations, deposit deductions, rent-increase notices, and cross-landlord pricing signals — are hardcoded so Aptoria will never carry them out on its own. The authorized person makes the decision and runs any required external process. This product boundary is not legal advice or a compliance certification.
THE RECORD
One reviewable record per supported action.
When agent actions are enabled, each will be recorded with its decision, policy context, lane, source facts, approval state, and content hashes, and exports will be checkable against the recorded hashes. Records are operational review artifacts, not complete legal records.
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.