Trust boundary · Events

Events

An event request is received for human feasibility and availability review. It is not a booking, vendor confirmation, dispatch, purchase, safety determination, emergency-response promise, or custody of client funds. Do not include guest names, access credentials, payment details, medical records, or security-system information.

Module proof path

Events 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
01

Scope

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

02

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 this

Enforced boundary

What the Events module refuses to do.

All module boundaries

An event request is received for human feasibility and availability review. It is not a booking, vendor confirmation, dispatch, purchase, safety determination, emergency-response promise, or custody of client funds. Do not include guest names, access credentials, payment details, medical records, or security-system information.

EVENTS_BOUNDARY · apps/api/src/ironbound_api/modules/events/schemas.py:7

Copied verbatim from apps/api/src/ironbound_api/modules/events/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
  1. Owner submits a winter maintenance concern.
  2. Manager reviews urgency, access, and authority.
  3. Vendor receives only the package-local scope.
  4. 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.