01
Scope
Who needs the workflow, what is visible, and what stays out.
Loading this page.
Trust boundary · Properties
Property Home Base is a read-only property front door. It reports owner-safe counts, readiness posture, and links to governed modules; it does not expose request descriptions, access details, vendor notes, payments, staff notes, or security placement.
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
Property Home Base is a read-only property front door. It reports owner-safe counts, readiness posture, and links to governed modules; it does not expose request descriptions, access details, vendor notes, payments, staff notes, or security placement.
PROPERTY_HOME_BASE_BOUNDARY · apps/api/src/ironbound_api/modules/properties/router.py:1191
4 further boundary constants in this module
Property profile stores typed identity, physical, and operating facts. It does not store access instructions, credentials, utility account numbers, security placement, or free-form internal notes. Address and approach details remain in the separately governed location record.
PROPERTY_PROFILE_BOUNDARY · apps/api/src/ironbound_api/modules/properties/router.py:2746A property location is the address and, optionally, one coordinate a person typed after looking at a parcel map or standing in the driveway. Nothing here is geocoded, verified against a provider, or refreshed: this API makes no outbound calls. It is not a live position, a tracker, a boundary survey, a title record, or a routing engine, and it never changes which service area a property is in.
PROPERTY_LOCATION_BOUNDARY · apps/api/src/ironbound_api/modules/properties/router.py:3115Operating periods and access windows record when a property may be entered and in what condition it is being held. They are scheduling constraints reviewed by staff. They do not store alarm, gate, lockbox, or keypad codes; do not grant or revoke physical access; do not automatically dispatch, reschedule, or cancel work; and do not track occupants.
PROPERTY_OPERATING_BOUNDARY · apps/api/src/ironbound_api/modules/properties/router.py:3123Property taxonomy labels are owner-safe classification and onboarding guidance. They do not publish marketing copy, expose access/security details, create tenant records, change plans, dispatch vendors, or mutate destination profile sections.
PROPERTY_TAXONOMY_BOUNDARY · apps/api/src/ironbound_api/modules/properties/taxonomy.py:6Copied verbatim from apps/api/src/ironbound_api/modules/properties/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.