Scope
Who needs the workflow, what is visible, and what stays out.
Trust boundary · Vendor work packages
This assignment-only package contains the minimum service scope, window, checklist, package messages, vendor quote, and reviewed evidence needed for this work. It does not grant property browsing or expose owner contacts, owner totals or markup, internal notes, credentials, security details, other vendors, general communications, or unrelated assignments.
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
This assignment-only package contains the minimum service scope, window, checklist, package messages, vendor quote, and reviewed evidence needed for this work. It does not grant property browsing or expose owner contacts, owner totals or markup, internal notes, credentials, security details, other vendors, general communications, or unrelated assignments.
VENDOR_BOUNDARY · apps/api/src/ironbound_api/modules/vendor_work_packages/router.py:154
11 further boundary constants in this module
Vendor work packages are purpose-built, expiring assignments. Creating a package does not grant generic property access, confirm vendor availability, approve owner cost, or authorize work before explicit vendor acceptance, assignment, and operator dispatch.
OPERATOR_BOUNDARY · apps/api/src/ironbound_api/modules/vendor_work_packages/router.py:161Arrival guidance is assignment-scoped and manually acknowledged. The initial projection contains no exact address or coordinate. A deliberate navigation handoff lasts five minutes, requires the assigned technician during the approved service window and never infers arrival, work start, or completion from device position.
VENDOR_ARRIVAL_BOUNDARY · apps/api/src/ironbound_api/modules/vendor_work_packages/router.py:182Dispatch readiness combines recorded vendor windows, package assignments, and configured calendar connection metadata. It never treats a configured connection, a local schedule, or an availability window as an external provider confirmation; no calendar provider call or dispatch message is made by this read-only preflight.
VENDOR_DISPATCH_READINESS_BOUNDARY · apps/api/src/ironbound_api/modules/vendor_work_packages/router.py:188This contractor operations dashboard aggregates package-local schedule, communication, evidence, performance, and finance-review signals for operators. It is not a payment rail, 1099 system, owner charge, live SMS/WhatsApp sender, or vendor ranking automation.
VENDOR_OPERATIONS_DASHBOARD_BOUNDARY · apps/api/src/ironbound_api/modules/vendor_work_packages/router.py:166This owner-safe contractor progress report exposes reviewed status, windows, and evidence counts only. It omits vendor commercial amounts, internal notes, owner contacts, credentials, raw media, package messages, and unreviewed evidence captions.
VENDOR_OWNER_PROGRESS_BOUNDARY · apps/api/src/ironbound_api/modules/vendor_work_packages/router.py:171This phone integration readiness view plans Twilio/Aircall-style voice controls without placing calls, recording calls, exposing owner phone numbers, storing provider credentials, or treating caller ID as authentication. Live calls require consent, masking policy, signed webhooks, audit retention, opt-out handling, and operator-reviewed role access.
VENDOR_PHONE_READINESS_BOUNDARY · apps/api/src/ironbound_api/modules/vendor_work_packages/router.py:176Corrective-action execution records only package-local checklist guidance in the package message thread. It does not create tasks, exports, emails, provider calls, payment/tax records, owner-contact workflows, cross-vendor comparisons, rankings, or raw-media bundles.
VENDOR_CORRECTIVE_ACTION_EXECUTION_BOUNDARY · apps/api/src/ironbound_api/modules/vendor_work_packages/router.py:194Scorecard review sessions record a neutral package-local agenda summary in package message threads only. They do not create rankings, ratings, payment/tax records, owner-contact workflows, cross-vendor comparisons, raw-media bundles, exports, emails, tasks, or provider calls.
VENDOR_SCORECARD_REVIEW_SESSION_BOUNDARY · apps/api/src/ironbound_api/modules/vendor_work_packages/router.py:199Scorecard review-session closeout is a read-only readiness preview over package-local session notes, follow-up actions, and safety gates. It does not close packages, create tasks, export files, deliver email, trigger provider calls, approve payments, prepare tax records, contact owners, rank vendors, compare vendors, or expose raw media.
VENDOR_SCORECARD_REVIEW_SESSION_CLOSEOUT_BOUNDARY · apps/api/src/ironbound_api/modules/vendor_work_packages/router.py:205This contractor scorecard preview is a neutral, evidence-backed readiness summary for the selected vendor account or assignment-visible work packages. It is not a vendor ranking, disciplinary finding, payment approval, 1099 record, owner-facing report, or defamatory quality judgment, and it omits owner contacts, other vendors, internal notes, credentials, access details, vendor pricing, owner totals, wholesale or markup details, and raw media.
VENDOR_SCORECARD_PREVIEW_BOUNDARY · apps/api/src/ironbound_api/modules/vendor_work_packages/router.py:211The vendor packet and quality loop shows what is missing before quote, dispatch, closeout, correction, and payment review. It does not expose owner contacts, coordination markup, or access secrets, and it moves no payment: a packet reaching payment_ready is a packet ready for a human to review, not one that has been paid.
QUALITY_LOOP_BOUNDARY · apps/api/src/ironbound_api/modules/vendor_work_packages/router.py:6790Copied verbatim from apps/api/src/ironbound_api/modules/vendor_work_packages/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.