julian
bfe64032d8
Turborepo (pnpm workspaces) with all dependencies pinned to latest mutually-compatible versions: turbo 2.9, TypeScript 6, Fastify 5, React 19, Vite 8, better-sqlite3 12 + Drizzle ORM 0.45. Layout: - apps/server Fastify backend (local JWT auth + role guard, /health) - apps/web React 19 + Vite 8 operator SPA - packages/db Drizzle schema on SQLite/WAL; append-only events + users - packages/devices reader/printer/relay adapter interfaces (intent-only relay) - packages/shared shared domain types Architecture constraints from the design wiki are encoded in the scaffold: append-only hash-chained + signed event log, device-agnostic adapters, "a barrier is not a door" (relay expresses intent only), fully-local offline-first auth. wiki/ is an LLM-maintained Obsidian knowledge base (28 pages) ingested from the architecture & design notes, with its own maintenance schema. Verified: pnpm install, full turbo build (5/5), server boots and serves /health, drizzle-kit generates the initial migration.
1.2 KiB
1.2 KiB
type, tags, sources, updated
| type | tags | sources | updated | |||||
|---|---|---|---|---|---|---|---|---|
| concept |
|
|
2026-06-14 |
Event-Log Ingestion (making the UHPPOTE log trustworthy)
The host-side discipline that turns the uhppote-controller's log — undermined by the uhppote-udp-protocol — into a solid detection/audit layer. (See parking-system-architecture §6.)
- Track your own last-ingested index on the host. Do not rely on the controller's
current-index pointer — it's user-managed and settable by anyone (
set-event-index). - Walk absolute indices with
get-event <id>. Treat three things as alarms:- a gap in the sequence,
- an "event has been overwritten" error (you fell behind — data loss),
- any door-open event the host never requested.
- Use
set-listenerauto-push for low latency, but always reconcile by index (UDP pushes can drop). - Size polling cadence against the busiest lane's event rate so unread events never roll off.
- Land every event in the host's signed append-only-event-chain.
Net result: tamper-evident, behind network-isolation — a solid detection layer, but not tamper-proof. Prevention requires the esp32-custom-controller.