Incidents

Reserve provides issue acknowledgement and property coordination, not emergency dispatch, alarm monitoring, physical security, guaranteed arrival, or guaranteed resolution.

BOUNDARY · apps/api/src/ironbound_api/modules/incidents/router.py:78

11 further boundary constants in this module

• This is a staff-only, read-only incident triage projection over authorized properties. It excludes observed facts, internal notes, owner and vendor contact details, security information, assignment identities, monitoring feeds, and dispatch controls. Open the canonical incident to review or record a human decision.

  OPERATIONS_BOUNDARY · apps/api/src/ironbound_api/modules/incidents/router.py:82

• Owner-facing Reserve updates must be explicitly reviewed. They exclude staff notes, observed facts, responder identities, contact details, routes, security instructions, monitoring feeds, vendor pricing, and any claim of emergency dispatch, arrival, or resolution.

  OWNER_CONFIDENCE_BOUNDARY · apps/api/src/ironbound_api/modules/incidents/router.py:88

• Reserve release gates control whether the property team may make a customer-facing Reserve service claim. A blocked or review gate means the claim stays internal-only.

  RELEASE_CHECKLIST_BOUNDARY · apps/api/src/ironbound_api/modules/incidents/router.py:124

• This preview models consent, suppression, channels, retry posture, and owner acknowledgement without sending live SMS, WhatsApp, email, or push notifications.

  NOTIFICATION_PREVIEW_BOUNDARY · apps/api/src/ironbound_api/modules/incidents/router.py:93

• Coverage planning is an internal readiness view. It is not an arrival promise, live dispatch roster, alarm-monitoring service, or substitute for emergency services.

  COVERAGE_BOUNDARY · apps/api/src/ironbound_api/modules/incidents/router.py:97

• Field response passes are assigned-only execution aids. They do not expose access codes, security instructions, owner contact details, routes, broad incident facts, or emergency dispatch controls.

  FIELD_RESPONSE_BOUNDARY · apps/api/src/ironbound_api/modules/incidents/router.py:101

• A Reserve handoff links a human-confirmed incident to a separate workflow or maintenance request. The linked record retains its own lifecycle, approval, vendor, billing, and closeout authority.

  HANDOFF_BOUNDARY · apps/api/src/ironbound_api/modules/incidents/router.py:106

• Reserve analytics are internal operating measurements with explicit denominators. They are not a public service-level claim, vendor scorecard, arrival guarantee, resolution guarantee, or substitute for human review.

  ANALYTICS_BOUNDARY · apps/api/src/ironbound_api/modules/incidents/router.py:111

• Audit packets are internal review artifacts. They redact staff notes, contacts, access details, security instructions, raw monitored payloads, routes, pricing, and credentials.

  AUDIT_EXPORT_BOUNDARY · apps/api/src/ironbound_api/modules/incidents/router.py:116

• Retention review is policy posture only in this release. It defines review queues and deletion modes; it does not delete records or alter legal holds.

  RETENTION_BOUNDARY · apps/api/src/ironbound_api/modules/incidents/router.py:120

• Support operations separates ticket triage, field work, vendor jobs, and calendar-linked service while preserving a single owner-safe timeline. It does not auto-dispatch, hide SLA breaches, expose internal notes to owners, or replace emergency response procedures.

  SUPPORT_OPERATIONS_BOUNDARY · apps/api/src/ironbound_api/modules/incidents/router.py:1928

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