makiolaj
1689794da6
Fifth round of review fixes for the silence-after setting. A ring whose start the clock has moved back behind is now re-anchored to now, once, and stored. Before, the negative age lingered, and every later re-measure gave the ring a fresh window. With that fixed, onAutoSilence can safely re-arm again when the ring is still inside the window in force, so a backstop queued behind a raised setting no longer ends the ring early. The timers' setting is now written through TimerEngine.setTimerSilenceAfter, which records a session that has already outrun the old window as lapsed, so raising the setting cannot restart a timer that went quiet while no service pass was running. The lapse rule and the lapsed anchor live in TimerRingPolicy, shared by the policy and the engine. Refs #17
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.