makiolajandClaude Opus 5
1e6443c907
How Clockula is built today: the layers and the data seam, the package layout, the four tables column by column, dependency injection, and the JVM-first testing posture. The section on the two clocks is the one a future contributor will need most — which aggregate resolves against which clock and why, the timer's three anchors, and the reboot window where a dead anchor can still read as live, stated as it actually behaves rather than as it was first assumed to. Closing that window needs a persisted boot id; M3's BOOT_COMPLETED receiver is where it belongs. Also says plainly what is not built yet, and points each at its milestone. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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 — 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 |
Any third-party code carried in-tree and under what licence. Created only if we actually lift something (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.