01
Scope
Who needs the workflow, what is visible, and what stays out.
Loading this page.
Trust boundary · Property binder
Property binder
Spatial media records are append-only revisions attached to normalized property places. Provenance and validation are recorded; dimensions and accuracy are never inferred from media.
Module proof path
Property binder connects API boundaries to public proof.
See the workflow, proof, and operating limits in one scan before reviewing the detailed path.
Inspect proof Open demo02
Proof
Screenshot, proof card, or demo path that makes the claim inspectable.
03
Boundary
What requires human review or source evidence.
Why this page is short
This page only publishes the boundary buyers should rely on.
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
What the Property binder module refuses to do.
Spatial media records are append-only revisions attached to normalized property places. Provenance and validation are recorded; dimensions and accuracy are never inferred from media.
BOUNDARY · apps/api/src/ironbound_api/modules/property_binder/spatial_media_router.py:31
4 further boundary constants in this module
Staff projection includes staff notes, source labels, asset service history, 2D map marker seeds, safe 3D tour links, and staff-only asset identifiers for binder setup, but still does not store access codes, credentials, camera/security maps, payment data, rental channel data, or emergency dispatch.
STAFF_BOUNDARY · apps/api/src/ironbound_api/modules/property_binder/router.py:108Owner projection shows owner-visible structures, zones, documents, assets, and reviewed service history, map markers, and safe 3D tour links only. Staff notes, source labels, hidden records, unsafe embeds, access/security details, camera/security maps, serial/model/manufacturer identifiers, vendor cost, payment, guest, and rental channel data are excluded.
OWNER_BOUNDARY · apps/api/src/ironbound_api/modules/property_binder/router.py:114The asset register reports identifiers, placement confidence, service history, warranty and replacement posture, and evidence readiness across the portfolio. It is not real-time surveillance, does not guarantee GPS accuracy, stores no access codes or credentials, and tracks only the identifier technologies that have a record behind them.
INVENTORY_BOUNDARY · apps/api/src/ironbound_api/modules/property_binder/router.py:3873Work may name the structure, floor, room, zone, exterior area, asset or unit it targets. That is an operational fact, and it is not a commercial unit. This system does not price per door, per unit, or per room, and a place link never becomes a billable line: the unit of value is a human-reviewed, evidence-backed action, and per-door economics are the economics of deleting human review.
PLACE_GRANULARITY_BOUNDARY · apps/api/src/ironbound_api/modules/property_binder/places.py:52
Copied verbatim from apps/api/src/ironbound_api/modules/property_binder/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
Show the platform through one real operating story.
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.
Recommended demo path
- Owner submits a winter maintenance concern.
- Manager reviews urgency, access, and authority.
- Vendor receives only the package-local scope.
- Field evidence becomes a reviewed owner update.
We respond with the recommended demo route, who should attend, and what production access would require.