Scope
Who needs the workflow, what is visible, and what stays out.
Trust boundary · Vendor admin
Sourcing validates recorded fit and opens RFQ invitations through the existing project ledger. It does not rank protected traits, auto-award work, dispatch a vendor, approve payment, determine tax treatment, or treat missing evidence as poor performance.
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
Sourcing validates recorded fit and opens RFQ invitations through the existing project ledger. It does not rank protected traits, auto-award work, dispatch a vendor, approve payment, determine tax treatment, or treat missing evidence as poor performance.
BOUNDARY · apps/api/src/ironbound_api/modules/vendor_admin/sourcing_router.py:26
6 further boundary constants in this module
Vendor administration stores business profile, service-fit, compliance metadata, and review posture only. It does not store raw W-9/TIN values, bank details, payment instructions, access/security codes, vendor markups, or evidence object keys.
VENDOR_ADMIN_BOUNDARY · apps/api/src/ironbound_api/modules/vendor_admin/router.py:68Contractor cockpit data is projected from the vendor's own account, workspace link, compliance posture, team access, and assignment-scoped work packages. It omits owner contacts, security instructions, raw tax/payment data, internal markup, object keys, unrelated properties, and other vendor records.
VENDOR_COCKPIT_BOUNDARY · apps/api/src/ironbound_api/modules/vendor_admin/router.py:78Vendor self-service is restricted to the active vendor account and exposes profile plus compliance status metadata needed for onboarding and renewal. It never exposes other vendors, owner contacts, property browsing, payment rails, tax identifiers, or internal pricing.
VENDOR_SELF_BOUNDARY · apps/api/src/ironbound_api/modules/vendor_admin/router.py:73Contractor availability windows are scheduling inputs only. They do not dispatch work, promise emergency coverage, reveal property addresses or owner contacts, or store access codes, payment data, tax identifiers, or internal pricing.
VENDOR_AVAILABILITY_BOUNDARY · apps/api/src/ironbound_api/modules/vendor_admin/router.py:84Vendor network intelligence is a read-only projection of recorded service coverage, capacity, compliance, RFQ, work-package, evidence, and invoice-handoff facts. Candidate explanations never auto-award work, use protected traits, treat missing data as poor quality, approve payments, or expose internal notes, owner details, credentials, pricing, or other vendors to a contractor.
VENDOR_NETWORK_BOUNDARY · apps/api/src/ironbound_api/modules/vendor_admin/router.py:89The contractor work queue is restricted to the active vendor account and capability-visible assignments. It omits operator notes, owner details, hidden pricing, raw evidence, credentials, and every other vendor's identity or activity.
VENDOR_SELF_QUEUE_BOUNDARY · apps/api/src/ironbound_api/modules/vendor_admin/router.py:96Copied verbatim from apps/api/src/ironbound_api/modules/vendor_admin/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.