Keel

Keel · Guides · Routines & Programs

Read and manage a program

What does the cockpit tell me?

The program’s detail leads with its Plan block — where the block stands, what is active, the next change — then Mark program completed, Reactivate program, Delete program, and the Analytics section (Pro).

AvailabilityFree · Pro only for: Program analytics; more than one active program

Written for Keel 1.0.0 · build 1Content 2026.09.14 · 2026.09.17-batch2Screens from working tree 7e41269 (NOT a candidate)

Where to start

+ › Manage routines › the program’s card (under Active program or Past programs).

A Plan block reading Week 7 of 12, a horizontal rail with dates at its ends and today marked, a line Testosterone Cypionate · 0.35 mL · until Oct 8, a line Oct 8 — Testosterone Cypionate phase ends (the next plan boundary), and a note Recorded before plan history began.
Fictional program: where the block stands, its rail from start to end, what is active now, and the next plan boundary.

DisclosureThe line “Oct 8 — Testosterone Cypionate phase ends” marks a planned dose change (to 0.5 mL from that date); the routine continues.

  1. Week 7 of 12
  2. rail
  3. active routine lines
  4. next plan boundary
Where this screen comes from
File
C5-F1-program-plan-block.png (1320×720); C5-F1-program-plan-block.webp is a lossy encode of it
Derivative SHA-256
346d5e6bc12d7b8a157c42f9267ccaffe44668d21b042b1d7fa2ec7308ea7e45
Source
C5-F1.png in package Keel-WT-7e41269-guide-figures-B2-20260924-111151-1756
Source SHA-256
71001c08a4ebde2997273e71f60b67f84aa5e71e5c751f357855c9913efba76e
Package seal
f9b0083234734b6b16f58e455596067bde9182e8e0ff62c5e84cdfae8ad22c6f
Captured from
Keel 1.0.0 (1), implementation working tree 7e41269 (NOT a candidate; head 7e4126919da3a44a9ad2f2efaf3ad2467c1fbff7, build-input tree c863167fe1474c471d3562fe90f5f107c9598edff3903cdfc58b89bc7ae3032c, build build-20260924-103514-93133)
Operation
crop x0 y500 w1320 h720 (source pixels, origin top-left)

The numbered markers are drawn by the page, not into the image.

The plan position

The Plan block leads with Week n of n for a bounded program, Since <date> for an open-ended one, or Starts <date> before it begins; a rail shows past, current and future spans with its start, today and end dates; then one line per active routine ("Name · dose · until <date>") and the next change ("<date> — Name changes to <dose>" or "… phase ends"). With Pro and attached supply, a supply line sits under the position.

Complete

  1. Tap Mark program completed. The program moves to Past programs; its end date becomes today if it had none or a later one — never earlier than its start, so a program that has not started yet ends on its start date.

Reactivate

  1. On a past program tap Reactivate program; a past end date is cleared, so it runs open-ended. On Free with another program active the button carries a Pro badge and opens the Pro sheet; the footer explains.

Delete

  1. Tap Delete program › Delete this program? › Delete program only: "The routines in it, their schedules, and all logs stay exactly as they are."

What changes

Under the overview (status, dates, Logged / Skipped / Missed counts for the whole window) the Analytics section (Pro; Free sees the locked Program analytics row) shows "n% taken · x of y due so far", a weekly bar chart once two weeks exist, each routine’s taken/due, and "Supply used · <name>". A week with nothing due plots as 0 %; there is no "How calculated" note here; "n doses need review" counts synced logs awaiting resolution.

Where: The program’s detail, under the overview

An Analytics section with a large percentage, the words taken · x of y due so far, a bar chart of weekly adherence, and rows naming two routines with percentages and taken/due counts.
Fictional program analytics: the share taken of what has come due, week by week, and each routine’s own count.
  1. percent taken · due so far
  2. weekly bars
  3. per-routine taken/due
Where this screen comes from
File
C5-F2-program-analytics.png (1320×1070); C5-F2-program-analytics.webp is a lossy encode of it
Derivative SHA-256
b94f90421c16181078223524eea7a38528adb074a067fb7f5a8604f526aed4b0
Source
C5-F2.png in package Keel-WT-7e41269-guide-figures-B2-20260924-111151-1756
Source SHA-256
db06a4149723e0b6a194c91b0bef505eb4f6c332e0b7357454767aaa78577c24
Package seal
f9b0083234734b6b16f58e455596067bde9182e8e0ff62c5e84cdfae8ad22c6f
Captured from
Keel 1.0.0 (1), implementation working tree 7e41269 (NOT a candidate; head 7e4126919da3a44a9ad2f2efaf3ad2467c1fbff7, build-input tree c863167fe1474c471d3562fe90f5f107c9598edff3903cdfc58b89bc7ae3032c, build build-20260924-103514-93133)
Operation
crop x0 y1680 w1320 h1070 (source pixels, origin top-left)

The numbered markers are drawn by the page, not into the image.

When the plan can’t be read

  • "Recorded before plan history began" (older data), "Sync left N competing versions of this plan’s history", "N active programs state different plans for this routine", or "Couldn’t read this program’s plan." with Try again — the cockpit withholds lines it cannot state; your logs are unaffected.
  • "Can’t do that yet" with "Your plan allows one active program at a time. Complete the current program first." — the Free cap.

The cockpit and analytics describe the plan and record you entered; nothing here rates your adherence or advises a change.