What it is
Two systems live in this monorepo. The Access Portal was built for a residential building’s daily flow: a public kiosk is the front door; residents generate visitor passes rendered as QR codes, checkable and revocable at the door, and package pickups run on one-time release codes instead of signatures in a binder. Staff roles (manager/clerk) handle package intake and release queues, a staff directory, PIN resets and building configuration held in D1.
Underneath, a newer property-management kernel (pms/) rebuilds the same domain on stricter rules: append-only grant/request/parameter history and compare-and-swap decisions, so no state ever changes without a record of what it changed from. Security is treated as a feature with a changelog: timing-safe HMAC cookie comparison, exception-safe token validators, foreign-key guards on staff deletion, and a 22-step post-deployment verification walk (kiosk → login → pass grant → revoke → package release → manager override).
Code
packages/core/src/index.ts — the shared core (exact opening):
// 2099-12-31T23:59:59Z in milliseconds
export const INDEFINITE_EPOCH = 4102444799000;
Achievements
- Phase 7.0 release point reached, with the 22-step verification suite documented in the deployment handoff.
- Kernel conformance work landed 2026-10-20: append-only history + compare-and-swap decisions in the PMS core.
Lessons
- Building systems fail socially before they fail technically. A revoked pass must verify as revoked at the door, in one glance — the state machine exists to serve that moment.
- Append-only history is cheaper than regret. In a system where staff actions affect residents’ homes, “who changed this, from what, when” is not an audit luxury.
Status: Active · TypeScript monorepo, Hono, Drizzle/D1, React 19, Cloudflare Pages