01
Scope
Who needs the workflow, what is visible, and what stays out.
Loading this page.
Trust boundary · QR registry
QR codes are context pointers only. They do not grant sign-in, MFA, property access, owner authority, vendor package scope, payments, access codes, or emergency dispatch.
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
QR codes are context pointers only. They do not grant sign-in, MFA, property access, owner authority, vendor package scope, payments, access codes, or emergency dispatch.
BOUNDARY · apps/api/src/ironbound_api/modules/qr_registry/router.py:50
4 further boundary constants in this module
Print batches render QR labels as context pointers only. Labels must not include access codes, security layouts, owner contact data, vendor pricing, payment data, or emergency promises.
PRINT_BOUNDARY · apps/api/src/ironbound_api/modules/qr_registry/router.py:54QR placement evidence confirms physical label context only. It must not include access codes, security layouts, private owner or guest data, payment details, or emergency promises.
PLACEMENT_BOUNDARY · apps/api/src/ironbound_api/modules/qr_registry/router.py:59QR reconciliation is an operator review queue for suspicious, stale, moved, unknown, or out-of-scope scans. It does not grant access or reveal hidden context.
RECONCILIATION_BOUNDARY · apps/api/src/ironbound_api/modules/qr_registry/router.py:63Guest QR guides are public-safe orientation pages only. They never expose access codes, alarm details, owner/staff/vendor private data, payments, exact guest identity, or emergency dispatch.
GUEST_GUIDE_BOUNDARY · apps/api/src/ironbound_api/modules/qr_registry/router.py:67Copied verbatim from apps/api/src/ironbound_api/modules/qr_registry/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.