Files
julian bfe64032d8 Initial scaffold: Turborepo monorepo + design wiki
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.
2026-06-14 00:34:11 +02:00

22 lines
881 B
Markdown

---
type: concept
tags: [parking, safety, devices]
sources: [parking-system-architecture]
updated: 2026-06-14
---
# Fail-State & Safety (custom controller)
For the [[esp32-custom-controller]], fail-state behaviour is to be treated **as seriously as the
crypto**. (See [[parking-system-architecture]] §7.)
- **Define behaviour on power/network/host loss:** **entry fails closed**, **exit fails open** —
**never trap a vehicle** (often a legal egress requirement).
- **Hardware manual override** (key switch/button) that opens the barrier **with the ESP32 dead**.
- **Watchdog** with a defined safe default.
- The **barrier operator still owns physical safety** — the ESP32 only signals intent
([[barrier-not-a-door]]).
The general "fail-open on exit" principle is also an [[open-questions|open question]] (#2) for
the system as a whole, not just the custom controller.