Parisar

Engineering journal

How the commitments are actually built

A monthly note on what we built and what it cost us. We have no customers to quote yet, so this is the only evidence we can honestly offer: the decisions themselves, written down while they are being made.

August 2026 · 9 min read

Giving every notification a ceiling it cannot exceed

Politeness implemented per-feature always decays. We moved the decision into the delivery layer: a message declares a priority, the platform decides the loudest form it may ever take, and no feature can pass a value the schema does not allow.

Read the entry

July 2026 · 12 min read

A visitor pass that verifies with no network

Why we sign passes instead of looking them up, how short-lived keys reach the tablet, what an attacker with a stolen device can and cannot do, and the two cases where we still fail closed.

Read the entry

June 2026 · 7 min read

Modelling a tenant as a full resident

The data model most vendors use makes the owner the account and the tenant a guest. Ours makes the household the unit — which meant giving up a simpler permissions tree and rewriting the handover flow twice.

Read the entry

Placeholder — three entries shown; index paginates at twelve, no newsletter capture

Following this without giving us your address

There is an RSS feed and nothing else. No newsletter list, no tracking pixel in an email, no "subscribe" modal — for the same reason there are no ads in the product.

Journal RSS feed