01
Scope
Who needs the workflow, what is visible, and what stays out.
Loading this page.
Module · Compliance
Prepare compliance tasks, move-in/out checklists, nonpayment workflows, notices, evidence, and review packets.
Module proof path
See the workflow, proof, and operating limits in one scan before reviewing the detailed path.
Inspect proof Open demoWho needs the workflow, what is visible, and what stays out.
Screenshot, proof card, or demo path that makes the claim inspectable.
What requires human review or source evidence.
Who it is for
Pain
Compliance work often mixes law-sensitive language, evidence, deadlines, mail, owner visibility, and tenant communication in fragile manual files.
Workflow
Select a jurisdiction-aware workflow template.
Collect facts, evidence, dates, parties, and required attachments.
Route drafts and notices through human review.
Track delivery posture, response windows, and follow-up tasks.
Preserve the history with legal-boundary disclaimers.
Proof
Related modules
Product proof
Module pages show how a signal moves through the product without becoming a false automation claim.
Module receives a synthetic operational signal.
Module pages show how a signal moves through the product without becoming a false automation claim.
Safe sample scenario · illustrative operational state only.
Enforced boundary
Compliance localization tracks jurisdiction, source, version, review, export, and delivery posture. It does not provide legal advice, jurisdiction-specific legal wording, court filing, eviction authority, or automated notice sending.
COMPLIANCE_BOUNDARY · apps/api/src/ironbound_api/modules/compliance/router.py:19
Copied verbatim from apps/api/src/ironbound_api/modules/compliance/router.py and regenerated from apps/api/src/ironbound_api/modules. The API returns these same strings in its boundary fields, and a drift check fails the build if this page and the source stop agreeing.
Boundary
Module landing pages describe buyer-facing product workflows and controlled-pilot proof. They do not change billing, permissions, legal advice, emergency monitoring, payments, or live integrations.
Pilot access
The best demo is not a feature checklist. It follows a request from owner intake to manager triage, vendor packet, field evidence, reviewed closeout, and owner-safe reporting.
We respond with the recommended demo route, who should attend, and what production access would require.