Jean-Luc MakiolaandClaude Opus 5
9fb02d5083
Copied from Agendula, which is the family's current template: AGP 9.x conventions, the shared version catalog, and the F-Droid reproducibility invariants that are load-bearing rather than cosmetic — no foojay toolchain resolver anywhere, vcsInfo off on release, dependenciesInfo out of the APK. floret-kit comes in as a git submodule wired up as a Gradle composite build, so the kit is built from source and pinned by commit, exactly as its ARCHITECTURE.md prescribes. Two deliberate divergences from Agendula's catalog: - Room replaces Glance. Clockula owns its storage (docs/PLAN.md §0) and ships no widget in v1 (§1, decision 2). The schema is exported to a committed directory, because a migration is only reviewable against a recorded previous version. - :provider and core-reminders are dropped. There is no vendored task provider here, and Agendula's reminder lead-time model is not the shape Clockula's scheduling takes. Version starts at 0.1.0 / 100. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L94fydiJC37LtxVusNQBDy
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.