makiolaj
9516dc1198
The announcer now records only which alarm a user action set, and when. What the snackbar says is derived from upcoming() while a screen shows it, re-subscribed per announcement so the first read is from after the write. That removes the second resolve path through the engine lock (upcomingFor is gone), the publish lock, and the flash of a pre-write countdown. The engine is observed only while an announcement stands. Freshness is judged when a screen picks the announcement up, so one already showing is not cut off half-way. Consuming matches a sequence number. Latest action wins across alarms again: the sentence names no alarm, so a settling announcement must never land on top of a newer action on another one. Switching an alarm off announces nothing, and a dismissal retracts before it skips. Refs #19
Clockula — documentation
Clockula is a Material 3 Expressive clock app for Android: alarms, timers,
stopwatch and world clock. Third floret of the bloom, after
Calendula (calendar) and
Agendula (tasks). See the top-level
../README.md for the pitch.
Unlike its siblings, Clockula owns its storage, because there is no open provider behind
a clock. What that costs and how the open-standards commitment is honoured anyway
is the first section of PLAN.md.
Index
| Doc | What it covers |
|---|---|
PLAN.md |
The spec. Thesis, locked decisions, the alarm engine, data model, system interop, identity, pipeline, and how ClockMaster is used. The "why". |
ROADMAP.md |
Status and the work queue: milestones M0–M11 and post-v1. What the build loop works through. |
ARCHITECTURE.md |
How Clockula is built today: layers, the data seam, the alarm engine, DI, build/tooling, manifest. Written from M2 onward. |
RELEASING.md |
How to cut a release. Written at M0 alongside the pipeline. |
PROVENANCE.md |
Third-party code and assets carried in-tree, and under what licence (PLAN.md §11). |
Also: ../CHANGELOG.md (Keep a Changelog format; tag sections
feed the release notes).
How the docs relate
- PLAN is the design decisions (stable; the "why").
- ARCHITECTURE is the current shape of the code (kept in sync as it grows).
- ROADMAP is the moving status layer (updated as milestones land).
- RELEASING is the operational runbook.