wiki: design the business layer (session, tariff, permit, vision, shift, ops)
Pivot from the hardware/integrity layer to the parking operation. All wiki-only; no code yet. Core principle throughout: business entities are projections over the signed append-only event log, never mutable tables. New concepts: parking-session, tariff (composable/versioned, FX-ready), shift (manned-only Z-report), capacity-occupancy, validation-discounts, reporting-analytics, clock-integrity, ticket-encoding, anti-passback. New entities: permit, opencv-anpr-service, blocklist. Decisions: session-model, vision-service (host-side ANPR + vehicle verification; scoped AGPL exception for the isolated service). Updates: append-only-event-chain (new event types + vision witness), local-jwt-auth (drop 8h expiry -> until logout; code change pending), lpr-camera (host-side recognition supersedes edge-AI), standing-decisions (AGPL exception), open-questions (+FX, +pay-station money corners, backup). Deferred + flagged: intercom/help-call, receipts/refunds/change, FX engine, lane topology (#1).
This commit is contained in:
@@ -14,6 +14,10 @@ The decisions treated as settled in the design notes. (See [[parking-system-arch
|
||||
- **Stack:** [[turborepo]] · [[fastify]] (Node) · [[react-vite-spa]] · [[sqlite]] +
|
||||
[[drizzle-orm]] · [[local-jwt-auth]]. All MIT/Apache/BSD — **no vendor lock, no rug-pull
|
||||
risk** (see [[payload-cms]]). Full table in [[technology-stack]].
|
||||
- **Scoped exception (2026-06-15):** the [[opencv-anpr-service]] — a **separate local process**,
|
||||
not linked into the app — **may use AGPL** components (plate/vehicle models). The exception is
|
||||
bounded to that process; the Node/React app stays strictly MIT/Apache/BSD. See
|
||||
[[vision-service]].
|
||||
- **Platform:** a **dedicated, hardened Linux appliance** (LUKS + GRUB password + Secure Boot),
|
||||
**not Windows/WSL** — see [[disk-os-hardening]].
|
||||
- **Integrity:** append-only, hash-chained, [[atecc608]]-signed event log
|
||||
|
||||
Reference in New Issue
Block a user