Hall Security

Snapshot

Hall Security is a private Rust-based research instrument for hall-entry identity verification and security monitoring. It is intentionally observe-only: the system records and evaluates observations, but it cannot open a door or grant access.

The project is useful portfolio evidence because the safety boundary is part of the product definition. The system is not described as a finished access-control product, and the remaining release blockers are documented rather than hidden.

Problem and constraints

The system explores how identity observations, security events, and operator review can be collected without giving an experimental recognition pipeline the authority to actuate a physical security control. That constraint changes the architecture: observation, evidence, audit, and operator visibility are separate concerns.

Architecture decisions

• Rust components are split into hall-vision, hall-control, hall-dashboard, and shared types.
• PostgreSQL stores system records and audit data.
• TLS/mTLS protects service communication.
• Audit records use a hash-chain design so tampering is detectable.
• A disk-backed outbox gives the system a recovery path when downstream delivery is unavailable.
• Shared types are generated for the TypeScript dashboard from Rust definitions.

Verification and safety

The repository includes invariant tests, generated-type checks, formatting and lint gates, dependency audits, dashboard checks, and backup/restore verification. A quality review found 52 issues; 50 were fixed and re-tested. The remaining issues are recorded as release blockers.

Current status

This is a research prototype, not a production-ready security product. Recognition thresholds are not calibrated, and the documented release blockers still matter. The honest claim is that the project demonstrates Rust systems work, explicit safety boundaries, security modeling, and verification discipline—not that it is ready to control a building.