Trust boundary · Systems

Systems

Home technology records show reliable status and planned care only. They exclude raw CCTV, continuous telemetry, access or alarm credentials, remote controls, network secrets, drone mitigation, and automated dispatch.

Module proof path

Systems 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 Systems module refuses to do.

All module boundaries

Home technology records show reliable status and planned care only. They exclude raw CCTV, continuous telemetry, access or alarm credentials, remote controls, network secrets, drone mitigation, and automated dispatch.
SYSTEM_BOUNDARY · apps/api/src/ironbound_api/modules/systems/router.py:50

1 further boundary constant in this module

The physical security registry tracks equipment, responsibility, privacy posture, service tier, and maintenance readiness. It does not promise emergency monitoring, police dispatch, live surveillance staffing, or access-code disclosure, and it stores no credential, stream URL, or provider secret.
SECURITY_DEVICE_BOUNDARY · apps/api/src/ironbound_api/modules/systems/router.py:403

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