Jean-Luc MakiolaandClaude Opus 5
5ddec0f248
Clockula's seed is #6B7A5C, the third step of the family's colour cycle. Calendula's slate (#5C6B7A) and Agendula's mauve (#7A5C6B) are the same three bytes rotated — and that byte rotation is exactly a 120° hue rotation, so the three seeds sit at 210°, 330° and 90° with identical saturation and lightness. The fallback schemes are therefore not eyeballed: they are Agendula's hand-picked scheme with its hue rotated the same 120°, which keeps the three apps structurally one palette turned rather than three colours picked. The cycle closes at three. The launcher icon keeps the family's Calendula bloom badge path-for-path and swaps the task card for a clock dial, drawn as a 308° arc so the badge overhangs into a gap rather than colliding with the stroke — the same device Agendula uses to open its card's corner. MainActivity is M0 scaffolding: theme plus the crash surface, with a placeholder where the four-tab shell and the live pill land in M4. The theme follows stored preferences from M2, once there are any. The manifest declares no permissions yet, deliberately. Clockula's permission set belongs to the alarm engine and is declared in M3 alongside the receivers and the ringing service that need it, so the manifest never claims a capability the code cannot honour. 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.