julian
72ba4099ea
Make the device-adapter pattern selectable so the admin chooses hardware at install — per lane, from a catalog of supported drivers. Adding a device = registering one more driver; no business-logic change. packages/devices: - interfaces.ts: AccessControlDevice / ReaderDevice / CameraDevice / PrinterDevice (adds CameraDevice for entry/exit snapshot-on-event; access relay stays intent-only per "a barrier is not a door"). - registry.ts: driver catalog with per-driver config fields + factory, config validation, and a catalog payload for the setup UI. - drivers/: stub adapters — access (zkteco, esp32-relay), reader (wiegand, tcp-ip), camera (hikvision, dahua). Real vendor protocols TBD. packages/db: - lane_devices + setup_state tables (migration 0001); re-export query helpers. apps/server: - routes/setup.ts: GET /api/setup/catalog (public schema), and admin-only /assign, /state, /complete with registry validation before persisting. - extract auth.ts (requireJwtSecret, requireRole, JWT type aug). apps/web: - SetupWizard scaffold + api client: pick a driver per category for a lane, render its config fields. wiki: device-registry + first-run-setup concept pages; cross-link from device-adapter-pattern; index + log updated. Verified: full turbo build (5/5); catalog lists all drivers; admin assign persists; missing-config and no-token requests are rejected.
70 lines
3.8 KiB
Markdown
70 lines
3.8 KiB
Markdown
---
|
|
type: overview
|
|
tags: [parking, index]
|
|
updated: 2026-06-14
|
|
---
|
|
|
|
# Index
|
|
|
|
Content catalog for the wiki. Start at [[overview]]. Maintained on every ingest.
|
|
Counts: 1 source · 14 entities · 10 concepts · 2 decision records.
|
|
|
|
## Overview & navigation
|
|
- [[overview]] — the top-level synthesis and entry point.
|
|
- [[index]] — this catalog.
|
|
- `log.md` — chronological record of ingests/queries/lints.
|
|
|
|
## Sources
|
|
- [[parking-system-architecture]] — design notes: stack, threat model, devices, UHPPOTE, ESP32, readers, BOM, open decisions.
|
|
|
|
## Entities — technology stack
|
|
- [[technology-stack]] — the full stack table; all MIT/Apache/BSD, chosen to avoid lock-in.
|
|
- [[fastify]] — Node backend; hosts device-driver plugins + auth; serves the SPA.
|
|
- [[sqlite]] — local single-writer DB (WAL); limits & why it fits.
|
|
- [[drizzle-orm]] — ORM; schemas port to PostgreSQL for remote sync.
|
|
- [[turborepo]] — monorepo tool.
|
|
- [[react-vite-spa]] — React/Vite frontend served by Fastify.
|
|
- [[local-jwt-auth]] — fully local auth (JWT + bcrypt + role guard); forced by offline-first.
|
|
|
|
## Entities — rejected alternatives
|
|
- [[payload-cms]] — strong, but rejected over BSL license shift (the rug-pull cautionary case).
|
|
- [[refine]] — dropped for plain React; UI too simple to justify a framework.
|
|
- [[logto-zitadel-oidc]] — OIDC providers ruled out by offline-first.
|
|
|
|
## Entities — hardware & devices
|
|
- [[uhppote-controller]] — current access controller; cheap, tamper-evident, open-UDP, fixed firmware.
|
|
- [[esp32-custom-controller]] — prevention-grade upgrade; device-level auth.
|
|
- [[atecc608]] — secure element; non-extractable signing key (host events + controller auth).
|
|
- [[wiegand]] — reader standard feeding the controller directly (autonomous permit-holder path).
|
|
- [[lpr-camera]] — edge-AI plate recognition; host-side casual-identity source.
|
|
- [[bom]] — reference bill of materials (barrier, loops, controller, readers, payment, host, network).
|
|
|
|
## Concepts — foundational forces
|
|
- [[offline-first]] — no network dependency in core operation; what it forces (and doesn't).
|
|
- [[threat-model]] — the operator-at-the-booth reframing; why encryption defends the wrong threat.
|
|
|
|
## Concepts — integrity & anti-fraud
|
|
- [[append-only-event-chain]] — append-only + hash chain + ATECC608 signing = unforgeable log.
|
|
- [[reconciliation]] — the real anti-fraud control; what remote sync actually is.
|
|
- [[disk-os-hardening]] — LUKS/GRUB/Secure Boot; worthwhile but not the main event.
|
|
|
|
## Concepts — device architecture & safety
|
|
- [[device-adapter-pattern]] — business logic talks to interfaces; swap hardware → new adapter.
|
|
- [[device-registry]] — catalog of selectable drivers per category (admin-configurable).
|
|
- [[first-run-setup]] — admin assigns devices per lane from the catalog at install.
|
|
- [[barrier-not-a-door]] — never timed-close a barrier; safety lives in barrier firmware.
|
|
- [[trust-boundary]] — the core fork: network vs. device; auditable vs. unforgeable.
|
|
- [[fail-state-safety]] — entry fails closed, exit fails open; manual override; watchdog.
|
|
|
|
## Concepts — access control
|
|
- [[uhppote-udp-protocol]] — open UDP weakness + the unauthenticated commands that undermine the log.
|
|
- [[network-isolation]] — mandatory VLAN isolation; the network as security boundary.
|
|
- [[event-log-ingestion]] — host-side index tracking that makes the UHPPOTE log trustworthy.
|
|
- [[challenge-response-auth]] — asymmetric nonce scheme for the ESP32 (auth + anti-replay).
|
|
- [[entry-exit-readers]] — two populations, two integration paths; both can share a relay.
|
|
- [[uhppote-vs-esp32]] — comparison: detection vs. prevention.
|
|
|
|
## Decisions
|
|
- [[standing-decisions]] — settled decisions (stack, platform, integrity, access control, readers).
|
|
- [[open-questions]] — 7 open items (6 procurement + JWT key choice); ESP32 device auth deferred.
|