GoldenBlink — Written while your child is still a child

GoldenBlink

Written while your child is still a child

Parents get roughly eighteen years of knowing their children as children, then forty or fifty of knowing them as adults. Almost nobody registers that they are inside the short window until they are out of it.

Private Self-hosted Proposal

The unit of value is a parent noticing something.

GoldenBlink exists to make that short window conscious while it is still open, and to leave behind a record the child can read later. Everything else in the system is scaffolding around the act of writing one thing down.

A captured moment is a blink. That is the word in the interface and in the database, and it is the only word for it.

Three of its rules will look like missing features until you know what they are for. They are decisions with reasons attached, and the schema is the enforcement rather than the terms of service.

The rules it keeps.

Positive frame only

Every blink answers one question: what I loved about today with my child. No ratings, no behaviour tags, no free-form title. The schema enforces it, not the terms of service.

Author-private by default

No household-owner view, no admin view, and no way for one parent to audit the other’s log. Of four sharing surfaces, only the child’s own timeline is on by default.

A co-parent adds and never takes away

Deleting a blink is checked against its author, and revoking a grant is checked by trigger against the same person, so a child’s log fills from both sides and neither can empty the other’s half.

What was revealed stays revealed

Nothing cascades from a relationship changing, because a gift withdrawn when the adults fall out is leverage. Retention is not part of the subscription, so an archive is not swallowed by an account lapsing.

A data layer and no interface.

Thirteen tables, ten migrations, and a test suite that boots real Postgres to check the rules the schema is supposed to hold. No screens, no API, no authentication, no deployment.

Of six open design questions, five are settled.

Handling of data is covered in the Locke Werks Privacy Policy. For access, or a conversation about what it would take to use this, write to nyx@lockewerks.com.