← Changelog

Base, Stretch, and the Sunday Form

The PSP toolkit now speaks the program's language and runs on the cohort's clock, and every outcome shows how far it has to go.

Why Care?

Every Sunday afternoon, everyone in a ChoiceCenter Leadership Legacy cohort fills in the same Google Form: top three results, breakthroughs, this week's declarations, enrolling conversations, daily practices. It's due whether or not you tracked anything during the week. This round makes the toolkit about that Sunday. If you log during the week (any rhythm, any assistant), Sunday becomes review-and-paste instead of a blank page.

It also stops translating. The program says base and stretch, so now the toolkit does too. Weeks run Sunday to Saturday, as the cohort's do. And outcomes, the things you can't do directly but want (weight, income, a finished song), now show where they stand and where the current rate is heading, every week.

What's New?

  • A spec for the dashboard and the weekly form. Progress-Dashboard-for-Flexible-PSP-Dataviz captures all four pages of the program's weekly questionnaire, which answers can be drafted from a log, and the privacy rule that matters most: other people's names never land in a public repo.

  • One PSP folder, three ways to use it. The README now walks a member through picking a folder and explains what happens with an assistant that can open files, a Claude or ChatGPT Project, or a single chat ("stay in this chat, or download and re-attach").

  • Every Sunday. README and AGENTS lay out the Sunday session: catch up the unlogged days, score the week, draft what the log supports, ask for the rest, never submit the form for anyone.

  • Base and stretch. Renamed across the skill, references, templates, splash, and code. Older floor: / target: files keep working.

  • The cohort's clock. week_starts: sunday makes Week 1 the part-week from Day 1 to the first Saturday, with its bars prorated.

  • More habit shapes. A monthly cadence (Weeks 1–4, 5–8, …), an hours measure, and aggregate: max for things like a fast, where the longest stretch counts: 24 hours against a 36-hour bar is two-thirds done, not a miss.

  • Reasons beside results. A week log can say why a bar was missed. The status doesn't change; an ⓘ opens a popover anchored to it, for the coach or buddy who asks.

  • Bonus is green. A habit with no base this week shows green when done and neutral ("Optional") when not.

  • An outcomes panel. The week view opens with a tile per outcome: latest reading, a meter from start to goal, and a projection to the goal's day ("at this rate: X by Day 90"). Levels like a monthly income run-rate show where they stand instead of projecting.

How It Works

Everything is still two plain files any assistant can edit: tracker.yaml (the plan as numbers) and one log/week-NN.yaml per week. New keys, all optional:

YAML
# tracker.yaml
week_starts: sunday
  - id: fast
    measure: hours
    aggregate: max        # the week's longest, not the sum
    base: 36
    stretch: 36
  - id: income-after-tax  # an outcome
    projection: none      # a level, read as it stands

# log/week-NN.yaml
reasons:
  calls: "Contacts aren't imported into my email system yet."
readings:                 # one per outcome, every Sunday
  - { date: 2026-10-04, weight: 208 }

Under the Hood

  • tracker.ts gained weekOffset for the cohort clock, generic cadence windows (spanWeeks / windowStart), outcomeSeries (readings against the paced band) and outcomeProgress (share, linear projection, variance). Status keys are stretch / base / miss / bonus / optional.

  • New OutcomesPanel.astro; SummaryView gets an "Outcomes, week by week" trend section with neutral ink, so status lives only in labelled chips.

  • The popover is a native popover element positioned by a small script against its button, flipping above when there's no room, with the arrow aimed at the ⓘ.

  • All of it was ported to and exercised on mpstaton.com, against a real Week 1 and a fictional sample, before landing here.

What's Next

  • Fold the program's own daily practices (journaling, meditation, gratitude walk, books, buddy support) into the tracker template as a standing block.

  • Teach the skill the Sunday form itself, so it drafts answers page by page.

  • Tie each habit to the outcome it drives, so "income goal met" doesn't read as license to drop fundraising outreach.

  • Smooth projections once there are a few weeks of readings.