Agentic property operations glossary
The terms operators and AI agents meet when evaluating property operations software, defined in plain language. Related guides are linked where a term deserves a deeper read.
Agentic property operations
Software that runs enabled property work end to end: gathering context, choosing the permitted action, executing across configured systems, verifying provider results, handling exceptions, and recording the outcome. Customers can assign automatic, notify, approval, or human-only mode to each action.
Definition guide →Approval gate
The hold-for-approval option in Dwelon's four-mode autonomy model. It can be assigned to a selected action instead of automatic, run-and-notify, or human-only execution.
Approval gate design →Autonomous action
An eligible action Dwelon executes without a human in the loop because the workspace's data, connected providers, permissions, and policy authorize it.
Audit trail
The record of what was done, which rule authorized it, and who approved or intervened. Produced as a byproduct of governed workflows.
Claims register
A machine-readable list of product claims with status, scope, and evidence URLs. Dwelon publishes one at /claims.json so operators and AI agents can verify assertions.
Open the claims register →Data isolation
The separation of one customer's documents and processing from another's at the storage, processing, and access levels, including commitments that your data is not used to train shared models.
Security brief →Escalation ladder
The defined sequence of rent actions: reminder, factual follow-up, permitted payment or fee action, reconciliation, and a recorded outcome. Each step follows its configured autonomy mode.
Collection playbook →Evidence receipt
The record of what an AI action was based on: source document, relevant passage, rule, autonomy mode, performed action, provider response, and outcome. This record is what makes actions explainable.
Guarded autonomy
The model where an agentic platform executes inside explicit, inspectable boundaries. Each eligible action can run automatically, run and notify, hold for approval, or remain human-only. Required legal, licensed, safety, and provider authority still applies.
Guardrails guide →Holdover
A resident who remains in the unit after the lease term ends without a signed renewal. It is the expensive outcome of a missed notice window.
llms.txt
A plain-text file at the site root that indexes a website's content for AI agents, listing the docs an agent should fetch. Dwelon publishes llms.txt and llms-full.txt.
Agent index →Notice window
The period defined by the lease within which renewal or non-renewal notice must be given. Renewal economics are decided by whether the conversation starts inside the window.
Renewal checklist →Payment plan
A structured agreement to pay arrears over defined installments. Dwelon can assemble and execute a permitted plan from lease, ledger, communication, and policy context under the action's configured autonomy mode.
Retention policy
The written commitment for how long documents are kept and how deletion works across storage, caches, and provider processing. Confirm it before uploading sensitive records.
Communication autonomy mode
The per-action setting that determines whether a message runs automatically, runs and notifies, waits for approval, or remains human-only. Defined high-impact actions still require qualified human approval.
Communication guide →Service record
The accumulated history of a unit or resident: repairs, lateness, complaints, and improvements. It should inform renewal offers and vendor decisions.
Severity model
The classification of maintenance requests at intake into emergency, urgent, routine, and capital-review categories, each with a defined workflow path.
Triage guide →System of record
The application that remains authoritative for money and legal documents. Any Dwelon write-back depends on the configured integration, permission, provider result, and reconciliation path.
Turnover
The work between a vacancy and the next move-in: cleaning, inspection, maintenance, and re-keying. A workflow-driven chain rather than a coordination scramble.
Work order
The context contract handed to a vendor: severity, issue summary, photos, access instructions, approved spend, warranty notes, and completion window.
Vendor coordination →.well-known
The standard location for machine discovery files. Dwelon publishes a versioned custom documentation manifest under /.well-known/ for AI agents.
AI discovery endpoint →