Trust boundary · Event vendor packages

Event vendor packages

Event vendor packages are purpose-built, expiring grants tied to an approved owner option. Offering a package does not confirm availability, dispatch work, move money, or imply legal or safety approval. Vendor acceptance remains separate from owner approval.

Module proof path

Event vendor packages connects API boundaries to public proof.

See the workflow, proof, and operating limits in one scan before reviewing the detailed path.

Inspect proof Open demo

Scope

Who needs the workflow, what is visible, and what stays out.

Proof

Screenshot, proof card, or demo path that makes the claim inspectable.

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 this

Enforced boundary

What the Event vendor packages module refuses to do.

All module boundaries

Event vendor packages are purpose-built, expiring grants tied to an approved owner option. Offering a package does not confirm availability, dispatch work, move money, or imply legal or safety approval. Vendor acceptance remains separate from owner approval.
OPERATOR_BOUNDARY · apps/api/src/ironbound_api/modules/event_vendor_packages/router.py:101

2 further boundary constants in this module

This expiring assignment contains only the event label and window, service scope, exclusions, count band, terms, package quote, package messages, and evidence needed by this vendor. It does not grant property browsing or expose owner contacts, owner totals or markup, internal costs, readiness records, master schedules, dietary detail, credentials, security details, other vendors, or generic communications.
VENDOR_BOUNDARY · apps/api/src/ironbound_api/modules/event_vendor_packages/router.py:89
Vendor launch packets are assignment-scoped, package-local projections for execution day. They omit owner contact, internal cost or markup, property browsing, security/access secrets, full event plans, other vendors, owner totals, dietary details, and unrestricted messaging.
VENDOR_LAUNCH_BOUNDARY · apps/api/src/ironbound_api/modules/event_vendor_packages/router.py:96

Copied verbatim from apps/api/src/ironbound_api/modules/event_vendor_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

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.

Request a guided demo

We respond with the recommended demo route, who should attend, and what production access would require.