Every other tracker in the suite records a category. SmallHours has milestones, MediaPassport has what was watched, BitsyGo has where a child was. Nothing catches the afternoon itself.
The calendar is what was intended. Passive capture is what actually happened. Sparks, loops and moments are what it meant. Same timeline, three densities, and the day arrives already half written so the user only ever supplies the meaning.
It ranks by significance rather than urgency. That single inversion is what stops it becoming a to-do app with a diary bolted on: the chore never gets to shout, and the good thing never gets buried under six overdue items.
The product layer is deliberately undecided. Whether this is one app or two, whether it replaces a calendar, and where its seams fall are open questions, and a scaffold that guessed at screens would be answering them by accident.
There is no screen that shows the record, and that is on purpose. What is built is the part that was actually decided, and most of it is the part an agent talks to: the schema, the retrieval layer, a versioned API that describes itself, calendar subscriptions, and circles.
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.