Scope
Who needs the workflow, what is visible, and what stays out.
Trust boundary · Rentals
Notifications contain only a case reference, reviewed event label, and expiring case link. They never include request descriptions, access details, attachment names, provider secrets, or emergency-dispatch claims. Provider acceptance is not recipient delivery.
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.
Why this page is short
Some areas are intentionally represented by a narrow public boundary instead of a full feature page. That keeps sensitive operations, access rules, and unfinished marketing claims out of the buyer-facing experience.
How we evidence thisEnforced boundary
Notifications contain only a case reference, reviewed event label, and expiring case link. They never include request descriptions, access details, attachment names, provider secrets, or emergency-dispatch claims. Provider acceptance is not recipient delivery.
PUBLIC_NOTIFICATION_BOUNDARY · apps/api/src/ironbound_api/modules/rentals/public_service_notifications.py:43
10 further boundary constants in this module
Rental operations retain unit/listing references, stay timing, occupancy count, availability blocks, import status, and owner-safe summaries. Guest identities, messages, payment data, channel credentials, private calendar URLs, and access details are not stored or shown.
RENTAL_BOUNDARY · apps/api/src/ironbound_api/modules/rentals/router.py:136Supported channel labels are airbnb, vrbo, booking_com, direct, manual, ical, pms, and other. iCal is availability-only; CSV/manual import can follow; PMS/channel-manager integration is preferred; direct Airbnb/Vrbo APIs require approved programs and are not implemented here.
CHANNEL_BOUNDARY · apps/api/src/ironbound_api/modules/rentals/router.py:137PMS adapter previews normalize partner-provided sample records into owner-safe counts, reconciliation actions, and source manifests only. They do not connect to live Airbnb, Vrbo, Booking.com, PMS, or channel-manager systems; do not store channel credentials; do not scrape dashboards; and do not enable writeback.
PMS_ADAPTER_BOUNDARY · apps/api/src/ironbound_api/modules/rentals/router.py:138Marketability reports are owner-safe planning aids built from recorded listing, stay, readiness, reviewed financial, snapshot, and recommendation sources. They are not appraisals, tax advice, investment guidance, or guaranteed revenue projections.
MARKETABILITY_BOUNDARY · apps/api/src/ironbound_api/modules/rentals/router.py:139Valuation-support language is a source-backed narrative only: it may describe history, readiness, amenities, and income-potential support, but it must not guarantee valuation, forecast income as certain, or replace a licensed appraisal.
VALUATION_SUPPORT_BOUNDARY · apps/api/src/ironbound_api/modules/rentals/router.py:140Listing channel-change previews are human-review fixtures only. They compare recorded listing copy, readiness, rate, and availability posture for Airbnb, Vrbo, direct, and PMS/channel-manager review, but they do not publish, update channels, call provider APIs, custody credentials, scrape dashboards, change prices/calendars, or create owner approvals.
LISTING_CHANGE_PREVIEW_BOUNDARY · apps/api/src/ironbound_api/modules/rentals/router.py:141Unit tenancies record which unit is occupied, by what kind of arrangement, and over what window. They hold no tenant identity, contact details, payment data, lease documents, or screening results, and recording a tenancy neither creates nor terminates a legal agreement.
TENANCY_BOUNDARY · apps/api/src/ironbound_api/modules/rentals/router.py:1912Tenant lifecycle workflows organize reminders, checklists, evidence, and review packets. They do not provide legal advice, jurisdiction-specific notice automation, court filing, eviction authority, or payment collection, and they hold no tenant identity.
TENANCY_LIFECYCLE_BOUNDARY · apps/api/src/ironbound_api/modules/rentals/router.py:2175Resident lifecycle views show only plain next steps, safe property instructions, checklist status, and scoped request intake. They do not expose owner, staff, vendor, legal-review, payment, contact, internal-note, access-code, alarm, or security details.
RESIDENT_LIFECYCLE_BOUNDARY · apps/api/src/ironbound_api/modules/rentals/router.py:2181This link opens only this service case. It does not expose another stay, resident, property record, access code, payment, staff note, vendor contact, or live vendor location. For fire, gas, medical danger, active flooding, or another immediate threat, call 911 or the appropriate utility first.
PUBLIC_SERVICE_BOUNDARY · apps/api/src/ironbound_api/modules/rentals/router.py:2519Copied verbatim from apps/api/src/ironbound_api/modules/rentals/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.
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.