Operations overview

Historical directory migration reference. Telephone routing data is masked by default; this workspace cannot control community systems.

Canonical units —

Grouped directory records —

Unresolved review records —

Imported source records —

Directory normalization

Canonical units lead the operating view. Imported source records remain provenance for migration review.

Unit-linked records

—

Review queue

—

Normalization ruleUnit labels are presented as bare values. Property type is a separate field; where it is absent in legacy data, it remains unclassified for review.

Migration posture

Connection and command functions are unavailable in this local application.

Controlled points

—

Property type

Review

Ask Tina

Question

Units Directory

Canonical units with residents and directory entries grouped beneath them.

Canonical units

Property type	Unit	People / entries	Source status

Unit detail

Select a unit to see grouped, allowed directory fields and provenance.

Select a unit.

Unresolved Review Queue

Records that cannot be safely assigned to a canonical unit.

Name	Source	Reason	Routing retained

Review ruleThese records are intentionally not merged by name, group, or routing value alone. A verified unit/identity mapping is required before assignment.

Doors & Gates

Named controlled points from legacy configuration records.

Name	Type	Site / location	Panel	Relay / lock profile	Status

Access Groups

Group relationships shown through canonical units where available.

Group	Unit-linked records	Review records	Status

Connection Profiles

Configuration records are separate from communications.

Adapter state

Command path

Connection profile

Audit destination

Audit History

Local migration history. Credential and access-event logs are excluded.

Event	Scope	Result
Unit normalization applied	Location-backed records grouped beneath canonical units	Recorded
Review queue retained	Records without a proven unit link	Review
Credential fields excluded	PIN, card, code, password, relay-code, and access logs	Recorded

Future Raspberry Pi Bridge

Architecture placeholder for a later, separately authorized project.

Concept

A Raspberry Pi 3 or newer could be installed securely on the same local network as the call-box or panel environment. A future design may use USB/serial for legacy hardware, an optional local camera, and a separate internet/data-backed notification path to a resident’s phone or computer.

Notification clarificationGoogle Voice can send an image as a message attachment, but a normal phone call cannot contain an image. This page does not configure Google Voice or any notification service.

Future consideration: video-assisted visitor verification and, subject to privacy/legal review and explicit community approval, optional facial-recognition assessment.

Draft configuration

Device name

Site / installation location

Local network status

Panel connection type

Optional camera

Notification destination

Future architecture onlyHardware and protocol validation, power and physical-security review, and explicit authorization are required before any operational bridge. This application performs no network scan, camera access, serial/socket communication, login, notification, message sending, door action, gate action, biometric collection, face detection, face matching, identity inference, or facial-recognition workflow.

Notes

Ideas and future work to keep on the community’s planning list.

Add a note

Area

Title

Note

Notes are saved in this browser on this computer.

Planning list

System Settings

Local workspace and operational controls.

Privacy boundary

This workspace contains sensitive directory information. It must not be shared, published, or opened by unauthorized users. Credential-type information is not included.